> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Upgrading to a Patch Release

xorlab Security Platform version numbering follows the `Major.Minor.Patch` semantics. For example, `9.X.2` means patch no. 2 to the X<sup>th</sup> minor release of the 9<sup>th</sup> major version of the software.

This guide supports system administrators who want to update XSP to a patch release. Please make sure that you read the *[Changelog](https://docs.xorlab.com/changelog.md)* to find detailed information on what issues have been resolved with the patch you’re about to install.

> [!WARNING]
>
> **Backup and rollback**
>
> Before proceeding, please make sure you have a recent backup available. Please see *[Manual backup](backup-recovery.md/#manual-backup)* and *[Patch Rollback](backup-recovery.md/#patch-rollback)* for instructions on how to perform a manual backup and roll back the upgrade.

## Upgrade Process

The upgrading process is performed automatically by a migration script that executes host migration instructions. The migration script must be run on each machine or VM that is running ActiveGuard components. The script is interactive and may ask questions, otherwise **no manual intervention is required**.

### Order of Process

Upgrade XSP Services in the following order:

1. Sandbox (for an on-premises instance)
2. XCC
3. MTA

If multiple services run on the same host, the migration script ensures the correct order automatically.

### Execute the Script

Run the following command as the `admin` user on each host, following the upgrade order above:

```shell theme={null}
# Replace the X letters with the correct patch and version numbers
xorlab-upgrade {{ major_version }}.0.X
```

## Troubleshooting

If you experience issues or have questions, refer to the support documentation or contact our support team at [support@xorlab.com](mailto:support@xorlab.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.