Upgrade highlights

The following sections include specific highlights for upgrading from a given version.

General upgrade notes

Note the following general information when upgrading.

Category	Description
Backups	Make sure to have viable accessible backups of your relational database (either Oracle or SQL Server), Elasticsearch, and the repository folder on your file system.
Cluster	Make sure to stop services for all cluster nodes before upgrading.
STP/LTP Upgrade	You can choose between two upgrade paths: Short-term path (STP). Upgrade to each new service pack (for example, from 25.3 to 26.1). If you choose this path, you need to go through all the interim service packs to upgrade to the following release. Long-term path (LTP). Upgrade directly from one LTP release to the next (for example, from 25.1 directly to 26.1), without having to upgrade to each of the interim service packs. Refer to the release's upgrade path details below.

Upgrade to 26.1

Category	Description
Upgrade path	This version is an LTP release. You can upgrade to this version directly from 25.1 (the previous LTP release), or from 25.3.

Upgrade to 25.3

Category	Description
Upgrade path	This version is an STP service pack, meaning that you can only upgrade to 25.3 from 25.1. If you have not yet upgraded to version 25.1, upgrade now.
System requirements	Elasticsearch 8.14 and above is required (up to the latest 8.x release). Recommended: 8.14

Upgrade to 25.1 (LTP release)

Category	Description
Upgrade path	This version is an LTP release. You can upgrade to this version directly from 24.3 (the previous LTP release).
Harden the authentication	You must harden the authentication mechanism by replacing the existing hpssoconfig.xml configuration file and storing the encryption key in a keystore file.

Upgrade to 24.3 (LTP release)

Note the following when upgrading to 24.3 (LTP release).

Category	Description
Upgrade path	This version is an LTP release. You can upgrade to this version directly from 16.2.100 (the previous LTP release), or from 24.1.
Java version	JDK 21 is required and must be installed before you upgrade. Before you install JDK 21, make a backup copy of the default Java keystore (cacerts) file from the existing JDK 11 installation. Then, after you install JDK 21, use the backup copy to replace the cacerts file that is provided with JDK 21. This avoids potential issues with the new cacerts file.
Elasticsearch version	For the supported and recommended Elasticsearch versions, refer to the support matrix. The version is validated on startup.
Elasticsearch re-index	The upgrade triggers Elasticsearch re-index. Indexes are re-indexed to version 8. When a space's post-upgrader is running, its Elasticsearch features are not all disabled during the entire process. Instead, features are in downtime only when an index they are dependent on is in the downtime phase of its re-indexing. For details, see "Prepare for Elasticsearch re-indexing" in the 24.3 Upgrade Guide. Note: Re-index must be completed successfully, or you cannot upgrade to the next release.
OData version	OData 4.0 is required. OData version 2.0 services will no longer work and will be fully replaced by OData version 4.0. To continue using OData, your connection must be updated to OData version 4.0. The OData 4.0 URI format is: <https://<server>/odata/v4/shared_spaces/<space_ID>/workspaces/<workspace_ID>/

Upgrade to 24.1

Note the following when upgrading to 24.1.

Category	Description
Upgrade path	This version is an STP service pack, meaning that you can only upgrade to 24.1 from 23.4. If you have not yet upgraded to 23.4, upgrade now.
Elasticsearch version	Elasticsearch 8.x is required. This is enforced on startup.

Upgrade to 23.4

Note the following when upgrading to 23.4.

Category	Description
Upgrade path	This version is an STP service pack, meaning that you can only upgrade to 23.4 from 16.2.100. If you have not yet upgraded to 16.2.100, upgrade now.