Risky to stop health check? (case 03880409)

[acatic]

I got a health check running on a rather large backup job of one VM. It looks like it's going to take the whole day to finish. However, I have a need to reboot the backup server so that the tape job can run for other backups. When I proceed to stop the health check, I'm given the warning "Backup's files for this job will be left in the inconsistent state. One or more instances will have incomplete, unusable restore points. Stop the job anyway?"
I don't want to lose a day of tape runs, while also not wanting to break the subject job's backup files.
Thank you for all assistance.

[nitramd]

@acatic,

If I remember correctly, a health check occurs before a backup begins.

I believe that if you rebooted then the health check would restart.

[Gostev]

No, actually health check runs at the end of the job. Also, the message is related to the actual backup job, you can disregard it during health check. There's no risk to stop health check, as it is a read-only operation. Thanks!

[foggy]

If I remember correctly, a health check occurs before a backup begins.

This is true for the backup copy job, but not for the regular backup job. Thanks!

[nitramd]

That's it! Thanks Foggy!

[YouGotServered]

This is true for the backup copy job, but not for the regular backup job. Thanks!

Out of curiosity, what is the reasoning for this change in logic between the two jobs?

[nitramd]

I suspect that it has to do with copying data from one repo to another.