Health Check Verification is running on disabled backup copy jobs

[italmi]

Dear All,

I am writing to address an issue we are experiencing with our Backup Copy Job, which we use for our monthly offsite backup.

This is an offsite backup, so the designated repository is not always connected to the Veeam Backup Server.
The Backup Copy Job runs manually upon request, and it remains disabled at all other times.

We have enabled the Health Check Verification feature intending to run when the job is enabled and the repository is attached.
However, despite the job being disabled, the Health Check Verification will run failing, as the relevant repository is
unavailable since it is stored offsite.

We kindly request that the Health Check Verification only run for active jobs or that you provide an option (such as a checkbox)
to ignore or skip it when the job is set to "disabled."

[veremin]

Since some time ago, health check operations have been running in the background and therefore are not dependent on the state of the parent job. Whether it's enabled or not, the health check will still be performed.

If you are already manually enabling and disabling the job or doing so through scripts, you might probably also enable and disable the health check for it as needed.

Thanks.

[italmi]

Dear Veremin,

This is an R&D request to implement an option to disable the health check on a disabled job.
From Veeam's Support, I was told to submit my request here on the forums.

A task being run on a disabled job does not make any sense.
This is why I ask for an option to be added to enable/disable the health check upon the user's request.

Thank you for your kind understanding,

[veremin]

Sure, we've taken your request. Such a change was not in our immediate plans, but the situation might change if the number of requests for this functionality increases. Thanks!