Backup Files Health Check

[APangF1]

The Backup Files Health Check sounds like a nice feature, but unfortunately it cannot be scheduled to start at a specific time OR immediately after a backup has finished. We're using good quality redundant storage for backup repositories. Any comments on whether this feature is more trouble than it's worth?

Thanks

[foggy]

Health check is performed at the end of the backup job run, right after the backup is completed. Its performance is defined by the storage I/O capabilities, so only the actual test can tell if it fits your backup window.

[tomnewman]

If my understanding is correct, the health check compares the metadata to what is on your repo. This ensures the integrity of the backup files on the repo i.e. checks what is stored on the repo hasn't been corrupted. As such I would see it as an essential part of any backup. We run it weekly before the backup gets dumped to tape.

Its only a tickbox so as long as your window is big enough its well worth doing but it can take a while to run. You can also add Surebackup to test restorability but it takes a bit more setting up. We do both.

[APangF1]

Thanks. Does information about the Health Check run appear as part of the related backup job (in the statistics/report for that backup job)? Or does the logging of details about the Health Check jobs require VeeamOne to be installed?

[foggy]

Health Check is reported as a part of the corresponding job run.

[rlspeeks]

As per @APangF1

The Backup Files Health Check sounds like a nice feature, but unfortunately it cannot be scheduled to start at a specific time OR immediately after a backup has finished. We're using good quality redundant storage for backup repositories. Any comments on whether this feature is more trouble than it's worth?

Please, please, please make this so it can be a separate scheduled job. Thanks for listening.

[foggy]

Hi Rebecca, your voice is counted. We are thinking of including this in the list of future optimizations. Thanks!