Use backup and restore recovery
Prepare branch backup and restore routines so owners can recover from device failure, wrong changes, or service disruption.
Owners know what to back up, when to verify it, and how to approach restore work without making a bad situation worse.
Before you start
- Know where the branch backup settings and files are managed.
- Limit backup and restore access to owners or trusted operators.
- Keep recovery contacts and installer locations documented.
Create a backup routine
Backups are useful only when they run regularly and owners know where they are.
- Schedule backup review as part of owner operations.
- Keep backup storage separate from a single risky device when possible.
- Record who can access backups and restore tools.
Verify backups
A backup that nobody checks may fail silently. Verification should be simple and regular.
- Check recent backup date and status.
- Confirm backup files are not stored only on a failing machine.
- Review backup health after major updates or hardware changes.
Restore with care
Restore work can overwrite current state. Treat it as an owner or support task, not a normal cashier action.
- Stop and document the current problem before restore work.
- Confirm the restore point and expected result.
- Test core branch flows after recovery before live operation resumes.
Verify it worked
- The owner can identify the latest backup location and date.
- Backup health is reviewed after updates or device changes.
- Restore access is limited to trusted operators.
Troubleshooting
No recent backup exists.
Do not pretend recovery is ready. Set up a backup routine and review device risk with the owner.
Restore might overwrite useful current data.
Pause, document the current state, and confirm the restore point with the owner or support before continuing.