> 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.8-monthly-release-notes.md).
# Backup & Archive (v4.6.8) - Monthly Release Notes
{% hint style="info" %}
#### Release Details - Backup & Archive - v4.6.8 - April 15th, 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**
* A registered and configured Flosum Cloud Apps tenant
* Appropriate Flosum user permissions (SystemAdministrator or equivalent)
{% endhint %}
##  Summary
This article documents the monthly release for **Backup & Archive (v4.6.8)**. It introduces the following features:
* A configurable limit on the number of binary data records processed per backup run to improve reliability and performance for organizations with large file volumes during initial backups.
* The ability to view archived Content Documents directly from related records in the Related Archives component.
* The ability to preview and download binary object files from backed-up or archived records in the Record View component.
###  Binary Data Backup Limit
Backup & Archive now includes a configurable limit on the number of binary data records (ContentVersions, Attachments) processed per run during the initial backup phase. By default, up to **5,000** records are backed up per run. The process continues automatically across multiple scheduled runs until every file record has been backed up at least once; after that, the limit is lifted, and only new or modified records are processed.
{% hint style="info" %}
This limit addresses a Salesforce platform constraint in which file content is delivered per record rather than in bulk, which can cause backup jobs in large orgs to run for hours or become unresponsive. All major backup vendors enforce similar limits; Flosum's default of 5,000 provides faster initial coverage than most alternatives.
{% endhint %}
**How It Works**
The limit is configurable in the organization settings and applies only to the first full Composite Backup of an organization. It does not apply to Template Backup, Template Archive, or Import Backups/Archives.
* **Default (minimum) value:** 5,000 records per run
* **Maximum value:** 999,999 records per run
All non-file data (standard objects, custom objects, metadata) is always backed up fully in every run. The limit applies only to binary objects during the initial backup phase. Once the per-run count is reached, the job completes gracefully, and the next scheduled run picks up where it left off.
For more details on this feature, see the following article:
* [Understanding Binary Data Backup Limits](/backup-and-archive/backup-and-archive/backups/understanding-binary-data-backup-limits.md)
###  **Show Content Documents in Related Archives**
The Related Archives component of Flosum’s Backup & Archive Salesforce package now includes a **Content Documents** card. This card displays a table of related Content Document records archived in the Backup & Archive application.
**Use Case Scenario**
Prerequisites:
1. The user has an organization with an Account object and at least one record that has related files.
2. The user has run an archive job in the Backup & Archive application that includes Content Document and Content Versions related to Account records.
Flow:
1. Open the **Account** record in the Salesforce organization.
2. Open the **Related Archives** component.
3. The component shows the new **Content Documents** card.
4. The **Content Documents** card displays a list of archived Content Document records.
5. Select a Content Document record to open it in the **Record view** component.
###  **Preview and Download Binary Object Files**
This feature lets users preview or download binary object files from backed-up or archived records in the Record View component of Flosum’s Backup & Archive Salesforce package.
* The **Preview** button is displayed for Binary fields on the Record View component.
* The **Download** button is displayed in the Preview window for a Binary field.
**Use Case Scenario**
Prerequisites:
1. The user has an organization with an Account object and at least one record that has related files.
2. The user has run an archive job in the Backup & Archive application that includes Content Document and Content Versions related to Account records.
Flow:
1. Open the **Account** record in the Salesforce organization.
2. Open the **Related Archives** component.
3. The component shows the new **Content Documents** card.
4. The **Content Documents** card displays a list of archived Content Document records.
5. Select a Content Document record to open it in the **Record view** component.
6. The component displays data from the Content Document record.
7. Click the **Preview** icon for the binary field to open a modal window with a document preview and a **Download** button.
8. Click **Download** to download the file from the Backup & Archive application.
---
# 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.8-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.
