> 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/general-information/faq-and-guidance/backup-and-archive-implementation-best-practices.md). # Backup & Archive: Implementation Best Practices ### ![](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 Proper implementation of Backup & Archive is essential to ensure your Salesforce data is secure, recoverable, and resilient against loss or disaster. This guide outlines key best practices for planning, configuring, and maintaining a robust data protection strategy with Backup & Archive. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Develop a Comprehensive Backup Strategy** * Define what data needs to be backed up and how often. * Identify critical data (e.g., customer, financial, transactional) for high-frequency backups. * Include procedures for testing and validating backup completeness. * Align backup frequency with business continuity and RTO/RPO objectives. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Understand Data Growth and Impact** * Monitor which data types are expanding (e.g., objects with frequent inserts/updates). * Use Salesforce analytics tools (e.g., Einstein Analytics) to identify growth trends. * Ensure storage infrastructure is scalable to accommodate future growth. {% hint style="info" %} Classify data by criticality to determine backup cadence (daily, weekly, etc.). {% endhint %} *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Use SSDs for Self-Hosted Cloud Environments** * If you deploy Flosum in a self-hosted environment, choose **SSDs** (Solid State Drives) over **HDDs**. * SSDs offer significantly faster write speeds and reliability—critical for backup performance. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **System Scheduled Backups** * All organizations connected to Backup & Archive include two system-defined scheduled backups: * **Default Composite Backup**: Runs daily at a specified time. This frequency follows best practices, provides comprehensive protection, and reduces storage use by backing up only changes. * **Default Composite & Sync Backup**: Runs monthly at a specified date and time. This frequency follows best practices and syncs deleted records by flagging them in the backed-up data. This keeps your backup data up to date with any Salesforce deletions. * Review the system-defined backup scheduled times and adjust them to fit your needs. * See the following articles to learn more about system-defined backups 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) *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Set API Quotas for Initial Full Backups** * After org connection, go to **Organization Settings** and set: * **REST API quota**: 80–90% * **Bulk API quota**: 80–90% * This allows the system to allocate maximum API capacity during the first full backup. * Once the initial backup is complete, you can reduce the quotas since subsequent composite backups use fewer API calls. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Test Backup and Restore Procedures Regularly** * Simulate recovery scenarios in sandbox or test environments. * Validate that the restored data is complete and accurate. * Document and refine your recovery process regularly. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Develop a Disaster Recovery Plan** * Define a clear step-by-step plan for restoring backups. * Include contact information for stakeholders and escalation paths. * Review and test the plan quarterly or after major releases. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Store Backups Securely** * Backup & Archive encrypts backups by default. * Ensure access is limited to authorized users only. * Use access controls and audit logs to track access events. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Monitor Backup and Recovery Activity** * Use logs and success/failure reports to validate backup jobs. * Set up alerts for failed or skipped jobs. * Regularly review status reports to detect anomalies. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Use Version Control for Historical Tracking** * Leverage version control within Backup & Archive to retain historical data states. * Quickly restore previous versions of records when needed for audits or rollback scenarios. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Integrate Backups into Change Management** * Configure Backup & Archive to trigger backups after key system changes. * Supports compliance and rollback if a change introduces errors. * Useful for deployments, CPQ changes, or regulatory data operations. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Handle Refreshed Sandboxes Correctly** * A refreshed sandbox has a new Org ID and is treated as a **new org**. * Reconnect the refreshed sandbox using **Add Organization**. * Remove the obsolete org and its backup data to avoid confusion. {% hint style="warning" %} You will not be able to access backups from the previous sandbox after Salesforce deletes it. {% endhint %} *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Use Multiple Backup Locations** * Store copies in both cloud and off-site environments. * Helps protect against regional outages, physical damage, or ransomware. * Backup redundancy enhances availability and supports compliance mandates. *** ### ![](https://646917531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Focom3JROuDKOidclKbQx%2Fuploads%2F7mmNsCAYTdPv7oisxuWI%2FEnhance-Icon-Small.svg?alt=media\&token=8cf277ef-21c2-4252-bf4a-b9fd4fca0128) **Restrict Access by Source IP** * Limit data access by configuring IP whitelisting at the infrastructure level (e.g., EC2 security groups). * Helps ensure that only trusted IP addresses can retrieve or manage backup data. *** {% hint style="success" %} By following these best practices, organizations using Flosum Backup & Archive can dramatically reduce the risk of data loss, maintain compliance, and support high-availability disaster recovery plans. Whether deployed in a Flosum-hosted or self-hosted model, the recommendations in this guide help ensure secure, efficient, and reliable backup operations. {% endhint %} --- # 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/general-information/faq-and-guidance/backup-and-archive-implementation-best-practices.md?ask=&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.