Architecture
Control plane
Control plane and data plane separation — responsibilities, the Management Server that implements the control plane, and how each scales.
- Product
- Datamotive Platform
- Version
- v2.0.3
- Last updated
- Updated
- Reading time
- 1 min read
The Datamotive architecture separates management and orchestration operations (control plane) from replication data movement and recovery operations (data plane). The control plane is implemented by the Management Server, deployed at both the protected and recovery sites — entirely inside your own infrastructure.
Responsibilities
| Plane | Responsibilities | Implemented by |
|---|---|---|
| Control plane | Scheduling, policy management, inventory tracking, recovery orchestration, monitoring, API management, metadata operations. | Management Server |
| Data plane | Block replication, chunk streaming, flow control, cloud storage writes, data integrity validation, recovery reads. | Replication Nodes (the Management Server also acts as one for small deployments) |
This separation provides better scalability, improved fault isolation, simplified horizontal expansion, and independent scaling of management and replication workloads — replication throughput scales by adding Replication Nodes without touching management capacity, and vice versa.
The Management Server
The Management Server is the central orchestration and control-plane component. It provides the UI, CLI, and RESTful APIs for Day 0–Day N operations, and maintains operational metadata, workflow state, inventory information, and recovery orchestration logic. It hosts an internal database (mysqld) and serves the console and APIs over TLS at port 5000.
All Datamotive appliances are based on CIS-hardened Ubuntu Server images, shipped as OVAs (VMware) or cloud-native machine images (AWS, Azure, GCP).
Sizing by environment scale
| Environment scale | vCPU | Memory | Storage |
|---|---|---|---|
| Very small | 4 | 8 GB | 120 GB SSD |
| Small | 4 | 16 GB | 200 GB SSD |
| Medium | 8 | 24 GB | 500 GB SSD |
| Large | 16 | 32 GB | 1 TB SSD |
| Very large | 32 | 64 GB | 2 TB SSD |
Actual sizing depends on protected workload count, recovery orchestration concurrency, historical data retention, reporting, API activity, and multi-site scale.
Day-2 visibility
For estates spanning many sites, the optional Day2Operation Node adds a centralized monitoring portal — protection plans, alerts, replication status, and operational metrics across the deployed DR infrastructure. See Nodes.
Sovereign and regulated environments
Because the control plane is self-hosted on both sites, no metadata leaves your boundary. Outbound connectivity is required only to the platform-manager APIs of the clouds in use, and carries orchestration calls — no organization data. See the Sovereign Cloud platform page for deployment context.
Related docs
Was this page helpful?