Before you start
You need access to the backup scope and the corresponding write permission for recovery actions. Establish which newer material must be preserved and who authorised the intended restoration.
What to do
- Open Backups and select the intended scope, such as Nexus & designs or Websites & databases. Review capture status and existing recovery points before creating another.
- Select Browse files for the intended recovery point and check its identifier and creation time. Search for the exact backed-up path rather than choosing a similarly named file.
- Use Recover a separate copy when that separate recovery is intended and permitted. Inspect the resulting operation and recovered location before relying on it; do not assume it replaced the live material.
- For an eligible individual file, use Preview restore and review the exact path and recovery point. The interface states that the current file will be backed up first; retain that predecessor and the operation evidence.
- Use Restore this file only when its exact replacement scope is intended and the action remains available. Database files and protected recovery locations can be blocked from this individual-file action.
- Inspect the final operation output, the restored file and the affected application. A successful capture or recovery message alone is not proof that the intended material is usable.
What happens next
You can distinguish an inspected recovery point, a separate recovered copy and an accepted individual-file replacement, with evidence for the actual scope performed.
If something goes wrong
Check scope, file search and capture status when a recovery point or file is missing. A disabled restore can indicate an unsupported file type, protected path or unavailable current-file check; do not bypass it with a broader restore. If the live file changed after preview or the outcome is uncertain, preserve current state and ask the infrastructure administrator to reconcile it before another attempt.
