A client of ours recently notified us of what seems to be a major flaw in Veeam's logic...
They have a job which backs up their ESXi VMs to NAS using reverse incrementals and then a backup copy job which runs every night to copy them to tape. The tape job has consistently been successfully so the logs weren't getting checked, however the client, who gets the reports too, informed us they had started taking 4 seconds instead of the usual 8 hours to run so they don't think it's working and could we check.
We discovered a lot of logs like the following for each job going back 2 weeks:
21/09/2015 18:52:24 :: Backup file \\ds\Veeam\Server Group 1\Server Group 1.vbk on This server requires retry, postponing.
The job would then end and send a successful notification.
I created a case with Veeam support - 01033144. They logged on remotely and we re-created the tape job, this didn't fix the problem.
I ran an active full backup but re-enabled the old tape jobs (to test) - this didn't fix the problem.
I then used the new tape jobs we'd created and these ran ok - indicating we needed a new tape job and to run an active backup of the VMs.
Anyway the point of this post is I asked support whether there was any chance the successful logic for tape backups could maybe make the above situation a warning at the very least so someone can pick up on it and fix it.
Support recommended I post in the forum. Here we are.