The roles of backup and replication
Backup provides recovery from historical points. Replication prepares a second environment for a specific source-target pairing. A second copy alone does not replace historical backups and retention policies.
REPLICATION & BUSINESS CONTINUITY
A prepared second environment.
A planned recovery.
Maintaining backup history and preparing a second recovery environment serve different needs. Plan both around your business continuity objectives.
STEP-BY-STEP GUIDES
From installation to recovery.
01
02
Replication Guide
Prepare replication acceptance with site mappings, the first Full seed, incremental generations and a verified checkpoint.
Open guide02Disaster Recovery Guide
Prepare service recovery with checkpoint selection, isolated testing, fencing, controlled failover and failback planning.
Open guideHOW IT WORKS
Steps that work together.
- 01
Define scope
Select the VMs, dependencies and second location.
- 02
Validate the initial transfer
Check target checkpoints and data integrity after the full transfer.
- 03
Track changes
Monitor incremental generations and transfer results.
- 04
Rehearse recovery
Test source isolation, target startup and application access.
DEFINE YOUR SCENARIO
Continue from a verified point
The initial full transfer and subsequent incremental generations in the OpenStack workflow use a verified checkpoint chain. Target data integrity and VM startup are evaluated together during environment acceptance.
Map source and target together
Define target cloud, volume backend, flavor and network mappings in advance. Correct target-side storage and access prerequisites matter as much as data transfer.
Controlled activation
Include isolation, source fencing and operator control in the recovery plan to prevent conflicting services from running at source and target. Plan failback and return to production separately.
COMMON QUESTIONS
Start with
the right questions.
Is zero data loss or a fixed recovery time guaranteed?
RPO and RTO depend on architecture, schedules and application dependencies. No fixed time or zero-loss guarantee is made without measured environment acceptance.
Does this cover VMware and other platforms too?
Each source-target combination requires separate validation. OpenStack replication acceptance does not establish general VMware-to-VMware or VMware-to-OpenStack support.
START WITH YOUR INFRASTRUCTURE
Replication and Disaster Recovery — let’s discuss your needs.
Share your workloads and recovery objectives. Let’s define the technical scope together.
