vzdump.adoc: use continuations

[pve-docs.git] / vzdump.adoc

diff --git a/vzdump.adoc b/vzdump.adoc
index 7137a5a91f8529099f75d17a401a9a74431d4047..67ce1f3f2a35f479d66c229070614b7882d77fa8 100644 (file)
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -25,7 +25,7 @@ Backup and Restore
 include::attributes.txt[]
 endif::manvolnum[]
 
-'vzdump' is an utility to make consistent snapshots of running virtual
+'vzdump' is a utility to make consistent snapshots of running virtual
 machines (VMs). It basically creates an archive of the VM private
 area, which also includes the VM configuration files. 'vzdump'
 currently supports LXC containers and QemuServer VMs.
@@ -38,23 +38,30 @@ Stop the VM during backup. This results in a very long downtime.
 
 `suspend` mode::
 
-For containers, this mode uses rsync to copy the VM to a temporary
-location (see option `--tmpdir`). Then the VM is suspended and a second
-rsync copies changed files. After that, the VM is started (resume)
-again. This results in a minimal downtime, but needs additional space
-to hold the VM copy.
-
+For containers, this mode uses rsync to copy the container data to a temporary
+location (see option `--tmpdir`). Then the container is suspended and a second
+rsync copies changed files. After that, the container is started (resumed)
+again. This results in minimal downtime, but needs additional space
+to hold the container copy.
++
+When the container is on a local filesystem and the target storage of the backup
+is an NFS server, you should set `--tmpdir` to reside on a local filesystem too,
+as this will result in a many fold performance improvement.
+Use of a local `tmpdir` is also required if you want to backup in `suspend`
+mode a local container using ACLs to an NFS server.
++
 For QemuServer, this mode will suspend the VM, start
-a live backup, and resume the VM.
+a live backup, and resume the VM. This does not require a temporary
+storage.
 
 `snapshot` mode::
 
 For containers, this mode uses the snapshotting facilities of the
 underlying storage. A snapshot will be made of the container volume,
 and the snapshot content will be archived in a tar file.
-
++
 For QemuServer, this mode will do a live backup similar to the
-`snaphost` mode, but without suspending/resuming the VM.
+`suspend` mode, but without suspending/resuming the VM.
 
 A technical overview of the Proxmox VE live backup for QemuServer can
 be found online
@@ -63,14 +70,14 @@ https://git.proxmox.com/?p=pve-qemu-kvm.git;a=blob;f=backup.txt[here],
 Backup File Names
 -----------------
 
-Newer version of vzdump encodes the virtual machine type and the
+Newer versions of vzdump encode the virtual machine type and the
 backup time into the filename, for example
 
  vzdump-lxc-105-2009_10_09-11_04_43.tar
 
-That way it is possible to store several backup into the same
+That way it is possible to store several backup in the same
 directory. The parameter `maxfiles` can be used to specify the
-maximal number of backups to keep.
+maximum number of backups to keep.
 
 Restore
 -------
@@ -78,7 +85,7 @@ Restore
 The resulting archive files can be restored with the following programs.
 
 
-`pct restore`:: Containers restore utility
+`pct restore`:: Container restore utility
 
 `qmrestore`:: QemuServer restore utility
 
@@ -116,14 +123,14 @@ File Exclusions
 First, this option is only available for container backups. 'vzdump'
 skips the following files with option `--stdexcludes`
 
- /var/log/.+
- /tmp/.+
- /var/tmp/.+
- /var/run/.+pid
+ /var/log/?*
+ /tmp/?*
+ /var/tmp/?*
+ /var/run/?*pid
 
 Or you can manually specify exclude paths, for example:
 
- # vzdump 777 --exclude-path '/tmp/.+' --exclude-path '/var/tmp/.+'
+ # vzdump 777 --exclude-path /tmp/ --exclude-path '/var/foo*'
 
 (only excludes tmp directories)
 
@@ -139,7 +146,7 @@ configuration files to the default dump directory (usually
 
  # vzdump 777
 
-Use rsync and suspend/resume to create an snapshot (minimal downtime).
+Use rsync and suspend/resume to create a snapshot (minimal downtime).
 
  # vzdump 777 --mode suspend