Automated backup & recovery for Salesforce - records of every standard and custom object (deleted and archived ones included), files and attachments, metadata. Compare a record with the live org field by field and restore what changed, into the same org or a sandbox.
| Authentication | An External Client App created in your org (new connected apps are disabled by default since Spring '26), OAuth 2.0 client credentials flow run as a dedicated user backup-svc. One secret (consumer key + consumer secret + My Domain URL) for backup AND restore, encrypted AES-256-GCM, never in a URL. A permission set "CYBBACK Backup", never the System Administrator profile. |
|---|---|
| API & quota | Bulk API 2.0 queryAll for records (REST when an object does not support Bulk), Metadata API for metadata. Every call is counted against a budget: 20 % of the daily quota by default, with a reserve of 30,000 calls (capped at half the quota), both adjustable per org. |
| Backup mode | Incremental forever per object on SystemModstamp (5-minute overlap). Deletions: recycle bin via queryAll, purges via getDeleted (15 days) and a periodic reconciliation of the ids. |
| Large orgs | One sub-task per object (a failing object is retried alone), resume on the same Bulk job after an interruption, files copied in a second phase and spread over several nights, capped per backup. |
| Selection | Every queryable object or a selection of objects; files, metadata and field history as options. |
| Restore | Asynchronous, dry run by default, cancellable, idempotent (a re-run never duplicates). Records, selections, whole objects, parents and master-detail children; into the same org or another connected org (sandbox). |
| Exports | ZIP - one CSV per object (JSON as an option), metadata as a deployable package (package.xml), files as an option, summary report |
| Hosting region | Google Cloud - europe-west1 (Belgium) |
| Records still in the Salesforce recycle bin | Undeleted, original ids kept |
|---|---|
| Purged records | Recreated with new ids; references between restored records remapped in two passes |
| Existing records | Changed fields only (default), overwrite (explicit confirmation) or left untouched |
| Missing parents | Recreated from the backup (option); master-detail children as an option |
| Validation rules, flows, triggers | Stay active: CYBBACK never deactivates them; a refusal is reported record by record |
| Original dates and authors | Kept only if "Set Audit Fields upon Record Creation" is granted to backup-svc |
| Files | Latest version restored; earlier versions are not backed up |
| Metadata | Custom objects and fields, record types, global value sets, page layouts and tabs restorable; the other types are backed up for export |
| Users, profiles, sharing | Not restored |
| Field history | Exported only, never rewritten |
| Big Objects, external objects | Not backed up |
| Volume per restore | Up to 50,000 records per restore operation |
Create the backup-svc user and the External Client App, paste the secret into CYBBACK and run your first backup.