Use backups
Use branch backups as an operator safety habit for setup recovery, support handoff, and safer changes.
The owner and supervisors know when to create backups, where to check backup status, and when restore should be handled carefully.
Before you start
- Use an owner/admin account.
- Confirm the branch Controller service is reachable.
- Avoid restore actions during active customer sessions unless support instructs you.
When to create a backup
Create backups before changes that affect many branch records or before support investigates a risky issue.
- Back up before major setup changes.
- Back up before large imports or restructuring work.
- Back up before applying a recovery process you are unsure about.
Check backup health
A backup habit only helps if backups are actually created and available when needed.
- Review backup status after setup milestones.
- Keep notes on what changed after a backup.
- Check cloud or local backup warnings when available.
Restore carefully
Restoring can change branch state. Treat it as an operational decision, not a casual troubleshooting click.
- Avoid restoring during busy live operation.
- Confirm which data will be affected.
- Ask support or the owner before restoring if active sessions or recent cashier work may be impacted.
Verify it worked
- A backup exists after major setup is completed.
- The owner knows where backup status is shown.
- Staff understand that restore actions require care.
Troubleshooting
Backup status is unavailable.
Check Controller service availability and branch network health before assuming backup data is missing.
A restore may overwrite recent live work.
Pause and confirm the restore scope with the owner or support before proceeding.