08-05-2016 02:55 AM
Backup Policy: vmware type with GRT, Weekly = Full , Daily = Diff
Sometimes has backed up failed on Diff backup(never failed on full backup) with different virtual machine.
Quiesce snapshot by manually is successful.
Next time backup is succssful.
Do you have solution?
------------------------------------------------------------------------------------------------------------
Backup log:
Monday, July 11, 2016 at 11:15:02 PM
A quiesced snapshot could not be created for the virtual machine (DC)Datacenter(DC)\vm\Discovered virtual machine\AAA.
Thursday, August 4, 2016 at 01:03:54 AM
A quiesced snapshot could not be created for the virtual machine (DC)Datacenter(DC)\vm\Discovered virtual machine\BBB.
---------------------------------------------------------------------------------------------
VMware.log:
\AAA Server\
SnapshotVMXTakeSnapshotComplete: Done with snapshot 'SYMC-DIFF 12-07-2016 00:51': 187
SnapshotVMXTakeSnapshotComplete: Snapshot 187 failed: Failed to quiesce the virtual machine (31).
SnapshotVMXTakeSnapshotComplete: Cleaning up incomplete snapshot 187.
SnapshotVMXTakeSnapshotComplete: Starting snapshot consolidation for cleaning up incomplete snapshots.
SnapshotVMX_Consolidate: Starting online snapshot consolidate operation.
\BBB Server\
SnapshotVMX_TakeSnapshot start: 'SYMC-DIFF 04-08-2016 00:59', deviceState=0, lazy=0, logging=0, quiesced=1, forceNative=0, tryNative=0, saveAllocMaps=0 cb=20405C00, cbData=32425FC0
SNAPSHOT: SnapshotPrepareTakeDoneCB: Prepare phase complete (The operation completed successfully).
ToolsBackup: changing quiesce state: STARTED -> DONE
SnapshotVMXTakeSnapshotComplete: Done with snapshot 'SYMC-DIFF 04-08-2016 00:59': 0
SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (31).
VigorTransport_ServerSendResponse opID=231026e7-a-1758 seq=2494464: Completed Snapshot request.
-------------------------------------------------------------------------------------------------------------------------------
08-10-2016 09:59 PM
What is the version of ESX/ESXi? OS of the VM? do you install latest VMware tools to the VM?
08-14-2016 08:13 PM
Environment:
Backup Sever: BE15FP4, Win2012R2
Vmware 6 u2, vmware tool is lasted version.
08-17-2016 12:43 AM
Failed to Quiesce errors usually relate to VSS operations within the VM itself where teh VSS operation either completely fails or times out as taking too long. Which means you need to look at the event logs within the VM itself (for VSS issues) and you may also need to run things like VSSADMIN LIST WRITERS within the VM itself to check that everything is stable.
If this is intermittent it is may be a timeout situtaion as an outright failure would normally always fail and again if timeouts are internittent this may be a resources issue (RAM, CPU etc) within the VM itself - so how busy are the processes running on the affected VMs during the tmeframe that the snapshot requests are being made?
08-17-2016 12:05 PM
Perform a backup with granular recovery to capture file and folder metadata for a virtual machine. By default, granular recovery is enabled for all streaming backups, but you can disable it if you do not need to restore files and folders from a virtual machine. If granular recovery is not enabled for a backup, file and folder information can still be browsed (Live Browse) and restored (Live File Recovery). These options add time to browse and restore operations, and Live File Recovery is not available for backups that used granular recovery. If granular recovery is enabled but some file information could not be read (for example, ext4 data for a Linux VM), partial metadata is collected during the backup, and you can only browse files and folders for which metadata was successfully captured. To enable Live File Recovery to be used in such situations, you can add the bAllowPartialVMMetadata additional setting to the Virtual Server Agent proxy and set the value to false. With that setting, partial metadata for a virtual machine is discarded, enabling Live File Recovery to be used for browse and restore operations. For steps, see Add or Modify an Additional Setting.