# Create a unique timestamp :local timestamp [/system clock get date] :local time [/system clock get time] :local backupName ("auto_backup_" . $timestamp . "_" . $time) /system backup save name=$backupName 2. The Editable Export (Sensitive included) /export file=$backupName sensitive 3. Upload to FTP/SCP immediately (Off-site) /tool fetch upload=yes src-path=($backupName . ".backup") dst-path=("/backups/" . $backupName . ".backup") user=ftp_user password=ftp_pass ftp://192.168.1.100/
/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
system-backup-suite
#!/bin/bash # Restore script for MikroTik ROUTER_IP=$1 BACKUP_FILE=$2 curl -k -u admin:password -F "file=@$BACKUP_FILE" "https://$ROUTER_IP/rest/system/script/run" # Create a unique timestamp :local timestamp [/system
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. $time) /system backup save name=$backupName 2
If you manage a MikroTik RouterOS device, you likely know the drill: right-click, click "Backup," save the file, and move on with your day. It feels safe. It’s quick. It is also, quite frankly, a disaster waiting to happen.