Veeam Backup & Replication - Failed Health Check stopped by job

Note: The description in this article is based on Veeam Backup & Replication 12.3, licensed using Veeam Universal License (VUL), which is equivalent to Enterprise Plus.

Situation Description and Error

We have a backup infrastructure where backups and health checks (Health Check for Backup Files) run without issues. Suddenly, the Health Check for one job ends with an error, indicating that it failed to verify the backup file of one VM.

[Error] Failed to verify backup file [VM name] Error: Stopped by job '[Backup Job name]' (Backup) Agent failed to process method
 {Signature.FullRecheckBackup}.

The Log for the given VM contains these messages:

Succeeded Backup has been locked
Succeeded Verifying backup metadata (100% done) 0:01:25
Failed Verifying disks (100% done) 2:25:39
Failed Stopped by job '[Backup Job name]' (Backup) Agent failed to process method {Signature.FullRecheckBackup}.  
Failed Processing finished with errors at 01.02.2025 0:31:01

During the next health check run, the error didn't appear. But it occurred again later. Searching through discussions, I couldn't find a similar situation. There are often discussions about errors containing Agent failed to process method {Signature.FullRecheckBackup}. However, these usually include additional information like Failed to open storage for read access or A data integrity checksum error occurred.

Error Cause and Solution

The cause of the error is actually very simple, but I had to contact Veeam support for guidance. In retrospect, I can see that the error message hints at this in the part Stopped by job '[Backup Job name]'. The Health Check was stopped by the backup job. This refers to the job whose backup is being health checked.

A condition was violated that states that backup job and health check runs must not overlap. The Health Check was scheduled before the backup job and used to complete before the job started. However, as the VM size grew, the health check duration increased. When the Health Check was still running and the backup job started, the health check was terminated with an error.

The solution is simple. Just reschedule the Health Check process so it cannot overlap with the Backup Job. Alternatively, you can change the start time of the backup job, but this is probably more difficult to plan.