> For the complete documentation index, see [llms.txt](https://docs.trilio.io/openstack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trilio.io/openstack/upgrading-to-t4o-6.x-from-older-supported-versions/upgrade-triliovault.md).

# Supported Trilio Upgrade Path

The following versions can be upgraded to each other:

| From                                | To    |
| ----------------------------------- | ----- |
| 4.1 GA (4.1.94) or 4.1.HFx          | 5.x.x |
| 4.2 GA (4.2.64) or 4.2.HFx or 4.2.x | 5.x.x |
| 5.0 GA or 5.x.x                     | 6.x.x |
| 6.1.x                               | 6.2.x |

### Notes for upgrades to 6.2.x

Trilio for OpenStack 6.2 introduces the [Dynamic Mount Service (DMS)](/openstack/about-trilio-for-openstack/triliovault-for-openstack-architecture.md#dynamic-mount-service-dms), which changes how backup targets are mounted on controller and compute nodes. Upgrading from 6.1.x to 6.2.x therefore has a one-time migration beyond the usual package upgrade:

1. The `trilio-dms` service is deployed alongside the existing Trilio services on **every controller and compute node** that needs backup-target access. Deployment scripts in `triliovault-cfg-scripts` (branch `6.2.x`) handle this automatically.
2. The `/etc/triliovault-dms/` configuration tree — `server.conf`, `client.conf`, `rootwrap.conf`, `rootwrap.d/dms.filters` — is laid down on each node.
3. A database schema migration adds the `backup_target_mount_ledger` table used by DMS. This is applied by `workloadmgr-manage db sync` and the equivalent `dmapi` migration step, both of which are run automatically by the upgrade playbooks.

Detailed platform-specific steps are in the platform upgrade guides.

> **Platform availability at 6.2.0 GA:** the upgrade path from 6.1.x to 6.2.x is supported on **RHOSO 18.0** at GA. Support for other platforms will land in subsequent 6.2.x releases.