---
title: "How it works"
canonical: "https://sesame-software-documentation.refined.site/space/bandr/374505479/How%20it%20works"
format: markdown
---
![image]()

Sesame Software’s **Backup and Recovery** solution leverages a straightforward yet powerful architecture to protect your Salesforce data. It operates using the source-target model: Salesforce serves as the **data source**, and your preferred **target database** - Oracle, SQL Server, or PostgreSQL - acts as the destination for securely storing your backup.

The product is designed for fast deployment and intuitive use through a **web-based interface** that allows you to manage backups with minimal technical overhead. Whether you're backing up manually or on a recurring schedule, the process is optimized for **speed, control, and data integrity**.

### 📝 **Core Process Overview**

1. **Establish Connections**  
Begin by configuring your **Salesforce connection** and selecting your **target database** (Oracle, SQL Server, or PostgreSQL). These configurations define the scope of the backup and where the data will reside.
2. **Configure Backup Settings**  
Through the UI, you can:
  - Choose which objects and fields to include
  - Set filters or exclusions
  - Define retention policies
  - Enable alerts for job status or failures
3. **Run or Schedule Backups**  
Backups can be executed **on demand** or **automated** to run at custom intervals using a built-in scheduler. This flexibility supports near real-time backup workflows without relying on external cron jobs or scripts.
4. **Secure Storage**  
Backups are stored directly in your target database in a **queryable, non-proprietary format**, giving you full access and ownership of your data.
5. **Recovery & Restore**  
When needed, the system allows you to **restore Salesforce data down to a single record** or an entire object - without overwriting unrelated data. You can select any historical point-in-time snapshot to restore from, making it easy to recover from errors, deletions, or data corruption.
6. **Monitor & Manage**  
Use the centralized dashboard to view job history, monitor current activity, and manage your backup definitions. Built-in reporting and logging help ensure transparency and traceability.

---

### 🔑 **Key Benefits**

- **User-Friendly Interface** – No need to write queries or code custom scripts
- **Granular Control** – Backup and recover objects or records with precision
- **Enterprise-Grade Security** – All data stays within your configured environment
- **Transparent Architecture** – Your data remains accessible and fully under your control
- **Scalable** – Suitable for teams managing multiple Salesforce orgs or large data volumes

---

### 🏅 **Best Practices for Salesforce Backup and Recovery**

| **Category** | **Best Practice** | **Why It Matters** |
| --- | --- | --- |
| **Connection Setup** | Use a dedicated integration user for Salesforce connections. | Prevents disruptions from changes to personal user accounts or permissions. |
|  | Use read-only access where possible. | Minimizes risk and adheres to the principle of least privilege. |
| **Backup Scheduling** | Schedule backups during off-peak hours. | Reduces load on the Salesforce org during business-critical hours. |
|  | Align backup frequency with the rate of data change. | Ensures critical data is captured without overconsuming resources. |
| **Retention Policies** | Balance retention length with storage costs and compliance requirements. | Keeps storage efficient while supporting audit and regulatory needs. |
|  | Periodically review and remove outdated backups. | Optimizes performance and reduces clutter in the target database. |
| **Target Database** | Index tables on commonly queried fields. | Improves performance during restore and reporting operations. |
|  | Use a separate schema or database for backups. | Enhances data isolation, organization, and security. |
| **Restore Operations** | Test restore workflows regularly. | Confirms that backups are valid and recovery procedures are understood. |
|  | Use point-in-time restore selectively. | Restores only what’s needed, avoiding unnecessary data rollback. |
| **Monitoring & Alerts** | Enable alerts for failed or missed backup jobs. | Helps teams stay proactive in resolving issues promptly. |
|  | Review logs and job history regularly. | Maintains operational visibility and ensures long-term backup success. |