Backing up and restoring RouterOS configurations
Purpose: Understand the critical difference between binary .backup files and human-readable .rsc text exports so you can recover failed hardware safely.
Prerequisites
- WinBox or SSH access to the MikroTik router.
Step-by-Step Configuration
In Files -> Backup (or /system backup save name=core-rtr), create a password-encrypted .backup file. Use binary backups ONLY to restore onto the exact same router model.
In New Terminal, run /export file=core-rtr-export (or show-sensitive in v7 if credentials are required) to produce a readable .rsc script.
Copy both files from WinBox Files to your secure off-site backup server—files left solely on router flash are lost if the board fails.
For identical hardware, upload .backup and click Restore. For replacement/upgraded models, reset the replacement unit to no-defaults, review the .rsc script interface names, and import via /import file-name=core-rtr-export.rsc.
CLI / Configuration Snippet
# RouterOS v7.x — Create Encrypted Binary Backup & Text Export /system backup save name=DOS-CORE-01-2026 encryption=aes-sha256 password="BackupSecretKey!" /export show-sensitive file=DOS-CORE-01-2026
Both encrypted binary recovery archives and editable text configuration scripts are stored safely off-device.
Troubleshooting Matrix
Always encrypt .backup files and store show-sensitive .rsc exports in an encrypted vault because they contain PPPoE, Wi-Fi, and RADIUS secrets.
Automate scheduled nightly backup exports emailed or SFTP-pushed to your infrastructure backup server.
Manages daily NOC telemetry, subscriber ticket queues, and on-site client turn-ups across corporate and residential estates in Nairobi.