Test a Backup

Review the weekly restore tests, test any backup on demand, and understand what passed, failed and could not run each mean for a backup.

Before you start: At least one successful backup.

  1. 1

    Review restore verification

    The Restore verification panel on Backups shows the latest restore test, and Each source lists every source’s latest result. Each source’s newest backup is tested every week automatically.

  2. 2

    Test a backup now

    Test restore on any completed backup fetches it onto its server, verifies it byte for byte, loads its database into a scratch database, reads every table and drops the scratch copy. Your live data is not touched.

  3. 3

    Understand the results

    Passed means the backup restores. Failed means it would not, and the account is emailed. Could not run means the test was blocked, for example by an unreachable server or low disk space. It says nothing about the backup, and is shown in amber rather than red.

  4. 4

    Check the badges in Backup history

    Each backup shows how far it has been verified: Confirmed stored, Restore tested or Failed verification. A backup that failed verification no longer counts toward the copies a schedule keeps.