This website use cookies to help you have a superior and more admissible browsing experience on the website.
Share This Article：
If you’ve ever taken a VMware snapshot using the vSphere Client, you’ve probably noticed that tiny checkbox: “Quiesce guest file system”. If you need your VM backups work when disaster strikes, it is necessary to understand what this checkbox means.
In this guide, we will explain what it means and whether you really need it.
What does “Quiesce guest file system” mean?
“Quiescing a file system” is the process of placing the data on a virtual disk into a state that is suitable for backups. It involves coordinating with the operating system and applications to flush dirty buffers out of memory and momentarily pause write operations so that every bit of data on disk makes sense.
When creating a VM snapshot, there are generally two types of VM snapshots you can take:
- Memory State Snapshots: These capture the VM’s RAM and CPU state, so you can revert to a precise running state later. Great for testing patches, terrible for backups because they do nothing to guarantee data consistency.
- Quiesced Snapshots (also called VSS‑aware snapshots): When you check the “quiesce guest file system” box and uncheck “Include virtual machine’s memory”, VMware uses special tools inside the guest to create a crash‑consistent file system state at minimum, and application‑consistent state when configured correctly. This is the only snapshot type that should ever serve as the basis for a reliable backup.
Note:
- File‑System Consistency: The file system metadata and write operations are flushed to disk. No NTFS or ext4 corruption. This happens when VSS simply freezes the file system if no application writers are active. For Windows Server 2008 and later, VSS snapshots can be file-system or application-consistent depending on the VM platform and state.
- Application Consistency: Databases, email servers, and other VSS‑aware applications temporarily suspend their work, commit pending transactions, and then inform the OS that they’re ready. This is achieved through VSS Writers, and it’s the gold standard for backup.
Thus, when you see the checkbox “quiesce guest file system”, what you’re really telling vCenter is: “Please use VMware Tools and Microsoft VSS inside the guest to quiesce all I/O and make this snapshot application‑consistent.”
How VMware Quiescing Uses VSS
For Windows virtual machines, the quiesce guest file system mechanism relies on a tight collaboration between three components:
- VMware Tools — specifically the VMware VSS component installed in the guest. This component is automatically installed when you install VMware Tools on Windows virtual machines.
- Microsoft Volume Shadow Copy Service (VSS) — a framework that coordinates backup operations.
- VSS Writers — application‑specific components (SQL Writer, Exchange Writer, Active Directory Writer, Hyper‑V Writer, etc.) that know how to gracefully pause and flush those applications.
Here is the step‑by‑step flow that occurs the moment you click “Create” for a quiesced snapshot:
1. vCenter sends the instruction to the ESXi host. The host contacts the VMware Tools running inside the guest OS.
2. VMware Tools initiates a VSS snapshot request inside the guest. It asks the Volume Shadow Copy Service to begin a backup sequence.
3. VSS signals all registered VSS Writers to enter the “PrepareForBackup” state. Each Writer instructs its application: “finish critical transactions, write in‑memory data to disk, and then quiet down.”
4. After the writers report readiness, VSS tells the file system to hold all new I/O requests for a few seconds (the freeze window).
5. Windows flushes every remaining dirty buffer to disk. The file system is now completely consistent.
6. The VMware VSS component signals back to ESXi: “The guest is quiesced and ready.”
7. ESXi takes the virtual disk snapshot. The entire process typically completes within seconds, unless the I/O freeze times out.
8. Once the snapshot is created, VSS thaws the file system, and applications resume normal operations.
⚠️ Critical detail administrators often miss: If VSS quiescing fails inside the guest (for example, a VSS Writer rejects the request), VMware may silently fall back to a non‑quiesced, crash‑consistent snapshot and generate only a warning. This means vCenter reports “success,” but the snapshot is not application‑consistent. Always verify from inside the guest.
It’s also worth noting that a VMware VSS quiesced snapshot reports as VSS_BT_COPY to VSS, meaning no automatic log truncation occurs for applications like SQL Server or Exchange. If you need log truncation after backup, you must use an enterprise backup solution that explicitly supports it.
On the Linux side, quiescing works differently because there is no native VSS equivalent. With a modern Linux distribution and VMware Tools, the system driver uses the FIFREEZE / FITHAW ioctl calls to freeze the file system before the snapshot. This option is available only with kernel versions newer than 2.6.32 on Linux VMs running VMware Tools 5.x or higher (vSphere 5.0 and later).
If custom applications need to be quiesced, VMware Tools can also execute pre‑freeze and post‑thaw scripts. These scripts must be placed in /etc/vmware-tools/backupScripts.d and must be able to handle freeze, freezeFail, and thaw arguments. VMware Tools version 10.2 or higher is required for this functionality.
This entire mechanism explains why quiescing is not just “ticking a box” — it’s a complex orchestration that completely transforms the snapshot into a recovery‑safe artifact.
When to Quiesce and When Not To
Not every VM needs a quiesced snapshot. Overusing it on the wrong workload can cause I/O penalties.
► When you need to use “Quiesce guest file system”:
- Virtual machines running databases (SQL Server, Oracle, MySQL, PostgreSQL) that require transaction‑level consistency.
- Domain controllers (Active Directory) — to prevent USN rollback and authentication issues upon restore.
- Email servers (Exchange) where log truncation and consistency matter.
- Any application that has a VSS Writer and cannot tolerate crash‑consistent recovery.
- When your backup solution explicitly triggers an application‑aware, quiesced snapshot for the VM.
► When it’s safe to skip quiescing (crash‑consistent is acceptable):
- Non‑critical web servers or static file servers with no active database.
- Linux VMs where you have no custom freeze scripts and only file‑system consistency is required. (Note: Without custom scripts, Linux quiescing provides only file‑system consistency via the sync driver.)
- VMs that are protected by an alternative agent‑based backup that handles application consistency inside the guest.
- Long‑running snapshots that serve only as a temporary safety net before a risky patch (and you accept the recovery risk).
► Critical pitfalls to keep in mind:
- Quiescing briefly pauses I/O. For ultra‑latency‑sensitive systems, test the impact during maintenance windows first.
- Dynamic disks in Windows are not supported for VSS quiescing; snapshots will fall back to file‑system consistency.
- VMware snapshots themselves are not backups. A quiesced snapshot is a point‑in‑time foundation, but you must still copy the data to a separate backup repository using a backup application.
- Large snapshot chains can cause time drift inside the VM. If your app relies on real‑time clock accuracy, monitor this.
- VMware VSS snapshots report as VSS_BT_COPY, meaning no automatic log truncation. If your backup strategy relies on truncating SQL or Exchange logs after backup, you must use a backup application that supports this explicitly.
How to Quiesce Guest File System during Snapshot Creation in VMware
- Prerequisites:✎…
- VMware Tools must be installed and up‑to‑date in the VM. (The VM’s status should show “Running” and “VMware Tools: OK”.)
- Make sure the guest OS supports VSS (Windows Server 2003 and later, modern Windows editions) or for Linux file‑system freeze.
- Enough free disk space on the datastore to accommodate the snapshot delta files (typically 20% or more).
- Avoid performing quiesced snapshots during periods of extremely high I/O if possible, as freeze timeouts can occur.
- For Windows guests using application consistency, ensure the Volume Shadow Copy Service is set to Manual or Automatic and that no third‑party VSS providers are conflicting.
Step-by-step Quiesced Snapshot Procedure
Step 1. Right‑click the running virtual machine and select “Snapshots” > “Take Snapshot”.
Step 2. Enter a name and description (e.g., “Pre‑patch quiesced snapshot”).
Step 3. Uncheck the box labeled “Include virtual machine’s memory”. A memory snapshot is incompatible with true application‑consistent quiescing for backup purposes.
Step 4. Check the box “Quiesce guest file system (requires VMware Tools installed)”.
Step 5. Click “Create”.
Step 6. Monitor the recent tasks pane. A successful snapshot will appear.
Verify that quiescing worked
Just because vCenter reports “Snapshot creation completed” doesn’t automatically mean the application‑level quiesce worked perfectly. VMware may fall back to a file‑system‑consistent snapshot silently if VSS fails inside the guest. Here is how to verify.
1. Check for vss_manifests.zip
Browse the VM folder on the datastore. If the quiesce process engaged VSS successfully, you should find a file named vss_manifests.zip generated at the time of the snapshot. Inside that zip is backup.xml, which contains the metadata of all the VSS Writers that participated. If this file is absent or backup.xml is incomplete, the VSS quiescing did not fully initialize.
2. Review Guest Event Viewer Logs
Open Event Viewer in the Windows guest and navigate to Windows Logs > Application. Look for VSS events around the snapshot timestamp. You want to see information entries from source “VSS” stating that writers are stable. Errors like “VSS writer rejected the request” or timeout‑related entries immediately indicate a problem.
3. Monitor VSS Admin State
Before taking critical snapshots, run vssadmin list writers inside the guest. All writers should be in the “Stable” state with no errors. If a writer reports “Failed” or “Waiting for completion”, your quiesced snapshot will likely miss that application’s consistency.
Always validate from within the guest, not just from the vSphere UI.
Beware of the “false success” scenario: vCenter may report success, yet the snapshot is only file‑system‑consistent because the VMware VSS component silently fell back to a non‑VSS freeze. This often happens when the VM’s .vmx file contains disk.EnableUUID = "TRUE" — a parameter known to prevent VSS from reading disk UUIDs on Windows VMs and to entirely break quiescing on Linux VMs.
Troubleshooting Common Quiesce Guest File System Failures
Whenever the quiescing operation fails, something has to give — usually with a clear error message. Here are the most frequent nightmares and how to fix them:
1. “Snapshot operation exceeded the time limit for holding off I/O”
Root Cause: The I/O freeze window (typically 20 seconds) expired before the snapshot was created. This happens when the VM is under extreme disk load, when VSS writers take too long to respond, or when the VM’s disks are on extremely slow storage.
Fix: Reschedule the backup or snapshot during low‑I/O windows. Increase VM disk resources if possible. Ensure the guest has sufficient free RAM and disk space, as excessive paging can slow the flush. Update VMware Tools to the latest version, which often includes VSS timeout improvements.
2. “VssSyncStart operation failed: IDispatch error #8449”
Root Cause: This cryptic error means the VSS coordinator couldn’t start the sync because a required VSS Writer is in a bad state or a third‑party backup agent (like a legacy backup client) has hijacked the VSS Provider. Broadcom KB 394014 confirms this issue typically arises due to conflicts or problems with the application hosting the VSS writer, or misconfigurations within the writer’s environment.
Fix: Open the guest OS and run vssadmin list writers to identify any writer with errors. Common culprits are SQL Writer or Exchange Writer stuck in a non‑retryable state. Reboot the guest or restart the relevant application services. If the problem persists, uninstall and reinstall VMware Tools, ensuring the VMware VSS component is explicitly enabled during the custom installation. Also check disk space and VSS service status.
3. The disk.EnableUUID Trap
Symptom: Quiescing fails with errors, or appears to succeed but the generated backup is only file‑system‑consistent with no vss_manifests.zip.
Root Cause: The disk.EnableUUID parameter in the VM’s .vmx file controls whether the virtual disk presents a UUID to the guest OS — a requirement for application‑level VSS quiescing on Windows Server 2008 and later. The behavior differs by OS:
- On Windows VMs: VSS requires disk UUIDs to be enabled for application‑consistent snapshots.VMs created on vSphere 4.1 or later have disk.EnableUUID enabled by default.If the parameter is missing or set to FALSE, VMware falls back to file‑system‑consistent quiescing only.If set to TRUE but VSS still fails, the problem may be that VSS cannot read the disk UUID — a scenario documented in Broadcom KB articles.
- On Linux VMs: Setting disk.EnableUUID = TRUE is a known cause of quiescing failure. Broadcom KB 341553 documents that snapshot quiescing fails in Linux guests when this parameter is set to TRUE.
Fix:
- For Windows VMs requiring application consistency, ensure disk.EnableUUID is set to TRUE (the default for VMs created on modern vSphere versions). If quiescing fails despite this, investigate the VSS writer state inside the guest.
- For Linux VMs, ensure the disk.EnableUUID is set to FALSE or remove the parameter entirely to avoid quiescing failures.
To check or modify: Edit VM settings > VM Options > Advanced > Configuration Parameters, locate or add a disk.EnableUUID. A reboot is required for changes to take effect.
4. VMware VSS Component Not Properly Installed
Symptom: The “Quiesce” checkbox stays greyed out, or snapshots fail without any VSS error in the guest.
Fix: Perform a full “Modify” installation of VMware Tools, and ensure the VMware VSS component is selected (it is checked by default but can be accidentally disabled). If necessary, remove and reinstall VMware Tools completely.
Quiescing in Modern Backup Solution
Guest file system quiescing is a native VMware feature, but enterprise backup products have built on top of it to provide even smarter consistency. Solutions like Info2Soft’s i2Backup integrate application‑aware processing that leverages the same VSS mechanism. However, they go further by allowing:
- Log truncation: After a successful quiesced snapshot, the backup software can instruct Exchange or SQL Server to truncate transaction logs, freeing up guest disk space.
- Indexing and granular recovery: A quiesced snapshot with VSS metadata enables restoring a single table from a database without restoring the entire VM.
In addition, i2Backup supports many other features to meet various backup needs.
- Backup scheduling: i2Backup runs backup tasks based on preset backup types (full, incremental, and differential) and backup intervals (hourly, daily, weekly, monthly, etc.).
- Scalable Backup: Supports the horizontal scaling of backup nodes to meet rapidly growing backup requirements.
- Instant Recovery: Mount the VMware backup quickly and make it usable. So you don’t need to wait for full data recovery for a long time.
- High-level Security: Support encrypted backup with the AES-256 standard algorithm to ensure data security. Support immutable backup to prevent backup from being changed or deleted by ransomware.
You can click the button below to request a 60-day free trial of i2Backup:
Conclusion
Without quiescing the guest file system, a VMware snapshot captures in‑flight writes and uncommitted transactions, leaving databases and Active Directory vulnerable to silent corruption on restore. Quiescing ensures your snapshots are application‑consistent, so domain controllers, SQL Servers, and Exchange can be recovered exactly as they were, with no post‑recovery repair needed.
But a manual quiesced snapshot is not a true backup. To fully protect your virtual machines, you need a professional VMware backup solution – Info2Soft’s i2Backup. It automates application‑aware quiescing, moves backup copies off‑site, manages retention, and enables granular recovery.
{{ author_info.name }}
{{author_info.introduction || "No brief introduction for now"}}
More Related Articles
Table of Contents:
Stay Updated on Latest Tips
Subscribe to our newsletter for the latest insights, news, exclusive content. You can unsubscribe at any time.
Ready to Enhance Business Data Security?
Start a 60-day free trial or view demo to see how Info2Soft protects enterprise data.
Please fill out the form and submit it, our customer service representative will contact you soon.
By submitting this form, I confirm that I have read and agree to the Privacy Notice.
