by mkretzer » Wed Dec 06, 2017 9:55 am people like this post
But it always shows the error in the vbk: 06.12.2017 09:54:42 :: Disk wsus_1-flat.vmdk of VM wsus.sw.buhl-data.com is corrupted, possible reason: Storage I/O issue. Corrupted data is located in the following backup files: wsus.vm-781264D2017-12-04T132056.vbk
If there is an incremental point after that (which fixes the "chain" but not the vbk until merge and another health check will run will Veeam still show the corruption in this health check?
by mkretzer » Wed Dec 06, 2017 3:31 pm people like this post
Then this does not seem to work. In the today copy job a corruption of a smaller VM got detected, the new incement was transfered but validator still shows the corruption. But i really have the feeling that validator checks only the vbk or at least starts with the vbk.
I will try to get a health check running and see if the result differs.
by mkretzer » Thu Dec 07, 2017 4:11 pm people like this post
Strange: According to support health check might not really fix these issues: "About the HealthCheck - we can't be sure that it will be able to heal this particular corruption, and probably BackupCopyJob chain should be recreated. "
by DGrinev » Fri Dec 08, 2017 2:48 pm people like this post
Unfortunately, there are several unique conditions leading to inconsistency of the backup chain without ability to fix it by Health Check. I assume the support team found those conditions during the investigation and report you the negative results. Thanks!
by Gostev » Mon Dec 11, 2017 4:23 pm 1 person likes this post
The answer to this question is in the name of the feature, which is "storage-level corruption guard". And it does just that, nothing more and nothing less: detects silent data corruptions in your backup storage, and attempts to make the latest restore point restorable by copying all corrupted blocks over again from the source.