Backup and restore issues
A backup that stopped, a copy that is missing, a restore that was refused.
A backup is taking long
A backup is a sequence of small steps and the platform continues it where it stopped; a slow backup is not a failed one. The platform decides failure only from the site's own reported progress — no change for a set time, or a backup older than its ceiling. Leave it; check the site's Backups page for its step and percentage.
A backup failed
The row says why. The reasons that recur:
- Worker inactive — the scheduled slot came and the platform could not reach the site. One retry follows an hour later; the site's connection is the thing to fix.
- External storage unavailable — the policy needs object storage the workspace has not configured or that refused the credential. Configure it under workspace settings; a policy that needs external storage is never quietly downgraded to keeping the copy on the site.
- Stalled / timeout — the site stopped reporting progress. Usually the host killing requests; see Hosting limitations. Resume tries again from the last step.
- Verification failed with a chunk named — a chunk in storage does not match what the site computed. The backup is not a restore point; take another.
A copy is "missing" or "unreachable"
Every backup shows the state of each copy. Unreachable means the site or the storage could not be asked; the copy still counts and is asked again next hour. Missing means the site or the storage answered that it is not there. A backup with no available copy is not offered for restore. Check copies reconciles now. The platform never deletes an artifact while reconciling; if a copy is missing, something else removed it.
A restore was refused
- Backup not local — the site's copy is not wholly on disk; the platform fetches the external copy instead when there is a whole one, and says so if there is not.
- Worker does not support fetch — restoring from external storage needs worker 2.2.0 or later on the site.
- Another operation is running — wait for it; the restore is queued behind the site's lock.
A restore completed but the site looks wrong
A restore from a backup made before a change puts the site back before that change, including plugins and settings — except, from worker 2.3.0, the site's connection to the platform and the work in flight. Check which backup was restored from and its date.