Verifying backups is a hot topic—everyone wants to be certain their data is safe, but few think beyond “does my backup match production?”. The reality is, backup verification isn’t as straightforward as ticking a box. Let’s explore the differences between what’s commonly asked for and what’s genuinely needed to ensure true recoverability.
The Basics: Matching Backups to Source
Most start with the basics: “Does my backup match the live VM?” Veeam handles this with storage-level corruption guards, performing CRC checks to confirm the backup files aren’t silently corrupted. It’s a good start, but it’s not the whole story.
The catch? If there’s a problem hidden in production—a missing system file, a corrupt OS, an application that’s quietly broken—your backup will faithfully preserve that issue. Garbage in equals garbage out. The backup matches production perfectly, but if production is flawed, your backup will be too. That problem won’t reveal itself until you next reboot or, worse, when you need to restore.
Go Further: Will It Actually Boot and Run?
This is where SureBackup comes into play. Rather than just checking file integrity, SureBackup boots the VM in a sandbox, verifyng the operating system responds to ping tests and has a ‘heartbeat’.
SureBackup doesn’t check every byte of data, but it does confirm that the core OS boots and the application stack is functional. That’s a much better guarantee than simple bit-level matching.
Application Testing: Beyond “It Boots”
For business-critical systems, it’s not enough to know the OS comes online. You want proof that the applications are present and responsive. Veeam’s SureBackup lets you automate tests like:
- Is SQL accepting connections?
- Can IIS serve a webpage?
- Does Active Directory respond to LDAP queries?
The built-in Active Directory test works by probing port 389 in the virtual lab. If the backup boots and responds to connection attempt, the test passes—proving the DC isn’t just alive, but ready to serve. For deeper checks, you can add custom scripts to probe more complex scenarios.
Don’t Forget Security: Malware Verification
Backup verification should also include a security angle. SureBackups enables you to also schedule malware scanning of backups, helping prevent reinfection. With ransomware on the rise, this step is more important than ever.
The Best Approach: Combine Methods
The most reliable backup verification strategy is layered:
- Storage-level corruption guard (CRC parity check)
- SureBackup verification (boot and application checks)
- Malware scanning (Veeam Threat Hunter, YARA rules or third-party AV integration)
Each method covers different risks. Storage checks catch silent corruption, SureBackup exposes OS and application issues, and malware scanning protects against cyber threats.
Conclusion
Backup verification isn’t just about matching files; it’s about proving recoverability. Most people start by asking for file-level checks, but what you really need is a solution that confirms your systems and applications will actually work when restored. If you’re only running a storage-level corruption guard check and skipping SureBackup, you’re missing half the picture—and if you’re not scanning for malware, you’re leaving the door open to trouble.
Your backup is only as good as your last test. Make sure that test proves what matters.