OpenVZ Virtuozzo Containers Wiki - User contributions [en]

Proxmox Mail Gateway in container

2014-03-15T11:12:48Z

Martinmaurer: /* Backup considerations, live migration, and HA Cluster */ updated dead link

The Proxmox Mail Gateway 2.2 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

== Prerequisites ==
I assume you have already a running OpenVZ server. This howto is based on an fresh CentOS 4.4 installation with OpenVZ kernel 2.6.9 but should also work with all other combinations. I used a Dual Xeon with 2 GB RAM.

== Installation ==
Download the Proxmox OpenVZ template:
wget http://download.proxmox.com/appliances/mail/debian-6.0-proxmox-mailgateway_3.1-2_amd64.tar.gz

Copy the template into the template cache, usually to /vz/templates/cache/

== Create a default config ==
Create a reasonable default config if you don’t have one. The following command creates the file <code>/etc/vz/conf/ve-default.conf-sample</code> which contains reasonable defaults if you plan to run 5 containers:
vzsplit -n 5 -f default

== Create a container ==

Choose a free CT ID, we use 777 for this guide.

<pre>vzctl create 777 --ostemplate debian-6.0-proxmox-mailgateway_3.1 --config default</pre>

== Configure the container ==

Set IP address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save

Set guaranteed memory to 1024MB, maximum disk space to 4GB.

vzctl set 777 --vmguarpages 1024M:unlimited --privvmpages 1G:1100M --diskspace 4000M:4400M --save

== Start the container ==

vzctl start 777

And finally set the root password:
vzctl set 777 --userpasswd root:YOURPASSWORD

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

== Backup considerations, live migration, and HA Cluster ==
You can run the mail gateway on any OpenVZ platform and on the [http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster Proxmox VE Cluster]. This include live-migration and online backups.

For online backups, see [[backup of a running container with vzdump]].

For live migration, see [[checkpointing and live migration]].

