You should not be relying on veeam to validate the integrity of your data anyways. All veeam can do is validate that the backup file itself is not corrupted and that the VM can boot up if you test that, but that doesn't mean what it backed up to begin with was 100% fine. Basically, if veeam incorrectly ingested the data for a few blocks, a health check won't know, because as far as it is concerned the backup file itself may be perfectly fine.

You should test the backup yourself a few times per year by doing an instant restore and run a script that checks file by file some kind of hash compared to the live version. If any files (excluding anything after the time the backup was last started) start showing up as not matching then you need to ask some questions.

Going the extra mile like this can also help you identify file corruption not related to the backup at all. Maybe your have silent data corruption going on, and you're backing up corrupted files and don't even know it, if you catch it early enough maybe an older backup has good versions.

This is why I run everything on ZFS now. Veeam agents back up images of the system at a point in time in case a config screws up or an OS dies, but ZFS (synced to multiple identical devices at different locations) is what keep the actual data integrity.