Planning
Prerequisites
Baseline infrastructure, cloud, source environment, and operational prerequisites for scalable Easy Hybrid DR deployments.
- Product
- Easy Hybrid DR
- Version
- v2.3.1
- Release status
- GA
- Documentation status
- Published
- Last updated
- Updated
- Reading time
- 2 min read
Use this page before sizing or onboarding production workloads. The scale and performance guidance in the docs assumes the infrastructure, cloud account, source platform, and operating model meet these baseline conditions.
Infrastructure assumptions
Cloud assumptions
Cloud targets must be prepared before protection plans are placed into production:
- Enterprise cloud subscriptions or accounts are active.
- Datamotive has the IAM permissions required for replication and recovery workflows.
- Cloud quotas can be increased before large-scale onboarding or DR testing.
- Recovery compute capacity is available in the target region or zone.
Hypervisor and source assumptions
Source environments must be healthy enough for frequent snapshot and changed-block operations:
- Changed Block Tracking or an equivalent changed-region mechanism is enabled where applicable.
- Snapshot creation, deletion, and consolidation operate normally.
- Source storage latency is within vendor-recommended limits.
- Supported hypervisor and cloud versions are deployed.
- Backup tools, snapshot tools, and migration tools are scheduled so they do not contend with replication windows.
Operational assumptions
Operational readiness matters as much as infrastructure capacity:
- Replication schedules are staggered for large environments.
- DR drills and recovery testing are performed periodically.
- Recovery networks, DNS, IAM, and quota readiness are validated during drills.
- Protection plans are grouped so large recoveries can be executed in controlled batches.
- Monitoring is configured for cycle duration, RPO drift, queue depth, node pressure, and cloud throttling.
Scalability assumptions
The sizing and performance pages assume:
- Rolling-window replication protocol v2 is enabled.
- Multi-threaded replication is enabled.
- Replication nodes use the recommended sizing profile for their workload set.
- Horizontal scaling is used for large environments.
Actual scale depends on workload change rates, CBT fragmentation, WAN bandwidth and latency, cloud API behavior, storage throughput, and recovery concurrency.
Related docs
Was this page helpful?