Settings

The admin-only Settings page is where you tune how ProxDR behaves. A table of contents (a sticky rail on wide screens, a Jump to… menu on narrow ones) lets you jump between sections.

Replication / DR planning type (topology)

Choose how this site participates in DR: a simple single active/passive pair, or a multi-site hub, mesh, or guest fan-out topology. This governs how pairs relate and how capacity is planned across incoming pairs.

Operator defaults

Set the defaults new work inherits — target RPO, recovery storage, whether recovered guests power on, and the console session timeout.

Dual control for failover

Turn on two-person approval and pick which operations require a second approver. See Users & security.

Web console URL

Advertise the address peers should use to deep-link back to this console. This is the same value offered in the first-run wizard.

Replication limits

Bound replication with bandwidth caps, blackout windows, and concurrency limits so DR traffic doesn’t crowd production.

Sync settings with paired sites

Optionally mirror settings to your paired sites so both ends of a pair stay consistent, and pull the latest on reconnect.

Controller backup & restore

Back up the controller’s configuration (its database and keys) and restore it from the UI — so a lost controller is quickly rebuildable. You can also do this from the CLI.

Experimental features

Opt into capabilities that are built but still being validated on production hardware, from a dedicated, clearly-labeled section. Each is local to this site (not synced across a pair) and off by default unless noted:

• Cross-site DR control — drive DR operations from either paired site over the peer link. Shipped and validated, so this one is on by default; you can still turn it off.
• Native ZFS send/receive — for ZFS-to-ZFS pairs, replicate with zfs send | recv instead of the universal dirty-bitmap engine. Enable it on both sites of the pair.
• Fast reverse baseline — after a planned failover, skip the full whole-disk re-seed on the first reverse cycle: ProxDR quiesces the source at fence time so the recovery copy is exact, then establishes the reverse baseline with a small incremental — and lets forward protection resume incrementally after failback too. It always falls back to a full seed on any doubt, and never applies to an unplanned (down-primary) failover. ZFS/LVM-thin volumes only.
• Whole-disk failback verify — a belt-and-braces companion to Fast reverse baseline. With it off (the default), a fast-baseline failback trusts its change-tracking and verifies only the ranges it shipped — near-instant. Turn it on to additionally re-read the whole disk on both sides and compare byte-for-byte before trusting the copy, at the cost of a few minutes of local reads. Either way, any mismatch falls back to a full re-seed.

Continue to the CLI reference for host-side tasks.