This isn't a backup file, but it is a backup mechanism. Before making changes, click the button in Winbox or type /system safe-mode in the terminal.
/export file=$filename
MikroTik offers two distinct methods to save your configuration. Mixing them up is the most common cause of failed restores. Binary Configuration Files (.backup)
The following RouterOS script automatically generates an encrypted binary backup and a sanitized plaintext export, then emails them to an off-site administrative inbox. mikrotik backup restore better
/import file=config.rsc
While binary backups are vital for quick disaster recovery on identical hardware, plaintext configuration exports ( .rsc files) are vastly superior for everyday network management, auditing, and hardware migrations. Hardware Independence
Your router's internal storage or a local FTP server is not a safe final destination. A true "better" backup strategy requires multiple copies in different locations. This isn't a backup file, but it is a backup mechanism
/system backup save name=nightly.backup encryption=aes-sha256 password=strongpass
Think of this as a "system snapshot." It is a binary file that includes everything: user accounts, passwords, and device-specific certificates.
To go from average to exceptional, you must implement with scripts and centralized management with tools like Ansible. Finally, ensure your strategy is complete by storing your backups not just locally, but also in multiple off-site locations like MikroTik Cloud or a secure remote server. Mixing them up is the most common cause of failed restores
If you manage more than a handful of MikroTik routers, managing individual email scripts becomes inefficient. Consider migrating to centralized management tools:
A complete, encrypted snapshot of the router's entire system state.