Independent recovery points
Choose full or incremental capture. Each completed snapshot stands on its own, so browsing and recovery do not depend on replaying an incremental chain.
Salesforce / Backup & Recovery
Salesforce Backup. A recovery point you can inspect.
Protect Salesforce records and files with full or incremental backups. Browse independent snapshots, export what you need, and preview record recovery before an administrator approves a write.
- 01Capture a snapshot
Selected objects, accessible records, optional files
- 02Preview the restore
Records, fields, relationships, warnings
- 03Review the receipt
Completed writes and record mappings
Recovery targets the original Salesforce org. Review intended writes before confirmation.
Recovery with a clear preview
Inspect fields, relationships, warnings, and files before confirming. Create copies or overwrite eligible existing records in the original org.
Distinct operational roles
Operators run backups and viewers browse or export snapshots. Scheduling and restore writes require administrator access, with receipts for recovery activity.
The workflow
A clear path from capture to recovery.
Backups run independently from archive and reclamation. Keep a usable snapshot and a controlled restore process for the moment data changes unexpectedly.
- 01
Choose objects and files
Select the objects to protect and include accessible Salesforce Files and classic Attachments. Capture respects the source user’s visibility.
- 02
Capture on your schedule
Run full or incremental backups on demand, or schedule hourly, daily, or weekly captures. Review job status and the visible capture window.
- 03
Inspect and preview
Browse completed runs, export records, or download verified files. Select up to 200 records for a restore preview and review the fields, destination, and warnings.
- 04
Confirm and reconcile
An administrator confirms the preview. Inspect the restore receipt and record mappings, then verify the workflow. Salesforce validation rules and automation still apply.
On premises or in your cloud
Your database.
A defined deployment.
Choose where the data lives. Agree the engine, network access, permissions, storage capacity and recovery responsibilities before rollout.
Read the deployment guides| Database | What to plan for |
|---|---|
| SQL Server | Independent record snapshots and file storage, separate from archive tables. Validate the host and recovery workflow for your installation. |
| PostgreSQL | A separate backup storage adapter with the same snapshot and recovery contract. Confirm your host and deployment acceptance. |
- Data and file coverage
- Protect selected accessible records and supported files. This is record and file recovery, separate from metadata or a full-org disaster-recovery image.
- Recovery behaviour
- Create copies with selected relationship remapping, or overwrite captured writable fields on existing records. Recovery targets the original org.
- Storage planning
- Use SQL Server or PostgreSQL in your approved deployment environment. Independent snapshots and file versions need capacity planning, retention ownership, and database-level backups.
- Recovery objectives
- Capture spans a time window rather than an atomic org snapshot. Measure recovery with your record set, relationships, source limits, and automation.
Before you begin
Know the scope.
How is backup different from archiving?
Backup keeps recovery points for loss or unwanted changes. Archiving moves inactive history out of the production workload while retaining access. Backup capture does not enter the archive or purge lifecycle.
Can we restore an entire Salesforce org?
Recovery covers selected records and supported files in the original org. It does not restore Salesforce metadata, provide cross-org recovery, or recreate an entire org as a disaster-recovery image.
What happens to relationships and files?
When creating copies, selected parent and child references are remapped where supported. Unselected lookups retain their original IDs. Included Salesforce Files and classic Attachments are recreated on restored parents; existing files remain.
Does an incremental backup depend on older snapshots?
A completed incremental result is an independent snapshot. Unchanged record payloads are copied from the baseline while changed records are fetched again. This reduces source payload, not the storage needed for each snapshot.
Start with your Salesforce data.
Bring the objects, files, destination and outcome you have in mind. We will define the scope and acceptance checks together.