> 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/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.6.0-monthly-release-notes.md). # Backup & Archive (v4.6.0) - Monthly Release Notes {% hint style="info" %} ## Release Details - Backup & Archive - v4.6.0 - Febuary 11th, 2026 This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance. **Release Type** * Monthly * Applies to Flosum-hosted and self-hosted **Prerequisites** * Backup & Archive tenant setup * Appropriate Flosum user permissions (SystemAdministrator or equivalent) {% endhint %} ## ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary This article documents the patch release for **Backup & Archive (v4.6.0)**. This release adds support for Encryption Key rotation, composite metadata backups, and Token Expired logging. ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Encryption Key Rotation for Backup & Archive The Backup & Archive app now allows for encryption key rotation, enhancing control and security for protected data. You can rotate your encryption key at any time (up to once per month) without affecting existing backups or restore functionality. {% hint style="info" %} #### Rotate Key Rotating an organization's encryption key is performed in **Global Settings** and is included in [Global Settings (v1.6.9) - Monthly Release Notes](/release-notes/global-settings/monthly-releases/global-settings-v1.6.9-monthly-release-notes.md). {% endhint %} **Highlights** * Rotate encryption keys on demand (once per organization per month). * The new key is securely stored in the Backup & Archive database and automatically used for all new backups. * Existing backups remain accessible and are not re-encrypted. * Restores automatically use the correct key version. * No disruption to backup or restore processes. * An email notification is sent whenever a key is rotated. * Available for both Flosum-hosted and self-hosted customers. * The Rotate Key option is visible only to organizations assigned the B\&A app. {% @arcade/embed flowId="grZ5ChvcRKsPEtitclWx" url="" %} ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Metadata Backup Now Composite Metadata backups are now performed as a composite backup, improving performance when metadata is enabled. Following the v4.6.0 release, the first backup to include metadata will perform a full metadata backup, while subsequent backups will only capture new or modified metadata. This reduces the duration of backup jobs that include metadata. Previously backed-up metadata remains restorable with the same effective process, allowing selected metadata to be restored in a single step. {% hint style="info" %} Metadata will be included in a backup only if the **Metadata** checkbox is checked in the Job Settings. {% endhint %} ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Expired Token Logging When an organization’s access token expires, the backup job now logs an **Expired Token** error instead of a generic **500** error. This change makes it easier to identify the cause of failed backup jobs and resolve the issue quickly.
--- # 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/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.6.0-monthly-release-notes.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.