Restore and Verify
Restore over a database or into a new one, and prove a backup restores.
A backup is only useful if it restores. VPSPilot can prove that it does, and restore either over the original database or next to it.
Verify a backup
Verification downloads the backup if needed, checks its checksum, decrypts it, restores it into a throwaway database, and drops that database afterwards. The result is recorded on the backup as passed or failed, with details.
POST /api/v1/backups/{run_id}/verifyVerify a recent backup after any change to a database’s schema or engine version, and periodically for critical data.
Restore
POST /api/v1/backups/{run_id}/restore{ "mode": "new", "into": "app_restored" }Take a fresh backup first, or restore with new, inspect the result, and switch your app over. Restores are recorded in the audit log.
Redis
For Redis, verification decrypts the backup and checks it is a valid RDB snapshot. Restoring a managed Redis instance replaces its whole dataset in place: VPSPilot stops it, loads the snapshot, rebuilds its append-only file and starts it again. If anything fails, the previous data is put back. Redis logins are kept. External Redis instances are restored by hand (see the recovery kit for decrypting a backup).
Deleting backups
Deleting a backup removes the local file and the copy in storage. Retention does the same for backups beyond each policy’s limit.