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

# Backup & Archive (v4.8.11) ‐ Monthly Release Notes

{% hint style="info" %}

#### Release Details - Backup & Archive - v4.8.11 - November 9, 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.8.11)**. This release adds an MCP server, so AI assistants and other MCP-compatible clients can work with Backup & Archive through natural language. It also improves Archive Job performance, especially for organizations with large volumes of data.

### MCP Server Integration

#### What Changed

**Backup & Archive** now provides an MCP (Model Context Protocol) server. AI assistants and other MCP-compatible clients can connect to it and work with Backup & Archive through a standard interface.

The MCP server provides tools that let you:

* Retrieve information about Salesforce connections and check their status.
* Access backup and archive job information, including execution status and progress.
* Review backup contents and object-level statistics.
* Retrieve job logs and execution details.
* Access backup, operation, Salesforce, and tenant analytics.
* View and manage backup and archive templates.
* Inspect Salesforce object metadata and relationships.
* Validate template filters and estimate the number of matching records.
* Create and manage backup and archive schedules.
* Start backups.

#### Why It Was Done

This integration makes Backup & Archive available to AI-powered workflows and MCP-compatible applications. You can retrieve operational information, analyze backup activity, and perform supported operations in natural language through your preferred AI assistant. It also provides a foundation for future AI-driven automation and for integration with external tools and workflows.

#### What You Will Notice

You can connect an MCP-compatible client to the Backup & Archive MCP server and work with Backup & Archive in natural language. Instead of navigating the application or making API requests, you can ask an AI assistant to retrieve backup information, analyze job results, inspect templates, or manage supported configurations.

The operations available to you depend on the tools the MCP server provides and on the permissions of the connected user.

#### MCP Server Endpoints

The MCP server is available in each region:

<table><thead><tr><th width="180">Region</th><th>Backup &#x26; Archive MCP Server</th></tr></thead><tbody><tr><td>United States</td><td>https://backup-us-mcp.flosum.app</td></tr><tr><td>Germany</td><td>https://backup-de-mcp.flosum.app</td></tr><tr><td>Japan</td><td>https://backup-jp-mcp.flosum.app</td></tr><tr><td>Australia</td><td>https://backup-au-mcp.flosum.app</td></tr></tbody></table>

A SystemAdministrator must create a Connected App for MCP access in Global Settings. If your organization already has one for the DevOps MCP server, the same Connected App works for Backup & Archive. For the steps, see the following article.

* [Creating a Connected App for MCP Access](https://docs.flosum.com/global-settings/security/connected-apps/creating-a-connected-app-for-mcp-access.md)

{% hint style="info" %}

#### Important

* Your MCP client must be configured to connect to the Backup & Archive MCP server.
* Operations that change configurations or may affect existing data require your confirmation.
* The MCP server is an additional way to work with Backup & Archive. It does not replace the Backup & Archive UI or API.
  {% endhint %}

### Faster Archive Job Execution

#### What Changed

**Backup & Archive** now runs Archive Jobs more efficiently, especially for organizations with large volumes of data. The improvements optimize record deletion and other parts of the Archive Job workflow, which reduces overall execution time and improves job stability.

#### Why It Was Done

These improvements address performance bottlenecks in the Archive Job process and reduce execution time when large amounts of data are processed.

#### What You Will Notice

Archive Jobs run faster and perform better overall, particularly when you archive large volumes of records.

{% hint style="info" %}

#### Important

The optimization does not change the existing archive workflow or the expected results of archiving.
{% 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/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.8.11-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.
