Has anyone noticed hanging HealthChecks after a server reboot?

[utleyab]

Hello,

I have recently started to get HealthChecks working on a monthly basis for our clients, and I have noticed something. I'm unsure if this is a new development since V12, but it hasn't gone away after upgrading to the newest version of Veeam since I started this endeavor.

If the HealthChecks take a while to run, I usually run them on the weekend, however, that's also when we tend to do our server maintenance. And usually, once a month, servers will get rebooted on a specific schedule. Because of that, I've had HealthChecks interrupted by reboots of the VBR server. When that happens, sometimes the job in the Veeam UI will say it's stopped and will log its status as "Failed", but in the statistics the job is still either pending, running, or hung. Most of the time it's hung.

To fix this before, I've discovered that it could just be a SQL error and that the job says "Aborted" in the database, but there's no evidence of it running anywhere else. A reboot does not fix it, nor does an upgrade of Veeam. It can run again with no qualms. When that happens, I can discover the ID of the entry and remove it with no problems. I've now found that sometimes it doesn't say aborted in the SQL database, and instead says "HealthCheck 92%" (or whenever the HealthCheck had been interrupted on), and it will not run again. Both situations, the time continues climbing up, so something is definitely left running, but I don't know where it is or what it is.

I was wondering if anyone had come across this issue as well? I have opened two cases with Veeam about it so far: Case #07284664 for the solved case where the job was aborted and Case #07353277 for the case I have open with the job that has not been aborted and won't run again.

Thanks!

[PetrM]

Hello,

Please continue working with our support team to find out the root cause, our ability to troubleshoot the technical issues through the forum posts is quite limited.

Thanks!

[utleyab]

No problem, I'm working with Support currently to get it solved, I was just wondering if anyone else has run into this issue before to see if it's repeated or if it's just a problem unique to our solutions.

Thank you!