Choose Your Evaluation
Start from the outcome you need to prove. This page chooses the route; the linked guide contains the implementation steps.
Which Route Fits?
| Your starting point | Use this route | Proof you should leave with |
|---|---|---|
| New to XReplicator | Quickstart: Prove One Restore | One verified backup and one restored file |
| XReplicator is already running | First Restore Test | A recorded restore result from an existing restore point |
| Installing packages on VMs | Installation | Healthy server, UI, and connected agent before the restore test |
| Kubernetes is part of the evaluation | Kubernetes and Helm deployment | A working cluster deployment followed by the same first restore proof |
| Testing Azure disaster recovery | Azure-to-Azure DR | A documented precheck, failover, and recovery result |
| Evaluating multi-customer operations | MSP and Enterprise | Tenant, operator, scale, and commercial requirements agreed |
If you have not used XReplicator before, run the Quickstart with one non-production machine. Do not begin with production topology or multiple workloads.
What Counts as Success?
Every backup evaluation should end with recovery evidence, not only a green backup job. Record:
- The protected machine and restore point.
- The verification mode and result.
- What was restored and where.
- Whether the recovered data matched the expected result.
- Any blocker to resolve before expanding the evaluation.
After the first restore passes, use the Restore Challenge for a broader team evaluation or review Deployment Models before production rollout.
Last updated on