A recovery path your backup team can explain.
No account is required. Share your environment and the recovery question you want to explore.
For backup administrators and MSP engineers, VaulTrust turns recovery into an ordered review: read the integrity evidence, satisfy the approval gate, then restore with server-side safeguards and an audit trail.
This is an explanatory walkthrough of the current product behavior. It does not load a customer workspace, and the labels and fields below are not customer records.
- 01
Integrity summary
Start with the evidence the workspace can actually show.
The summary is a compact read of protected-workload coverage, finding severity, and the latest verification evidence. It gives an operator a bounded starting point before any recovery action is considered.
The summary vocabularyThese are explanatory labels from the existing summary contract. A live workspace supplies its own counts and timestamps.
HealthyThe latest completed verification passed.
At riskEvidence exists, but the latest verification did not pass.
No dataNo protected workload or integrity evidence is available yet.
Coverage
Protected workload count
The number of protected workloads in the current workspace summary.
Findings
Low countMedium countHigh countCritical countCounts are grouped by low, medium, high, and critical severity.
Latest finding
Newest observed finding timestamp, or no record
Latest verification
Pass or fail with completion time, or no completed verification
- 02
Quorum approval
Make the recovery decision require distinct kinds of proof.
When the auto-heal path reaches its approval boundary, the restore is not armed by a single browser action. The existing M-of-N policy evaluates distinct approver kinds on the server.
Default gate: 2 of 2Recovery not armedThe day-one default is a minimum of two distinct kinds, with a two-kind cap. Quorum is met only after the threshold is reached.
agent_telemetryStamped server-side when the quarantine is created.
admin_sessionThe first human approval from an authenticated administrator.
second_adminAn optional second human kind for a hardened policy.
The important boundary: telemetry is carried server-side, and the human kinds are existing admin approvals. Until the required distinct kinds are present, the quarantine remainsawaiting_quorumand recovery cannot be mounted. - 03
Restore safeguards
Select, execute, and record the recovery under one boundary.
Once quorum is met, the server chooses the recovery target and advances the state machine. The restore path keeps the chosen snapshot, execution result, replay behavior, and audit visibility tied together.
What happens after approvalChoose the recovery point
The server selects the latest clean snapshot that is still unlocked, bounded before the quarantine request when that timestamp is available. When quorum is met, that chosen snapshot is WORM-locked before the restore is started.
Run the restore with explicit states
The state can move through
revertingtorestored, or end in a recordedfailedstate. If no clean snapshot exists, the approval route reports that condition rather than inventing a restore target.Prevent replay and keep the trail visible
The idempotency key makes a terminal replay return as already applied instead of firing the restore again. Successful and failed restore attempts write a RestoreLog entry, while the audit operations surface makes restore and quorum recovery activity reviewable.
revertingThe restore call is in progress.
restoredThe VM snapshot revert completed successfully.
failedThe restore or an earlier safeguard failed, with a reason recorded.
clearedAn operator released the quarantine without performing a restore.
Keep exploring
See the full operating model behind the walkthrough.
Explore VaulTrust features, or talk with the team about how this recovery path fits your VMware workloads and MSP operating model.