Performing Health Check and Repair for Unstructured Data Backups

In this section you will learn how to perform:

Health Check for File Share Backup Files

You can manually perform a health check for the backup chain. During the health check, Veeam Backup & Replication performs a CRC check for metadata and a hash check for data blocks in backup files to verify their integrity. The health check helps make sure that the restore point is consistent, and you will be able to restore data from this restore point.

To run the health check:

  1. Open the Home view.
  2. In the inventory pane, select Jobs > Backup.
  3. In the working area, select a job of the File Backup or Object Storage Backup type and click Run Health Check on the ribbon or right-click the job and select Run health check.

To run the health check periodically, you must enable the Perform backup files health check option in the backup job settings and define the health check schedule. By default, the health check is performed on the last Friday of every month. You can change the schedule and run the health check weekly or monthly on specific days. To learn how to configure periodic health check, see Maintenance Settings.

Important

If you store your file backups on public cloud object storage repositories, running the health check operations may result in constantly downloading and uploading data to and from the storage, which may lead to higher costs. To avoid this, use helper appliances, configured for the repositories within the public clouds. For more information, see the Object Storage as NAS Backup Repository section.

Run Health Check

Repair of File Share Backup Files

If during the health check Veeam Backup & Replication detects some inconsistency in the file share backup files, you can run the backup repair procedure to fix the issues.

To run the backup repair:

  1. Open the Home view.
  2. In the inventory pane, select Jobs.
  3. In the working area, select a job of the File Backup type, right-click the job and select Repair backup.

Run Repair

Page updated 3/19/2024

Page content applies to build 12.1.2.172