Sadly, replication where the storages have different names is not (yet) supported. You'd need to rename one of the pools (can be done with zpool export/import rather easily).
Different storage devices shouldn't lead to any problems, but as already said, live migration between CPUs from different vendors won't always work (it might if you're lucky, but there's a reason we don't officially support it
). HA with only two servers is not possible, because you don't have quorum when the other server is down.Okay, so this is currently out of my scope to rename my storage different.Sadly, replication where the storages have different names is not (yet) supported. You'd need to rename one of the pools (can be done with zpool export/import rather easily).
Different storage devices shouldn't lead to any problems, but as already said, live migration between CPUs from different vendors won't always work (it might if you're lucky, but there's a reason we don't officially support it
There also is pve-zsync (needs to be installed manually), where the storage names don't need to be the same. But it's also less tightly integrated, so e.g. migration won't recognize that the disks are already replicated.
Yes, you should not live-migrate then. For offline migration there also is a
targetstorage option, but it's not (yet) exposed in the UI.The current solution if VM is offline is only backup from server B and restore on server A - this is not really "sexy".
Thanks pve-zsync sounds interessting to me.
That requires some manual interaction as described in the wiki article. But with two nodes, you don't have quorum when one is down. That means you can't write to
/etc/pve/, start VMs etc. You can add a QDevice to assist with quorum, but maybe you don't even want a two node cluster at all (pve-zsync also works with standalone nodes).Membership information
----------------------
Nodeid Votes Qdevice Name
0x00000002 1 A,V,NMW 10.0.5.1 (local)
0x00000003 1 A,V,NMW 10.0.5.2
0x00000000 1 Qdevice