6,534
edits
Changes
no level 1 headings, better formatting; VE->CT; category tags should not be in the middle
There are several ways to provide consistency:
Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.
--restore FILENAME restore FILENAME
== Examples ==Use a running container, for example install this: [[Proxmox Mail Gateway in VEcontainer]].
=== Backup ===
Simply dump CT 777 - — no snapshot, just archive the container private area and configuration files to the default dump directory (usually <code>/vz/dump/</code>).
Use rsync and suspend/resume to create a snapshot (minimal downtime).
Backup all containers and send notification mails to root.
Use LVM2 to create snapshots (no downtime).
Note that using LVM2 and vzdump to create snapshots requires 512Mb of free space in your VG as described [http://weblogs.amtex.nl/index.php?blog=2&title=using_vzdump_snapshot_to_backup_without_downtime&more=1&c=1&tb=1&pb=1 here].
=== Restore == Restore above backup to CT 600=
== Bugs ==
vzdump will fail under Debian Etch in version 1.0-2 (tested) if it is invoked with parameter "--snapshot" and if the logical volume name contains a hyphen.
One possible workaround is to rename the logical volume in question thus it doesn't contain any hyphen.
A bug report was sent to proxmox on 02 June 2008.
[[Category: HOWTO]]