Skip to content
Datamotive

Common workflows

Initial deployment

Deploy and configure the Datamotive nodes — Management, Replication, DeDupe, Windows Prep, and Day2Operation — and verify the installation.

Product
Datamotive Platform
Version
v2.0.3
Last updated
Updated
Reading time
2 min read

This workflow deploys the Datamotive nodes and verifies the installation. Complete the Prerequisites first — deployment location, networking and firewall rules, and platform roles.

Deploy the nodes

Each node ships as an OVA for VMware (deploy via vCenter GUI, OVFTool, or ESXi) and as a native machine image for AWS, GCP, and Azure (deploy via the cloud console; enable IMDSv2 on AWS). Image names follow the pattern dm-<type>-<platform>-<version>, e.g. dm-mgmt-VMware-<version>.ova, dm-repl-AWS-<version>, dm-dedupe-GCP-<version>, dm-win-prep-Azure-<version>, dm-dop-VMware-<version>.ova.

After deploying each node, configure its networking (static IP — see Firewall) and reboot.

Configure each node

  1. Management Node

    Open https://<vm-ip>:5000/mgmt to validate the GUI — the Datamotive login screen should render. Log in with the default credentials Administrator / admin and change the default password.

  2. Replication and DeDupe Nodes

    In the Management Server console, go to Nodes in the left navigation and click Add Node. Enter the node details — the node's name must match the name of the deployed VM. Default credentials are Administrator / admin. Successful registration confirms correct deployment.

  3. Windows Prep Node

    Deploy and register the same way via Nodes → Add Node (name must match the VM name). The default system credentials are Administrator / M0v3@nywh3r3.

  4. Day2Operation Node (optional)

    Deploy with default credentials Administrator / admin. It provides a centralized monitoring portal across the DR estate.

Verify the installation

  1. Console reachable

    Open https://<management-node-ip>:5000. The login screen should display (a self-signed-certificate warning is expected).

  2. Services running

    If the UI does not render, SSH into the node and check the mysqld, nginx, dm-auth, dm-mgmt, dm-repl-server, dm-repl-client, and dm-mon services. Restart order and Day2Operation services: Maintenance.

  3. Networking validated

    Run the telnet/nc connectivity checks between management, replication, prep, and dedupe nodes, plus external access for cloud deployments: Maintenance — network validation.

Optionally replace the self-signed SSL certificate with a CA-signed one — see Maintenance — SSL.

Next steps

With nodes deployed and verified, register the remote management node, create sites, and install the license — then you're ready for the first replication.

Related docs

Related articles

Was this page helpful?