# Backup
/system backup save name=full.backup
/export file=full.rsc show-sensitive
The binary backup (.backup file) is a binary dump of the router’s entire configuration. It’s tiny, fast, and includes all sensitive data (WiFi passwords, PPPoE secrets, private keys).
How to create it:
/system backup save name=2025-04-12_pre_update.backup
The major caveat: You can only restore a binary backup to the exact same RouterOS version and same hardware platform (or very similar). Restoring a backup from a CCR to an RB750 will likely fail or cause silent corruption. mikrotik backup restore better
When to use it: Emergency rollback after a bad change on the same device.
/export file=backup_config hide-sensitive # Backup
/system backup save name=full
To backup "better," you should use both methods for different purposes.
#!/bin/bash
ROUTER_IP="192.168.88.1"
USER="backup_user"
ssh $USER@$ROUTER_IP "/system backup save name=remote.backup"
scp $USER@$ROUTER_IP:/flash/remote.backup ./mikrotik-$(date +%F).backup
You need to replace an old RouterBoard 750G with a new hAP AC3. Your binary .backup will fail. Your .rsc will also fail because interface names differ (ether1 vs. ether2). But you can fix this. The major caveat: You can only restore a
If you manage a MikroTik RouterOS device, you already know that a single misconfigured firewall rule can lock you out, a failed hard drive can erase months of work, or a beta update can bring your network to its knees. You know you need backups. But are you doing it better?
The default method of clicking "Backup" in WinBox works, but it is fragile, architecture-dependent, and often leads to failure during restore. To truly achieve a better MikroTik backup and restore strategy, you must move beyond the basics.
This article will teach you the three layers of backup, which method restores fastest on different hardware, how to automate encrypted offsite backups, and the "export" trick that saves you when the binary backup fails.