Backup & Recovery
Backup verification is the core of BlockForge's reliability promise. Every backup goes through an automated restore test in a Docker container — the database is loaded, WordPress boots, and the site is validated. A backup that hasn't been verified isn't a backup.
The Challenge
You cannot manually restore-test hundreds of backups across dozens of sites. The math simply does not work. Each manual restore test takes 15-30 minutes, and you would need to do it daily. Without automation, verification never happens consistently.
Auditors and enterprise clients increasingly require proof that disaster recovery plans actually work. A backup schedule is not enough — they want verification logs showing that restores have been tested. BlockForge generates these reports automatically.
Restore failures are always discovered at the worst possible moment — during a site outage, after a hacked site, or when a client is watching. The time to discover a backup is broken is not during the emergency. It is during the verification.
How It Works
BlockForge does not just check if the backup file exists or if the archive is valid. It performs a complete restore in an isolated Docker environment. The archive is extracted, the database is imported into a fresh MySQL instance, WordPress configuration is applied, and the application boots. Then BlockForge makes an HTTP request to the restored site and validates the response — status code, page title, and content structure. Only backups that pass every stage earn the verified badge.
acme-corp.com
All checks passed
acme-corp.com
5/5 checks passed · 12.4s
shop.example.de
5/5 checks passed · 18.7s
blog.startup.io
DB import failed · charset mismatch
client-portal.net
5/5 checks passed · 9.1s
When a verification fails, BlockForge alerts you immediately with the specific reason: database charset mismatch, missing files, WordPress boot error, or HTTP failure. You get actionable information to fix the problem now, not during a crisis. The verification history gives you a complete timeline across all your sites, making it easy to spot patterns and address issues proactively.
Key Capabilities
Every verification runs in a fresh Docker container with its own PHP, MySQL, and web server. No shared state, no contamination between tests. The container is destroyed after verification completes.
WordPress is fully booted including wp-load.php execution, database connection, and theme activation. BlockForge validates that the WordPress application stack initializes without fatal errors.
The database import is validated beyond row counts. Table structures are verified, character sets are checked for consistency, and critical WordPress tables are queried to ensure data accessibility.
BlockForge captures a screenshot of the restored site and compares it against a baseline. Visual regression detection catches rendering issues that status code checks alone would miss.
Every verification produces a detailed report with timestamps, check results, file sizes, and durations. Reports are stored for compliance and can be exported as PDF for client or auditor review.
When any verification check fails, BlockForge sends immediate notifications via email and Slack with the specific failure reason. Alerts include actionable context so you can diagnose the issue quickly.
Every backup verified in a Docker container. Every restore tested before you need it. Start today.