Downloading, verifying and pinning backups
What you can do with a finished backup: download it, check it again, keep it past retention, and recover without us.
Open any backup from Backup History. The Stored backup card says what was proved about it, and owners and admins can act on it from there.
Verification status
Every backup is checked as it uploads: your storage must hold it at the size sent, its bytes are proved by the storage's checksum where the provider allows, and the archive is opened and read. The card says exactly which of those happened. "Size checked" means your provider's checksum could not be compared, so only the size was.
Verify now
On a job with a server, that server downloads the backup from your storage, hashes it against the checksum recorded when it was taken, and opens it again, so it does not pass through VPS Snaps; your storage provider may charge for the download. On a job without one (the agent, WordPress, a managed database, Kubernetes) your storage is asked whether it still holds the backup at the same size and checksum, and nothing is downloaded. Either way it finds a backup that has changed, been truncated or been deleted since.
Download
Gives your browser a link, valid for 15 minutes, straight to the file in your own bucket. It does not pass through VPS Snaps. Each download is recorded in the workspace's audit log.
Pin
A pinned backup is kept however old it gets, until you unpin it, whatever the job's retention. A job can keep five pinned. It stays in your own storage, on your bill.
Pin the last good backup before a migration or an upgrade, so it cannot age out while you need it.
Clone a job
Copies a job, paused: the same kind of backup, from the same place, to the same storage, on the same schedule. Change what it backs up, then switch it on.
Recovery runbook
Each job has one, from its page. It names the job's own bucket, newest backup and checksum, and gives the commands to download and restore it without VPS Snaps. Print it or download it, and keep a copy somewhere else. It holds no passwords or keys.
Who can do what
- Anyone in the workspace can see a backup and its verification status.
- Owners and admins can download, verify and pin.
- Anyone who can create jobs can clone one.