DRBD for OpenVZ Containers

[hisaltesse]

I read your documentation on the wiki about DRBD and setting up the additional storage device etc.

One thing I am unclear about is:

- How can DRBD be used for OpenVZ containers? I only use proxmox for OpenVZ containers. I don't care about KVM etc… and I would like to understand how I can setup HA with DRBD for the purpose of having the other server take over in case a component fails on the first server.

- My configuration on each Proxmox server is: Proxmox installed on the main storage drive which is provided by a hardware RAID controller configured in RAID 10.

Your help would be appreciated. Thanks.

 

[udo]

Hi,
can't work without an hack. Because you need an clusterfilesystem (mounted on both systems) and you must change the migration! Normaly migration use rsync (in this case very fast, because the data already there) and than remove the data on the old node - due DRBD this remove the data also on the new node! And all is gone...

Udo

 

[Duduhandelman]

Im using something similar.
Two machines sync via drbd /var/lib/vz and the configuration located on the shared disk.
I'm using heartbeat to mount the drbd drive and start the vz service.
It's an active passive cluster only one host is up.

It's the best ha solution that I found for Linux.

You can read about this setup at the openvz wiki.

Good luck.

 

[Riverman]

Hi,

I'm interested in this kind of installation too. I realize that vzmigrate will rsync all files even if it's there, but what do I need to change?
I looked into vzmigrate and found this:

online=0
verbose=0
remove_area=1
keep_dst=0
debug=0
confdir="/etc/vz/conf"
vzconf="/etc/vz/vz.conf"
tmpdir="/var/tmp"
act_scripts=

Could this be the changes needed together with DRBD?
online=1
remove_area=0
keep_dst=1

Is there something else that need to be handle?