Azure DR Proof

Measured Azure-to-Azure DR drill

Review measured Azure-to-Azure disaster recovery timing for XReplicator, including failover strategy, test scope, RTO variables, and validation steps.

Attach as-is

Under 40 seconds

Measured on a VM with a 30 GB OS disk and 4 GB data disk when staged DR disks were healthy and synced.

Best fit for production recovery when the staged disks are ready and the priority is fastest VM creation.

Create from snapshot

Around 70 seconds

Measured on the same VM while creating isolated snapshot-derived disks before the recovered VM was created.

Best fit for drills, validation, or controlled recovery where an isolated copy is preferred.

Published Test Scope

  • Product path: XReplicator v1.3.1 Azure-to-Azure DR orchestration.
  • Measured workload: one Azure VM with a 30 GB OS disk and 4 GB data disk.
  • Failover choices measured: attach already-synced staged disks directly, and create isolated disks from snapshots.
  • Readiness requirement: DR sources were healthy and synced before failover.
  • Validation target: creation of the recovered Azure VM using the selected DR blueprint path.

Why Your RTO May Differ

Disaster recovery timing depends on more than backup software. These measurements are most useful when compared against your Azure environment, VM profile, and application startup requirements.

  • Azure control-plane response time during the failover window.
  • Target VM size and regional capacity.
  • Operating system boot time.
  • Network, identity, DNS, and application startup dependencies.
  • Whether recovery attaches staged disks directly or creates isolated copies first.

RTO Planning Notes

  • The timing above is a measured drill result, not a universal RTO guarantee.
  • Larger disks, different VM sizes, regional capacity, network design, and application startup requirements can change recovery time.

How To Validate In Your Environment

  1. Pick a representative non-production Azure VM.
  2. Enable Azure-to-Azure DR and wait for healthy staged disks.
  3. Run strict precheck before the drill.
  4. Trigger failover using attach as-is and record VM creation time.
  5. Repeat with snapshot-based recovery if isolated disk copies are required.
  6. Record OS-ready and application-ready times separately from VM-created time.

Related DR Resources

Disaster Recovery overviewAzure DR runbookAzure-to-Azure DR docs