Editing Backup of a running container with vzdump

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
−
Vzdump is a utility to make consistent snapshots of running OpenVZ containers (and KVM virtual machines if you are using [http://pve.proxmox.com Proxmox VE]). It basically creates a tar archive of the container's private area, which also includes the CT configuration files.
+
Vzdump is a utility to make consistent snapshots of running OpenVZ containers (and KVM virtual machines if you are using [http://pve.proxmox.com Proxmox VE]. It basically creates a tar archive of the container's private area, which also includes the CT configuration files.
  
 
There are several ways to provide consistency:
 
There are several ways to provide consistency:
Line 10: Line 10:
  
 
== Download ==
 
== Download ==
−
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/ .
+
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://www.proxmox.com/cms_proxmox/en/technology/oss-software/openvz/
 +
 
 +
For rpm based systems:
 +
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump-1.1-1.noarch.rpm</pre>
  
 
For Debian based systems:
 
For Debian based systems:
−
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-16_all.deb</pre>
+
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_1.1-1_all.deb</pre>
−
 
 
−
 
 
−
For future versions, Proxmox will not release rpm´s, so you need to take a look at the sources. (maybe someone else can maintain vzdump rpm packages?)
 
  
 
== Installation ==
 
== Installation ==
 
For rpm based systems:
 
For rpm based systems:
−
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>
+
<pre>rpm -i vzdump-1.1-1.noarch.rpm</pre>
  
 
For Debian based systems:
 
For Debian based systems:
−
<pre>dpkg -i vzdump_1.2-16_all.deb</pre>
+
<pre>dpkg -i vzdump_1.1-1_all.deb</pre>
  
 
== Synopsis ==
 
== Synopsis ==
Line 31: Line 31:
  
 
vzdump OPTIONS [--all | <VMID>]
 
vzdump OPTIONS [--all | <VMID>]
−
       --exclude VMID          exclude VMID (assumes --all)
+
 
 +
       --exclude VPSID        exclude VPSID (assumes --all)
 
       --exclude-path REGEX    exclude certain files/directories. You
 
       --exclude-path REGEX    exclude certain files/directories. You
 
                               can use this option more than once to specify
 
                               can use this option more than once to specify
 
                               multiple exclude paths
 
                               multiple exclude paths
−
       --stdexcludes          exclude temporary files and logs
+
       --stdexcludes          exclude temorary files and logs
 
       --compress              compress dump file (gzip)
 
       --compress              compress dump file (gzip)
−
      --storage STORAGE_ID    store resulting files to STORAGE_ID (PVE only)
 
−
      --script                execute hook script
 
 
       --dumpdir DIR          store resulting files in DIR
 
       --dumpdir DIR          store resulting files in DIR
−
      --maxfiles N            maximal number of backup files per VM.
+
       --tmpdir DIR            store temporary files in DIR. --suspend and --stop are using this directory to store a copy of the VM.
−
       --tmpdir DIR            store temporary files in DIR. --suspend and --stop
 
−
                              are using this directory to store a copy of the VM.
 
 
       --mailto EMAIL          send notification mail to EMAIL. You can use
 
       --mailto EMAIL          send notification mail to EMAIL. You can use
 
                               this option more than once to specify multiple
 
                               this option more than once to specify multiple
 
                               receivers
 
                               receivers
−
       --stop                  stop/start VM if running
+
       --stop                  stop/start VPS if running
−
       --suspend              suspend/resume VM when running
+
       --suspend              suspend/resume VPS when running
 
       --snapshot              use LVM snapshot when running
 
       --snapshot              use LVM snapshot when running
 
       --size MB              LVM snapshot size (default 1024)
 
       --size MB              LVM snapshot size (default 1024)
Line 54: Line 51:
 
                               lock. vzdump uses a global lock file to make
 
                               lock. vzdump uses a global lock file to make
 
                               sure that only one instance is running
 
                               sure that only one instance is running
−
                               (running several instance puts too much load
+
                               (running sereral instance puts too much load
 
                               on a server). Default is 180 (3 hours).
 
                               on a server). Default is 180 (3 hours).
 
       --stopwait MINUTES      maximal time to wait until a VM is stopped.
 
       --stopwait MINUTES      maximal time to wait until a VM is stopped.
−
 
+
      --restore FILENAME      restore FILENAME
 +
 
== Examples ==
 
== Examples ==
 
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].
 
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].
Line 80: Line 78:
  
 
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].
 
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].
−
 
−
=== Set-up LVM ===
 
−
While the LVM solution is the cleanest, since it allows to create an online backup without having to stop or suspend the virtual machine, it is also the hardest to set up. There are a few dependencies you should be aware of before setting up your LVM:
 
−
 
−
* You need to have at least 512MB free in your LVM volume group, to be able to create snapshots
 
−
* The directory where you are writing your backup dumps to (usually <code>/vz/dump</code>) should be on a different volume group than the one you are taking a backup from (usually <code>/vz/private</code>)
 
