A router's configuration represents hours (sometimes years) of accumulated firewall rules, VLANs, queues, and VPN peers — none of which you want to rebuild from memory after a failed upgrade, a fat-fingered command, or a dead device that needs replacing. MikroTik gives you two different backup mechanisms, and picking only one leaves you missing something the other would have covered.
Take a binary backup
This captures the router's full configuration state, byte for byte, including user passwords, in a proprietary binary format.
/system backup save name=myrouter-backupCopy the resulting .backup file off the router (WinBox's Files list, or FTP/SFTP) — a backup sitting only on the router it backs up doesn't survive whatever takes the router down.
Also take a text export
An export produces a human-readable script of the commands needed to recreate the configuration — useful for review, diffing between two routers, or copying a chunk of config (like one firewall chain) into a different device.
/export file=myrouter-exportBy default, passwords are stripped out of an export. If you specifically need them included (for a full disaster-recovery copy), use:
/export show-sensitive file=myrouter-export-fullTreat that second file like the password vault it now is.
Restore from a binary backup
Upload the .backup file to the router's file list, then:
/system backup load name=myrouter-backupThis requires a reboot and only restores cleanly onto the same RouterOS version and architecture (or close to it) that created the backup.
Restore from a text export
Upload the .rsc file, then run it as a script:
/import file-name=myrouter-export.rscThis applies the commands on top of whatever configuration already exists on the router, rather than replacing it wholesale — useful when you're migrating config into a router that already has its own base setup, but read through the script first if you're not sure what's already there.
Why do it this way
A binary backup restores an exact, working replica — but only onto matching hardware and a matching (or very close) RouterOS version, and you can't read it or edit it before applying it. A text export is portable and human-readable, so you can review it, adapt it, or move a piece of it to different hardware entirely — but restoring it means running a script against whatever state the router is already in, not wiping it back to a known point. Keeping both means you have a fast, exact recovery path for "put this router back exactly as it was" and a flexible, inspectable one for "move this configuration somewhere else" — two different jobs that a single backup type can't both do well.
How MoniTik helps
Automated backups are on our roadmap as a feature that runs on a schedule without anyone having to remember to trigger it — the kind of thing that's easy to do once and then forget for six months. If that would help your fleet, let us know; in the meantime, MoniTik's remote WinBox access at least means you can run these commands on a router that has no public IP without a site visit.
Isabela writes about the everyday MikroTik tasks that never quite make it into the official docs.