Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-10-18 07:33:10 +03:00
Code Releases Activity

qm: document when fs-freeze is issued for VMs

Browse Source 
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Link: https://lore.proxmox.com/20250814144602.423927-1-m.sandoval@proxmox.com
[FE: minor language improvements]
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
This commit is contained in:
Maximiliano Sandoval
2025-08-14 16:45:53 +02:00
committed by Fiona Ebner
parent 74a80c343f
commit f1f9faa14b
1 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
qm.adoc
View File

@@ -1506,11 +1506,20 @@ run as expected. Subsequent ones, until the next reboot, will only consider
parts of the filesystem that changed since then.
[[qm_qga_fsfreeze]]
Filesystem Freeze & Thaw on Backup
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Filesystem Freeze & Thaw
^^^^^^^^^^^^^^^^^^^^^^^^
By default, guest filesystems are synced via the 'fs-freeze' QEMU Guest Agent
Command when a backup is performed, to provide consistency.
By default, if the QEMU Guest Agent is enabled in the guest's config and if the
agent is available inside of the guest, then the virtual machine's filesystems
are synced via the 'fs-freeze' QEMU Guest Agent command when certain operations
are performed. This is done to provide data consistency.
An 'fs-freeze' will be issued for any of the following operations on a VM:
* Performing a backup in snapshot mode
* Creating a clone of a VM while it is running
* Replicating a VM while it is running
* Taking a snapshot without RAM of a running VM
On Windows guests, some applications might handle consistent backups themselves
by hooking into the Windows VSS (Volume Shadow Copy Service) layer, a