> For the complete documentation index, see [llms.txt](https://codehas.gitbook.io/repair-box/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/repair-box/tools/database-backup.md).

# 🗄️ Database Backups

The Database Backup & Restore feature ensures your restaurant data is always safe and recoverable. Whether you’re migrating servers, applying updates, or protecting against accidental loss, backups give you confidence and continuity — with minimal effort.

<figure><img src="/files/T90OV4MmGcLZccAqlLpR" alt=""><figcaption></figcaption></figure>

***

#### 🔐 Why Use Database Backups?

* ✅ Data Protection – Safeguard essential records from corruption or accidental deletion.
* 🔄 Easy Recovery – Quickly restore your system to a previous working state.
* 💼 Business Continuity – Avoid disruptions and maintain smooth daily operations.
* 🧠 Peace of Mind – Make changes knowing your data is secure and backed up.

***

#### ⚙️ How to Use

<br>

**📤 Creating a Backup**

1. Go to  > Database Backups
2. Click “Generate Backup.”
3. A .sql backup file will be created and saved securely on your server

<br>

> ⚠️ Note: Backup files are not downloadable from the browser for security reasons.

> You’ll need server access (FTP or control panel) to retrieve the files manually.

***

**📥 Restoring a Backup**

1. Navigate to  > Database Backups
2. Locate the desired backup file
3. Click “Restore.”
4. Confirm the restoration – your current database will be overwritten

<br>

> ⚠️ Warning: This action is irreversible. Always double-check before proceeding with a restore.

***

#### 🧹 Managing Backups

* Old backups can be safely deleted to conserve server space
* It’s recommended to retain the latest 3–5 backups for redundancy
* Use the timestamped file names to identify versions (e.g., backup-2025-07-23.sql)

***

#### 🔄 Backup Best Practices

| Task             | Recommendation                                          |
| ---------------- | ------------------------------------------------------- |
| Backup Frequency | Weekly backups (daily for high-activity environments)   |
| Before Updates   | Always create a fresh backup before updating the system |
| Storage          | Keep backup copies on server or secure cloud storage    |
| File Naming      | Use consistent naming patterns for easy tracking        |

***

#### 🛠️ Troubleshooting

* Restore Fails?

  → Check if the backup file is valid and if the server has proper write permissions.
* Can’t Create Backup?

  → Make sure there’s enough storage space and correct file permissions on the server.
* Missing Data After Restore?

  → Confirm you selected the correct backup file version.