CLI tasks & recovery

These are the commands you’ll reach for when the UI isn’t the right tool — a locked -out password, a controller rebuild, or scripting setup. All accept the global --data-dir flag.

Reset the admin password

Locked out of the console? Reset it from the host:

proxdr auth set-password [--password PW]

Omit --password to be prompted. This is the documented recovery path when the first-run admin password is lost.

Back up & restore the controller

Protect the thing that protects everything else — the controller’s own config:

proxdr backup [--out FILE]        # write a config backup (DB + keys)
proxdr restore --in FILE          # restore one (run with the daemon stopped)

Restoring rebuilds a lost controller from a backup. You can also do both from Settings → Controller backup & restore in the UI.

Licensing

proxdr license [status]           # show licensing / trial state
proxdr license activate --key KEY # install an activation key
proxdr license deactivate         # remove the key (revert to trial)

Remotes (Proxmox connections)

proxdr remote add ...             # add a cluster/node
proxdr remote list                # list managed remotes
proxdr remote test [--name NAME]  # test connectivity (all, or one)
proxdr remote rm --name NAME      # remove a remote
proxdr inventory                  # list resources across all remotes

Site identity & pairs

proxdr site [rename --name NAME]  # show / rename this site's identity
proxdr pair add ...               # configure a DR Site Pair to a peer
proxdr pair list                  # list pairs
proxdr pair rm --uuid UUID        # remove a pair

Disaster-recovery operations

Drive failover, failback and DR tests headless. These call the local daemon and honour the same guards (and audit log) as the UI — most operators run DR from the web console, but the CLI is here for scripts and break-glass access.

proxdr dr status                              # each guest's DR posture (source / recovery)
proxdr dr failover  --pair UUID --vmid N      # boot the guest at the RECOVERY site
proxdr dr failback  --pair UUID --vmid N      # return the workload HOME (final delta + boot)
proxdr dr test      --pair UUID --vmid N      # start an isolated, non-disruptive DR test
proxdr dr test-stop --pair UUID --vmid N      # tear down a running DR test
proxdr dr reseed    --pair UUID --vmid N      # rebuild the DR copy onto the primary

Add --reason TEXT to record why in the audit log. Run proxdr dr status to find a pair’s UUID.

proxdr dr reseed is the recovery path for a diverged or stalled reverse lane — it forces a full reverse re-seed so the next failback has a clean copy to work from, without any database surgery. It’s the CLI equivalent of the Rebuild DR copy button on a guest’s replication page.

Everything here has a UI equivalent — the CLI just lets you do it headless or in a script.