Plan and install
Sizing guidelines
A quick sizing model for Datamotive deployments, with links to detailed Easy Hybrid DR Management Server and Replication Node sizing.
- Product
- Datamotive Platform
- Version
- v1.0
- Documentation status
- Published
- Last updated
- Updated
- Reading time
- 1 min read
Sizing starts with workload count, changed-data rate, recovery objectives, source platform behavior, WAN capacity, and cloud quota readiness. Use this page for first-pass planning, then use the product-specific sizing page before production deployment.
Key input variables
Collect these values before selecting a deployment size:
- Protected workload count - the number of VMs or instances in scope.
- Protected disk count - the number of disks that can replicate in parallel.
- Average changed data per disk - the expected changed data per replication interval.
- RPO target - the maximum acceptable time between recoverable checkpoints.
- WAN capacity and latency - sustained throughput available for replication.
- Target cloud quota readiness - vCPU, disk, snapshot, NIC, IP, and API limits in the recovery region.
First-pass replication sizing
| 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 ranges assume approximately 500 MB of changed data per disk per 30-minute replication interval. Actual sizing depends on churn, fragmentation, source storage latency, cloud write behavior, and recovery concurrency.
Bandwidth planning
For steady-state replication, estimate bandwidth from changed data per interval:
Required Mbps = (changed data GB per interval * 8192) / interval secondsThen adjust for compression, deduplication, peak concurrency, and headroom. Do not use link bandwidth alone as the sizing metric; source reads, cloud writes, and API throttling can become the limiting factor.
Scale out
Use multiple Replication Nodes for large environments:
| 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+ |
Detailed sizing
Was this page helpful?