For the complete documentation index, see llms.txt. This page is also available as Markdown.

System-Defined Default Composite vs Default Composite & Sync Backups

Overview

This article explains the difference between Default Composite Backup and Default Composite & Sync Backup in the Flosum Backup & Archive app. Each Salesforce org has two System-Defined scheduled backup jobs:

  • Default Composite Backup

  • Default Composite & Sync Deleted Backup.

These jobs are managed by the system and cannot be deleted, though you can control when they run. Each method serves a specific purpose in maintaining comprehensive, restorable snapshots of your org's data. The sections below explain how each default backup operates and the differences between them, helping you determine which method to use, understand how deleted records are flagged, and optimize backup frequency for your Salesforce environment.

A User-Defined Composite backup allows you to back up your Salesforce data whenever needed—such as before major changes or after significant record updates by multiple users. For more information, see the following articles on User-Defined Composite backups.

Default Composite Backup:

A Default Composite Backup is a lightweight process that tracks changes across your Salesforce org daily. After an initial full composite backup has been created, it saves any new, modified, or soft-deleted (Recycle Bin) records. By default, this system backup runs daily and can be used as an alternative to a user-defined composite backup.

  • Tracks new and updated records.

  • Flags records that are deleted and sent to the Recycle Bin.

  • Optimized for daily execution.

Recommended Frequency

Run daily to ensure continuous backup coverage without impacting system performance.

Default Composite & Sync Backup:

A Default Composite & Sync Backup is a more intensive method that compares every record in your live Salesforce org to the ones stored in Flosum’s backup repository. It detects even permanently deleted records, ensuring full fidelity. By default, this system backup runs monthly to detect purged records and ensure backup completeness. While a monthly backup schedule is recommended, you can change this backup to run on a weekly basis.

  • Performs a full record comparison.

  • Flags hard-deleted records that are no longer in Salesforce.

  • Identifies discrepancies between the org and the backup.

Recommended Frequency

Run monthly to detect purged records and ensure backup completeness. (Optional) May be run weekly, depending on the org size and performance needs.

Why Composite & Sync Backup Shouldn’t Be Run Daily

Composite & Sync performs a full record comparison, consuming more compute resources. Running it daily may degrade performance in larger orgs. Composite Backup offers a lighter alternative for daily use while still tracking most deletions.

Quick Comparison

Feature
Composite Backup
Composite & Sync Backup

Frequency

Daily

Monthly

Captures new/modified records

Captures soft-deleted (Recycle Bin)

Captures hard-deleted records

Performs full record comparison

System performance impact

Low

High

How Deleted Records Are Flagged

Backup Method
What It Flags as Deleted

Default Composite Backup

Records that were moved to the Salesforce Recycle Bin.

Default Composite & Sync Backup

Records that are missing in Salesforce but are still present in Flosum Backup & Archive.

Restoring Deleted Records

Restoring deleted records is based on the backup flagging the record as deleted. The restoration process is as follows:

  1. Identify backups from before and after the deletion.

  2. Flosum Backup & Archive detects the flagged records.

  3. Restore the deleted records directly to Salesforce.

Example

A Contact is deleted and purged. The next Composite & Sync Backup flags the missing record, allowing it to be restored during recovery.

See the following article to learn how to restore records:

Last updated

Was this helpful?