stevil wrote:One of the reasons given in the log is that vCenter was too busy to service the request in a timely fashion. I'm thinking that Veeam is hogging the vCenter VM and stopping it completing the task quickly enough.
Yes, I think you've nailed it, moreover I guess it might also happen if you try to use any other resource-intensive software on this machine.
By the way what's the hardware configuration for this vCenter Server? Is it powerfull enough? Furthermore, how do you protect this vCenter Server? Anyway, reading back through my posts above I suggest having two seprate machines, one for backup console and another for vCenter Server.