ifdef::manvolnum[]
vzdump(1)
=========
-include::attributes.txt[]
:pve-toplevel:
NAME
ifndef::manvolnum[]
Backup and Restore
==================
-include::attributes.txt[]
:pve-toplevel:
endif::manvolnum[]
`stop` mode::
This mode provides the highest consistency of the backup, at the cost
-of a downtime in the VM operation. It works by executing an orderly
-shutdown of the VM, and then runs a background Qemu process to backup
-the VM data. After the backup is complete, the Qemu process resumes
-the VM to full operation mode if it was previously running.
+of a short downtime in the VM operation. It works by executing an
+orderly shutdown of the VM, and then runs a background Qemu process to
+backup the VM data. After the backup is started, the VM goes to full
+operation mode if it was previously running. Consistency is guaranteed
+by using the live backup feature.
`suspend` mode::
A technical overview of the Proxmox VE live backup for QemuServer can
be found online
-https://git.proxmox.com/?p=pve-qemu-kvm.git;a=blob;f=backup.txt[here].
+https://git.proxmox.com/?p=pve-qemu.git;a=blob_plain;f=backup.txt[here].
NOTE: Proxmox VE live backup provides snapshot-like semantics on any
storage type. It does not require that the underlying storage supports
-snapshots.
+snapshots. Also please note that since the backups are done via
+a background Qemu process, a stopped VM will appear as running for a
+short amount of time while the VM disks are being read by Qemu.
+However the VM itself is not booted, only its disk(s) are read.
.Backup modes for Containers:
supports snapshots. Using the `backup=no` mount point option individual volumes
can be excluded from the backup (and thus this requirement).
-NOTE: bind and device mount points are skipped during backup operations, like
-volume mount points with the backup option disabled.
-
+// see PVE::VZDump::LXC::prepare()
+NOTE: By default additional mount points besides the Root Disk mount point are
+not included in backups. For volume mount points you can set the *Backup* option
+to include the mount point in the backup. Device and bind mounts are never
+backed up as their content is managed outside the {pve} storage library.
Backup File Names
-----------------