Metadata management

Datamotive separates workload data from metadata. Workload data moves only between your protected and recovery sites; metadata lives in the Management Servers you deploy — there is no external service involved.

What the Management Server maintains

The Management Server coordinates platform activity while maintaining:

• Operational metadata — sites, nodes, protection plans, recovery configurations, boot orders, schedules.
• Workflow state — replication iterations, recovery/migration jobs, point-in-time checkpoint jobs and their statuses.
• Inventory information — discovered VMs, protected machines, disk associations, platform details.
• Recovery orchestration logic — checkpoint catalogs, preserved checkpoints, playbooks, scripts.
• Monitoring data — events, alerts, reports, bandwidth statistics, RPO/RTO tracking.
• Users, roles, and privileges — see RBAC.

Metadata does not include block-level disk content, file contents, or application data from protected workloads — that data flows only through the replication path between your sites.

Where metadata lives

Each Management Server hosts an internal database (the mysqld service on the node). Both sites' management nodes hold the state needed for their role; replication metadata transfers between nodes alongside the data path, secured like all inter-node traffic (see Ports).

Sensitive values are protected — for example, email credentials configured for notifications are encrypted before being saved to the database.

Operational notes

• The internal database is one of the core services checked during service verification — it starts first in the documented restart order.
• Database revert during an upgrade rollback is a manual, support-guided procedure — see Unsupported configurations.
• Exported playbooks capture a plan's configuration and current state, doubling as portable plan documentation.

Related docs

• Control plane

• Maintenance

• RBAC