MikroTik Backup & Disaster Recovery: ISP Operations Continuity Guide

Why ISP Router Backups Are Critical

Your MikroTik routers hold the entire configuration that makes your ISP work: firewall rules, queue trees, PPP profiles, RADIUS settings, routing tables, and VPN configs. Losing this configuration means rebuilding everything from scratch — hours of downtime for your subscribers.

Hardware failures, firmware upgrade failures, accidental configuration changes, and even power surges can wipe out a router. Regular automated backups are your insurance policy.

Binary Backup vs Export: Understanding the Difference

MikroTik offers two backup methods, and you should use BOTH:

Automated Backup Script

Create a RouterOS script that runs daily via scheduler to create both backup types and upload to an FTP server:

# Create the backup script
/system script
add name=daily-backup source={
  :local hostname [/system identity get name]
  :local date [/system clock get date]
  :local backupName "$hostname-$date"

  # Create binary backup
  /system backup save name=$backupName dont-encrypt=yes

  # Create text export
  /export file=$backupName

  # Upload both to FTP server
  /tool fetch address=10.10.0.5 src-path="$backupName.backup"     user=backup password=BackupPass123     dst-path="/backups/mikrotik/$backupName.backup"     mode=ftp upload=yes
  /tool fetch address=10.10.0.5 src-path="$backupName.rsc"     user=backup password=BackupPass123     dst-path="/backups/mikrotik/$backupName.rsc"     mode=ftp upload=yes

  # Clean up local files (keep last 3)
  :foreach file in=[/file find name~"$hostname"] do={
    :local fileName [/file get $file name]
    /file remove $file
  }

  :log info "Backup completed: $backupName"
}

# Schedule daily at 3 AM
/system scheduler
add name=daily-backup interval=1d start-time=03:00:00     on-event=daily-backup

Off-Site Backup Storage

Local backups on the router are useless if the router dies. Always store backups off-site:

• FTP/SFTP server — dedicated backup server on your management network
• Email — RouterOS can email backups (good as secondary method)
• Cloud storage — upload to S3-compatible storage for geographic redundancy
• Version control — store .rsc exports in Git for change tracking and rollback

# Configure email for backup notifications
/tool e-mail
set server=smtp.yourisp.com port=587     from=router-backup@yourisp.com     start-tls=yes user=backup@yourisp.com     password=SmtpPass123

# Send backup via email
/tool e-mail send to=noc@yourisp.com     subject="Router Backup - $hostname - $date"     body="Automated backup attached"     file="$backupName.backup,$backupName.rsc"

Disaster Recovery Procedure

When a router fails, follow this procedure for rapid recovery:

• Step 1 — If same hardware: Netinstall RouterOS, restore binary backup via Winbox Files → Restore
• Step 2 — If new hardware: Netinstall RouterOS same version, import the .rsc export file
• Step 3 — Verify critical services: check PPPoE server status, RADIUS connectivity, routing table, firewall rules
• Step 4 — Test subscriber connectivity: verify a few PPPoE sessions establish correctly
• Step 5 — Monitor for 30 minutes: watch CPU, memory, and session counts to confirm stability

How ISPbills Complements Your Backup Strategy

ISPbills stores the authoritative subscriber and package configuration in its database — not on the router. This means:

• Router is replaceable — lose a router, replace it, and ISPbills re-provisions all subscribers automatically via RADIUS and API
• Configuration sync — ISPbills can push PPP profiles, queues, and firewall address lists to a fresh router
• Audit trail — all configuration changes made through ISPbills are logged with timestamps and user attribution
• Multi-router resilience — subscriber data lives in ISPbills, not spread across individual routers