the irony is killing me! lol
as soon as I sent this in, got a reply!
"You are in kind of a Catch-22 situation with updates. It's never easy to find time to reboot in a production environment. Apparently, there is a known issue where there is some risk of corrupted data if a backup job runs during that time after updates have been installed and the reboot. It can cause VSS writers to act erratically, for example. I suppose it makes a difference what exactly is updated.
Here is a link to our documentation for managing backups and replicas: https://helpcenter.veeam.com/backup/hyp ... ckups.html
Basically, what likely happened is that the update possibly cause the VSS writers to act erratically during a merge or some other part of the backup operation that involves the full. It depends on how your retention is configured.
I hope this answers your questions."
this unfortunately, does not answer my questions at all... is this really a known issue in veeam? I highly doubt veeam would let that issue become a caveat that cant be addressed. veeam has been rock solid for us and like I said before, we have always patches our servers in this way. if this "known issue" was the case, then I assume we would see this issue every single month when we apply MS patches to 30+ servers..
anyways, I've gone ahead and removed the bad backup job, the chain, and removed from config DB rescanned the repo. am now in the process of recreating the job. im hoping I didn't miss anything....