For HA Cluster, see [[HA cluster with DRBD and Heartbeat]] and [http://www.proxmox.com/proxmox-mail-gateway/features feature page on Proxmox].

== Proxmox configuration ==
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com/

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2014-03-15T11:09:33Z

Martinmaurer: Updated links and minor updates

The Proxmox Mail Gateway 2.2 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

== Prerequisites ==
I assume you have already a running OpenVZ server. This howto is based on an fresh CentOS 4.4 installation with OpenVZ kernel 2.6.9 but should also work with all other combinations. I used a Dual Xeon with 2 GB RAM.

== Installation ==
Download the Proxmox OpenVZ template:
wget http://download.proxmox.com/appliances/mail/debian-6.0-proxmox-mailgateway_3.1-2_amd64.tar.gz

Copy the template into the template cache, usually to /vz/templates/cache/

== Create a default config ==
Create a reasonable default config if you don’t have one. The following command creates the file <code>/etc/vz/conf/ve-default.conf-sample</code> which contains reasonable defaults if you plan to run 5 containers:
vzsplit -n 5 -f default

== Create a container ==

Choose a free CT ID, we use 777 for this guide.

<pre>vzctl create 777 --ostemplate debian-6.0-proxmox-mailgateway_3.1 --config default</pre>

== Configure the container ==

Set IP address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save

Set guaranteed memory to 1024MB, maximum disk space to 4GB.

vzctl set 777 --vmguarpages 1024M:unlimited --privvmpages 1G:1100M --diskspace 4000M:4400M --save

== Start the container ==

vzctl start 777

And finally set the root password:
vzctl set 777 --userpasswd root:YOURPASSWORD

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

== Backup considerations, live migration, and HA Cluster ==
You can run the mail gateway on any OpenVZ platform and on the [http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster Proxmox VE Cluster]. This include live-migration and online backups.

For online backups, see [[backup of a running container with vzdump]].

For live migration, see [[checkpointing and live migration]].

For HA Cluster, see [[HA cluster with DRBD and Heartbeat]] and [http://www.proxmox.com/products/proxmox-mail-gateway/mail-gateway-ha-cluster/ proxmox.com].

== Proxmox configuration ==
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com/

[[Category: HOWTO]]
[[Category: Templates]]

Partners

2014-03-15T10:59:49Z

Martinmaurer: /* Proxmox */ - updated links

Here are some companies that are working together with OpenVZ project in one or another way. Feel free to add your company profile here ('''in alphabetical order''').

{{Note|Hosting service providers should add their entries to [[Hosting providers]], not here. Thanks.}}

== K7 Computing ==
[http://www.fluidvm.com BinaryKarma], now acquired by K7 Computing is offering an multi-hypervisor platform, FluidVM that also supports OpenVZ, apart from Xen. FluidVM supports local and SAN storage and is also extensible via an XML-RPC based API. FluidVM ships with a browser based interface with which users can manage multiple servers and VEs. BinaryKarma is also the developer of [http://sourceforge.net/projects/easyvz/ EasyVZ], a GPL'd free GUI available for OpenVZ.

== Blended Perspectives ==

[http://www.blendedperspectives.com Blended Perspectives] is a strategy-to-execution consultancy based in Toronto, Canada. Our core offerings are centered on provision of Wiki platforms and OpenVZ is a favoured host operating environment to achieve scale and resiliency.

== ClearCorp ==

[http://www.clearcorp.co.cr ClearCorp] provides '''Complete Custom Solutions''' using OpenSource tools. As a part of our group, [http://www.clearnet.co.cr ClearNet] use OpenVZ to do very fast server provisioning and to implement scalable and reliable network designs. We are also working directly with the [http://www.softwarelibrecr.org RCSL] (Costarican Free Software Network).

== Computer Tyme ==
[http://ctyme.com Computer Tyme] is using OpenVZ for their spam filtering service [http://junkemailfilter.com Junk Email Filter dot com]. They are active proponents of OpenVZ; Marc Perkel worked at the OpenVZ booth during LinuxWorld Expo 2007.

== Fortech I.T. Solutions ==
[http://FortechITSolutions.ca Fortech I.T. Solutions] is an IT consulting company based in Halifax (Nova Scotia, Canada) specializing in open-source solutions. We offer services in a variety of areas, including virtualization solutions based on a number of platforms - including OpenVZ.

== Fry-IT Ltd ==
[http://www.fry-it.com Fry-IT Ltd] is a London based web, mobile and hosting consultancy and among the services we provide are system solutions involving Clustering, Load Balancing and High Availability, with OpenVZ as the virtualization technology of choice.

An example of our consulting work is the OpenVZ cluster powering 6 applications at [http://www.da.mod.uk/ MOD Defence Academy] in the UK, the public website being one of the applications. To our clients, hosted with us or running their own infrastructure, we provide a complete solution from custom OpenVZ scripts, a container resource limits management web application to thorough documentation of system management procedures.

== Impulso Srl ==
[http://impulso.it Impulso] offers white label Internet Services and uses OpenVZ cluster for their managed email services like [http://postalinda.it Posta Linda]. Impulso also offers support for OpenVZ in Italy.

== Inguza Technology AB ==
[http://inguza.com/ Inguza Technology AB] maintains the Debian GNU Linux version of OpenVZ.

== LastSpam ==
[http://www.lastspam.com LastSpam] offers managed e-mail security services (anti-spam and anti-virus/bad content) and uses OpenVZ to deliver excellent service and support to its customers. Ugo Bellavance, LastSpam's head server architect and manager is an active member of the OpenVZ community: helping on the forum, making suggestions, and submitting patches.

== netVOICE communications ==
[http://www.netvoice.ca/ netVOICE communications] is an Internet Telephony Service Provider (ITSP) that uses OpenVZ as the basis for their [http://www.vpas.ca/ Virtual Private Asterisk Server (VPAS)] offering. They also offer consulting on running Asterisk (the leading Open Source telephony platform) on OpenVZ. netVOICE is a Digium Approved Reseller and has a Digium Certified Asterisk Professional [http://www.digium.com/en/training/certifications/ (dCAP)] on staff.

== Openwall ==

At [http://www.openwall.com Openwall], we develop our own Open Source software with a focus on security, including [http://www.openwall.com/Owl/ Openwall GNU/*/Linux] (or Owl for short), a security-enhanced server platform.
Our [http://www.openwall.com/services/ professional services] include remote installation (you boot off CD, we do the rest) and maintenance (systems and security administration) of OpenVZ-enabled servers and mini-networks of such servers. We typically use the OpenVZ kernel, the Owl userland for the host system, and arbitrary Linux distributions for the containers (most often that's Owl as well - with additional software to meet your needs). We readily have software solutions for provision of advanced LAMP hosting with cross virtual host security separation within each container (that is, not only the containers are separated due to OpenVZ, but also virtual hosts within containers are separated at the OS level), multi-server backups (incremental, remote, encrypted, integrity-checked), monitoring (many custom Nagios sensors, including for things such as backups, filesystem errors, RAID status, etc.), and more.

== OpenWorx ==

[http://www.openworx.nl OpenWorx] is an IT company specialized for small and medium scaled business. Support on Linux and Open Source: webapplications, virtualization (OpenVZ), linux desktops and servers (Ubuntu, Debian, Centos).

== Planettel ==
[http://www.planettel.com.sg PlaNetTel] Asia Pacific Pte Ltd is a Singapore registered company providing OpenVZ support and appliances besides other Open Source technologies with a focus on SaaS and Asterisk based CRM services. Development and support is assisted by Open Source developer [http://www.apmuthu.com Ap.Muthu] and Marketing and Sales by [http://www.planettel.com.sg Thomas Festus]. The OpenVZ Templates contributed and supported by use include [http://pve.proxmox.com/wiki/EyeOS eyeOS], [http://pve.proxmox.com/wiki/VTigerCRM vTigerCRM], [http://pve.proxmox.com/wiki/OpenGOO OpenGOO / FengOffice], [http://pve.proxmox.com/wiki/FrontAccounting FrontAccounting], [http://pve.proxmox.com/wiki/Moodle Moodle], MediaWiki v1.16., Joomla v1.6, SimpleGroupWare among others. '''Support''' for Planettel / [http://www.gnuacademy.org GNUAcademy] released OpenVZ Templates is '''[http://www.planettel.com.sg/contact-us/hosted-appliance-order available]'''.

== Proxmox ==

[http://pve.proxmox.com Proxmox VE] is an easy to use Open Source virtualization platform for running pre-built Virtual Appliances and Virtual Machines (based on OpenVZ and [http://www.linux-kvm.org KVM] for full virtualization).

The Proxmox spam filtering appliance can run as an OpenVZ container. (see [[Proxmox Mail Gateway in container]]). Proxmox is also the author of [[Vzdump]] utility.

== Revolution Linux ==

[http://www.revolutionlinux.com/ Revolution Linux] is an IT company specialized in large scale infrastructure deployement using Open Source technologies. Most/all of our deployements rely extensively on containers (OpenVZ and Linux Vserver). We also offer OpenVZ training to our customers when deploying an infrastructure.

== SNB ==
[http://www.snb.at SNB] uses OpenVZ for own services and supports servers managed or in customers environments. In common vm's are deployed with RedHat/CentOS. SNB offers many standard vm's as mailserver with antispam, webserver, monitoring services, mysql-server & cluster ...

== Solarspeed Ltd. ==
[http://www.solarspeed.net Solarspeed Ltd.] is a CentOS + BlueQuartz server specialist, selling server systems and software solutions. We developed [http://www.aventurin.net Aventurin{e}], which is a Linux Virtualization Appliance Software. It is based on OpenVZ and is available in a non-clustering and a clustering version. The clustering version uses DRBD and Heartbeat. The GUI interface of [http://www.aventurin.net Aventurin{e}] is based on the [http://www.bluequartz.org BlueQuartz] and allows to easily manage and create virtual servers or to perform administrative tasks on the master node. [http://www.aventurin.net Aventurin{e}] is available as [http://www.solarspeed.net/cart.php?target=product&product_id=16261&category_id=272 ISO image download], as a ready to run [http://www.solarspeed.net/cart.php?target=product&product_id=16263&category_id=272 Linux Virtualization Appliance] or as a ready to run [http://www.solarspeed.net/cart.php?target=product&product_id=16264&category_id=272 Linux Virtualization Appliance Cluster].

== Solutions First ==
[http://www.solutionsfirst.com.au Solutions First] is a Linux and Open Source infrastructure specialist company. Amongst many other FOSS products, we sell and support OpenVZ for our customers. We are happy to provide support of OpenVZ any Asia-Pacific customers. We have experience in generic container hosting environments, templated applications, HA clusters and much more OpenVZ specific applications.

== SpiderTools.com ==
[http://spidertools.com SpiderTools] provides training for OpenVZ servers. Students work on live servers to gain skills on how to implement OpenVZ. 20% of all sales go back to OpenVZ for development. Students will get 6 weeks of live instruction and support.

== Thomas-Krenn.AG ==
[http://www.thomas-krenn.com/ Thomas-Krenn.AG] is a server specialist, selling server systems and solutions. One of the solution products is a pre-installed [http://www.thomas-krenn.com/en/system-solutions/ha-linux-cluster.html cluster system], built with Virtuozzo. They published how to build such a cluster with OpenVZ at [[HA cluster with DRBD and Heartbeat]].

== Unixservice ==
[http://www.unixservice.com/ Unixservice] provides SLAs for critical internet infrastructure provisioning. As we have grown over the past 10 years we have become fervent advocates of running such services on a grid/cluster of OpenVZ (or Virtuozzo) servers. The main R&D team leader has just released our own C based unxsVZ grid/cluster manager (unxsVZ) released under a GPL license, including [http://openisp.net/openisp/unxsVZ/wiki/UBCAutonomics autonomic functions] that we have developed based on discrete mathematics and CMU/IBM research. [http://openisp.net/openisp/unxsVZ unxsVZ source, yum repository and RPMs here.] Call us now with questions; we even provide free deployment support and container tuning support for DNS/BIND, RADIUS, HTTP Apache hosting, ESMTP stores, ESMTP out and MX edge server farms on large VZ grids.

== See also ==

* [[Hosting providers]] — HSPs using OpenVZ
* [[Download mirrors]] — people and companies providing mirrors for OpenVZ software
* [[Control panels]]
* [[2006 contributions]]

Backup of a running container with vzdump

2010-09-19T09:34:02Z

Martinmaurer: /* Installation */

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com.

For Debian based systems:
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-7_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 ==
For rpm based systems:
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.2-7_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]
--exclude VMID exclude VMID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temporary files and logs
--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
--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.
--mailto EMAIL send notification mail to EMAIL. You can use
this option more than once to specify multiple
receivers
--stop stop/start VM if running
--suspend suspend/resume VM when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running several instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzrestore /space/backup/vzdump-777.tar 600
OR
vzdump --restore /space/backup/vzdump-777.tar 600

== 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/:

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.

''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.
Other distributions or versions may be affected, too.

== Hooks ==

http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity

[[Category: HOWTO]]

Backup of a running container with vzdump

2010-09-19T09:33:47Z

Martinmaurer: /* Download */

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com.

For Debian based systems:
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-7_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 ==
For rpm based systems:
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.2-5_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]
--exclude VMID exclude VMID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temporary files and logs
--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
--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.
--mailto EMAIL send notification mail to EMAIL. You can use
this option more than once to specify multiple
receivers
--stop stop/start VM if running
--suspend suspend/resume VM when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running several instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzrestore /space/backup/vzdump-777.tar 600
OR
vzdump --restore /space/backup/vzdump-777.tar 600

== 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/:

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.

''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.
Other distributions or versions may be affected, too.

== Hooks ==

http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity

[[Category: HOWTO]]

Proxmox Mail Gateway in container

2010-07-15T10:58:41Z

Martinmaurer: /* Backup considerations, live migration, and HA Cluster */

The Proxmox Mail Gateway 2.2 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

== Prerequisites ==
I assume you have already a running OpenVZ server. This howto is based on an fresh CentOS 4.4 installation with OpenVZ kernel 2.6.9 but should also work with all other combinations. I used a Dual Xeon with 2 GB RAM.

== Installation ==
Download the Proxmox OpenVZ template:
wget ftp://download.proxmox.com/appliances/mail/debian-4.0-proxmox-mailgateway_2.5-1_i386.tar.gz

Copy the template into the template cache, usually to /vz/templates/cache/

== Create a default config ==
Create a reasonable default config if you don’t have one. The following command creates the file <code>/etc/vz/conf/ve-default.conf-sample</code> which contains reasonable defaults if you plan to run 5 containers:
vzsplit -n 5 -f default

== Create a container ==

Choose a free CT ID, we use 777 for this guide.

<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.5 --config default</pre>

== Configure the container ==

Set IP address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save

Set guaranteed memory to 512MB, maximum disk space to 4GB.

vzctl set 777 --vmguarpages 512M:unlimited --privvmpages 1G:1100M --diskspace 4000M:4400M --save

== Start the container ==

vzctl start 777

And finally set the root password:
vzctl set 777 --userpasswd root:YOURPASSWORD

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

== Backup considerations, live migration, and HA Cluster ==
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) — all can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups, see [[backup of a running container with vzdump]].

For live migration, see [[checkpointing and live migration]].

For HA Cluster, see [[HA cluster with DRBD and Heartbeat]] and [http://www.proxmox.com/products/proxmox-mail-gateway/mail-gateway-ha-cluster/ proxmox.com].

== Proxmox configuration ==
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com/

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2010-07-15T10:57:10Z

Martinmaurer: /* Create a container */

The Proxmox Mail Gateway 2.2 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

== Prerequisites ==
I assume you have already a running OpenVZ server. This howto is based on an fresh CentOS 4.4 installation with OpenVZ kernel 2.6.9 but should also work with all other combinations. I used a Dual Xeon with 2 GB RAM.

== Installation ==
Download the Proxmox OpenVZ template:
wget ftp://download.proxmox.com/appliances/mail/debian-4.0-proxmox-mailgateway_2.5-1_i386.tar.gz

Copy the template into the template cache, usually to /vz/templates/cache/

== Create a default config ==
Create a reasonable default config if you don’t have one. The following command creates the file <code>/etc/vz/conf/ve-default.conf-sample</code> which contains reasonable defaults if you plan to run 5 containers:
vzsplit -n 5 -f default

== Create a container ==

Choose a free CT ID, we use 777 for this guide.

<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.5 --config default</pre>

== Configure the container ==

Set IP address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save

Set guaranteed memory to 512MB, maximum disk space to 4GB.

vzctl set 777 --vmguarpages 512M:unlimited --privvmpages 1G:1100M --diskspace 4000M:4400M --save

== Start the container ==

vzctl start 777

And finally set the root password:
vzctl set 777 --userpasswd root:YOURPASSWORD

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

== Backup considerations, live migration, and HA Cluster ==
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) — all can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups, see [[backup of a running container with vzdump]].

For live migration, see [[checkpointing and live migration]].

For HA Cluster, see [[HA cluster with DRBD and Heartbeat]] and [http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/ proxmox.com].

== Proxmox configuration ==
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com/

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2010-07-15T10:56:44Z

Martinmaurer: /* Installation */

The Proxmox Mail Gateway 2.2 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

== Prerequisites ==
I assume you have already a running OpenVZ server. This howto is based on an fresh CentOS 4.4 installation with OpenVZ kernel 2.6.9 but should also work with all other combinations. I used a Dual Xeon with 2 GB RAM.

== Installation ==
Download the Proxmox OpenVZ template:
wget ftp://download.proxmox.com/appliances/mail/debian-4.0-proxmox-mailgateway_2.5-1_i386.tar.gz

Copy the template into the template cache, usually to /vz/templates/cache/

== Create a default config ==
Create a reasonable default config if you don’t have one. The following command creates the file <code>/etc/vz/conf/ve-default.conf-sample</code> which contains reasonable defaults if you plan to run 5 containers:
vzsplit -n 5 -f default

== Create a container ==

Choose a free CT ID, we use 777 for this guide.

<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.2 --config default</pre>

== Configure the container ==

Set IP address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save

Set guaranteed memory to 512MB, maximum disk space to 4GB.

vzctl set 777 --vmguarpages 512M:unlimited --privvmpages 1G:1100M --diskspace 4000M:4400M --save

== Start the container ==

vzctl start 777

And finally set the root password:
vzctl set 777 --userpasswd root:YOURPASSWORD

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
CTID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

== Backup considerations, live migration, and HA Cluster ==
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) — all can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups, see [[backup of a running container with vzdump]].

For live migration, see [[checkpointing and live migration]].

For HA Cluster, see [[HA cluster with DRBD and Heartbeat]] and [http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/ proxmox.com].

== Proxmox configuration ==
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com/

[[Category: HOWTO]]
[[Category: Templates]]

Backup of a running container with vzdump

2010-07-05T10:12:21Z

Martinmaurer: /* Installation */

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com.

For Debian based systems:
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-5_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 ==
For rpm based systems:
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.2-5_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]
--exclude VMID exclude VMID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temporary files and logs
--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
--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.
--mailto EMAIL send notification mail to EMAIL. You can use
this option more than once to specify multiple
receivers
--stop stop/start VM if running
--suspend suspend/resume VM when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running several instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzrestore /space/backup/vzdump-777.tar 600
OR
vzdump --restore /space/backup/vzdump-777.tar 600

== 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/:

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.

''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.
Other distributions or versions may be affected, too.

== Hooks ==

http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity

[[Category: HOWTO]]

Backup of a running container with vzdump

2010-07-05T10:11:59Z

Martinmaurer: /* Installation */

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com.

For Debian based systems:
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-5_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 ==
For rpm based systems:
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.2-5_all.deb</pre> v

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]
--exclude VMID exclude VMID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temporary files and logs
--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
--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.
--mailto EMAIL send notification mail to EMAIL. You can use
this option more than once to specify multiple
receivers
--stop stop/start VM if running
--suspend suspend/resume VM when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running several instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzrestore /space/backup/vzdump-777.tar 600
OR
vzdump --restore /space/backup/vzdump-777.tar 600

== 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/:

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.

''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.
Other distributions or versions may be affected, too.

== Hooks ==

http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity

[[Category: HOWTO]]

Backup of a running container with vzdump

2010-07-05T10:11:27Z

Martinmaurer: /* Download */

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/ or for newest version, check http://download.proxmox.com.

For Debian based systems:
<pre>wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/vzdump_1.2-5_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 ==
For rpm based systems:
<pre>rpm -i vzdump-1.2-5.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.2-5_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]
--exclude VMID exclude VMID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temporary files and logs
--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
--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.
--mailto EMAIL send notification mail to EMAIL. You can use
this option more than once to specify multiple
receivers
--stop stop/start VM if running
--suspend suspend/resume VM when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running several instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzrestore /space/backup/vzdump-777.tar 600
OR
vzdump --restore /space/backup/vzdump-777.tar 600

== 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/:

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.

''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.
Other distributions or versions may be affected, too.

== Hooks ==

http://nachtmann.it/blog/vzdump-hook-ftp-backup-script - Backup to FTP with limited capacity

[[Category: HOWTO]]

Backup of a running container with vzdump

2009-07-24T08:18:49Z

Martinmaurer: Update to vzdump-1.1-2

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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-2.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_1.1-2_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-1.1-2.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.1-2_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]

--exclude VPSID exclude VPSID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temorary files and logs
--compress compress dump file (gzip)
--dumpdir DIR store resulting files in DIR
--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
this option more than once to specify multiple
receivers
--stop stop/start VPS if running
--suspend suspend/resume VPS when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running sereral instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.
--restore FILENAME restore FILENAME

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzdump --restore /space/backup/vzdump-777.tar 600

== Bugs ==

(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.
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.
Other distributions or versions may be affected, too.

[[Category: HOWTO]]

Backup of a running container with vzdump

2008-11-26T13:19:44Z

Martinmaurer:

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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:
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_1.1-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-1.1-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.1-1_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]

--exclude VPSID exclude VPSID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temorary files and logs
--compress compress dump file (gzip)
--dumpdir DIR store resulting files in DIR
--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
this option more than once to specify multiple
receivers
--stop stop/start VPS if running
--suspend suspend/resume VPS when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running sereral instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.
--restore FILENAME restore FILENAME

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzdump --restore /space/backup/vzdump-777.tar 600

== Bugs ==

(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.
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.
Other distributions or versions may be affected, too.

[[Category: HOWTO]]

Backup of a running container with vzdump

2008-11-26T13:18:44Z

Martinmaurer: Added links to new rpm´s, updated syntax

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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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:
<pre>wget http://pve.proxmox.com/debian/dists/etch/pve/binary-amd64/vzdump_1.1-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-1.1-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.1-1_all.deb</pre>

== Synopsis ==

see also:
<pre>man vzdump</pre>

vzdump OPTIONS [--all | <VMID>]

--exclude VPSID exclude VPSID (assumes --all)
--exclude-path REGEX exclude certain files/directories. You
can use this option more than once to specify
multiple exclude paths
--stdexcludes exclude temorary files and logs
--compress compress dump file (gzip)
--dumpdir DIR store resulting files in DIR
--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
this option more than once to specify multiple
receivers
--stop stop/start VPS if running
--suspend suspend/resume VPS when running
--snapshot use LVM snapshot when running
--size MB LVM snapshot size (default 1024)
--bwlimit KBPS limit I/O bandwidth; KBytes per second
--lockwait MINUTES maximal time to wait for the global
lock. vzdump uses a global lock file to make
sure that only one instance is running
(running sereral instance puts too much load
on a server). Default is 180 (3 hours).
--stopwait MINUTES maximal time to wait until a VM is stopped.
--restore FILENAME restore FILENAME

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzdump --restore /space/backup/vzdump-777.tar 600

== Bugs ==

(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.
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.
Other distributions or versions may be affected, too.

[[Category: HOWTO]]

Backup of a running container with vzdump

2008-11-26T12:57:47Z

Martinmaurer: updated to vzdump 1.1-1

Vzdump is a utility to make consistent snapshots of running OpenVZ containers. 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:

* Stop the CT during backup (very long downtime)
* Use rsync and suspend/resume (minimal downtime)
* Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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.0-2.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://pve.proxmox.com/debian/dists/etch/pve/binary-amd64/vzdump_1.1-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-1.0-2.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_1.1-1_all.deb</pre>

== Synopsis ==

vzdump OPTIONS [--all | <CTID>]
--compress compress dump file (gzip)
--dumpdir DIR store resulting files in DIR
--xdelta create a differential backup using xdelta
--mailto EMAIL send notification mail to EMAIL
--stop stop/start container if running
--suspend suspend/resume container when running
--snapshot use LVM snapshot when running
--restore FILENAME restore FILENAME

== Examples ==
Use a running container, for example install this: [[Proxmox Mail Gateway in container]].

=== 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>).

vzdump 777

Use rsync and suspend/resume to create a snapshot (minimal downtime).

vzdump --suspend 777

Backup all containers and send notification mails to root.

vzdump --suspend --all --mailto root

Use LVM2 to create snapshots (no downtime).

vzdump --dumpdir /space/backup --snapshot 777

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 the above backup to CT 600:

vzdump --restore /space/backup/vzdump-777.tar 600

== Bugs ==

(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.
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.
Other distributions or versions may be affected, too.

[[Category: HOWTO]]

Bare Metal Installer

2008-11-26T12:47:57Z

Martinmaurer: removed beta status, added GUI for vzdump

== Introduction ==
A good way for beginners and a fast way to install OpenVZ to a new server is the [http://pve.proxmox.com Proxmox VE] bare-metal ISO installer.
== Features ==
Proxmox VE installs the complete operating system and management tools in 3 to 5 minutes (depends on the used hardware).

''"Bare-metal" means that you start from a empty server - there is no need to install a base operation system.''

Including the following:

* Complete operating system (Debian Etch 64)
* Partition the hard drive with LVM2, optimized for [[Backup of a running container with vzdump|vzdump]]
* Backup/Restore tools - GUI for [[Backup of a running container with vzdump|vzdump]]
* Proxmox VE Kernel with OpenVZ and [http://kvm.qumranet.com KVM] support
* Web based management interface
* Integrated virtual appliance download
* Configuration Cluster

Please note, the complete server is used and all existing data is removed.

== License and Download ==
Proxmox VE is licensed under GPLv2 (Open source).

[http://pve.proxmox.com/wiki/Downloads Download Proxmox VE]

[[Category: HOWTO]]
[[Category: Debian]]
[[Category: Installation]]

Bare Metal Installer

2008-04-18T15:41:12Z

Martinmaurer: Create Article

=Introduction=
A good way for beginners and a fast way to install OpenVZ to a new server is the [http://pve.proxmox.com Proxmox VE] bare-metal ISO installer. Currently it´s beta software using a development OpenVZ kernel (2.6.24).
=Features=
Proxmox VE installs the complete operating system and management tools in 3 to 5 minutes (depends on the used hardware).

''"Bare-metal" means that you start from a empty server - there is no need to install a base operation system.''

Including the following:

* Complete operating system (Debian Etch 64)
* Partition the hard drive with LVM2, optimized for [[Backup of a running container with vzdump|vzdump]]
* Backup/Restore tools
* Proxmox VE Kernel with OpenVZ and [[http://kvm.qumranet.com KVM]] support
* Web based management interface
* Integrated virtual appliance download
* Configuration Cluster

Please note, the complete server is used and all existing data is removed.
=License and Download=
Proxmox VE is licensed under GPLv2 (Open source).

[http://pve.proxmox.com/wiki/Downloads Download Proxmox VE]

[[Category: HOWTO]]
[[Category: Debian]]
[[Category: Installation]]

Control panels

2008-04-18T15:06:20Z

Martinmaurer: small typo

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare-metal ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage]
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin]
* Vtonf: [http://www.vtonf.com/ homepage]

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

Control panels

2008-04-18T14:59:33Z

Martinmaurer: Added Proxmox VE

This page contains links to different control panels for OpenVZ, written by third parties. If you know the project that's missing here, please add it.

== Free software / Open source ==
* Proxmox Virtual Environment: [http://pve.proxmox.com Proxmox VE Wiki] - including bare metall ISO installer
* WebVZ: [http://webvz.sourceforge.net/ homepage]
* Webmin: [http://www.webmin.com/ homepage] | [http://www.webmin.com/cgi-bin/search_third.cgi?search=OpenVZ OpenVZ plugin]
* Vtonf: [http://www.vtonf.com/ homepage]

== Proprietary / non-free ==
* FluidVM: [http://www.binarykarma.com Home Page] • [http://www.binarykarma.com/demo.php Demo Videos] • [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots]
* VZ-Manager: [http://vzmanager.de/ homepage (German)]
* HyperVM: [http://lxlabs.com/software/hypervm/ homepage]
* vzAdmin: [http://www.vzAdmin.info/ homepage (German)]
* Aventurin{e}: [http://www.aventurin.net/ homepage (English)]

== Frozen projects ==
* VZAdmin: [http://www.ronny-goerner.de/ homepage] ''seems not available now''
* WVZ: [http://homaly.dunanet.hu/wvz/ homepage] ''seems frozen''
* New OpenVZ Web Based Control Panel by rsailor: {{forum|230}} ''seems not available now''
* EasyVZ: [http://easyvz.sourceforge.net/ screenshots] | [http://sourceforge.net/projects/easyvz sf.net project page] (little bit outdated, but only working and free control panel?) (requires Unix/Linux)
* Mwamko: [http://mwamko.devjavu.com/ homepage]
* OpenVZ Control panel for Windows(r): {{forum|1491}} | [http://downloads.qmailrocks.ru/vz/ downloads] ''unknown license''

Partners

2008-04-18T14:56:18Z

Martinmaurer: /* Proxmox */

Here are some companies that are working together with OpenVZ project in one or another way. Feel free to add your company profile here ('''in alphabetical order''').

== BinaryKarma ==
[http://www.binarykarma.com BinaryKarma] is offering an multi-hypervisor platform, FluidVM that also supports OpenVZ, apart from Xen. FluidVM supports local and SAN storage and is also extensible via an XML-RPC based API. See [http://www.binarykarma.com/fluidvm_screenshots.php Screen shots] and [http://www.binarykarma.com/demo.php Demo Videos] for more information. FluidVM ships with a browser based interface with which users can manage multiple servers and VEs. BinaryKarma is also the developer of [http://easyvz.sourceforge.net EasyVZ], a GPL'd free GUI available for OpenVZ.

== Computer Tyme ==
[http://ctyme.com Computer Tyme] is using OpenVZ for their spam filtering service [http://junkemailfilter.com Junk Email Filter dot com]. They are active proponents of OpenVZ; Marc Perkel worked at the OpenVZ booth during LinuxWorld Expo 2007.

== Fry-IT Ltd ==
[http://www.fry-it.com Fry-IT Ltd] is a London based web, mobile and hosting consultancy and among the services we provide are system solutions involving Clustering, Load Balancing and High Availability, with OpenVZ as the virtualization technology of choice.

An example of our consulting work is the OpenVZ cluster powering 6 applications at [http://www.da.mod.uk/ MOD Defence Academy] in the UK, the public website being one of the applications. To our clients, hosted with us or running their own infrastructure, we provide a complete solution from custom OpenVZ scripts, a container resource limits management web application to thorough documentation of system management procedures.

== LastSpam ==
[http://www.lastspam.com LastSpam] offers managed e-mail security services (anti-spam and anti-virus/bad content) and uses OpenVZ to deliver excellent service and support to its customers. Ugo Bellavance, LastSpam's head server architect and manager is an active member of the OpenVZ community: helping on the forum, making suggestions, and submitting patches.

== netVOICE communications ==
[http://www.netvoice.ca/ netVOICE communications] is an Internet Telephony Service Provider (ITSP) that uses OpenVZ as the basis for their [http://www.vpas.ca/ Virtual Private Asterisk Server (VPAS)] offering. They also offer consulting on running Asterisk (the leading Open Source telephony platform) on OpenVZ. netVOICE is a Digium Approved Reseller and has a Digium Certified Asterisk Professional [http://www.digium.com/en/training/certifications/ (dCAP)] on staff.

== Openwall ==

At [http://www.openwall.com Openwall], we develop our own Open Source software with a focus on security, including [http://www.openwall.com/Owl/ Openwall GNU/*/Linux] (or Owl for short), a security-enhanced server platform.
Our [http://www.openwall.com/services/ professional services] include remote installation (you boot off CD, we do the rest) and maintenance (systems and security administration) of OpenVZ-enabled servers and mini-networks of such servers. We typically use the OpenVZ kernel, the Owl userland for the host system, and arbitrary Linux distributions for the containers (most often that's Owl as well - with additional software to meet your needs). We readily have software solutions for provision of advanced LAMP hosting with cross virtual host security separation within each container (that is, not only the containers are separated due to OpenVZ, but also virtual hosts within containers are separated at the OS level), multi-server backups (incremental, remote, encrypted, integrity-checked), monitoring (many custom Nagios sensors, including for things such as backups, filesystem errors, RAID status, etc.), and more.

== Proxmox Virtual Environment==

[http://pve.proxmox.com Proxmox VE] is an easy to use Open Source virtualization platform for running pre-built Virtual Appliances and Virtual Machines (based on OpenVZ and also [http://kvm.qumranet.com/kvmwiki KVM] for full virtualization).

[http://proxmox.com Proxmox] is [http://www.proxmox.com/cms_proxmox/en/virtualization/openvz/ using OpenVZ] for their spam filtering appliance (see [[Proxmox Mail Gateway in container]]). Proxmox is also the author of [http://www.proxmox.com/cms_proxmox/en/virtualization/openvz/vzdump/ vzdump] utility.

== Solarspeed Ltd. ==
[http://www.solarspeed.net Solarspeed Ltd.] is a CentOS + BlueQuartz server specialist, selling server systems and software solutions. We developed [http://www.aventurin.net Aventurin{e}], which is a Linux Virtualization Appliance Software. It is based on OpenVZ and is available in a non-clustering and a clustering version. The clustering version uses DRBD and Heartbeat. The GUI interface of [http://www.aventurin.net Aventurin{e}] is based on the [http://www.bluequartz.org BlueQuartz] and allows to easily manage and create virtual servers or to perform administrative tasks on the master node. [http://www.aventurin.net Aventurin{e}] is available as [http://www.solarspeed.net/cart.php?target=product&product_id=16261&category_id=272 ISO image download], as a ready to run [http://www.solarspeed.net/cart.php?target=product&product_id=16263&category_id=272 Linux Virtualization Appliance] or as a ready to run [http://www.solarspeed.net/cart.php?target=product&product_id=16264&category_id=272 Linux Virtualization Appliance Cluster].

== Solutions First ==
[http://www.solutionsfirst.com.au Solutions First] is a Linux and Open Source infrastructure specialist company. Amongst many other FOSS products, we sell and support OpenVZ for our customers. We are happy to provide support of OpenVZ any Asia-Pacific customers. We have experience in generic container hosting environments, templated applications, HA clusters and much more OpenVZ specific applications.

== SpiderTools.com ==
[http://spidertools.com SpiderTools] provides training for OpenVZ servers. Students work on live servers to gain skills on how to implement OpenVZ. 20% of all sales go back to OpenVZ for development. Students will get 6 weeks of live instruction and support.

== Thomas-Krenn.AG ==
[http://www.thomas-krenn.com Thomas-Krenn.AG] is a server specialist, selling server systems and solutions. One of the solution products is a pre-installed [http://www.thomas-krenn.com/en/system-solutions/ha-linux-cluster.html cluster system], built with Virtuozzo. They published how to build such a cluster with OpenVZ at [[HA cluster with DRBD and Heartbeat]].

== See also ==

* [[Hosting providers]] — HSPs using OpenVZ
* [[Download mirrors]] — people and companies providing mirrors for OpenVZ software
* [[Control panels]]
* [[2006 contributions]]

Proxmox Mail Gateway in container

2007-11-20T09:45:41Z

Martinmaurer: Updated links pointing to Version 2.1

The Proxmox Mail Gateway 2.1 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-4.0-proxmox-mailgateway-2.1.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.1 --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your environment.

<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 \
--nameserver 192.168.2.100 --nameserver 192.168.2.101 \
--hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB.

<pre>vzctl set 777 --vmguarpages 512M:2147483647 --privvmpages 1G:1100M --diskspace 4000M:4400M --save</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Backup considerations, live migration, and HA Cluster =
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) - All can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups: see [[Backup_of_a_running_VE_with_vzdump]]

Live migration: see [[Checkpointing_and_live_migration]]

For HA Cluster: see http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2007-10-31T09:38:10Z

Martinmaurer: /* Configure the VPS */

The Proxmox Mail Gateway 2.0 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-4.0-proxmox-mailgateway-2.0.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.0 --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your enviroment
<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 --nameserver 192.168.2.100 --nameserver 192.168.2.101 --hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB
<pre>vzctl set 777 --vmguarpages 512M:2147483647 --privvmpages 950M:1G --diskspace 4000M:4400M –-save</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Backup considerations, live migration, and HA Cluster =
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) - All can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups: see [[Backup_of_a_running_VE_with_vzdump]]

Live migration: see [[Checkpointing_and_live_migration]]

For HA Cluster: see http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2007-07-04T10:38:19Z

Martinmaurer: update description

The Proxmox Mail Gateway 2.0 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as with full virtualization - due to the minimal overhead. Proxmox offers free and commercial licenses.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-4.0-proxmox-mailgateway-2.0.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.0 --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your enviroment
<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 --nameserver 192.168.2.100 --nameserver 192.168.2.101 --hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB
<pre>vzctl set 777 --vmguarpages 512M --privvmpages 1G --diskspace 4000M:4400M --save</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Backup considerations, live migration, and HA Cluster =
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) - All can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups: see [[Backup_of_a_running_VE_with_vzdump]]

Live migration: see [[Checkpointing_and_live_migration]]

For HA Cluster: see http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2007-07-04T10:28:05Z

Martinmaurer: Updated links for the new Proxmox 2.0 template

The Proxmox Mail Gateway 2.0 template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as on the virtualization solutions from the market leader - due to the minimal overhead in OpenVZ.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-4.0-proxmox-mailgateway-2.0.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-4.0-proxmox-mailgateway-2.0 --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your enviroment
<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 --nameserver 192.168.2.100 --nameserver 192.168.2.101 --hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB
<pre>vzctl set 777 --vmguarpages 512M --privvmpages 1G --diskspace 4000M:4400M --save</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Backup considerations, live migration, and HA Cluster =
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) - All can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups: see [[Backup_of_a_running_VE_with_vzdump]]

Live migration: see [[Checkpointing_and_live_migration]]

For HA Cluster: see http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Backup of a running container with vzdump

2007-03-29T11:18:01Z

Martinmaurer: examples

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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-0.4-1.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_0.4-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.4-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.4-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
Use a running VE, for example install this: http://wiki.openvz.org/Proxmox_Mail_Gateway_in_VE

== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>

[[Category: HOWTO]]

Proxmox Mail Gateway in container

2007-03-27T07:57:16Z

Martinmaurer: Added backup and live migration

The Proxmox Mail Gateway template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as on the virtualization solutions from the market leader - due to the minimal overhead in OpenVZ.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-3.1-proxmox-mailgateway.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-3.1-proxmox-mailgateway --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your enviroment
<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 --nameserver 192.168.2.100 --nameserver 192.168.2.101 --hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB
<pre>vzctl set 777 --vmguarpages 131072:2147483647 --diskspace 4000000:4400000 --save</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Backup considerations, live migration, and HA Cluster =
The Proxmox HA Cluster consists of a master and several nodes (minimum one node) - All can be run on different OpenVZ servers within the same subnet. Configuration is done on the master, all configuration and data is synchronized to all cluster nodes over a VPN tunnel.

For online backups: see [[Backup_of_a_running_VE_with_vzdump]]

Live migration: see [[Checkpointing_and_live_migration]]

For HA Cluster: see http://www.proxmox.com/cms_proxmox/en/technology/proxmox-ha-cluster/

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Proxmox Mail Gateway in container

2007-03-27T07:41:39Z

Martinmaurer: Initial post

The Proxmox Mail Gateway template is an OpenVZ OS template that allows you to run the Antispam & Antivirus Mail Gateway. Proxmox runs in different virtualization environments but in OpenVZ it is almost twice as fast as on the virtualization solutions from the market leader - due to the minimal overhead in OpenVZ.

= Prerequisites =
I assume you have already a running OpenVZ server. This HowTo is based on an fresh Centos 4.4 installation with OpenVZ kernel 2.6.9 but should work also with all other combinations. I used a Dual Xeon with 2 GB Ram.

= Installation =
Download the Proxmox OpenVZ template
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/bittorrent/debian-3.1-proxmox-mailgateway.tar.gz</pre>

Copy the template into the template cache, usually to /vz/templates/cache/

= Create a default config =
Create a reasonable default config if you don’t have one. The following command creates the file /etc/vz/conf/ve-default.conf-sample which contains reasonable defaults if you plan to run 5 VEs:
<pre>vzsplit -n 5 -f default</pre>

= Create the VPS =

Choose a free VPS ID, we use 777 inside this guide and
<pre>vzctl create 777 --ostemplate debian-3.1-proxmox-mailgateway --config default</pre>

= Configure the VPS =

Set IP Address and DNS nameservers, start servers automatically at boot time: please adapt these settings to your enviroment
<pre>vzctl set 777 --onboot yes --ipadd 192.168.2.110 --nameserver 192.168.2.100 --nameserver 192.168.2.101 --hostname proxmox --searchdomain yourdomain.tld --save</pre>

Set guaranteed memory to 512MB, maximum disk space to 4GB
<pre>vzctl set 777 --vmguarpages 131072:2147483647 --diskspace 4000000:4400000 --save</pre>

And finally set the root password:
<pre>vzctl set 777 --userpasswd root:YOURPASSWORT</pre>

= Start the VPS =

<pre>vzctl start 777</pre>

Now you have a running Proxmox! By typing vzlist you should have something like this.
<pre>[root@vz1 ~]# vzlist
VEID NPROC STATUS IP_ADDR HOSTNAME
777 56 running 192.168.2.110 proxmox
[root@vz1 ~]#</pre>

= Proxmox configuration =
For the Proxmox configuration point your web browser to the given IP address.

More information on http://www.proxmox.com

[[Category: HOWTO]]
[[Category: Templates]]

Backup of a running container with vzdump

2007-03-26T16:13:22Z

Martinmaurer: /* Installation */

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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-0.4-1.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_0.4-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.4-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.4-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>

[[Category: HOWTO]]

Backup of a running container with vzdump

2007-03-26T16:12:55Z

Martinmaurer: Update downloadlinks pointing to 0.4-1

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
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-0.4-1.noarch.rpm</pre>

For Debian based systems:
<pre>wget http://www.proxmox.com/cms_proxmox/cms/upload/vzdump/vzdump_0.4-1_all.deb</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.3-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.3-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>

[[Category: HOWTO]]

Backup of a running container with vzdump

2007-03-23T10:36:52Z

Martinmaurer:

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/

For rpm based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump_0.3-1_all.deb</pre>

For Debian based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump-0.3-1.noarch.rpm</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.3-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.3-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>

[[Category: HOWTO]]

Backup of a running container with vzdump

2007-03-23T10:07:59Z

Martinmaurer: Initial post

= Vzdump =
Vzdump is an utility to make consistent snapshots of running OpenVZ VEs. It basically creates a tar archive of the VE private area, which also includes the VE configuration files.

There are several ways to provide consistency:

- Stop the VE during backup (very long downtime)

- Use rsync and suspend/resume (minimal downtime)

- Use LVM2 (no downtime)

Vzdump stores the backup on the disk in a single file. This file should go to a tape backup for archiving.

== Download ==
Download vzdump rpm or deb packages from http://download.openvz.org/contrib/utils/vzdump/

For rpm based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump_0.3-1_all.deb</pre>

For Debian based systems:
<pre>wget http://download.openvz.org/contrib/utils/vzdump/vzdump-0.3-1.noarch.rpm</pre>

== Installation ==
For rpm based systems:
<pre>rpm -i vzdump-0.3-1.noarch.rpm</pre>

For Debian based systems:
<pre>dpkg -i vzdump_0.3-1_all.deb</pre>

== Synopsis ==

<pre>vzdump OPTIONS [--all â <VEID>]

--compress compress dump file (gzip)

--dumpdir DIR store resulting files in DIR

--xdelta create a differential backup using xdelta

--mailto EMAIL send notification mail to EMAIL

--stop stop/start VPS if running

--suspend suspend/resume VPS when running

--snapshot use LVM snapshot when running

--restore FILENAME restore FILENAME
</pre>

= Examples =
== Backup ==

Simply dump VE 777 - no snapshot, just archive the VE private area and configuration files to the default dump directory (usually /vz/dump/).

<pre>vzdump 777</pre>

Use rsync and suspend/resume to create a snapshot (minimal downtime).

<pre>vzdump --suspend 777</pre>

Backup all VEs and send notification mails to root.

<pre>vzdump --suspend --all --mailto root</pre>

Use LVM2 to create snapshots (no downtime).

<pre>vzdump --dumpdir /space/backup --snapshot 777</pre>

== Restore ==

Restore above backup to VE 600

<pre>vzdump --restore /space/backup/vzdump-777.tar 600</pre>