Disaster recovery and replication

Keep critical services safe with continuous replication, checkpoints about every five seconds, and controlled, tenant-aware failover.

How it works

A primary site running live virtual machines, continuously replicated to a recovery site with checkpoints about every five seconds. At failover, or in a test on a sandboxed network, the replicas are brought online at the recovery site.

Key benefits

  • VM data kept current by ongoing replication, not only backups

  • Checkpoints, journaled recovery and controlled failover

  • Failover tests in a sandboxed network, with live services untouched

  • Replication and recovery coordinated across sites

  • Replication restored after temporary failures, with no replanning

  • VMs brought online at the recovery site, for faster service restoration

Feature breakdown

  1. Continuous replication, per disk

    Replicate Proxmox VMs continuously and manage replication for each disk, since not every disk matters equally. You get better recovery points and a strategy that fits real workloads.

  2. Journaling, checkpoints and retention

    Journals and checkpoints keep recovery possible through changes and disruptions, so teams use set recovery points instead of last-minute rollbacks. Retention-aware recovery balances options with efficient operations.

  3. Failover and sandboxed testing

    Run a live failover, or a test on sandboxed networking that leaves production untouched. Regular testing becomes routine, not a once-a-year event.

  4. Cross-site coordination and recovery-site VMs

    Replication and recovery stay in sync across sites and carry on through temporary interruptions. VMs are built and brought online at the recovery site, shortening recovery time.

What it means in practice

Offer resilient tenant services with verifiable DR readiness.

Be ready before you need it