Workflows
Failback
Reverse replication returns recovered workloads to the original source site — entity types, differential vs full transfer, and the reverse wizard.
- Product
- Easy Hybrid DR
- Version
- v2.0.3
- Last updated
- Updated
- Reading time
- 2 min read
Failback (reverse replication) replicates recovered workloads back to their original source site after a failover. The Reverse action is available at plan level under Actions on the target site, and only after the plan is fully recovered. Reverse is supported between AWS, VMware, and Azure (in any combination).
Step 1 — Reverse plan: choose the recovery entity type
| Entity type | Behavior |
|---|---|
| Maintain Original | Reuses the original source VM for reverse replication. Example: if "mm-app" failed over, the same "mm-app" VM on the source receives the replicated data. |
| Create New Copy | Creates a new VM instead — for example "mm-app-dm-reversed" — and replicates into it. |
Step 2 — Virtual machines: replication type
Datamotive validates whether the original source VM and its last replicated snapshot still exist, and recommends a transfer type per VM:
- Differential — only data changed on the DR site is replicated back. Recommended when the original VM and snapshot are intact.
- Full — the entire VM data is replicated back.
If you override the recommendation, the selection is highlighted and an alert explains the impact; Apply Suggested restores the recommended choices.
Steps 3–8 — The familiar plan wizard, in reverse
The remaining steps mirror the protection plan wizard, now pointing back at the original source:
- Recovery configuration — instance type, encryption key, and network per VM; network fields come prefilled from the original source VM.
- Boot order — boot delay and order for the returning VMs.
- Replication configuration — start time, interval, encryption, compression, dedupe, plus Remove Associated Checkpoints (selected by default — deletes preserved checkpoints on the initial target site). AWS replication priority is available under Advanced Options.
- Scripts — plan-level replication and recovery scripts.
- Point-in-time configuration — optional checkpointing for the reversed direction.
- Summary — review and click Finish.
On success, replication jobs start for the plan's VMs in the reverse direction — monitor them under Jobs → Replication. Once the reversed plan is in sync, recover on the original site to complete the round trip, then clean up leftover volumes (the source-site cleanup option appears after the plan is reversed and recovered).
Related docs
Was this page helpful?