---
title: "Best Practices"
canonical: "https://sesame-software-documentation.refined.site/space/bandr/386596888/Best%20Practices"
format: markdown
---
Protect your business-critical data and stay compliant by following these recommended best practices when using **Sesame Software Backup and Recovery**.

![ChatGPT Image Feb 24, 2026, 08_51_09 AM.png](media://829e46a9-528f-4883-9904-529dca9eff1c)

---

## 📅 **1. Use a Combination of Automated and Manual Backups**

**Best Practice Checklist:**

- ✔️ Automate backups to run daily or hourly.
- ✔️ Run manual backups before major imports, updates, or structural changes.
- ✔️ Periodically verify your backup schedules and permissions.

> ℹ️ Combining automation with manual on-demand backups ensures maximum protection without extra effort.

---

## 📂 **2. Define Clear Backup Scopes**

- Include all critical parent and child objects.
- Review your backup scopes regularly as your org structure evolves.
- Exclude unnecessary objects to reduce storage costs.

> ℹ️ Regular scope reviews help you balance thorough protection with efficiency.

---

## 🧪 **3. Test Your Backups with Recovery Tests**

**How to Stay Ready:**  
✅ Schedule periodic recovery tests.  
✅ Use a sandbox or staging environment when possible.  
✅ Document the recovery steps so your team is prepared.

> ℹ️ A tested backup is a reliable backup.

---

## 🔐 **4. Implement Robust Data Retention Policies**

Use the **GDPR Clean** feature to automate compliance:

- Select your backup, object, and date field.
- Define retention in days.
- Create multiple tasks for different object needs.
- Deactivate, edit, or delete rules as requirements change.

> ℹ️ Retention policies keep your database lean and compliant.

---

## 📊 **5. Monitor Backup Status & Review Logs**

Keep backups healthy:

- Check backup status in **Details** for success rates and performance trends.
- Use interactive graphs for daily records and API calls.
- Download SoapTrace logs for deeper troubleshooting.

> ℹ️ Logs and graphs help you catch issues early and plan for growth.

---

## ⚠️ **6. Maintain a Clear Error Response Process**

- Use the `RJ_RECOVERY_RECORD` table and `DELETE_FLAG` codes to investigate recovery states.
- Rerun recoveries for missing objects or failed updates.
- Use the **Records** page to clean up duplicates efficiently.

| **Delete Flag** | **Meaning** |
| --- | --- |
| D | Deleted |
| I | Inserted |
| U | Updated |
| R | Recover |
| RU | Recover Update |
| RC | Recovery Completed |
| RE | Recovery Error |

> ℹ️ Understanding flags and logs keeps your recovery process smooth.

---

## 📅 **7. Schedule Periodic Reviews**

✔️ Audit your backup frequency, scope, and retention rules at least quarterly.  
✔️ Adjust your strategy as data volumes grow or regulations change.

> ℹ️ Regular reviews future-proof your backup strategy.

---

## 🔑 **Key Takeaway**

> Combine automation, thoughtful scoping, testing, and clear retention policies for a bulletproof backup plan - giving you confidence that your data is protected and always recoverable.