Workflows
Status check
The replication sync-status vocabulary, job statuses, plan running states, and the refresh recovery status workflow.
- Product
- Easy Hybrid DR
- Version
- v2.0.3
- Last updated
- Updated
- Reading time
- 1 min read
Datamotive reports health at three levels: protection plan running state, per-iteration job status, and per-VM sync status. This page is the vocabulary reference, plus the procedure for re-validating recovery status against the platform.
Plan running states
| State | Meaning |
|---|---|
| Initializing | The plan was just created and is getting initialized. |
| Running | Replication is enabled for all VMs. |
| Partial | Replication is disabled for at least one VM. |
| Stopped | Replication is disabled for all VMs. |
The plan header also shows the configured RPO with met/breached status per VM, and an in-sync count (VMs in sync within the configured RPO out of the plan total).
Replication job statuses
| Status | Meaning |
|---|---|
| Completed | Replication iteration completed successfully. |
| Running | Replication is running. |
| Partially Completed | Replication completed with errors. |
| Failed | Replication failed. |
| Queued | Scheduled; starts after a running job completes. |
VM sync statuses
| Sync status | Meaning |
|---|---|
| init-in-progress | First iteration is running. |
| init-sync-in-progress | First iteration is running and data transfer has started. |
| init-success | First iteration completed successfully. |
| init-sync-failed / init-failed | First iteration failed. |
| sync-in-progress | Data transfer in progress (second iteration onward). |
| in-sync | Iteration completed within the configured replication interval. |
| exceeded interval | Iteration completed but took longer than the configured interval — the RPO was missed. |
| sync-failed | Replication iteration failed. |
| resync-in-progress | Recovery configuration changed or reset-disk was used; disks are re-replicating. |
| resync-success / resync-failed | Outcome of the resync operation. |
Recovery job statuses
Recovery jobs (test, full, migration) report Completed, Started, Partially Completed (completed with errors — for example a failed post-script), or Failed, plus the recovered instance's IP address. Windows recoveries include an extra validation step; guests that cannot be validated show Pending CSP Validation.
Refresh recovery status
When a recovery job shows Pending CSP Validation or Failed but the instance state in the platform has changed (for example after you fixed the underlying issue), re-validate:
Open the refresh wizard
In the recovery jobs view, click Actions → Refresh Recovery Status. By default, all VMs in the full recovery / migration window are selected.
Retrieve and confirm
After the latest status is retrieved from the platform, either reset the workload status to its previous state or click Confirm Recovery Status to update it. Fix the issue causing Pending CSP Validation on the VM before confirming.
Close
Completed statuses move to the recovery page; remaining Pending CSP / Failed statuses stay visible in the refresh view.
Related docs
Was this page helpful?