How to Safely Backup and Restore Your MikroTik CHR Configuration
Managing a cloud router without a proper backup plan can quickly become risky, especially before upgrades, migrations, or unexpected failures. This guide explains a practical MikroTik CHR backup and restore workflow using automated exports and safe restore methods, so you can protect your configuration, reduce downtime, and avoid version-related problems.
If you are running CHR on MikroTik VPS hosting, having a clean backup and restore routine makes upgrades, recovery, and migration much easier.
Table of Contents
Understanding MikroTik Backup File Types
MikroTik RouterOS provides two methods for saving your data, including binary system backups and plain-text configuration exports. Understanding the difference between these two file types is the key to a safe and successful recovery.
- System Backup (.backup): Saves the complete device state, including MAC addresses, user databases, and certificates. This format is version-dependent and should only be restored on the same CHR and RouterOS version.
- Export (.rsc): Generates a readable plain-text script of your active configuration. This is version safe because you can easily read, edit, and import it across different hardware types or RouterOS versions.
Prerequisites for MikroTik CHR Backup and Restore Workflow
Before you start to set up MikroTik CHR backup and restore, make sure your MikroTik CHR instance is ready for both backup creation and safe restore testing. Having the right access, storage, and version details in place helps prevent restore errors and incomplete exports.
- A working MikroTik CHR with admin access via Terminal, WinBox, or SSH.
- Permission to create and manage files in RouterOS.
- Enough free space for .backup and .rsc files.
- Your current RouterOS version is noted for safe .backup restores.
- A clean target system for testing .rsc imports.
- Access to sensitive settings if you need show-sensitive.
If you use MikroTik VPS hosting through a reliable provider like PerLod Hosting, always save your exports externally or use server snapshots to guarantee recovery if an upgrade fails.
Method 1. Create and Restore MikroTik Binary Backups
A binary backup saves the exact state of your MikroTik CHR, including user accounts, passwords, and MAC addresses, into a .backup file. It is perfect for a quick restore if an upgrade fails, but you must only restore it on the same router and RouterOS version.
Run the following command to generate a full system state backup:
/system backup save name=chr-full-backupTo revert your system to a previous state, you can run the command below:
/system backup load name=chr-full-backup.backupThe load option reads the specified .backup file. The router will ask for confirmation and reboot immediately to apply the exact system state.
Method 2. Export and Import MikroTik Plain Text Configurations
A configuration export saves your MikroTik setup as a human-readable script rather than a binary backup, making it easier to migrate and safer for recovery planning across different setups.
To create a version-safe text script, you can run the command below:
/export file=chr-config-safe show-sensitive- export: Saves your current configuration as command lines.
- file: Sets the name of the export file, such as chr-config-safe.rsc.
- show-sensitive: Includes hidden secrets in RouterOS v7, such as passwords, private keys, and PPPoE secrets.
To import the configuration to a fresh system, you can run:
/import file=chr-config-safe.rscThis runs the configuration commands listed in the file sequentially to rebuild your setup.
Set up MikroTik Automated Exports
Manually exporting your configuration is easy to forget. To make sure you always have a recent backup ready for disaster recovery, you can set up a simple script to automatically export your CHR settings every 24 hours.
You can create a script that adds the current date to your export filename with the command below:
/system script add name="auto_export" policy=read,write,policy,test,password,sensitive source="
:local date [/system clock get date];
:local filename (\"auto-export-\" . \$date);
/export file=\$filename show-sensitive;"Then, you can add a scheduler to run your new script automatically with the command below:
/system scheduler add name="daily_export" on-event="auto_export" start-time=startup interval=1dThat’s it, you are done with setting up MikroTik CHR backup and restore workflow using system backup and exports.
FAQs
Can I restore a .backup file on a different MikroTik CHR?
No. Binary backups (.backup) save exact hardware details like MAC addresses. Restoring them on a different server causes network errors. Always use a plain-text export (.rsc) when moving to a new CHR.
Why are my passwords and VPN keys missing from my RouterOS v7 export?
By default, RouterOS v7 hides sensitive data like passwords and private keys in .rsc exports. You must add the show-sensitive flag to your export command to include them.
What is the difference between MikroTik system backup and export?
System backup creates an exact copy of the router state, including MAC addresses, for restoring the same device. Export creates a plain-text script of your commands for safe migration and editing.
Conclusion
A solid MikroTik CHR backup and restore strategy should include both binary backups for the same system recovery and .rsc exports for safer migration and rebuilds. By using regular backups, automated exports, and the show-sensitive flag in RouterOS v7, you can reduce downtime and make restores much more reliable.
We hope you enjoy this guide. Subscribe to our X and Facebook channels to get the latest updates and articles.
For further reading:
