cancel
Showing results for 
Search instead for 
Did you mean: 

VM Snapshot failed to quiesce the virtual machine. (156)

amutto
Level 4

Hi Everyone !!

We have a problem trying to backup a VM with Windows 7 64b.

This is the job detail:

**********************************************************

...

19/09/2017 14:37:41 - snapshot backup of client pm5081.afg.corp using method VMware_v2
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - VMware error received: An error occurred while saving the snapshot: Failed to quiesce the virtual machine.
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - 
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - 
19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - snapshot processing failed, status 156

19/09/2017 14:41:34 - Critical bpbrm (pid=6160) from client pm5081.afg.corp: FTL - snapshot creation failed, status 156

19/09/2017 14:41:34 - Warning bpbrm (pid=6160) from client pm5081.afg.corp: WRN - ALL_LOCAL_DRIVES is not frozen
19/09/2017 14:41:34 - Info bpfis (pid=9332) done. status: 156

19/09/2017 14:41:34 - end VMware: Create Snapshot; elapsed time 0:03:59
19/09/2017 14:41:34 - Info bpfis (pid=9332) done. status: 156: snapshot error encountered
19/09/2017 14:41:34 - end writing
Operation Status: 156

***************************************************************************

 

ESX /vCenter version: Version 6.0.0 Build 2559277

Applications are running on this VM: Siemens App like SIMATIC app; SEP antivirus and no other special soft.

No RDM disks on the VM; I can take a snapshot from vSphere client without errors 

VM logs while snapshot attempted during backup show: An error occurred while taking a snapshot: Failed to quiesce the virtual machine.

 

So, could you please help me on this issue?

Thanks

Ale

4 REPLIES 4

eduncan
Level 5
Employee

Per your error:

An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

So you can either disable Quiesce in the VMware Policy?  Or address why the quiesce is failing in the VM.

In the Event Logs there maybe an error in the VM about VSS that needs to be addressed.

sclind
Moderator
Moderator
   VIP   

We get status 156's all the time. I have a script that stop/starts these 3 services and then resubmits the backup:

sc.exe \\$my_host stop VSS
sc.exe \\$my_host stop VMTools
sc.exe \\$my_host stop vmvss

sc.exe \\$my_host start vmvss
sc.exe \\$my_host start VMTools
sc.exe \\$my_host start VSS

 

That solves 99% of my status 156 errors.

Hi eduncan, 

I don't have any errors on VM Event Log. On the other hand I found that on Veritas forum : 

***********************************************************

Without quiescing file activity, data consistency in the snapshot cannot be guaranteed. If not consistent, the backed up data may be of little or no value.
If this option is disabled, the snapshot is created without quiescing I/O
on the virtual machine. In this case, you must perform your own checks for data consistency in the backup data.
Caution: Symantec does not recommend that you disable quiesce. In most case, this option should be enabled.
 

**********************************************************

So, I don't want to take a risk. I will continue investigating where the problem is.

Thanks !

Ale

Thanks sclind, I tried twice and the problem go on. it seems that's not my case. 

Thanks !!