Hi,
If we look at this from a long-term retention perspective having the health checks running irrespective of backup copy job or primary job status would make sense. Veeam doesn't know that you have disabled those jobs because those workloads you were protecting are being retired and now that data in the repo is something that will be kept for a long period or it is because you having networking issues like in the case you referenced. Healthchecks ensures that when you do go to restore the data you can and there hasn't been any silent corruption in the storage layer. Because of that important function, they are enabled by default and require you to explicitly set it to off to make sure that it is not overlooked.
If we look at this from a long-term retention perspective having the health checks running irrespective of backup copy job or primary job status would make sense. Veeam doesn't know that you have disabled those jobs because those workloads you were protecting are being retired and now that data in the repo is something that will be kept for a long period or it is because you having networking issues like in the case you referenced. Healthchecks ensures that when you do go to restore the data you can and there hasn't been any silent corruption in the storage layer. Because of that important function, they are enabled by default and require you to explicitly set it to off to make sure that it is not overlooked.
Statistics: Posted by jason.berry — Aug 19, 2024 1:34 pm
