/system script add name="upload-backup-sftp" source= :local backupName ("router-". [/system identity get name] . "-" . [/system clock get date] . ".backup") /system backup save name=$backupName /tool fetch upload=yes src-path=$backupName dst-path="/backups/$backupName" user="backupuser" password="strongpass" url="sftp://192.168.100.10" /file remove $backupName
More flexible — you can edit the .rsc file before import to change IPs, interfaces, or skip errors.
Before we automate or complicate things, we must distinguish between the two types of backups MikroTik offers. They are interchangeable.
– Use a fetch script or SCP to pull these files to a central server. Backups on the router are useless if the storage fails.
I can provide the exact scripts, API commands, or Ansible playbooks tailored to your deployment. Share public link
Text-based scripts can be stored in Git, allowing you to track changes. Security: Encrypted backups protect sensitive credentials. Phase 1: The Better Backup Method (Binary + Export)
/import migration.rsc # Then rename back. This prevents errors.
To ensure that your Mikrotik backup and restore process is efficient and effective, follow these best practices:
/export file=myconfig.rsc Or for a cleaner output: /export terse file=myconfig.rsc
When moving to a new router, importing a script on top of an existing configuration causes conflicts. You must reset the device first.
MikroTik’s scripting engine allows you to push backups to external storage without third-party tools.
You can completely automate this process using RouterOS scripts and the built-in Scheduler. This system creates both a binary file and a text export, then pushes them to a secure remote server via FTP or SFTP. Step 1: Create the Backup Script
| Backup Type | Command / Method | Contents | Best for | |-------------|----------------|----------|----------| | | /system backup save | Entire router config in binary (encrypted, includes MAC addresses, private keys) | Full disaster recovery on same hardware/model | | Export | /export or /export compact | Human-readable script (commands) | Migrating to different hardware, version upgrades, documentation | | Cloud Backup | /system backup cloud | Binary backup stored on MikroTik cloud | Offsite backup, easy restore via same RouterOS account |
For network administrators, MikroTik RouterOS offers immense power and flexibility. However, with that power comes the crucial responsibility of maintaining stable configurations. Knowing how to backup and restore properly isn't just about disaster recovery; it's about efficient deployment, upgrading, and managing network changes without downtime. While basic backups are straightforward, implementing a backup and restore strategy ensures reliability, security, and portability across devices. Why "Better" Backup Matters
But the best approach is the .
Only when you are restoring to the exact same physical device (e.g., after a factory reset).
Revert specific configuration blocks without wiping the entire router.