DGrinev wrote:Hi Jennilyn,
No, it's not the same as Health Check, it uses a different algorithm to check backups.
You can review additional information about Validator in the User Guide.
Can you clarify a bit why are you asking? Thanks!
Do you have an actual managed server over on the remote side as a gateway? When going through our growing pains with Veeam we saw this happening cause the gateway for the remote device was being chosen on the source side so some data validation must have to go back to the source site. We spun up a proxy on the remote site and set that as the Gateway and it sped up the checks considerably.
PTide wrote:Health check speed depends on different factors, such as storage type, location, backup size, backup chain length, the way how restore point's data blocks are distributed within the chain. What is your setup?
Yes, validator will also work, however it won't automatically correct errors if case any found.
foggy wrote:Hi Thomas, health check performance is mostly defined by the backup size and by what the storage can provide in terms of the read speed. In your case, I suppose, both factors play the role, since the backup is pretty large and the storage is not top grade in terms of IOPS. Health check protects against storage bit rot and allows to detect in-flight backup file data corruptions. With periodic active fulls the need for health check is not that high, since even if existing backup file is corrupt, active full will create a brand new one, but it still allows to be informed about existing backups health.
Users browsing this forum: No registered users and 54 guests