Chiming in on this old thread.
Chris, recently we've been having that exact issue with Veeam and SM. The Veeam VSS service times out and the backup fails. Then within a few minutes we start getting alerts and customer reports of issues with email. Restarting the server just hangs and we have to do a hard reset. This results in JSON corruption. We know what to look for and can fix it quickly, but this is not ideal.
I have a ticket open with Veeam, but they're saying VSS isn't supported with SM and that we should disable that feature in our backup jobs. What's interesting is from the logs I pulled for Veeam I can see that only the C volume is being shadow copied. It's not even touching the volumes SM is using.
I'm just sharing our experience and seeing if anyone else has encountered the same. Chris it would be good to know if you continued to have this issue. Also, I know ST you have stated in the past that you use Veeam with VSS so if you have anything to add on this topic that would be appreciated.