Skip to main content
The Schedules page shows all active backup schedules across your connections.

​
What you see

For each schedule:
FieldDescription
ConnectionThe connection this schedule runs against
ServerWhich server the schedule lives on
CronThe cron expression (e.g., 0 2 * * *)
Next runWhen the next backup is scheduled
Last runWhen the last scheduled backup ran
RetentionHow many backups to keep

​
Managing schedules

Schedules are created and removed from the CLI on your server: 
capsule schedule add
capsule schedule remove
See capsule schedule for the full reference. The dashboard reflects schedule changes within seconds of them being made in the CLI.

​
Schedule execution

Schedules are executed by the Capsule daemon (capsule service) running on your server. The daemon must be active for scheduled backups to fire. If the daemon is stopped or the server reboots without the service enabled, scheduled backups will be missed. Capsule does not catch up missed backups after a restart. Check daemon status: 
systemctl is-active capsule

​
Missed backups

If a scheduled backup window is missed (daemon not running), no backup is created for that window and no automatic catch-up occurs. The next backup will run at the next scheduled time. To ensure backups run reliably, install the daemon as a boot-time service: 
sudo capsule install-service

​
Schedule limits

The number of schedules you can create depends on your plan. Each schedule counts independently — two schedules on the same connection count as two.