> 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.7.6-monthly-release-notes.md).

# Backup & Archive (v4.7.6) - Monthly Release Notes

{% hint style="info" %}

#### Release Details - Backup & Archive - v4.7.6 - June 22, 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 %}

## ![](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 monthly release for **Backup & Archive (v4.7.6)**. This release introduces the ability to exclude objects from Composite Backups, giving administrators finer control over which objects are included, and updates the underlying platform to the latest Salesforce API and MySQL versions for improved compatibility, performance, and security.

### ![](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) Composite Backup Exclusions

You can now directly define which objects are excluded from your backups in an Organization’s Settings. A new **Backup Exclusions** tab has been added to **Organization Settings**, where you can review and manage the list of objects to omit from backup operations.

Objects added to the exclusion list are excluded only from Composite Backups. Template Backups and Template Archives are not affected by these settings and will continue to process objects according to their own configuration.

This capability gives administrators greater control over backup scope, helping reduce backup size and processing time by omitting objects that do not require protection.

### ![](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) Salesforce API Version Update to 66.0

Backup & Archive now uses **Salesforce API version 66.0**. Upgrading to the latest API version ensures continued compatibility with Salesforce platform changes and provides access to the most recent metadata and data access improvements.

### ![](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) MySQL Version Update to 8.4.9

The underlying database engine has been updated to **MySQL 8.4.9**, the latest MySQL 8.4 LTS release. This update brings performance enhancements, security patches, and stability improvements to the Backup & Archive data layer.


---

# 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.7.6-monthly-release-notes.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.