# How to verify Veeam backup integrity

Learn how to verify Veeam backup integrity with health checks, SureBackup, and restore tests, so you know a restore point will actually restore.

You verify Veeam backup integrity by letting Veeam check the backup files and then proving a restore works. The health check confirms the files are readable, while a restore test or SureBackup confirms the data inside can actually be recovered. Run both on a schedule you can keep, and record the result for each restore point. 

- Run the backup file health check so Veeam reads the files and flags corruption early.
- A health check alone does not prove the data restores, so add a restore test.
- SureBackup starts a virtual lab and boots machines from the backup to confirm they work.
- A manual Veeam backup test restore to an isolated location covers virtual and physical workloads.
- Write down the outcome for each restore point so you can show the backup was verified.
 

## What backup integrity verification means in Veeam 

Backup integrity verification in Veeam Backup & Replication means checking that a restore point is complete and readable. Veeam backup verification works at two levels, the backup file itself and the data inside it. The first level catches damage to the file, and the second level proves the workload can come back. 

A restore point is one saved copy of a workload at a point in time, and it holds the blocks needed to rebuild that workload. Verifying a restore point checks that those blocks are present and consistent. Skipping this step leaves you with a file that looks present in the console but may not restore. 

Treat verification as part of the backup job, not a separate project. Each job can carry a health check, and you can schedule a restore test on a rhythm that matches how much data you can afford to lose. The result of each check belongs in a written record that names the job, the restore point and the outcome. 

## Run the backup file health check 

The backup file health check is the first layer of Veeam backup verification, and it examines the stored backup files for damage. Veeam reads the blocks of each restore point and confirms they match what was written. A failed check tells you a restore point is suspect before you need it. 

You enable the health check in the maintenance settings of a backup job. The check runs after the job finishes and consumes disk read capacity, so plan it away from busy backup windows. Full backup files and incremental files are both scanned, and a problem is reported in the job session. 

A health check does not boot the workload and does not prove the operating system starts. Treat a passed health check as proof that the files are intact, not as proof that the restore works. Pair it with a restore test so both layers are covered. 

- Open the backup job and its maintenance settings
- Turn on the health check for the job
- Set a schedule that fits your backup window
- Read the job session after the next run
- Record the result for each restore point
 

## Confirm a restore with SureBackup 

SureBackup is the Veeam feature that starts virtual machines from a backup inside an isolated virtual lab. The lab is a separate network, so the test machines do not touch production. SureBackup proves that a restore point boots and that the workload answers checks you define. 

A SureBackup job uses an application group, which lists the machines to start and the order to start them. You attach verification scripts to test services, ports or heartbeats, and a machine that fails a script is marked as failed. The job reports each machine separately, so you see which workload needs attention. 

Run SureBackup on a schedule that matches the value of the data and the capacity of your hosts. The lab needs memory and storage while it runs, so check that hosts have room before you schedule it. SureBackup covers virtual workloads; physical machines need a different test. 

## Perform a manual Veeam backup test restore 

A Veeam backup test restore is the manual proof that a restore point returns usable data to a chosen location. You pick a restore point, start a restore, and send the result to an isolated folder or a spare virtual machine. The test restore is the plainest answer to whether the backup works. 

Choose a restore target that cannot overwrite production data, such as a separate datastore or a disconnected network. Restore a single file for a quick check, and restore a whole workload when you need full confidence. Compare the restored content with the source before you mark the test as passed. 

A test restore for a physical server may need a spare machine or an isolated network segment, and that setup takes planning. Where the restore involves domain controllers or database servers, bring in the administrator who owns that system. A test that damages production is worse than no test at all. 

## Decide what to verify and how often 

Verification effort should follow how much a workload matters and how fast you need it back. A restore point for a file server and a restore point for a database server carry different weight. Sort workloads into groups, then assign a check to each group. 

Health checks can run on every job with modest extra load, so they suit nearly every workload. SureBackup and full test restores demand host capacity and time, so reserve them for workloads whose loss would stop work. The frequency you pick depends on your recovery targets, your host capacity and your staff time. 

Review the schedule when a workload changes, such as a new application or a move to different storage. A verification plan that no one runs is worth nothing, so keep the number of tests small enough to finish. Name the person who reads each result and the person who acts when a check fails. 
| Check | What it proves | Load it adds | 
| Backup file health check | Files are readable and intact | Disk read on the repository | 
| SureBackup job | Virtual machines boot and pass scripts | Host memory and lab storage | 
| Manual test restore | Data returns to a chosen target | Target storage and staff time |  

## Keep a record of each verification result 

A verification record turns a passed check into evidence you can show later. Write the job name, the restore point, the date of the check, the type of check and the outcome. Keep the record where the team can reach it without asking one person. 

When a check fails, record the failure and the action taken, not only the final success. A failed health check may call for a new full backup, and a failed SureBackup may call for a fix to the application group. The record links the symptom to the repair. 

Store the record with your other operational notes, and treat it as part of the backup itself. A short entry per restore point is enough, and it answers the auditor or manager who asks how you know the backup works. This habit mirrors any family record you keep for appointments, where one calm list beats scattered notes. 

## Act on a failed verification 

A failed verification is useful information, and the response depends on which layer failed. A damaged backup file calls for a new full backup and a check of the repository storage. A failed SureBackup calls for a review of the application group scripts and the guest operating system. 

Before you delete a failed restore point, confirm that another valid restore point exists for the same workload. Removing the only good copy to tidy the console leaves you exposed. Retire the damaged file only after the replacement passes its own verification. 

If the repository storage shows repeated damage, involve the storage or virtualization specialist who owns that system. Do not keep rerunning a check that fails on the same hardware without finding the cause. A pattern of failures points to the storage layer, not to the Veeam job settings. 

## Questions about Veeam backup verification 

### Does a Veeam health check verify backup integrity? 

A Veeam health check verifies that the backup files are readable and intact, which is one part of backup integrity. It does not boot the workload or prove the data restores. Pair the health check with SureBackup or a test restore for full restore verification. 

### How do I do a Veeam backup test restore? 

A Veeam backup test restore starts with a chosen restore point and a restore target that is isolated from production. Restore a file or a whole workload, then compare the result with the source. Record the outcome so the test counts as evidence. 

### What is the difference between SureBackup and a test restore? 

SureBackup starts virtual machines from a backup inside an isolated virtual lab and runs verification scripts against them. A test restore returns data to a target you choose, such as a folder or a spare machine. SureBackup covers virtual workloads, and a manual test restore also works for physical ones. 

### Can I verify a backup of a physical server? 

SureBackup verifies virtual machines, so a physical server needs a different path. Use a test restore to a spare machine or an isolated network segment, then check that the system starts and the data is present. Involve the administrator who owns the system before you test. 

### What should I do when a Veeam backup health check fails? 

A failed health check means a restore point is suspect, so check whether another valid restore point exists first. Create a new full backup and confirm it passes its own verification. If failures repeat on the same storage, bring in the storage specialist.
