Which option describes how to schedule a daily backup export using RouterOS scheduler?

Which option describes how to schedule a daily backup export using RouterOS scheduler?

• A. Create a script to run /export file=backup and configure /system scheduler to run daily with on-event="/export file=backup"
• B. /system scheduler add name=backup interval=1d on-event=/export file=backup
• C. Create a script to run /export file=backup on-system
• D. /system schedule add name=backup interval=1d on-event="/export file=backup"

Answer: (A)

Automating daily backups in RouterOS is best done by wrapping the export in a small script and then scheduling that script to run every day. The script gives you a controlled, repeatable process: you can name or timestamp the backup file, add logging, rotate old backups, or add error handling if something goes wrong. The scheduler then triggers this script on a daily interval, so backups happen automatically without manual intervention. That’s why the approach of creating a script that performs the export and configuring the scheduler to run daily on an event that calls that export aligns with solid automation practice. In practice you’d have a script (for example, one named backup-export) whose body runs /export file=backup, and a scheduler entry that executes that script once per day. This keeps the backup process maintainable and extensible, and makes it easy to adjust where backups are stored or how old backups are managed in the future. Options that try to run the export directly from the scheduler without a script lack that layer of flexibility and control. And any option that uses an invalid command path or syntax would not be operable in RouterOS.

Automating daily backups in RouterOS is best done by wrapping the export in a small script and then scheduling that script to run every day. The script gives you a controlled, repeatable process: you can name or timestamp the backup file, add logging, rotate old backups, or add error handling if something goes wrong. The scheduler then triggers this script on a daily interval, so backups happen automatically without manual intervention.

That’s why the approach of creating a script that performs the export and configuring the scheduler to run daily on an event that calls that export aligns with solid automation practice. In practice you’d have a script (for example, one named backup-export) whose body runs /export file=backup, and a scheduler entry that executes that script once per day. This keeps the backup process maintainable and extensible, and makes it easy to adjust where backups are stored or how old backups are managed in the future.

Options that try to run the export directly from the scheduler without a script lack that layer of flexibility and control. And any option that uses an invalid command path or syntax would not be operable in RouterOS.