🚧 In development — ProxDR is coming soon. You're viewing an early preview.

ProxDR
📚 Browse docs

Create a DR Site Pair

A DR Site Pair links this site to a second ProxDR controller — your recovery site. Replication and failover happen over this pair. You’ll need ProxDR installed at both sites first.

How pairing works

Pairing is a two-step handshake, done on the Site Pairs page:

  1. On one controller, create a pair. ProxDR generates a short pairing code and shows this site’s fingerprint.
  2. On the other controller, join using that code and the peer’s address.

The two sides authenticate each other, pin each other’s fingerprints, and establish a mutually-authenticated (mTLS) link on the peer port (:8444). Every message across the link is authenticated against the pair — there’s no global trust, so one controller can safely hold many independent pairs.

Over the internet

You don’t need a VPN for security: both the control channel and the replication data plane are mutually TLS-authenticated. A pair works across the internet with a public IP and port-forwarding to the peer port. At scale, teams often still put the data plane inside a WireGuard/IPsec tunnel because it uses a dynamic per-disk port range — convenient, not a security requirement.

Roles and direction

A pair has a primary (production) and a recovery side. Roles swap on failback — after you fail over and later return home, ProxDR reprotects in the original direction. Multi-site topologies (hub, mesh, guest fan-out) are selectable in Settings.

Next