Technical guide
MikroTik cloud backup: keep config off the router
A MikroTik backup stored only on the device disappears with it. A cloud controller keeps time-stamped exports off-site, scheduled, ready to restore.
Risks of local-only backups
RouterOS supports /system backup and export. Many teams stop there. The file stays on flash: hardware failure, theft, netinstall, bad upgrade — the config leaves with the device.
Without off-site history, post-incident recovery often starts from incomplete notes.
- Brick or netinstall: flash wiped
- Human error: config overwritten with no prior version
- Site unreachable: cannot fetch the local file
What to back up
A binary RouterOS backup captures state for restore on compatible hardware. RSC export is readable and useful for diffs. In practice a controller keeps time-stamped downloads.
Retention and restore drills
An untested backup is a hope. Define retention (e.g. 30 days), daily jobs, and a lab restore at least quarterly.
Align schedule timezones with the site so jobs do not land in peak production hours if you prefer night windows.
MikroTik backup with Routiv
Routiv schedules backups, stores them off the router, and lets you download from the device page — without opening ports at the customer site.
Enrol a test router, run a manual backup, verify the file in history. 30-day trial.
FAQ
Binary backup or export?+
Binary is for fast restore on similar hardware; export is better for readable diffs. Routiv focuses on operational cloud backup history.
Where are files stored?+
Off the router flash, on Routiv infrastructure, accessible from your account.
Recommended frequency?+
Daily for most sites; more often after major config changes.
Related guides
30-day trial — no credit card
30-day free trial