> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/backup-and-archive/backups/creating-a-user-defined-composite-backup.md).

# Creating a User-Defined Composite Backup

{% hint style="success" %}

#### Required User Credentials

\[**Flosum User**] - **Backup & Archive** license with **Backup & Archive** permissions
{% endhint %}

## <img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3f6faa4230b72167926fbc0a31dd17dc7d74581d%2FSummary2-Small-Icon.svg?alt=media" alt="" data-size="original">Overview

This article provides step-by-step instructions for creating a **User-Defined Composite Backup** in Flosum Backup & Archive. Composite Backups protect your Salesforce org by capturing ongoing changes, including new, modified, and soft-deleted records.

When you first run a Composite Backup, it creates a complete snapshot of your Salesforce org. After that, it only tracks and backs up incremental changes, like new records, field updates, and items sent to the Recycle Bin.

{% hint style="info" %}
You can run backups immediately or schedule them at regular intervals to ensure continuous protection. Designed for **daily use**, this backup type efficiently protects your org's evolving data with minimal processing overhead.
{% endhint %}

{% hint style="warning" %}
Every Salesforce org includes a System-Defined Composite backup called **Default Composite Backup**, which runs daily. Since this system backup already manages daily backups, creating an additional scheduled User-Defined Composite backup is unnecessary and redundant. Instead, User-Defined Composite backups are best for creating snapshots before making significant changes to your Salesforce data—such as when an administrator needs to update or delete records and wants to save the current state beforehand.

See the following article for more information on the **Default Composite Backup**:

* [System-Defined Default Composite vs Default Composite & Sync Backups](/backup-and-archive/backup-and-archive/backups/default-composite-vs-default-composite-and-sync-back.md)
  {% endhint %}

## Creating a User-Defined Composite Backup

{% stepper %}
{% step %}

### Create a Backup

1. Click **Backup & Archive** from the sidebar menu.
2. Click the **Organization Switcher** from the breadcrumb path.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-44f059e6bd47fe689aa15f0c67a2b3c05835a165%2FCreatingACompositeBackup-BackupCompositeRun-01.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
3. Select the organization you wish to back up.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-5ef1deb9d5ee2f2533c039eb643738eb4d4f72ee%2FCreatingACompositeBackup-BackupCompositeRun-02.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
4. Click **Composite Backup**.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-31d8940ccacad3320c5c030950eff50234ae74e0%2FCreatingACompositeBackup-BackupCompositeRun-03.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Configure Backup Job

1. Enter a name for the backup job.
2. Select the **Job Settings** checkboxes for the objects to back up. You can leave the default options or choose a custom selection, including Metadata for the backup job. **Note**: By default, all object types are selected except Metadata.

   <table><thead><tr><th width="168">Object Type</th><th>Purpose</th><th>Use Case Example</th></tr></thead><tbody><tr><td><strong>Big Objects</strong></td><td>Mass data storage</td><td>Logging millions of transactions</td></tr><tr><td><strong>Binary Objects</strong></td><td>File content storage</td><td>Attachments, ContentVersion</td></tr><tr><td><strong>Tag Objects</strong></td><td>Legacy tag relationships</td><td>Tagging Contacts by topic</td></tr><tr><td><strong>History Objects</strong></td><td>Field change tracking</td><td>View who changed what and when</td></tr><tr><td><strong>Feed Objects</strong></td><td>Chatter-related content</td><td>Comments, file shares, social posts</td></tr><tr><td><strong>Share Objects</strong></td><td>Record-level access management</td><td>Opportunity sharing via Apex</td></tr><tr><td><strong>Custom Metadata</strong></td><td>Deployable application settings</td><td>Business rules, field mapping</td></tr></tbody></table>
3. (Optional) Enter a description of the backup in the **Composite Backup** textbox to help identify the purpose or scope of this backup job.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-9136f5714421c2f82a8aa754829f7290df2e2bd1%2FCreatingACompositeBackup-BackupCompositeRun-04.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Run or Schedule the Backup Job

**Immediate Backup**

1. Click the **Run** button to start the Composite Backup.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-1cfe962d96fe4c5238e5629784da1cf2c7def74c%2FCreatingACompositeBackup-BackupCompositeRun-05.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
2. The Composite Backup job will now be in progress.

**Scheduled Backup**

A backup job can be scheduled to run at a specific date and time interval.

1. Switch the **Schedule** toggle to **Enabled**.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3225df39b625492faa7724361723bfab16bb46f7%2FCreatingACompositeBackup-BackupCompositeSchedule-01.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
2. Select the **Recurrence** of the backup to run **Daily**, **Weekly**, or **Monthly**.
3. Configure the **Schedule** options. Daily, Weekly, and Monthly each offer different options for setting the time and date the backup runs.
4. Click the **Schedule** button to schedule your backup job.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-3e38dab5ff497ba1f95991f6c003b23d58ba8b58%2FCreatingACompositeBackup-BackupCompositeSchedule-02.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>
5. Confirm the schedule is correct and click **Save**.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-28499f19d5b231429193a27f1473d939bb78e4a2%2FCreatingACompositeBackup-BackupCompositeSchedule-04.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Review Backup Job

**Immediate Backup**

1. From **Backup & Archive**, click the **History** tab to view the status of the backup job you created.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-450698b3659ade603cc0b700dd6221afbc3cd5b9%2FCreatingACompositeBackup-BackupCompositeRun-06.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

**Scheduled Backup**

1. From **Backup & Archive**, click the **Schedule** tab to view the scheduled backup job you created.
2. The scheduled User-Defined Composite Backup job is located in the **User Scheduled** section.

   <div align="left"><figure><img src="https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2Fgit-blob-9feda0af3c5a1099b9046af65b1d0f3564025f1e%2FCreatingACompositeBackup-BackupCompositeSchedule-05.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/backup-and-archive/backup-and-archive/backups/creating-a-user-defined-composite-backup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
