CT Migration between non-clustered Proxmox Servers with Local Storage Only

drott

Member
Apr 18, 2012
53
0
6
USA
Proxmox 2.2 Latest build, running LVM local storage for the CT's

I suspect I am missing something really basic. Looked a wiki, and looked at forums and did some searching.

Working from webui and I wanted to test CT migration between two proxmox servers-non-clustered-running with local storage only.

I am unable to select or otherwise enter the name of the other Proxmox box. It will not let me type in anything.

One could drop into the HN and and do a vzmigrate but would really like to try it from within the webui so as to reduce the risk of misplaced files due to a typeo.

I think the answer based on what I have read is you need at a minimum a two node cluster--preferred is 3 node--but with openvz it is not a requirement that you have a cluster to be able to migrate between machines.

DRBD based on forum postings either has had a number of concerns raised and it looks to have been a bit buggy dur to version lag. Version 9 is now out. There is the perenial concern with split brain for most implementations and recovery does take some effort and there is high risk you can really kill off the ct permanently.

I think DRBD has a lot of viability especially if you use CTs which is what I do. Is it possible to presume that future Proxmox implementations may well have a UI of some type to assist in configuring DRBD so that its done consistently and so that each machine can be identical.

Is there another way to register the non-clustered machine for migration purposes.

Thanks
 
Last edited:
Proxmox 2.2 Latest build, running LVM local storage for the CT's

I suspect I am missing something really basic. Looked a wiki, and looked at forums and did some searching.

Working from webui and I wanted to test CT migration between two proxmox servers-non-clustered-running with local storage only.

I am unable to select or otherwise enter the name of the other Proxmox box. It will not let me type in anything.

One could drop into the HN and and do a vzmigrate but would really like to try it from within the webui so as to reduce the risk of misplaced files due to a typeo.

I think the answer based on what I have read is you need at a minimum a two node cluster--preferred is 3 node--but with openvz it is not a requirement that you have a cluster to be able to migrate between machines.

DRBD based on forum postings either has had a number of concerns raised and it looks to have been a bit buggy dur to version lag. Version 9 is now out. There is the perenial concern with split brain for most implementations and recovery does take some effort and there is high risk you can really kill off the ct permanently.

I think DRBD has a lot of viability especially if you use CTs which is what I do. Is it possible to presume that future Proxmox implementations may well have a UI of some type to assist in configuring DRBD so that its done consistently and so that each machine can be identical.

Is there another way to register the non-clustered machine for migration purposes.

Thanks
Hi,
migration work only clusterwide.

Udo
 
Thanks Udo, That's what I thought.

I was hoping there was another way other than the CLI which you can do with openvz. So may have to play in DRBD purgatory.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!