Help
A backup failed or is missing
Tested with:Databasezy API v1 · zb CLI 0.1
Most “missing backup” reports have a simple cause: the Free plan has no scheduled backups, the instance was paused, or the backup ran at a different time than expected (schedules are in UTC). A backup that failed is retried automatically and you get an email; your last successful backup stays available. The sections below cover each case.
What your plan backs up
Section titled “What your plan backs up”| Plan | Scheduled backups | Manual snapshots |
|---|---|---|
| Free | None | 1 |
| Solo | Daily | Up to 3 |
| Team | Daily | Up to 10 |
| Enterprise | Hourly | Unlimited |
Retention, cross-region copies and point-in-time recovery also depend on the plan. See Backups, restore and PITR for the full policy. To see your instance’s effective schedule and your plan’s limits:
zb backups settings <instance_id>It prints the schedule (frequency and time in UTC), retention days, PITR days, and the plan’s caps.
No backup today
Section titled “No backup today”- Free plan. There are no scheduled backups. Take a manual snapshot with
zb backups create <instance_id> --label <label>(one at a time on Free). - The instance is paused. Scheduled backups do not run while an instance is paused. Existing backups stay under the normal retention rules. Resume the instance, or take a manual backup before you pause it.
- The schedule time. Daily backups start at 03:00 UTC unless you changed it. Check the time with
zb backups settings; the backup for “today” may not have run yet in UTC. - The instance is not
ready. A manual backup of an instance that is notready(paused, modifying, restoring) is refused withbackups need a running instance. Try again once it isready.
A backup shows failed
Section titled “A backup shows failed”zb backups get <instance_id> <backup_id>The error: line says what happened. timeout: no backup progress was observed before the configured timeout
means the backup job did not start or stopped reporting. When a backup fails, you get an email headed “Backup failed
for” followed by the instance name, with the number of consecutive failures. Failures are retried automatically and
our on-call team is paged after repeated failures. Automatic retention preserves your latest successful backup;
an explicit deletion is a separate action.
If a backup fails more than once in a row, or you need a fresh backup now (for example before a release), open a
ticket and take a manual snapshot when the instance is ready.
manual snapshot limit reached (N of M on plan X); delete one or upgrade
Section titled “manual snapshot limit reached (N of M on plan X); delete one or upgrade”Each plan allows a number of manual snapshots at a time; scheduled backups do not count against it. Open
Backups → Delete on a completed backup, or run zb backups delete <instance_id> <backup_id>, to free a slot
after deletion completes. You must confirm the instance name and have backups:write permission; human sessions also
need recent MFA. Object Lock, dependent incremental backups and active restores can block deletion. See
Delete a backup before removing recovery history.
A snapshot also stops counting when retention removes it (see expires in zb backups list). Automatic
retention preserves the latest successful backup even after expiry. If none can safely be removed, upgrade the plan.
Old backups disappeared
Section titled “Old backups disappeared”Backups are deleted when they pass the retention period of your plan (or the shorter retention you set). The most
recent successful backup of an instance is protected from automatic pruning, even past retention; an authorized
explicit deletion can still remove it. To keep a copy for longer, export it
with the engine’s own dump tool (for example pg_dump), since there is no one-step export yet.
Changing the schedule
Section titled “Changing the schedule”zb backups settings <instance_id> --frequency daily --time 01:30 --retention-days 7The settings must stay within your plan:
plan <plan> allows at most daily backups: hourly backups are on Enterprise only.must be 1..=N on plan <plan>: retention is above your plan’s maximum.scheduled backups cannot be disabled; pause the instance instead.plan free has no scheduled backups.
Frequency accepts daily or hourly.
Check backup health across the organization
Section titled “Check backup health across the organization”On Team and Enterprise, zb backups health lists every instance with a status (ok, warning or critical), its
last successful backup and its last error. A daily schedule turns warning after 26 hours without a successful backup
and critical after 50 hours; an hourly schedule after 2 and 6 hours. A failed restore verification also gives
warning. On other plans the report is refused with
the backup health report is included on Team and Enterprise plans.
Still stuck?
Section titled “Still stuck?”Search the help center or ask the assistant in the portal Help panel. If that does not solve it, open a support ticket
from the portal (Help → Open a ticket). Include the instance id, the backup id, the error line from
zb backups get, the region, and the time it happened in UTC. Never paste passwords, connection strings with
passwords, API keys or patient data (PHI) into a ticket. See How to get help.