Backup Scheduler for Salesforce Data Recovery Automation

The data your business runs on deserves better than a 15-day recycle bin

Salesforce holds your pipeline, your customer relationships, your contracts, and your revenue history. When data is accidentally deleted, overwritten by a bad import, or corrupted by a third-party integration, Salesforce gives you 15 days to notice — and a recycle bin that restores records without their related data intact.

For mid-sized enterprise IT teams, that is not a recovery strategy. It is a liability.

Sesame Software's Backup Scheduler automates the entire Salesforce backup and recovery lifecycle — continuous protection, scheduled backups, and surgical point-in-time restore at the record, field, and value level — so your team can recover from any data incident in minutes, not days.

What Salesforce's native backup cannot do

Most Salesforce administrators discover the limits of native backup at the worst possible moment. By then, the data is already gone.

Salesforce's Data Export Service produces a full CSV export of your org on a weekly or monthly schedule. It does not run continuously. It does not capture changes between export windows. And restoring from it means overwriting your entire org with data that may be days or weeks old — wiping out everything that changed in between.

Field History Tracking logs changes to up to 20 fields per object and keeps that history for 18 months. For organizations under HIPAA, SOX, or GDPR, 18 months does not satisfy a six or seven-year retention obligation. And for orgs with complex custom objects, 20 fields captures only a fraction of what actually matters.

The recycle bin keeps deleted records for 15 days. After that, they are gone permanently. There is no native mechanism to recover a record deleted six months ago, restore the related child records alongside it, or produce the audit trail of who deleted it and when.

Salesforce does not back up your metadata — the object definitions, field configurations, permission sets, profiles, and workflow rules that govern how your org operates. A botched deployment or an accidental admin change can break Salesforce entirely without touching a single data record.

Sesame Software's Backup Scheduler fills every one of these gaps — automatically, continuously, and without requiring developer resources to maintain.

What Backup Scheduler does

Backup Scheduler is Sesame Software's automated Salesforce backup and recovery platform. It runs continuously inside your own environment, captures every change to your Salesforce data and metadata, and gives your team the tools to recover anything — from a single field value to an entire object — at any point in time.

Automated backups run as frequently as every five minutes, creating a continuous recovery timeline across your entire Salesforce org. There are no manual steps, no export schedules to manage, and no backup windows to coordinate. The scheduler runs in the background, capturing data and metadata changes continuously, so your most recent recovery point is never more than minutes old.

Point-in-time restore operates at the level of precision your incident actually requires. If a sales representative deleted 200 Accounts yesterday afternoon, you restore those 200 Accounts to their state as of yesterday morning — without touching anything else that changed in the org since then. If a bad data import overwrote the values in a specific field across 5,000 records, you restore those field values to their pre-import state without triggering a full-org restore. If a single Opportunity was accidentally modified by a workflow rule, you restore that one record to its exact prior state — with its related Opportunity Line Items, Contacts, and Activities intact.

Relational integrity is preserved automatically on every restore. Parent records are restored with their child records. Object relationships are maintained across the restore operation. Your Salesforce org comes back whole, not in pieces.

Metadata backup captures your org configuration alongside your data. Object definitions, field configurations, permission sets, profiles, validation rules, workflow rules, flows, and page layouts — all backed up continuously alongside your records. The Metadata Compare feature provides a visual, side-by-side view of your org configuration at any two points in time, so your team can identify exactly what changed after a deployment or an admin modification. Metadata Restore brings previous configurations back through both Workbench and Salesforce CLI methods.

Non-technical restore operations mean your compliance manager, your Salesforce administrator, or your legal team can execute a targeted restore through the visual interface without filing an IT ticket or waiting for a data engineer. In an incident, every hour matters — eliminating the technical dependency from the recovery process is operationally critical.

Complete audit history captures every field change across every object with no field count limits and no platform-imposed retention ceiling. Every modification is logged with the previous value, the new value, the responsible user, and the timestamp. Deleted records are retained in the audit history well beyond Salesforce's 15-day recycle bin, for the customer-defined retention period that matches your compliance obligations.

The incidents Backup Scheduler protects against

Data incidents in Salesforce are not rare. They happen in every enterprise org, and they happen faster than teams expect.

A sales operations manager runs a data import to update territory assignments across 10,000 Account records. A field mapping error overwrites the Account Owner field with the wrong values across the entire dataset. With Backup Scheduler, the correct values are restored to all 10,000 records in minutes. Without it, the team spends days manually reconstructing the correct assignments from memory, email threads, and partial records.

A Salesforce administrator deletes a custom object that was believed to be unused. Three days later, a reporting team discovers that the object contained the historical activity data that feeds a quarterly compliance report. With Backup Scheduler, the object and all its records are restored to their state three days ago. Without it, the data is gone permanently.

A third-party integration writes incorrect data to a set of Opportunity records during a failed sync. The incorrect values propagate downstream into a revenue forecast before anyone notices. With Backup Scheduler, the affected Opportunities are restored to their pre-sync state and the downstream impact is contained. Without it, the team is manually auditing records against external systems to reconstruct what the correct values should have been.

A workflow rule fires incorrectly following a configuration change and blanks out a required field across a large set of Contact records. With Backup Scheduler, the field values are restored from the backup taken before the configuration change. Without it, the team has no record of what those field values were.

User error is not a technology failure. It is an operational reality. Backup Scheduler treats it that way — not as an edge case to plan for, but as a daily operational condition to protect against continuously.

