10-Minute Recovery. 10-Minute Failback. Every Single Time.
Traditional DR vendors promise recovery windows. Easy Hybrid DR engineers them - a flat, predictable 10-minute RTO for both failover and failback, verifiable in a live test before you sign.
Predictable 10-minute recovery — for both failover and failback.
*The 10-minute RTO applies to the failover and failback cutover under validated SLA conditions. Failback follows reverse synchronization and primary-site readiness validation. Verify the target in a live DR test with your own workloads.
Measurable Outcomes
Real results from enterprise DR deployments
Why CIOs Choose Easy Hybrid DR
Four architectural decisions that make predictable 10-minute recovery possible - every time, regardless of workload size.
Flat 10-Minute Failover - No Asterisks
The 10-minute recovery window is engineered into the architecture - not a best-case estimate. Pre-validated runbooks and automated orchestration fire the moment you trigger failover.
- Automated orchestration
- Pre-validated runbooks
- Health checks built-in
Failback in the Same 10 Minutes
Return to primary in the same 10-minute window. No manual reconfiguration, no data re-sync delays, no multi-day return window. Most DR vendors don't even offer a failback SLA.
- Reverse replication
- Delta sync only
- Same 10-min SLA, reversed
Multi-Cloud Freedom. Zero Lock-In.
Fail over between supported combinations - VMware to AWS, AWS to Azure, Nutanix to AWS - and back. Cloud-agnostic failover across supported hybrid and multi-cloud environments. Change your DR target at any time without re-architecting.
- Agentless architecture
- Cloud-agnostic design
- Single-pane management across VMware, Nutanix, AWS, Azure, and OpenStack
Protection in 90 Minutes, RPO as Low as 1 Minute
RPO as low as 1 minute with change-block tracking. Data lives inside your cloud account using native storage services - no Datamotive-side data custody, ever.
- Near-real-time replication
- Application-aware snapshots
- WAN optimization
Flat 10-Minute Failover - No Asterisks
The 10-minute recovery window is engineered into the architecture - not a best-case estimate. Pre-validated runbooks and automated orchestration fire the moment you trigger failover.
- Automated orchestration
- Pre-validated runbooks
- Health checks built-in
Failback in the Same 10 Minutes
Return to primary in the same 10-minute window. No manual reconfiguration, no data re-sync delays, no multi-day return window. Most DR vendors don't even offer a failback SLA.
- Reverse replication
- Delta sync only
- Same 10-min SLA, reversed
Multi-Cloud Freedom. Zero Lock-In.
Fail over between supported combinations - VMware to AWS, AWS to Azure, Nutanix to AWS - and back. Cloud-agnostic failover across supported hybrid and multi-cloud environments. Change your DR target at any time without re-architecting.
- Agentless architecture
- Cloud-agnostic design
- Single-pane management across VMware, Nutanix, AWS, Azure, and OpenStack
Protection in 90 Minutes, RPO as Low as 1 Minute
RPO as low as 1 minute with change-block tracking. Data lives inside your cloud account using native storage services - no Datamotive-side data custody, ever.
- Near-real-time replication
- Application-aware snapshots
- WAN optimization
Architecture Comparison
Agentless vs. Agent-Based DR
Most DR tools install an agent inside every protected guest OS. Datamotive is agentless — it integrates at the hypervisor layer for virtualized environments (VMware, Nutanix) and through cloud platform APIs for public clouds (AWS, Azure), with no agent in the guest OS.
Agent-Based
- Agent sprawl — deploy and update on hundreds of guests
- Guest-agent CPU and memory overhead
- OS-level version conflicts
- Cross-platform failback may require additional tools or manual processes
Agentless
- No guest-agent footprint on protected workloads
- No guest-agent CPU or memory overhead
- No version conflicts or agent sprawl
- Cross-platform failback across supported environments
How Easy Hybrid DR Works
Steady-state protection, non-disruptive DR testing, failover, recovery operation, reverse synchronization, and failback — ending back at continuous protection, not a fresh setup.
- 1Initial configuration< 90 minutes
Configure Protection
Agentless setup across VMware, Nutanix, AWS, Azure, and OpenStack. Define protection plans, target mappings, and recovery configuration.
- Continuous replication2Steady-state replicationRPO as low as 1 min
Continuous Replication
Block-level incremental replication streams only changed blocks to cloud-native storage on the recovery site. Production runs undisturbed.
- Failover3Production failover10-minute RTO
Failover
Orchestrated recovery boots protected workloads as native instances on the recovery site — network attachment, boot order, and health checks are automated.
- Operate in recovery4Recovery operationDuration of the event
Operate in Recovery Environment
Production traffic runs in the recovery environment. New changes accumulate there and are synchronized back before failback.
- Reverse synchronization5Reverse synchronizationDifferential
Reverse Synchronization
Only data changed in the recovery environment is replicated back to the primary site — differential reverse replication, not a full copy.
- Readiness validation6Readiness validationBefore cutover
Primary-Site Readiness Validation
Confirm the primary site is ready to receive workloads before the failback cutover begins.
- Failback cutover7Final failback cutover10-minute RTO*
Failback Cutover
Cut production back to the primary site once reverse synchronization and readiness validation are complete.
- Resume continuous protection8Resumed protectionSteady state
Resume Continuous Protection
Protection resumes in the original direction — back to continuous replication, not a fresh setup.
Branches from Continuous Replication:
- Isolated DR Drill
- Validate Recovery
- End Test
- Return to Continuous Protection
Runs in an Isolated Test Network. Production keeps running, replication continues uninterrupted, and no production failover or failback occurs.
Easy Hybrid DR continuously replicates protected workloads, supports isolated DR testing, orchestrates failover to the recovery environment, synchronizes changes back to the primary site, and completes failback before continuous protection resumes.
*The 10-minute RTO applies to the failover and the failback cutover under validated SLA conditions. Reverse synchronization and primary-site readiness validation complete before the failback cutover window.
The Real Cost of Legacy DR
Compare what your team actually experiences today versus what Easy Hybrid DR delivers contractually.
Without Datamotive
- Unpredictable, variable RTO — manual runbooks, uncertain outcomes
- Failback is a separate, slower process — often a different team and toolset
- Cloud vendor lock-in — one DR target, no flexibility
- Agent sprawl — software on every VM, version conflicts
- Standby infrastructure cost — pay for idle compute 24/7
- DR tests disrupt production — teams avoid testing at all
With Datamotive
- Flat 10-minute RTO — automated orchestration, verifiable in a live DR test
- Failback in the same 10-minute window — reversed direction
- Cross-cloud flexibility — change DR target at any time without re-architecting
- Agentless — no guest-agent footprint on production VMs
- Pay only on recovery — no persistent standby compute cost
- Unlimited non-disruptive DR drills — test without impacting production
WHY IT MATTERS
Native, agentless Nutanix AHV → AWS EC2 recovery, without requiring Nutanix NC2 clusters in AWS.
Companies running Nutanix AHV on-prem have limited DR options for AWS. Nutanix NC2 on AWS can require expensive bare-metal EC2 instances, traditional DR tools are often built for VMware or cloud-native recovery, and manual migration lacks orchestration, SLA, and real DR readiness.
The Datamotive Solution
Agentless, block-level replication from Nutanix AHV → AWS EC2. Recover natively on AWS without running Nutanix clusters in the cloud.
Datamotive · Nutanix NC2 · Traditional DR
SwipeRecovery architecture
✓ Agentless block-level replication to native AWS EC2
Nutanix clusters running on AWS
Varies by tool and platform
Steady-state AWS infrastructure
✓ AWS EBS snapshot storage — no standby compute
Bare-metal EC2 instances running 24/7
Standby compute and/or storage
Agent model
✓ Agentless
Agentless, with NC2 cluster overhead
Often agent-based
Failover workflow
✓ Automated orchestration to native EC2
Recover inside the NC2 cluster
Frequently manual runbooks
Failback method
✓ Differential reverse replication — changed data only
Full data copy
Varies; often a full data copy
Recovery compute model
✓ Provisioned on failover — no persistent DR compute
Persistent NC2 compute
Often persistent standby
Reverse synchronization
✓ Differential — transfers only changed data
Full copy
Varies by tool
Supported RTO
✓ 10-minute RTO target*
Depends on NC2 cluster scale
Scales with workload size
Evidence / qualification
✓ Verify in a live DR test with your workloads
—
—
| Capability | Datamotive native AWS recovery | Nutanix NC2 on AWS | Traditional DR approaches |
|---|---|---|---|
| Recovery architecture | ✓ Agentless block-level replication to native AWS EC2 | Nutanix clusters running on AWS | Varies by tool and platform |
| Steady-state AWS infrastructure | ✓ AWS EBS snapshot storage — no standby compute | Bare-metal EC2 instances running 24/7 | Standby compute and/or storage |
| Agent model | ✓ Agentless | Agentless, with NC2 cluster overhead | Often agent-based |
| Failover workflow | ✓ Automated orchestration to native EC2 | Recover inside the NC2 cluster | Frequently manual runbooks |
| Failback method | ✓ Differential reverse replication — changed data only | Full data copy | Varies; often a full data copy |
| Recovery compute model | ✓ Provisioned on failover — no persistent DR compute | Persistent NC2 compute | Often persistent standby |
| Reverse synchronization | ✓ Differential — transfers only changed data | Full copy | Varies by tool |
| Supported RTO | ✓ 10-minute RTO target* | Depends on NC2 cluster scale | Scales with workload size |
| Evidence / qualification | ✓ Verify in a live DR test with your workloads | — | — |
Architecture
Nutanix AHV → AWS EC2, Natively
Agentless, block-level replication keeps a recovery-ready copy in AWS storage during steady state. Compute is provisioned on the target only when you fail over — no NC2 clusters in AWS required.
%20--%3e%3csvg%20version='1.1'%20id='Layer_1'%20xmlns='http://www.w3.org/2000/svg'%20xmlns:xlink='http://www.w3.org/1999/xlink'%20x='0px'%20y='0px'%20viewBox='0%200%20304%20182'%20style='enable-background:new%200%200%20304%20182;'%20xml:space='preserve'%3e%3cstyle%20type='text/css'%3e%20.st0{fill:%23252F3E;}%20.st1{fill-rule:evenodd;clip-rule:evenodd;fill:%23FF9900;}%20%3c/style%3e%3cg%3e%3cpath%20class='st0'%20d='M86.4,66.4c0,3.7,0.4,6.7,1.1,8.9c0.8,2.2,1.8,4.6,3.2,7.2c0.5,0.8,0.7,1.6,0.7,2.3c0,1-0.6,2-1.9,3l-6.3,4.2%20c-0.9,0.6-1.8,0.9-2.6,0.9c-1,0-2-0.5-3-1.4C76.2,90,75,88.4,74,86.8c-1-1.7-2-3.6-3.1-5.9c-7.8,9.2-17.6,13.8-29.4,13.8%20c-8.4,0-15.1-2.4-20-7.2c-4.9-4.8-7.4-11.2-7.4-19.2c0-8.5,3-15.4,9.1-20.6c6.1-5.2,14.2-7.8,24.5-7.8c3.4,0,6.9,0.3,10.6,0.8%20c3.7,0.5,7.5,1.3,11.5,2.2v-7.3c0-7.6-1.6-12.9-4.7-16c-3.2-3.1-8.6-4.6-16.3-4.6c-3.5,0-7.1,0.4-10.8,1.3c-3.7,0.9-7.3,2-10.8,3.4%20c-1.6,0.7-2.8,1.1-3.5,1.3c-0.7,0.2-1.2,0.3-1.6,0.3c-1.4,0-2.1-1-2.1-3.1v-4.9c0-1.6,0.2-2.8,0.7-3.5c0.5-0.7,1.4-1.4,2.8-2.1%20c3.5-1.8,7.7-3.3,12.6-4.5c4.9-1.3,10.1-1.9,15.6-1.9c11.9,0,20.6,2.7,26.2,8.1c5.5,5.4,8.3,13.6,8.3,24.6V66.4z%20M45.8,81.6%20c3.3,0,6.7-0.6,10.3-1.8c3.6-1.2,6.8-3.4,9.5-6.4c1.6-1.9,2.8-4,3.4-6.4c0.6-2.4,1-5.3,1-8.7v-4.2c-2.9-0.7-6-1.3-9.2-1.7%20c-3.2-0.4-6.3-0.6-9.4-0.6c-6.7,0-11.6,1.3-14.9,4c-3.3,2.7-4.9,6.5-4.9,11.5c0,4.7,1.2,8.2,3.7,10.6%20C37.7,80.4,41.2,81.6,45.8,81.6z%20M126.1,92.4c-1.8,0-3-0.3-3.8-1c-0.8-0.6-1.5-2-2.1-3.9L96.7,10.2c-0.6-2-0.9-3.3-0.9-4%20c0-1.6,0.8-2.5,2.4-2.5h9.8c1.9,0,3.2,0.3,3.9,1c0.8,0.6,1.4,2,2,3.9l16.8,66.2l15.6-66.2c0.5-2,1.1-3.3,1.9-3.9c0.8-0.6,2.2-1,4-1%20h8c1.9,0,3.2,0.3,4,1c0.8,0.6,1.5,2,1.9,3.9l15.8,67l17.3-67c0.6-2,1.3-3.3,2-3.9c0.8-0.6,2.1-1,3.9-1h9.3c1.6,0,2.5,0.8,2.5,2.5%20c0,0.5-0.1,1-0.2,1.6c-0.1,0.6-0.3,1.4-0.7,2.5l-24.1,77.3c-0.6,2-1.3,3.3-2.1,3.9c-0.8,0.6-2.1,1-3.8,1h-8.6c-1.9,0-3.2-0.3-4-1%20c-0.8-0.7-1.5-2-1.9-4L156,23l-15.4,64.4c-0.5,2-1.1,3.3-1.9,4c-0.8,0.7-2.2,1-4,1H126.1z%20M254.6,95.1c-5.2,0-10.4-0.6-15.4-1.8%20c-5-1.2-8.9-2.5-11.5-4c-1.6-0.9-2.7-1.9-3.1-2.8c-0.4-0.9-0.6-1.9-0.6-2.8v-5.1c0-2.1,0.8-3.1,2.3-3.1c0.6,0,1.2,0.1,1.8,0.3%20c0.6,0.2,1.5,0.6,2.5,1c3.4,1.5,7.1,2.7,11,3.5c4,0.8,7.9,1.2,11.9,1.2c6.3,0,11.2-1.1,14.6-3.3c3.4-2.2,5.2-5.4,5.2-9.5%20c0-2.8-0.9-5.1-2.7-7c-1.8-1.9-5.2-3.6-10.1-5.2L246,52c-7.3-2.3-12.7-5.7-16-10.2c-3.3-4.4-5-9.3-5-14.5c0-4.2,0.9-7.9,2.7-11.1%20c1.8-3.2,4.2-6,7.2-8.2c3-2.3,6.4-4,10.4-5.2c4-1.2,8.2-1.7,12.6-1.7c2.2,0,4.5,0.1,6.7,0.4c2.3,0.3,4.4,0.7,6.5,1.1%20c2,0.5,3.9,1,5.7,1.6c1.8,0.6,3.2,1.2,4.2,1.8c1.4,0.8,2.4,1.6,3,2.5c0.6,0.8,0.9,1.9,0.9,3.3v4.7c0,2.1-0.8,3.2-2.3,3.2%20c-0.8,0-2.1-0.4-3.8-1.2c-5.7-2.6-12.1-3.9-19.2-3.9c-5.7,0-10.2,0.9-13.3,2.8c-3.1,1.9-4.7,4.8-4.7,8.9c0,2.8,1,5.2,3,7.1%20c2,1.9,5.7,3.8,11,5.5l14.2,4.5c7.2,2.3,12.4,5.5,15.5,9.6c3.1,4.1,4.6,8.8,4.6,14c0,4.3-0.9,8.2-2.6,11.6%20c-1.8,3.4-4.2,6.4-7.3,8.8c-3.1,2.5-6.8,4.3-11.1,5.6C264.4,94.4,259.7,95.1,254.6,95.1z'/%3e%3cg%3e%3cpath%20class='st1'%20d='M273.5,143.7c-32.9,24.3-80.7,37.2-121.8,37.2c-57.6,0-109.5-21.3-148.7-56.7c-3.1-2.8-0.3-6.6,3.4-4.4%20c42.4,24.6,94.7,39.5,148.8,39.5c36.5,0,76.6-7.6,113.5-23.2C274.2,133.6,278.9,139.7,273.5,143.7z'/%3e%3cpath%20class='st1'%20d='M287.2,128.1c-4.2-5.4-27.8-2.6-38.5-1.3c-3.2,0.4-3.7-2.4-0.8-4.5c18.8-13.2,49.7-9.4,53.3-5%20c3.6,4.5-1,35.4-18.6,50.2c-2.7,2.3-5.3,1.1-4.1-1.9C282.5,155.7,291.4,133.4,287.2,128.1z'/%3e%3c/g%3e%3c/g%3e%3c/svg%3e)
- Recovery trigger
- Provision AWS resources
- Apply target mappings & network
- Validate workload health
- Activate AWS EC2 (native)
Compute is provisioned only during recovery — AWS EC2 instances do not run during steady-state replication.
- AWS recovery workloads
- Differential reverse synchronization
- Primary-site readiness validation
- Failback cutover
- Nutanix AHV production resumed
Reverse synchronization and readiness validation complete before the failback cutover — not a single symmetric step.
Nutanix AHV workloads are replicated agentlessly to AWS EBS snapshot storage. During recovery, Datamotive provisions and validates native AWS EC2 workloads. Changes are later synchronized back before failback to Nutanix.
*10-minute RTO target under validated SLA conditions — verify in a live DR test.
Who Easy Hybrid DR Is Built For
Predictable recovery means different things to different stakeholders. Easy Hybrid DR delivers on all of them.
A DR Strategy You Can Verify Before You Sign
- Flat 10-minute RTO and failback - verifiable in a live test with your own workloads
- Up to 60% lower TCO vs. traditional DR - no standby compute, no active DR infrastructure
- Recovery across supported hybrid and multi-cloud environments - change your DR target at any time without re-architecting
- 100% data consistency guaranteed - no exposure windows, no compliance risk
Complete Visibility and Control Across Every DR Event
- Single-pane dashboard - monitor RPO/RTO metrics live across all protected workloads
- No agents to manage - agentless architecture eliminates sprawl and version conflicts
- Unlimited DR drills - test failover and failback without impacting production
- Automated runbooks - pre-validated orchestration fires the moment you trigger failover
Deterministic Recovery - Repeatable in Every DR Drill
- Unified dashboard with full visibility across source and target environments
- Single-click recovery workflows powered by integrated scripts
- Deterministic recovery - repeatable in every DR drill
A DR Strategy You Can Verify Before You Sign
- Flat 10-minute RTO and failback - verifiable in a live test with your own workloads
- Up to 60% lower TCO vs. traditional DR - no standby compute, no active DR infrastructure
- Recovery across supported hybrid and multi-cloud environments - change your DR target at any time without re-architecting
- 100% data consistency guaranteed - no exposure windows, no compliance risk
Complete Visibility and Control Across Every DR Event
- Single-pane dashboard - monitor RPO/RTO metrics live across all protected workloads
- No agents to manage - agentless architecture eliminates sprawl and version conflicts
- Unlimited DR drills - test failover and failback without impacting production
- Automated runbooks - pre-validated orchestration fires the moment you trigger failover
Deterministic Recovery - Repeatable in Every DR Drill
- Unified dashboard with full visibility across source and target environments
- Single-click recovery workflows powered by integrated scripts
- Deterministic recovery - repeatable in every DR drill
Questions We Hear Most
Honest answers about Easy Hybrid DR, the 10-minute SLA, and how it compares.
Test It Before You Commit
See the 10-Minute Recovery in Your Own Environment
Book a DR test with your actual workloads. Watch failover and failback happen in real-time. Verify the SLA yourself - no commitment, no synthetic data.