Wow... thanks for providing that information! I'll add your observations to our internal bug report on the issue.
It sure seems like Veeam has some role to play in this corruption.
I'll investigate adding a workaround into our virtual EFI firmware to try to prevent/recover from this situation, but it's looking like we should also report it to Veeam as well.
Cheers,
--
Darius