Backup & Archive (v4.6.0) - Monthly Release Notes

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)

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.

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.

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.

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.

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.

Metadata will be included in a backup only if the Metadata checkbox is checked in the Job Settings.

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.