system-backup-suite
/tool fetch upload=yes src-path=($backupName . ".rsc") dst-path=("/exports/" . $backupName . ".rsc") user=ftp_user password=ftp_pass ftp://192.168.1.100/ /file remove [find where name~"auto_backup" and type="backup" and creation-time<([/system clock get date] - 30d)] /file remove [find where name~"auto_backup" and type="script" and creation-time<([/system clock get date] - 30d)]
This happens because RouterOS v7 fundamentally changed syntax for interfaces (e.g., /interface bridge port rules) and wireless packages (WiFi wave2).
Log into your main router right now. Run /export file=manual_backup sensitive . Download that file. Store it somewhere outside your network. That single act is the first step to a "better" restoration strategy.
system-backup-suite
/tool fetch upload=yes src-path=($backupName . ".rsc") dst-path=("/exports/" . $backupName . ".rsc") user=ftp_user password=ftp_pass ftp://192.168.1.100/ /file remove [find where name~"auto_backup" and type="backup" and creation-time<([/system clock get date] - 30d)] /file remove [find where name~"auto_backup" and type="script" and creation-time<([/system clock get date] - 30d)] mikrotik backup restore better
This happens because RouterOS v7 fundamentally changed syntax for interfaces (e.g., /interface bridge port rules) and wireless packages (WiFi wave2). mikrotik backup restore better
Log into your main router right now. Run /export file=manual_backup sensitive . Download that file. Store it somewhere outside your network. That single act is the first step to a "better" restoration strategy. mikrotik backup restore better