4 include::attributes.txt[]
9 vzdump - Backup Utility for VMs and Containers
15 include::vzdump.1-synopsis.adoc[]
25 include::attributes.txt[]
28 'vzdump' is a utility to make consistent backups of running guest
29 systems. It basically creates an archive of the guest private area,
30 which also includes the guest configuration files. 'vzdump' currently
31 supports LXC containers and QemuServer VMs. There are several ways to
32 provide consistency (option `mode`), depending on the guest type.
34 .Backup `mode` for VMs:
38 This first performns a clean shutdown of the VM to make sure it is
39 stopped. It then starts the VM in suspended mode and uses the qemu
40 backup feature to dump all data. If the VM was running, we start
41 (resume) it immediately after starting the qemu backup task. This
42 keeps the downtime as low as possible.
46 This mode does not really make sense for qemu. Please use snapshot
51 This mode simply starts a qemu live backup task. If the guest agent
52 is enabled (`agent: 1`) and running, it calls 'guest-fsfreeze-freeze'
53 and 'guest-fsfreeze-thaw' to improve consistency.
55 A technical overview of the Proxmox VE live backup for QemuServer can
57 https://git.proxmox.com/?p=pve-qemu-kvm.git;a=blob;f=backup.txt[here].
59 NOTE: Qemu backup provides snapshots on any storage type. It does
60 not require that the underlying storage supports snapshots.
63 .Backup `mode` for Containers:
67 Stop the container for the duration of the backup. This potentially results in
72 This mode uses rsync to copy the container data to a temporary
73 location (see option `--tmpdir`). Then the container is suspended and a second
74 rsync copies changed files. After that, the container is started (resumed)
75 again. This results in minimal downtime, but needs additional space
76 to hold the container copy.
78 When the container is on a local filesystem and the target storage of the backup
79 is an NFS server, you should set `--tmpdir` to reside on a local filesystem too,
80 as this will result in a many fold performance improvement.
81 Use of a local `tmpdir` is also required if you want to backup a local container
82 using ACLs in suspend mode if the backup storage is an NFS server.
86 This mode uses the snapshotting facilities of the underlying
87 storage. First, the container will be suspended to ensure data consistency.
88 A temporary snapshot of the container's volumes will be made and the
89 snapshot content will be archived in a tar file. Finally, the temporary
90 snapshot is deleted again.
92 NOTE: `snapshot` mode requires that all backed up volumes are on a storage that
93 supports snapshots. Using the `backup=no` mountpoint option individual volumes
94 can be excluded from the backup (and thus this requirement).
100 Newer versions of vzdump encode the guest type and the
101 backup time into the filename, for example
103 vzdump-lxc-105-2009_10_09-11_04_43.tar
105 That way it is possible to store several backup in the same
106 directory. The parameter `maxfiles` can be used to specify the
107 maximum number of backups to keep.
112 The resulting archive files can be restored with the following programs.
115 `pct restore`:: Container restore utility
117 `qmrestore`:: QemuServer restore utility
119 For details see the corresponding manual pages.
124 Global configuration is stored in '/etc/vzdump.conf'. The file uses a
125 simple colon separated key/value format. Each line has the following
130 Blank lines in the file are ignored, and lines starting with a '#'
131 character are treated as comments and are also ignored. Values from
132 this file are used as default, and can be overwritten on the command
135 We currently support the following options:
137 include::vzdump.conf.5-opts.adoc[]
140 .Example 'vzdump.conf' Configuration
142 tmpdir: /mnt/fast_local_disk
143 storage: my_backup_storage
151 You can specify a hook script with option `--script`. This script is
152 called at various phases of the backup process, with parameters
153 accordingly set. You can find an example in the documentation
154 directory ('vzdump-hook-script.pl').
159 NOTE: this option is only available for container backups.
161 'vzdump' skips the following files by default (disable with the option
169 You can also manually specify (additional) exclude paths, for example:
171 # vzdump 777 --exclude-path /tmp/ --exclude-path '/var/foo*'
173 (only excludes tmp directories)
175 Configuration files are also stored inside the backup archive
176 (in `./etc/vzdump/`) and will be correctly restored.
181 Simply dump guest 777 - no snapshot, just archive the guest private area and
182 configuration files to the default dump directory (usually
183 '/var/lib/vz/dump/').
187 Use rsync and suspend/resume to create a snapshot (minimal downtime).
189 # vzdump 777 --mode suspend
191 Backup all guest systems and send notification mails to root and admin.
193 # vzdump --all --mode suspend --mailto root --mailto admin
195 Use snapshot mode (no downtime) and non-default dump directory.
197 # vzdump 777 --dumpdir /mnt/backup --mode snapshot
199 Backup more than one guest (selectively)
201 # vzdump 101 102 103 --mailto root
203 Backup all guests excluding 101 and 102
205 # vzdump --mode suspend --exclude 101,102
207 Restore a container to a new CT 600
209 # pct restore 600 /mnt/backup/vzdump-lxc-777.tar
211 Restore a QemuServer VM to VM 601
213 # qmrestore /mnt/backup/vzdump-qemu-888.vma 601
215 Clone an existing container 101 to a new container 300 with a 4GB root
216 file system, using pipes
218 # vzdump 101 --stdout | pct restore --rootfs 4 300 -
222 include::pve-copyright.adoc[]