Operate & Monitor Replication
Once a VM is enrolled, you monitor its protection and can drive syncs on demand from the VM's Replication tab. All commands live in the ACTIONS ▾ menu on the replication status header.
Trigger a manual sync
Replication runs automatically on your RPO schedule, but you can force one — for example just before an update or a planned failover.
- Open the VM's Replication tab.
- Click ACTIONS ▾ → Sync Now.
- Watch the task progress. On completion you'll see a success notice and the Last Successful Sync time updates.
TIP
A manual sync just before a planned failover minimizes the final catch-up and the switchover time.
Read replication health
The status panel shows an overall health state:
| Health | Meaning | What to do |
|---|---|---|
| OK | Syncs are succeeding on schedule. | Nothing. |
| Degraded | The last recovery point is valid locally, but the copy to the recovery site had a problem (e.g. an expired site token, or the target briefly unreachable). | Check the site pair and target reachability; the next sync usually recovers it. |
| Error | Sync is failing (e.g. no free space to stage the backup, or the guest can't be reached for a consistent snapshot). | Read the error on the panel and address the cause (below). |
Also on the panel:
- Last Successful Sync — the timestamp of the newest recovery point.
- Recovery points — the historical points retained on the recovery site (your rollback targets for failover).
Recovery points (point-in-time)
Each successful sync creates a recovery point on the recovery site. Retention (set at enrollment) keeps a rolling set of hourly/daily/weekly points and prunes the rest. When you fail over, you recover from the latest point by default; retained older points let you roll back to before a problem (e.g. corruption) occurred.
Behavior worth knowing
- Self-healing chains — if the recovery site is missing the parent a delta depends on (e.g. after cleanup), the source automatically re-establishes a fresh full baseline on the next sync rather than failing forever. You may see one larger sync when this happens.
- Fail-fast on low space — a sync needs local scratch space on the source to stage the backup. If space is short, the sync fails immediately with a clear message (need vs. available) instead of filling the disk. Free space, then it resumes on the next cycle.
- Backoff on repeated failure — after several consecutive failures a job backs off before retrying, so a persistent problem doesn't hammer the host. Fix the cause and it resumes.
- Slow ≠ stuck — a large baseline or a heavily-changed disk can take minutes; the panel reflects progress rather than hanging.
Stop replicating a VM
- On the VM's Replication tab, click Disable Replication and confirm.
- This stops the schedule and removes the recovery points on the recovery site. The VM's live copy at the primary site is untouched.