Hey Roopeshm,
I usually see this happen when a Windows Instance (both Virtual and Physical) have a ton of VSS snapshots, or have modified VSS snapshot configuration. For example, I saw this a few weeks ago in an environment where the IT team configured snapshots on an hourly basis, resulting in tons of VSS snapshots, causing a large amount of time needing snapshots to be processed.
When you add in a backup application, like Veeam, timeouts can be hit due to the increased amount of time for a VSS snapshot to be processed.
In most cases when I run in to this, if appropriate (need to verify you can), I'd remove all the VSS snapshots in the VM, check the configuration, and usually after clearing all snapshots, issues will be resolved.
Cheers,
Stephen
Original Message:
Sent: Mar 20, 2024 07:30 PM
From: roopeshm
Subject: Veeam Backup failed with error
In my veeam backup replication there is a backup failed with the below error.
"3/20/2024 1:12:19 PM :: Processing AD-DC1 Error: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details. (An error occurred while saving the snapshot: Failed to quiesce the virtual machine., An error occurred while taking a snapshot: Failed to quiesce the virtual machine.)" Upon checking i found the veeam unable to create snapshot.
So i went to vcenter and tried to start the quiesced snapshot and i got error. Checked the VM logs in vcenter found.
VssSyncStart' operation failed: IDispatch error #8449 (0x80042301). I have checked the VM tools service and VSS writers state everything is okay,