Schedule backups and retention

1. Enable scheduled backups in Backup & restore. Choose a quiet time and how long to retain old copies; check the company or store timezone.
2. The initial scheduler is already configured. Confirm its heartbeat and the last scheduled run separately: an on-demand or pre-update backup does not prove that the scheduled job ran.
3. Check success or failure after the first scheduled run. Download copies regularly; server retention cannot protect against losing that server. Delete only copies you no longer need.

Restore a selected recovery point

1. Arrange a quiet period and stop other staff entering transactions. Choose Restore beside a stored backup, or upload a known backup archive.
2. Review the backup date, app version and record counts. Restoring replaces current data with that recovery point, including changes made since the backup. Take a current backup first.
3. Complete the explicit confirmation and wait for validation and restore to finish. Do not force an archive that fails validation. Sign in again and check key records and balances.

Create, verify and keep backup copies

• Backup now creates a ZIP containing database records and the included uploads such as product images and the logo. It runs in the background, so you can leave the page and return to its result.
• Wait for the Success row and check time, file size and storage location. Download it and retain several recent copies outside the server. Deleting an old local copy frees server space.
• Schedules use the business timezone. A missed opening minute can catch up once within the allowed daily window; repeated ticks do not start overlapping copies. Check scheduled success/failure separately from manual or pre-update runs.
• Before restore, verify the archive summary and take a current backup. Type the confirmation word and allow the brief maintenance period; staff will sign in again afterwards. Manifest/archive checks block modified or unverifiable files. Contact support for full server recovery without weakening validation.