Proxmox Cluster with members running different versions of PMX

[rgproxmox1]

Hi,

I have a cluster running 3.4-6 with 3 members and I want to add a new member but that member is running 4.4-18. Can that be done? Will I be able to migrate VMs back and forth? (Maybe at first it would be OK if I can't migrate VMs). Can I keep the VM that I have created in the 4.4-18 server? I've made sure its ID doesn't conflict with the IDs of the VMs in the cluster. If there was a way to make sure that I can preserve the disk and then re-create the config I guess that would be OK (The disk is 4.5TB large, so I can't take a backup at the moment). Thanks

 

[LnxBil]

I have a cluster running 3.4-6 with 3 members and I want to add a new member but that member is running 4.4-18. Can that be done?

No, too much change. Almost everything is changed indeed. Biggest change from any PVE versions.

Will I be able to migrate VMs back and forth?

I've seen at least one guy who did it manually, but there is no online-upgrade path from 3 to 4.

Can I keep the VM that I have created in the 4.4-18 server? I've made sure its ID doesn't conflict with the IDs of the VMs in the cluster.

If adding would work (which does not), you'd loose the VM configuration files, because you always should add an empty node to a cluster the the pvecm assumes that (IIRC).

If there was a way to make sure that I can preserve the disk and then re-create the config I guess that would be OK (The disk is 4.5TB large, so I can't take a backup at the moment). Thanks

Yes, disks are preserved, yet why do you have local vms on a cluster node?

 

[rgproxmox1]

Thanks. I ended up installing a PMX 3.X server given your comments.

Local VMs on a cluster node:
- we use the local ones for DB servers sometimes. Better performance with the local drive. We also use other VMs that are not local, which allows us to take advantage of the cluster features.

 

[aderumier]

Hi,

I have a cluster running 3.4-6 with 3 members and I want to add a new member but that member is running 4.4-18. Can that be done? Will I be able to migrate VMs back and forth? (Maybe at first it would be OK if I can't migrate VMs). Can I keep the VM that I have created in the 4.4-18 server? I've made sure its ID doesn't conflict with the IDs of the VMs in the cluster. If there was a way to make sure that I can preserve the disk and then re-create the config I guess that would be OK (The disk is 4.5TB large, so I can't take a backup at the moment). Thanks

you can mix proxmox 3 && 4 nodes, because of corosync2 in proxmox4, not compatible with corosync1 in proxmox3.

If you have only vm, and if you can have downtime, simply upgrade to proxmox4, and reboot all nodes, you'll not loose your config.

It's possible to do it without downtime and live migration, but It's a little bit tricky, I have posted a procedure on the forum last year to do it.