Built for compliance — not just convenience

Backup Scheduler is not a convenience tool. For mid-sized enterprise IT teams in regulated industries, it is a compliance requirement.

HIPAA requires that covered entities maintain retrievable exact copies of electronic protected health information, with audit controls that record and examine access and modification activity. Backup Scheduler satisfies both requirements — continuous automated backup and complete field-level audit history — with data stored inside your own environment, not on Sesame Software's servers.

GDPR's right to erasure requires that deletion requests extend to backup copies, not just production records. Backup Scheduler supports governed deletion from backup storage as part of a complete erasure workflow. Article 32's appropriate technical measures requirement is satisfied by encrypted backup storage, RBAC, and the complete audit trail that Backup Scheduler produces.

SOX compliance for Salesforce environments containing financial data requires seven years of audit trail retention. Backup Scheduler's customer-defined retention periods and customer-controlled storage mean your retention schedule matches your regulatory obligation — not a vendor default.

All backup data is stored in your own environment. Sesame Software never retains, accesses, or has visibility into your backup data. Your storage location, your retention period, your access controls, your encryption keys. This is the architecture that satisfies data residency requirements by design, not by vendor assurance.

How Backup Scheduler compares to the alternative

Own (OwnBackup) is the most commonly evaluated alternative for Salesforce backup. It is a capable platform with good usability and strong coverage of standard Salesforce objects for organizations with straightforward backup requirements.

The architectural difference matters for compliance-sensitive organizations. Own is a cloud-hosted SaaS platform. Your Salesforce backup data is processed and stored on Own's infrastructure. Own offers regional storage options and holds SOC 2 Type II certification, but the fundamental model is vendor-hosted: Own's infrastructure is in the data path.

For organizations under GDPR with data residency requirements, or under HIPAA where ePHI must remain within the covered entity's own security perimeter, this architecture requires legal and compliance review before deployment. For organizations where customer-hosted backup is a hard requirement, Own cannot satisfy it.

Sesame Software's Backup Scheduler runs inside your own environment. No Sesame Software infrastructure is in the data path. For compliance teams that need to answer the question of where backup data is processed and stored with a simple, auditable answer — inside our own infrastructure — Backup Scheduler provides that answer. Own does not.

What your team gets from day one

Backup Scheduler is designed for self-service deployment by enterprise IT teams without dedicated data engineering resources. Setup takes under an hour. There is no custom code to write, no schema to configure manually, and no ongoing maintenance to manage.

From the moment the first backup completes, your team has a continuous recovery timeline across your entire Salesforce org — data and metadata, standard and custom objects, production records and deleted records. The restore interface is accessible to non-technical team members. The audit history is queryable without writing queries. The compliance documentation is produced by the platform, not assembled manually from log files.

Flat annual pricing covers unlimited backup frequency, unlimited data volume, and unlimited restore operations. There are no per-record charges, no per-restore fees, and no billing surprises as your Salesforce org grows. The cost of protecting your data does not scale with the size of your data.

Sesame Software has been protecting enterprise data for more than 30 years. Backup Scheduler reflects that experience — built for the operational realities of production Salesforce environments, not the idealized conditions of a product demo.

---

Salesforce Backup and Recovery software Frequently Asked Questions

How frequently does Backup Scheduler run?

Backup Scheduler runs automated backups as frequently as every five minutes. The backup interval is configurable based on your recovery point objective — the maximum data loss your organization can tolerate in a recovery scenario. For HIPAA environments and other regulated industries, five-minute intervals are the recommended configuration.

Can Backup Scheduler restore individual records without affecting the rest of the org?

Yes. Backup Scheduler supports granular point-in-time restore at the record level, the field level, and the value level. Restoring a specific set of records to their state at a specific timestamp does not affect any other data in the org. Relational integrity — parent-child relationships between Salesforce objects — is preserved automatically on every restore.

Where is backup data stored?

In your own environment. Backup Scheduler stores all backup data in the infrastructure you specify — on-premise servers, private cloud instances, or your own cloud storage accounts in your required geographic region. Sesame Software retains no copies of your backup data and has no access to it.

Does Backup Scheduler cover Salesforce metadata?

Yes. Backup Scheduler captures Salesforce metadata — object definitions, field configurations, permission sets, profiles, workflow rules, validation rules, flows, and page layouts — continuously alongside data records. The Metadata Compare feature provides visual comparison of metadata states across time. Metadata Restore supports recovery through Workbench and Salesforce CLI.

How does Backup Scheduler satisfy HIPAA and GDPR requirements?

Backup Scheduler satisfies HIPAA's Contingency Plan and Audit Controls standards through continuous automated backup and complete field-level audit history retained for the customer-defined period. It satisfies GDPR's Article 5, 17, 30, and 32 requirements through customer-controlled storage, governed erasure workflow support, data residency compliance, and encrypted backup with complete access logging. All data remains in the customer's own infrastructure — Sesame Software is never in the data path.

What happens if a restore operation affects related records incorrectly?

Backup Scheduler preserves Salesforce's parent-child relational integrity on every restore. The platform identifies related records — child objects, lookup relationships, master-detail relationships — and restores them in the correct sequence to maintain relational consistency. Restoring an Opportunity restores its Opportunity Line Items. Restoring an Account restores its associated Contacts and Cases. The org remains relationally intact after every recovery operation.

---

Found this post helpful? Share it with your network using the links below.