vzdump.adoc: use continuations

[pve-docs.git] / vzdump.adoc

diff --git a/vzdump.adoc b/vzdump.adoc
index fc4246807b900fc5dd51aaa1ead6ab81b867a9a7..67ce1f3f2a35f479d66c229070614b7882d77fa8 100644 (file)
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -38,21 +38,28 @@ Stop the VM during backup. This results in a very long downtime.
 
 `suspend` mode::
 
-For containers, this mode uses rsync to copy the VM data 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 (resumed)
+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 VM copy.
-
+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
 `suspend` mode, but without suspending/resuming the VM.