Skip to main content

Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

 

Hi Everyone,

I am here back with another issue.

If anyone is getting error taking backup snapshot of a virtual machine and getting the below error.

Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine.

Apr 28, 2021 2:22:55 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - vSphere_freeze: Snapshot task for virtual machine XXX-YYY (/vmmor/vm-341) failed, 0 retries remaining, error type: 263, error message: An error occurred while saving the snapshot: Failed to quiesce the virtual machine..
Apr 28, 2021 2:23:08 AM - Critical bpbrm (pid=15849) from client XXXX: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
Apr 28, 2021 2:23:09 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - 
Apr 28, 2021 2:23:09 AM - Critical bpbrm (pid=15849) from client XXXXXX: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
Apr 28, 2021 2:23:09 AM - Critical bpbrm (pid=15849) from client XXXXXX: FTL - 
Apr 28, 2021 2:23:09 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - snapshot processing failed, status 156
Apr 28, 2021 2:23:09 AM - Critical bpbrm (pid=15849) from client XXXXX: FTL - snapshot creation failed, status 156




Please follow the below steps and restart the VMware tools in the vm.

Open the below path

C:\ProgramData\VMware\VMware Tools\

you will find a file called  Tools.Config.Example

Copy the same file and paste it in the same location and rename the file to tools.conf

if you save it you will get a new Config file.

now open the file and look for the below statement.

[vmbackup]

#vss.disableAppQuiescing = true

If its False make it true and if the statement is not there then add the above the statement and save the file.

Once the file is saved go to Services.msc and restart the VMware tools service and now initiate the backup and it must completed without error.




Comments

Post a Comment

Popular posts from this blog

  PowerShell DSC log amount issue on operating system drive Overview Problem Impact Microsoft Ticket (Workaround) solution References Overview When using PowerShell DSC on a configured system in some (seldom) cases it can lead to log amount issues in a specific folder. The following folder grows (over time) so several GB size holding hundreds and thousands of JSON log files as visible in the following screenshot: Also sometimes it looks like this: Problem The problem is (but must not be) related to DSC configuration issues as far as it could be analyzed. The log folder „Configuration Status“ is filled with sometimes up to 7 Megabyte sized JSON files. This log folder (based on our analysis) is used for sending reports to report server but is not cleaned up automatically. Impact Some PowerShell DSC managed systems need extensive disk space due to log directory grown to 40 Gigabyte plus. This causes an alert in disk space / availability monitoring and could in some cases lead to non w...
Post a Comment
Read more

System Volume Information is taking more space

On one of the servers (running Windows Server 2012 R2) I faced a problem with the lack of free space on a system drive. I have cleared all resource-consuming locations ( WinSxS , TEMP directories, user profiles,  outdated updates , etc.), but it didn’t have any evident effect. At last, I have found that a large part of a system disk has been occupied by  System Volume Information  folder. Let’s consider why we need System Volume Information folder in Windows systems, what is stored in it and how to clean up it. Note . The instructions given in this article are applicable to other Windows versions as well:   Windows 10, Windows 7, Windows 8, Windows 2008 R2, Windows 2012 / 2012 R2. System Volume Information  folder is in the root of each disk. System data related to system recovery and Shadow Copy Service are stored in it. By default it is hidden and only the SYSTEM has access to it. Even the administrator cannot open it and look through the contents of th...
Post a Comment
Read more