> ## 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

> Apply a Major.Minor.Patch increment to an existing installation, with the backup and rollback steps around it.

<Warning>
  **Prerequisites**

  * Read the [Changelog](/changelog) to see the list of all changes.
  * Have a recent backup available, see [Manual backup](/latest/backup-recovery#manual-backup) and [Patch rollback](/latest/backup-recovery#patch-rollback).
</Warning>

xorlab version numbering follows the `Major.Minor.Patch` semantics. Use this guide to upgrade from e.g. `X.X.2` to `X.X.4`. For a major or minor upgrade, see [Upgrade xorlab](/latest/upgrade-guide) instead.

## Upgrade xorlab

To upgrade xorlab to a newer patch, run the following command as the `admin` user on all xorlab hosts in the provided order:

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

Upgrade order:

1. Sandbox (only applicable for on-prem DANA appliances)
2. XCC
3. MTA

After you ran the command on all hosts, the upgrade is finished. You can use `docker ps` on each host to verify that the new version is running.

## 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).
