By Alison / Last Updated September 5, 2022

What is a quiesced snapshot

A VM snapshot preserves the state and data of a VM at a specific point in time, makes it popular as a quick failsafe measure. In VMware vSphere environment, you can create VM snapshots in 2 ways:

  • Snapshot the virtual machine’s memory
  • Quiesce guest file system (needs VMware Tools installed)

Take quiesced snapshot

Quiesced virtual machine snapshot ensures that the guest file system is in a file-system and application consistent state for backup purposes. It can avoid inconsistent issue of SQL Server, Active Directory, and other applications.

Sometimes you may find yourself failed to quiesce the virtual machine, for example, cannot take a quiesced snapshot of Windows 2008 R2 virtual machine. In this article, I will analyze the reason why this error happens and how to fix failed to quiesce the virtual machine snapshot error.

Why it failed to quiesce the virtual machine

If you encounter a “Failed to quiesce the virtual machine” error while creating a quiesced snapshot or cloning your VM, there are plenty reasons that can cause you unable to quiesce guest file system during snapshot creation. For example:

  • The VMware Tools installed on the VM is not the latest version.
  • The Microsoft VSS is not installed in non-interactive mode.
  • The VMware Snapshot Provider service is not synchronizing with the Microsoft VSS providers.
  • Creating a quiesced snapshot on a virtual machine that does not have free space.
  • Installing a third-party backup agent inside the virtual machine without rebooting it.
  • The I/O in the virtual machine is high and the quiescing operation is unable to flush all the data to disk.
  • The VM has a GPT disk without an MSR (Microsoft Reserved) partition.

In this article, I will introduce how to troubleshooting and fix error Failed to quiesce the virtual machine snapshot.

Failed to quiesce the virtual machine

How to fix error “Failed to quiesce the virtual machine”

Since there are many reasons that can cause the “Failed to quiesce the virtual machine” error, the ways to solve it varies. In this section, I will introduce how to fix this error in different situations.

Before all of this, you need to perform the standard troubleshooting process, referring to VMware’s official documentation: Troubleshooting Volume Shadow Copy (VSS) quiesce related issues (1007696)

If the snapshot operation exceeded the time limit for holding off I/O in frozen VM

If you failed to take a quiesced virtual machine snapshot and the error reports:

"Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine"

Snapshot operation exceeded the time limit for holding off I/O

This occurs when you try to create a quiesced snapshot on a VM that does not have free space, or the I/O in the VM is high and the quiescing operation is unable to flush all the data to disk, while further I/O is created.

To solve this issue, try the following steps after troubleshooting:

1. Make sure that all virtual machine drives have enough free space.

2. Reduce the amount of ongoing I/O to the virtual machine.

If you cannot take a quiesced snapshot of Windows 2008 R2 virtual machine

If you cannot take a quiesced snapshot of Windows 2008 R2 virtual machine, and received the Volume Shadow Copy Service error: Unexpected error calling routine IOCTL_DISK_SET_SNAPSHOT_INFO(\\.\PHYSICALDRIVE1) fails with winerror 1168. hr = 0x80070490, Element not found.

This issue occurs because the VM has a GPT disk without an MSR (Microsoft Reserved) partition. VMware Snapshot Provider works under Microsoft VSS framework. The Microsoft VSS framework will send the IOCTL IOCTL_DISK_SET_SNAPSHOT_INFO to the disks. If the disk is a GPT disk without a MSR partition, the IOCTL would fail and whole VSS process fails.

To solve this issue, you can add a new GPT disk with an MSR, and migrate the data to the new disk, or shrink the volume by the default MSR size of 32MB or 128MB.

Extended thinking: is it necessary to backup virtual machine?

Although convenient as a quick failsafe, VM snapshot is still an unstable feature that may affect your VM performance and cannot be used as an independent backup method for restoration. Therefore, backup is still a necessary way of VM protection for enterprise. You can choose to use snapshot or backup depending on your needs.

For enterprise - level backups, it requires more efficient backups, you can only use a professional backup software to complete. So, you can try AOMEI Cyber Backup, the free virtual machine backup solution. It’s specialized in backup, and it can create backups for multiple virtual machines at the same time and schedule automatic backup tasks, as well as guarantee data security during backup and recovery.

Download FreewareVMware ESXi & Hyper-V
Secure Download

*You can choose to install this VM backup software on either Windows or Linux system.

Easy and secure procedures to create a perfect backup task

1. Click Backup Task >> Create New Task to automate a new VM backup.

create vmware backup

2. In the opened window, enter task name first and select VMware ESXi device and the virtual machines. Then select a location to store backup  files.

select backup target

3. In Schedule page, set up automatic backup task with different strategies.

schedule ESXi backup

4. (Optional) Set up Backup Cleanup policy that helps to delete unwanted backup files which save storage space. Note this funtion is available in Premium Edition.

VMware retention policy

3. Click Start Backup. You can monitor the backup status from the main screen.

backup process

The scheduled backup task will run VM backups automatically, and the backup files can be stored in local or network location and they are independent and secure from each other.

It is more convenient and safer to utilize a professional tool to protect your virtual machines. The regular backups allow you restore VM easily and fast without worrying about errors.

Summary

In this article, I summarized reasons that may cause you failed to quiesce the virtual machine snapshot, and briefly introduced 2 resolutions to solve this issue. But if you want a stable data protection insurance, VM backup may meet your needs better.