Troubleshooting
Common errors
Frequent issues and their fixes — console unreachable, node version mismatch, RPO breaches, recovery validation, and cleanup.
- Product
- Easy Hybrid DR
- Version
- v2.0.3
- Last updated
- Updated
- Reading time
- 1 min read
The most frequent operational issues, their likely causes, and the documented fixes.
Deployment and connectivity
| Symptom | Likely cause | Action |
|---|---|---|
| Console at https://<ip>:5000 unreachable | Datamotive services not running on the node | SSH in and check/restart services in the documented order (mysqld, nginx, dm-auth, dm-mgmt, dm-repl-server, dm-repl-client, dm-mon). See Maintenance. |
| Browser shows certificate warning | Nodes ship with a self-signed certificate | Expected. Replace with a CA-signed certificate via nginxCertsReplace.sh when required. |
| Nodes cannot reach each other | Security groups / firewall rules missing required ports | Run the telnet/nc validation matrix in Maintenance and compare against the Ports reference. |
| Node shows two IP addresses in the platform manager | Cloud-init netplan file still enables DHCP alongside the static IP | Disable DHCP in the extra netplan file under /etc/netplan, apply, reboot. A node must hold exactly one IP. |
| Node registration fails in Add Node | Node name does not match the deployed VM name, or wrong credentials | Use the exact VM name and the node credentials (Administrator/admin default). |
Replication
| Symptom | Likely cause | Action |
|---|---|---|
| Replications on hold after an upgrade | Source and target node versions mismatch | Upgrade the remaining nodes — replication resumes when versions match. The console shows a click-to-upgrade shortcut. |
| Sync status "exceeded interval" (RPO missed) | Bandwidth below the change rate, throttling too aggressive, or too many disks per node | Verify ≥150 Mbps dedicated per loaded node, review Settings → Throttling, or add replication node pairs (1 per 40 disks). |
| VMware VMs fail to replicate | CBT not enabled or VMware Tools missing | Re-run the plan wizard and accept the Enable CBT prompt; install VMware Tools in every protected VM. |
| More than 100 disks queued on AWS target | AWS limits parallel snapshot writes to 100 per account | Datamotive replicates 80 and queues the rest. Set per-VM replication priority, or switch VMs to EBS volume target storage. |
| Whole disks re-replicating unexpectedly | Recovery configuration changed or reset disk used (resync) | Expected behavior — sync status shows resync-in-progress; the next iterations return to incremental. |
Recovery
| Symptom | Likely cause | Action |
|---|---|---|
| Recovery job stuck at "Pending CSP Validation" | Windows guest validation could not complete against the platform | Fix the issue on the VM, then use Actions → Refresh Recovery Status to re-validate and confirm. See Status check. |
| Recovery job "Partially Completed" | A pre/post script exited non-zero | Check the script output; scripts must be executables (Shell, Bash, Python 3.x, Golang) and complete within the timeout (default 300 s). |
| Static IP not applied to recovered VM | Install System Agents not selected, missing credentials, or unsupported guest | Select Install System Agents, provide guest credentials, and confirm guest support (Windows; CentOS/RHEL 7.8–8.x, SLES 15 SP3 with nmcli). |
| Reverse (failback) only offers Full transfer | Recovered from a point-in-time copy, VMware target, or original snapshot missing | Expected per the reverse differential matrix — see Unsupported configurations. |
| Cloud costs climbing after drills | Test-recovered instances left running | Run Actions → Cleanup Recoveries → Cleanup Test Recoveries after every drill. |
Getting help
If the issue is not listed, generate a support bundle (Settings → Tech Support → + Generate, with a description of the problem), download it once complete, and send it with the plan name and job details to support@datamotive.io.
Related docs
Was this page helpful?