[TUTORIAL] What Replaces SRM and vSphere Replication on Proxmox?

bbgeek17

Distinguished Member
Nov 20, 2020
6,738
2,689
278
Blockbridge
www.blockbridge.com
Hi Everyone,

Disaster recovery keeps coming up with folks moving off VMware, usually as some version of "what replaces SRM?" We've answered pieces of this in threads for years, so we finally sat down and wrote the whole thing up properly.

Mapping VMware DR Features to Proxmox VE: SRM, vSphere Replication, and Site Recovery https://kb.blockbridge.com/technote/proxmox-vmware-disaster-recovery/

The technote maps each VMware DR feature to its nearest native PVE equivalent: pvesr and pve-zsync, the PBS two-site pattern, the HA manager, PDM, stretched clusters with Ceph stretch mode, and array-based replication. It also walks through what doing SRM's job by hand involves: configurations, identity, addressing, start order, and testing. There's a feature mapping table at the end if you want the one-screen version. We stuck to native tooling; third-party tools exist but are out of scope here.

Everything was checked against current docs (PVE 9.2 / PBS 4.2 / PDM 1.1) or confirmed in our lab, and where we couldn't verify something, we say so. One thing we'll say up front: we have never run Ceph RBD mirroring failover ourselves, and public operational reports are scarce. If you've run it through a real or rehearsed site failure, we'd love to learn more and update the doc.

If you're doing DR on PVE in a way we didn't cover, or you think we got something wrong, post it here. We'll update the article.

As always, let me know if you have questions, corrections, or if we've missed anything!

Enjoy, The Blockbridge Team!


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hi,

Thanks for your link.

We have run Ceph RBD mirroring (by pool, by image, snapshot-based and journal-based, one-way, two-ways). Not in production environment. Working as expected. Requires some care during implementation...

It needs some user friendly integration in WebUI, otherwise only advanced users can deploy.

But it is an essential feature - the multi-cluster equivalent of intra-cluster pvesr.

No doubt Proxmox Team is working on this.

Christophe.
 
Thanks, @christophe! That's more configuration coverage than most reports we've found. "The multi-cluster equivalent of intra-cluster pvesr" is a good way to put it.

Since you've run both modes in both directions, a few things you're in a rare position to answer:

1. What did "some care during implementation" involve? For example, journal mode needs the journaling feature enabled per image, which requires librbd and doesn't mix with the krbd storage option. Was it that kind of thing, or something else?

2. What did you observe on the primary side while a peer was unreachable? Journal growth in journal mode, or mirror-snapshot buildup in snapshot mode? Space behavior during an outage is where we have the least data.

3. Did you ever end up in split-brain after a forced promote? The docs say resync deletes the image and copies from scratch. Curious how long that took at your sizes, or whether you found a better path.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox