Planning
Sizing
Sizing guidance for Management Servers, Replication Nodes, platform-specific concurrency, horizontal scale, and recovery preparation.
- Product
- Easy Hybrid DR
- Version
- v2.3.1
- Release status
- GA
- Documentation status
- Published
- Last updated
- Updated
- Reading time
- 2 min read
Size Easy Hybrid DR from the workload set outward: source platform behavior, changed-data volume, WAN capacity, cloud API limits, and recovery concurrency all influence the final architecture. Add nodes horizontally when one node cannot sustain the required RPO or recovery concurrency.
Management Server deployment formats
| Platform | Deployment format |
|---|---|
| VMware | OVA |
| Nutanix | OVA |
| AWS | Cloud-native AMI |
| Azure | Cloud-native VM image |
Management Server sizing
The Management Server is the control-plane component for UI, CLI, REST APIs, policy management, replication orchestration, recovery orchestration, scheduling, monitoring, alerting, reporting, inventory, metadata, and day-0 through day-N workflows.
| Environment scale | vCPU | Memory | Storage |
|---|---|---|---|
| Very small | 4 vCPU | 8 GB | 120 GB SSD |
| Small | 4 vCPU | 16 GB | 200 GB SSD |
| Medium | 8 vCPU | 24 GB | 500 GB SSD |
| Large | 16 vCPU | 32 GB | 1 TB SSD |
| Very large | 32 vCPU | 64 GB | 2 TB SSD |
Actual Management Server sizing depends on protected workload count, recovery orchestration concurrency, historical data retention, reporting needs, API activity, and multi-site deployment scale.
Replication Node sizing
Replication Nodes execute the data-plane operations: block-level replication, incremental change processing, rolling-window transport, parallel stream handling, descriptor-driven chunk scheduling, data integrity validation, cloud-native storage writes, recovery reads, flow control, and recovery checkpoint finalization.
| Deployment scale | vCPU | Memory | Network | Recommended workloads | Recommended parallel disks |
|---|---|---|---|---|---|
| Very small | 4 | 8 GB | Up to 500 Mbps | Up to 30 | 60 to 80 |
| Small | 4 | 16 GB | 1-5 Gbps | 30 to 60 | 80 to 200 |
| Medium | 8 | 32 GB | 10 Gbps | 60 to 150 | 200 to 500 |
| Large | 16 | 64 GB | 10-30 Gbps | 150 to 300 | 500 to 1000 |
| Very large | 32 | 128 GB | 50 Gbps+ | 300+ | 1000+ |
These recommendations assume approximately 500 MB of changed data per disk per 30-minute replication interval. Compute-optimized instance families are recommended for large-scale deployments because replication operations are highly parallel.
Platform-specific replication scale
Replication scale varies by source platform, storage behavior, changed-block fragmentation, WAN quality, recovery concurrency, and cloud-native storage throttling.
VMware-based replication scale is influenced by CBT fragmentation, snapshot performance, VDDK read concurrency, datastore latency, snapshot chain depth, WAN throughput, and target cloud storage write throughput.
| Metric | Recommended scale per Replication Engine |
|---|---|
| Parallel replication jobs | Approximately 60 to 80 protected disks |
| Recommended parallel VMs | 30 to 40 VMs |
| Recommended sustained throughput | Approximately 1 Gbps WAN replication |
These are conservative values for fragmented enterprise VMware workloads. Actual scale depends on disk size distribution, average churn, CBT fragmentation, storage latency, and WAN quality.
Horizontal scaling guidance
For large enterprise environments, scale horizontally with multiple Replication Nodes.
| Environment size | Recommended Replication Nodes |
|---|---|
| Fewer than 50 workloads | 1 |
| 50 to 300 workloads | 2 to 4 |
| 300 to 1000 workloads | 4 to 8 |
| More than 1000 workloads | 8+ |
Horizontal scale increases aggregate throughput, distributes API usage, improves recovery concurrency, reduces node-level contention, and improves operational isolation.
Prep Node sizing
The Datamotive Prep Node is a Windows-based recovery preparation appliance deployed in the recovery environment. It is activated during Windows workload recovery, cross-platform migration, recovery preparation, boot remediation, and file system or registry compatibility checks.
| Metric | Recommended scale |
|---|---|
| Parallel Windows recoveries per Prep Node | Up to 20 workloads |
For larger recovery events, deploy additional Prep Nodes horizontally or use instance types that support a larger number of attached disks.
DeDup Node planning
The Datamotive DeDup Node is an optional optimization component in the recovery environment. It maintains chunk checksum indexes, previously transferred block metadata, deduplicated chunk references, and chunk reuse mappings.
Enable a DeDup Node when repeated block patterns are expected across the workload set or when WAN and cross-cloud transfer cost reduction are important. It is particularly effective for one-time migration use cases, similar workload datasets, and large-scale enterprise environments.
Deduplication effectiveness depends on workload similarity, operating system standardization, retention duration, and replication interval frequency.
Related docs
Was this page helpful?