−
* There is a bug in <code>VZDump.pm</code> that can make the snapshot creation fail
 
−
 
−
==== Partitioning ====
 
−
As described above, you need to keep a few things in mind when creating your LVM partitions. In the example setup below, there are a total of 4 partitions:
 
−
 
−
* <code>/</code>, which is hosting the default OS files, on a 10GB LVM logical volume
 
−
* <code>/boot</code>, which is hosting the kernel and bootloader config, on a 512MB standard Linux partition
 
−
* <code>/opt</code>, which is hosting the backup dump files, on a 100GB LVM logical volume
 
−
* <code>/vz</code>, which is hosting all virtual machine files, on a 1.6TB LVM logical volume
 
−
 
−
All logical volumes are hosted on a 1.8TB volume group of which only 1.7TB is used by the above partitions and 100GB is unallocated.
 
−
 
−
In this setup the 100GB of free volume group space and 100GB of backup directory have been chosen to hold the snapshots and tar files that will be created when the virtual machine will be backed up. As specified above, only 512MB of snapshot space is needed, but it's better to be safe than having to resize your volumes at a later stage when disk space is not an issue. The same holds for the backup directory.
 
−
 
−
==== Fixing VZDump.pm ====
 
−
When trying to backup a virtual machine, creation of the snapshot can fail. This is because of a bug in <code>VZDump.pm</code>. In CentOS (and other RHEL derivatives), this file is located in <code>/usr/share/perl5/PVE/VZDump.pm</code>.
 
−
 
−
On line 622, you will find the following:
 
−
 
−
if ($line =~ m|^\s*(\S+):(\S+):(\d+(\.\d+))M$|) {
 
−
 
−
Replace this with:
 
−
 
−
if ($line =~ m|^\s*(\S+):(\S+):(\d+([\.,]\d+))[mM]$|) {
 
−
 
−
Save and close the file. Snapshots will now work with <code>vzdump</code>
 
−
 
−
==== Example ====
 
−
Since in the above example we have relocated the dump directory, you will need to run backups with a command similar to the following:
 
−
 
−
vzdump --dumpdir /opt/backupdir --snapshot 101
 
  
 
=== Restore ===
 
=== Restore ===
Line 122: Line 83:
 
Restore the above backup to CT 600:
 
Restore the above backup to CT 600:
  
−
vzrestore /space/backup/vzdump-777.tar 600
 
−
OR
 
 
  vzdump --restore /space/backup/vzdump-777.tar 600
 
  vzdump --restore /space/backup/vzdump-777.tar 600
−
 
−
Note : vzdump --restore is not present in version 1.2-7, use vzrestore instead.
 
  
 
== Bugs ==
 
== Bugs ==
−
'''(not fixed in 1.2-4)'''
 
−
The rsync command used by vzdump to create the backup in suspend mode partially ignores the "--exclude-path" option.
 
−
In fact, even if the excluded paths won't appear in the final output, the whole VPS will be moved to the temporary directory, meaning that you need as much free disk space as your VPS size to use vzdump. It can be an issue in the case of a file server handling many files...
 
−
 
−
''Workaround:'' A workaround has been proposed on OpenVZ forum, see below for the excerpt. (http://forum.openvz.org/index.php?t=msg&goto=36924&)
 
−
<pre>
 
−
User: tatawaki
 
−
Messages: 3
 
−
Registered: December 2008  Junior Member
 
−
From: *sbm.shawcable.net
 
−
 
−
Line 694:
 
−
my $rsyncopts = "--stats --numeric-ids --bwlimit=${opt_bwlimit}";
 
−
 
−
# changes to
 
−
 
−
my $rsyncopts = "--stats --numeric-ids --bwlimit=${opt_bwlimit}";
 
−
$rsyncopts = $rsyncopts." --exclude-from=/home/backups/exclude_vzdump.txt";
 
  
−
the txt file contains <VEID>/home/:
+
(fixed in 1.1-1)
−
 
 
−
1094/home/
 
−
510/opt/
 
−
...
 
−
</pre>
 
−
 
 
−
'''(fixed in 1.1-1)'''
 
 
vzdump will fail under Debian Etch in version 1.0-2 if it is invoked with parameter "--snapshot" and if the logical volume name contains a hyphen.
 
vzdump will fail under Debian Etch in version 1.0-2 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.
−
''Workaround:'' 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.
 
A bug report was sent to proxmox on 02 June 2008.
 
Other distributions or versions may be affected, too.
 
Other distributions or versions may be affected, too.
  
−
<!--
 
−
link dead
 
−
== Hooks ==
 
−
 
−
http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity
 
−
-->
 
 
[[Category: HOWTO]]
 
[[Category: HOWTO]]

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
 If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)
Retrieved from "https://wiki.openvz.org/Backup_of_a_running_container_with_vzdump"