> For the complete documentation index, see [llms.txt](https://codehas.gitbook.io/restaurant-pos-pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codehas.gitbook.io/restaurant-pos-pro/more/database-backups.md).

# 💾 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

<figure><img src="https://1701705512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJYpDkVSaO95YKamONp0g%2Fuploads%2FoStTpuSA73bIM6XSHH6p%2Fimage.png?alt=media&amp;token=24a2753d-3c6d-46f1-a214-297fe5f96ede" alt=""><figcaption></figcaption></figure>

**📤 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.

<br>

> 🛑 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.

<br>

> ⚠️ 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.