Skip to content
Datamotive

Configure

Protection plans

Protection plans group workloads with their sites, replication schedule, recovery configuration, and boot order — the unit of replication and recovery.

Product
Easy Hybrid DR
Version
v2.0.3
Last updated
Updated
Reading time
1 min read

Protection plans are the logical groups for protecting workloads. A plan defines the source and target sites, the VMs to protect, their boot order, the replication schedule, and the per-VM recovery configuration. Replication, test recovery, failover, migration, and failback all run against a named plan.

Plans are created through an eight-step wizard — the full walkthrough is in Create a plan. This page covers what a plan contains, the plan dashboard, and the actions available on a configured plan.

What a plan defines

ElementPurpose
GeneralPlan name, protection (source) site, and recovery (target) site.
Virtual machinesThe VMs to protect. On VMware sources, CBT is enabled automatically on selection.
Recovery configurationPer-VM instance type, storage, network, and platform-specific options used to create the recovered instance.
Boot orderRecovery order and per-step boot delay for dependent workloads.
Replication configurationStart time, replication interval (RPO), encryption on wire, compression, dedupe, and reverse-replication options.
ScriptsPre/post replication and recovery scripts at plan and VM level.
Point-in-time checkpointsOptional checkpoint schedule and retention for point-in-time recovery.

Plan dashboard

Click a plan's name to open its dashboard. It surfaces:

  • Protection and recovery site details.
  • Virtual machines — protected machines (size, disks, OS, last run time, recovery status) and their recovery configurations, with per-VM edit actions.
  • Configuration — the settings chosen during plan creation.
  • Point-in-time checkpoints — available and preserved checkpoints. On the target site, checkpoints can be preserved (protected from expiry) or deleted.
  • Replication jobs and point-in-time jobs — per plan, per VM, and per disk. See Jobs.

Plan actions

Actions are context-sensitive: they depend on the plan's state and on whether you are viewing the plan on the protected or the recovery site.

On the source site

ActionBehavior
StartStarts replication for selected VMs. Requires a reason for the audit trail.
StopStops replication — either allow running replications to complete, or stop immediately. Stopping a subset of VMs sets the plan to Partially Running.
EditAdd or remove VMs (removal completes on the next successful iteration), modify recovery/boot/replication/checkpoint/script configuration, or resync disk replication to re-replicate entire disks.
Download PlaybookExports the plan configuration and current state as a playbook file.
RemoveDeletes the plan (must be stopped, with no running jobs). Optionally also deletes associated recovery instances and checkpoints from the target infrastructure.

On the target site

ActionBehavior
Test RecoveryNon-disruptive recovery into an isolated environment. See Recovery testing.
RecoverFull recovery (failover) of protected VMs. See Failover.
MigrateFinal cutover migration of workloads. See Easy Migrate.
ReverseReverse replication back to the original source (failback). Enabled after a full recovery. See Failback.
Cleanup RecoveriesLists test-recovered and recovered copies eligible for cleanup and deletes them from the infrastructure. Cleanup runs as jobs visible under Recovery jobs.
Refresh Recovery StatusRe-validates recovery job status against the actual instance state in the platform. See Status check.

Replication and RPO behavior

The replication interval defines the RPO target. Each iteration replicates changed blocks; the jobs view shows whether each VM is in-sync within the configured interval. The dashboard RPO widget aggregates plan health. Sizing the interval against bandwidth and change rate is covered in the Scale and performance guide.

Related docs

Was this page helpful?