๐Ÿ’พ Database Backups

The Database Backup & Restore feature helps ensure your restaurant data is protected and recoverable. Whether youโ€™re updating the system, migrating servers, or guarding against accidental loss, backups keep you covered with minimal effort.


๐Ÿ” Why Use Database Backups?

  • โœ… Data protection โ€“ Safeguard records from corruption or accidental deletion.

  • ๐Ÿ”„ Recovery made simple โ€“ Quickly revert to a previous state if needed.

  • ๐Ÿ’ผ Business continuity โ€“ Prevent disruptions and maintain smooth operations.

  • ๐Ÿง  Peace of mind โ€“ Be confident that your data is secure before making major changes.


โš™๏ธ How to Use

๐Ÿ“ค Creating a Backup

  1. Go to: Database Backups

  2. Click the โ€œGenerate Backupโ€ button.

  3. The system will generate a .sql file and save it to the server.

๐Ÿ›‘ Note: Backup files are not downloadable from the browser for security reasons. Youโ€™ll need server access (e.g., via FTP or control panel) to retrieve them.


๐Ÿ“ฅ Restoring a Backup

  1. Navigate to > Database Backups

  2. Click the โ€œRestoreโ€ button next to the desired backup.

  3. Confirm the restore process โ€“ this will overwrite your current database.

โš ๏ธ Always double-check before restoring โ€” this action cannot be undone.


๐Ÿงน Managing Backups

  • Old backups can be deleted to free up space.

  • We recommend retaining at least the latest 3โ€“5 backups on the server.

  • Use timestamps to identify backup versions.


๐Ÿ”„ Backup Best Practices

Task

Recommendation

Backup Frequency

Weekly (daily for active restaurants)

Before Updates

Always create a backup before system changes

Storage

Keep copies safely on the server or in secured cloud/server-side locations

File Management

Use a consistent naming pattern (e.g., backup-2025-07-19.sql)


๐Ÿ› ๏ธ Troubleshooting

  • Restore fails? Ensure the backup file is valid and the server has write permissions.

  • Cannot create backup? Check storage limits and file access rights.

  • Missing data after restore? Confirm the correct file was used.

Last updated