Skip to content

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
v2.0.3
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:

  1. Protected workload count - the number of VMs or instances in scope.
  2. Protected disk count - the number of disks that can replicate in parallel.
  3. Average changed data per disk - the expected changed data per replication interval.
  4. RPO target - the maximum acceptable time between recoverable checkpoints.
  5. WAN capacity and latency - sustained throughput available for replication.
  6. Target cloud quota readiness - vCPU, disk, snapshot, NIC, IP, and API limits in the recovery region.

First-pass replication sizing

Deployment scalevCPUMemoryNetworkRecommended workloadsRecommended parallel disks
Very small48 GBUp to 500 MbpsUp to 3060 to 80
Small416 GB1-5 Gbps30 to 6080 to 200
Medium832 GB10 Gbps60 to 150200 to 500
Large1664 GB10-30 Gbps150 to 300500 to 1000
Very large32128 GB50 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:

text
Required Mbps = (changed data GB per interval * 8192) / interval seconds

Then 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 sizeRecommended Replication Nodes
Fewer than 50 workloads1
50 to 300 workloads2 to 4
300 to 1000 workloads4 to 8
More than 1000 workloads8+

Detailed sizing

Was this page helpful?