ProxDR documentation

What ProxDR is, and the core concepts — sites, DR Site Pairs, and protected guests.

One-line install on a Linux host, the systemd service it sets up, and the ports it uses.

Set the admin password on first launch and step through the optional onboarding wizard.

Update an existing install to the latest release with one command, pin a version, or roll back.

Add the Proxmox cluster this controller manages, via SSH auto-provisioning or an API token.

Pair your production controller with a recovery-site controller using a pairing code and pinned fingerprint.

Choose where recovered VMs run, map production networks to recovery networks, and keep IPs on failover.

A tour of the ProxDR console — the navigation, the Overview dashboard, and where each task lives.

Connect and manage the Proxmox clusters this controller sees — nodes, guests, storage, and live utilization.

Create, join, and manage the DR Site Pairs that link this site to its recovery sites.

Protect guests, set RPO, use recovery points and the ransomware guard, restore from backups, and run failover, DR tests, and planned migration.

See every recovery replica across your sites — active and orphaned — and reclaim storage from replicas that are no longer needed.

Group guests into ordered runbooks with boot order and dependencies, then run failover or a DR test as one orchestrated operation.

Turn DR tests into exportable evidence, and schedule recurring tests and reports.

Understand the trial, activate a key, manage your pair pool, and how offline validation keeps DR running.

Accounts and roles (RBAC), dual-control approvals, the audit log, and automation hooks.

Topology mode, operator defaults, dual-control, web console URL, replication limits, settings sync, controller backup, and experimental features.

Running the daemon, the global data-dir flag, TLS options, and checking the version.

Quality-of-life commands — reset the admin password, back up and restore the controller, manage licensing, remotes, and pairs from the shell.

ZFS pvesr, Ceph RBD mirroring, the storage backends Proxmox can't replicate, and how QEMU dirty-bitmap replication fills the gap.

What RPO and RTO mean for Proxmox disaster recovery, how to choose them per workload, and how replication interval and orchestration drive each metric.