Skip to main content
A schedule runs a backup automatically on a cron cadence. DBDock Cloud executes it for you — there’s no cron daemon to run or server to keep awake.

​
Create a schedule

1

Open Schedules → New schedule

Choose the connection and storage destination.
2

Set the cadence

Pick a cron expression — for example, 0 2 * * * for every night at 2 AM.
3

Save and enable

DBDock queues the next run and shows when it will happen next on your dashboard’s Up next.

​
Run history

Each schedule keeps a full history of its runs. Open a schedule to see every backup it produced, with status, timing, and logs — so you can confirm last night’s job succeeded at a glance.

​
Reliability

Retries

Transient failures are retried automatically, so a brief network blip doesn’t cost you a backup.

Skip next

Skip the next scheduled run — handy before planned maintenance — without deleting the schedule.
Schedules run in the cloud even when your machine is off. To automate from your own environment instead, use dbdock schedule in the CLI.

​
Alerts

Pair schedules with alerts so you hear about failures immediately over email, Slack, or a webhook — instead of discovering them when you need a restore.

​
Plan availability

Scheduling is available on paid plans, with per-plan limits on how many schedules you can run. See Billing.

Backups

What each run produces.

Alerts

Get notified on failure.