X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=vzdump.adoc;h=2939cbed8936d83303dedfb0b0eb4e16f8e35658;hp=d9ccfe6adc4c45cfef8864217d02c5a0a99cc8d3;hb=63f956c8fad04141b71dd1330bcb06f6395b977d;hpb=d083d3d384304e74892ad5d6907c8eb9f1444fb8

diff --git a/vzdump.adoc b/vzdump.adoc
index d9ccfe6..2939cbe 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -64,7 +64,8 @@ not require that the underlying storage supports snapshots.
 
 `stop` mode::
 
-Stop the guest during backup. This results in a very long downtime.
+Stop the container for the duration of the backup. This potentially results in
+a very long downtime.
 
 `suspend` mode::
 
@@ -77,20 +78,29 @@ 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.
+Use of a local `tmpdir` is also required if you want to backup a local container
+using ACLs in suspend mode if the backup storage is an NFS server.
 
 `snapshot` mode::
 
 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.
+storage. First, the container will be suspended to ensure data consistency.
+A temporary snapshot of the container's volumes will be made and the
+snapshot content will be archived in a tar file. Finally, the temporary
+snapshot is deleted again.
+
+NOTE: `snapshot` mode requires that all backed up volumes are on a storage that
+supports snapshots. Using the `backup=no` mountpoint option individual volumes
+can be excluded from the backup (and thus this requirement).
+
+NOTE: bind and device mountpoints are skipped during backup operations, like
+volume mountpoints with the backup option disabled.
 
 
 Backup File Names
 -----------------
 
-Newer versions of vzdump encode the virtual machine type and the
+Newer versions of vzdump encode the guest type and the
 backup time into the filename, for example
 
  vzdump-lxc-105-2009_10_09-11_04_43.tar
@@ -121,7 +131,9 @@ format:
  OPTION: value
 
 Blank lines in the file are ignored, and lines starting with a '#'
-character are treated as comments and are also ignored.
+character are treated as comments and are also ignored. Values from
+this file are used as default, and can be overwritten on the command
+line.
 
 We currently support the following options:
 
@@ -147,29 +159,30 @@ directory ('vzdump-hook-script.pl').
 File Exclusions
 ---------------
 
-First, this option is only available for container backups. 'vzdump'
-skips the following files with option `--stdexcludes`
+NOTE: this option is only available for container backups.
+
+'vzdump' skips the following files by default (disable with the option
+`--stdexcludes 0`)
 
- /var/log/?*
  /tmp/?*
  /var/tmp/?*
  /var/run/?*pid
 
-Or you can manually specify exclude paths, for example:
+You can also manually specify (additional) exclude paths, for example:
 
  # vzdump 777 --exclude-path /tmp/ --exclude-path '/var/foo*'
 
 (only excludes tmp directories)
 
 Configuration files are also stored inside the backup archive
-(`/etc/vzdump/`), and will be correctly restored.
+(in `./etc/vzdump/`) and will be correctly restored.
 
 Examples
 --------
 
 Simply dump guest 777 - no snapshot, just archive the guest private area and
 configuration files to the default dump directory (usually
-'/var/liv//vz/dump/').
+'/var/lib/vz/dump/').
 
  # vzdump 777
 
@@ -181,7 +194,7 @@ Backup all guest systems and send notification mails to root and admin.
 
  # vzdump --all --mode suspend --mailto root --mailto admin
 
-Use snapshot mode (no downtime).
+Use snapshot mode (no downtime) and non-default dump directory.
 
  # vzdump 777 --dumpdir /mnt/backup --mode snapshot