Health-check option has been added recently and is set to "disabled" state so it does not change the behaviour of backup jobs that had been already configured.There must be a reason why the option is available on both, even though they're using the same backup files for the health check process. Other than spreading out the times when health checks run, I assume Veeam recommends to run on copy job, as that's the default setting?
That's not correct. Backup files produces by backup job and backup files produced by backup copy job are different sets of files. Backup copy health check protects your backup copy chain from storage corruption whereas backup health check protects you main backup chain from storage corruption.ven though they're using the same backup files for the health check process
No, it would not. However, there are some improvements on health-check planned in future releases.would it make more sense to run a health check on the backup job where parallel processing is available?
Yes if you run SureBackup on both backup and backup copy jobs. Did you mean backup validator when you said "backup file verification option"?Is it also safe to say that if SureBackup is being used, with the backup file verification option enabled, that health checks can be disabled on both backup jobs and copy jobs?
No, it would not. If you want to reduce fragmentation please use compact full backup file feature.Would disabling parallel data processing reduce disk fragmentation on the target backup repository?
No, as the amount of data to be checked stays the same.Would enabling use per-vm backup files possibly reduce the health check time?
Users browsing this forum: Google [Bot] and 1 guest