> 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/overview-of-backups.md).

# Overview of Backups

## ![](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)Overview

The Flosum Backup & Archive app offers a comprehensive range of backup solutions to ensure data security and accessibility. Key features include:

* **System-Defined Default Backups:** Automatically set up to reliably back up your org at regular intervals.
* **User-Defined Scheduled Backups**: Customize backups and schedules to fit your specific needs.
* **User-Defined Immediate Backups**: Initiate backups instantly for urgent data protection.

The sections below outline System-Defined and User-Defined backups, including links to related articles for further reading.

### System-Defined Default Backups

Each Salesforce org has two system-defined scheduled backup jobs: a Default Composite Backup and a Default Composite & Sync Deleted Backup. These backups are automatically scheduled to keep your org backed up, so you don't need to create your own scheduled backups. The system manages these jobs, and while they can’t be deleted, you do have some control over when the jobs are scheduled to run. The following articles explain in detail the difference between these backup jobs and how to edit them.

* [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)
* [Editing System-Defined Default Backups](/backup-and-archive/backup-and-archive/backups/editing-system-defined-default-backups.md)

### User-Defined Backups

The Backup & Archive app provides two types of backups: a full Composite Backup and a Templated Composite Backup. The Composite Backup allows you to back up all your data in a single step. The Templated Composite Backup provides the flexibility to select specific objects, data, and files for inclusion. Both options can be executed immediately or scheduled to run automatically at set intervals. The following articles explain in detail how to use these backups.

* [Creating a User-Defined Composite Backup](/backup-and-archive/backup-and-archive/backups/creating-a-user-defined-composite-backup.md)
* [Creating a Templated Backup](/backup-and-archive/backup-and-archive/backups/creating-a-templated-backup.md)
* [Viewing a Backup or Archive Job Details](/backup-and-archive/backup-and-archive/viewing-a-backup-or-archive-job-details.md)
* [Editing a User-Scheduled Backup or Archive Job](/backup-and-archive/backup-and-archive/scheduled-jobs/editing-a-user-scheduled-backup-or-archive-job.md)
* [Deleting a User-Scheduled Backup or Archive Job](/backup-and-archive/backup-and-archive/scheduled-jobs/deleting-a-user-scheduled-backup-or-archive-job.md)


---

# 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/overview-of-backups.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.