Backup Schedules
A schedule runs backups so you do not have to remember to. Pick how often, what to include, how long to keep them and where to send them, and the panel handles the rest, with a live countdown to the next run.
Backup → Scheduleshttps://YOUR-SERVER-IP:8443/backup/schedules| Schedule | When | Type | Next run | Actions |
|---|---|---|---|---|
| nightly | Daily 02:00 | incremental | 5h 12m | run · pause · edit · delete |
Setting the schedule
Frequency comes from a curated list of presets rather than raw cron typing: every few minutes, hourly variants, daily at a chosen hour, weekly, monthly. Each preset shows its underlying cron expression so you know exactly when it fires. Choose the backup type (full or incremental), the content to include (files, databases, emails, DNS, SSL as independent toggles), the domains (leave empty to mean all active domains), a compression level and whether to encrypt.
Retention and chain rotation
Two independent controls keep storage bounded. Retention deletes backups older than a set number of days (defaulting from your panel settings, typically 7 to 10). Chain rotation, for incremental schedules, forces a new full backup once the current chain reaches a maximum age in days or a maximum number of backups, whichever comes first, so incrementals never stretch into an endless fragile chain. A user cannot extend a chain past these limits by triggering manually; the rotation policy applies to manual runs too.
Remote targets
When the remote-backup feature is licensed, a schedule can fan its finished backups out to one or more remote storage destinations, in priority order, automatically after each run.
Managing schedules
Each schedule can be run now, paused/resumed, edited or deleted, and bulk actions cover trigger-all, pause-all, resume-all and delete-all (the last behind a typed DELETE). Status is active, paused or the effect of a failed run, shown per row alongside the last result.
Access
Behind the backup_scheduled license feature (remote sync additionally needs backup_remote), with seven granular permissions (create, edit, delete, run, toggle, trigger-all, delete-all). Schedules are scoped by the roles and permissions chain: each account manages its own schedules, an admin its chain, ROOT all.