Mikrotik Backup Restore Better Jun 2026

For MikroTik administrators, understanding the distinction between a binary and a text-based

This is a plain-text script of your settings. It is the "better" method for migrating to a new router or keeping a readable history of your config. Social WiFi Academy

/system backup save name=myconfig.backup

They store system-specific data like MAC addresses and user passwords. Restoring a binary backup onto a different hardware model will corrupt the interfaces or cause system instability. Configuration Exports (.rsc) mikrotik backup restore better

MikroTik’s scripting engine allows you to push backups to external storage without third-party tools.

The /system reset-configuration no-defaults=yes command is used prior to importing configuration scripts on new hardware.

Manual backups are easily forgotten. A resilient strategy automates both binary backups and script exports, storing them off-device on a remote server (such as an FTP, SFTP, or email server). Restoring a binary backup onto a different hardware

Here is a RouterOS script that generates both backup types, appends the system date to the filename, and can be scheduled to run automatically. The Automated Backup Script

You now have versioned backups. If you mess up a config at 3 PM, you can restore the 2 AM version. Storing offsite (FTP/SFTP/HTTP) saves you from physical theft, fire, or drive failure.

Restoring a binary backup onto a different router model will corrupt the configuration, mismatch interface names, and likely crash the system. Script Exports ( .rsc ) Manual backups are easily forgotten

What you prefer (SFTP, FTP, or Email)?

Before writing any scripts, it's crucial to understand the fundamental differences between a MikroTik .backup file and a .rsc export file. Think of a .backup as a "bit-for-bit" clone, while a .rsc is more like a blueprint.

:local sysname [/system identity get name]; :local datetime [/system clock get date] ; :local filename ($sysname . "-" . $datetime); # Generate Backups /system backup save name=$filename password=YourSuperSecretPassword encryption=aes-sha256; /export file=$filename compact show-sensitive; # Wait for files to write to disk :delay 5s; # Send Email /tool e-mail send to="admin@yourdomain.com" subject="Backup - $sysname" body="Automated backup files attached." file=("$filename.backup", "$filename.rsc"); # Wait for email transmission :delay 10s; # Clean up local storage /file remove "$filename.backup"; /file remove "$filename.rsc"; Use code with caution. Scheduling the Script

Most beginners know one method. Professionals use all three.

Identical hardware restores (e.g., swapping a broken hEX for a brand-new hEX).