60Web60

Understanding Backup Verification Processes

Backups & Restore4 min read·

This article explains how to verify that your Web60 backups are complete and working properly.

Understanding What Backup Verification Means

Backup verification checks that your backup files are complete and contain all the data needed to restore your website. A backup that looks successful might actually be missing files or contain corrupted data.

Web60 runs automatic verification checks on all backups, but you can also perform manual checks to ensure everything is working as expected.

How Web60 Verifies Your Backups

1. File Integrity Checks

Every backup includes a checksum - a unique fingerprint that changes if any file is corrupted or missing. Web60 compares these checksums to verify all files copied correctly.

2. Database Validation

The system checks that your WordPress database exported completely and can be read without errors. This includes verifying table structures and data integrity.

3. Size and Content Verification

Web60 compares backup sizes against expected ranges and checks that essential WordPress files (like wp-config.php) are present in every backup.

Checking Your Backup Status Manually

1. Access Your Web60 Portal

Log into your Web60 account and navigate to the "Backups" section. You'll see a list of all recent backups with status indicators.

2. Look for Status Indicators

  • Green tick: Backup completed and passed verification
  • Yellow warning: Backup completed but with minor issues
  • Red cross: Backup failed or failed verification

3. Review Backup Details

Click on any backup to see detailed information including file count, total size, and verification results. Compare these numbers across different backups - they should be similar unless you've made major changes to your site.

Testing Your Backups Work

The only way to truly verify a backup works is to test restoring from it. You can do this safely without affecting your live website.

Using Staging Sites

If you're unsure about your backup integrity, consider setting up WordPress staging sites where you can test restore processes without risk.

Partial Restore Tests

You can test individual components by downloading backup files and checking they contain the expected content. For guidance on this process, see downloading your backup files.

What to Do If Verification Fails

If you see backup verification failures:

  1. Check your website: Make sure it's running normally and not showing error messages
  2. Create a manual backup: Try creating a manual backup to see if the issue persists
  3. Contact support: If problems continue, Web60 support can investigate and fix underlying issues

Remember that one failed backup isn't critical - Web60 keeps multiple backup copies. However, repeated failures need immediate attention.

Setting Up Backup Notifications

To stay informed about backup status, you can set up automated backup notifications. This sends you alerts when backups fail verification, so you know about problems immediately.

If you're still stuck with backup verification issues, contact Web60 support through your portal. Include details about which backups are showing problems and any error messages you've seen.

FAQ

Q: How often does Web60 verify my backups?

A: Web60 verifies every backup immediately after it completes. This happens automatically for all daily backups and any manual backups you create.

Q: Can I verify my backups without downloading them?

A: Yes, you can check verification status and backup details through your Web60 portal without downloading files. This shows file counts, sizes, and integrity check results.

Q: What does "backup verification failed" mean?

A: This means the backup files are incomplete or corrupted. The backup might be missing files, have database errors, or contain damaged data that couldn't be verified.

Q: Should I be worried if one backup fails verification?

A: Not immediately, as Web60 keeps multiple backups. However, you should investigate if failures happen repeatedly or if your website is showing problems.

Q: How long are verified backups kept?

A: Web60 keeps verified daily backups for 30 days. Older backups are automatically removed, but you can download important backups for long-term storage.

Q: Can I force Web60 to re-verify an old backup?

A: No, but you can create a new manual backup which will be verified automatically. This is more reliable than re-checking old backup files.

Q: Do failed backups count against my storage limit?

A: No, only successfully verified backups count towards your storage allocation. Failed backups are automatically cleaned up.

Last updated: 1 March 2026