Upgrades

P4 DAM is shipped as a native operating system package, like .rpm or .deb, which greatly simplifies upgrades.

Upgrading P4 DAM is usually a zero-downtime operation and can be performed on a live system. Before upgrading, read the release notes for more information on any release specific upgrade instructions.

P4 DAM is built on top of Perforce TeamHub. To install P4 DAM, use the Perforce TeamHub packages.

Before you upgrade

P4 DAM uses MongoDB which is automatically upgraded during the P4 DAM upgrade. However, MongoDB does not support skipping release versions when upgrading, so you must follow the Upgrade instructions in the P4 DAM release notes. The correct order for upgrading P4 DAM is:

  • Make sure you are using P4 DAM 2025.2 before upgrading to 2025.3.

  • Make sure you are using P4 DAM 2023.2 or later before upgrading to 2025.2.

  • Make sure you are using P4 DAM 2023.1 before upgrading to 2023.2.

  • Make sure you are using P4 DAM 2022.2 before upgrading to 2023.1.

Step 1 - Upgrade P4 Server

Make sure the version of P4 Server you upgrade to is supported by the version of P4 DAM and P4 Search you are upgrading to. To learn more, see P4 authentication prerequisites.

P4 DAM features rely on using a minimum version of P4 Server. For example, the asset bundle feature is only supported by P4 Server 2024.2 and later. Consider upgrading to the latest P4 DAM supported version of P4 Server so that you get all of the P4 DAM features.

Upgrade the P4 Server. To learn more, see Upgrade the server in the P4 Server Administration Documentation .

If you upgrade P4 Server after you upgrade P4 DAM, you must restart the unicorn_backend service on the Standard node and all web nodes using the following hth-ctl command to make sure the correct P4 DAM features are enabled:

sudo hth-ctl restart unicorn_backend

Step 2 - Upgrade P4 Search

Make sure the version of P4 Search you upgrade to is supported by the version of P4 DAM you are upgrading to. To learn more, see P4 authentication prerequisites.

The P4 Search index structure changed to improve indexing speeds in P4 Search 2024.3. If you are upgrading from P4 Search 2024.2 or earlier, P4 Search will automatically migrate your index structure to the new one introduced in P4 Search 2024.3. While the migration is happening, the Elasticsearch Hosts service status will display In Progress on the P4 Search Service Status page, see View status. When the migration is complete, the Elasticsearch Hosts service status will change to Success. The time taken for the migration depends on the size of your index, it can be as short as a few minutes for a small index and hours for a larger index.

For P4 Search upgrade instructions, see Upgrading P4 Search in the P4 Search Documentation.

Step 3 - Upgrade P4 DAM

Download the TeamHub packages specific to the host operating system from Perforce's package repositories. After uploading the packages to the server, follow the commands below.

Alternatively, use the Perforce's package repositories directly to upgrade the packages instead of using the rpm -Uvh or dpkg -i commands below.

Standard

RHEL and CentOS upgrades

rpm -Uvh hth-X.X.X-stable.elX.x86_64.rpm
sudo hth-ctl reconfigure

Ubuntu

dpkg -i hth_X.X.X_amd64.deb
sudo hth-ctl reconfigure

Enterprise

When updating the Enterprise deployment type, the package install order (Web or DB) does not matter, as long as they are the same major version. Refer to the release notes for more information on the package install order.

Perforce TeamHub DB

Upload the hth-db package to the server designated for Database role and update the package:

RHEL and CentOS

rpm -Uvh hth-db-X.X.X-stable.elX.x86_64.rpm
sudo hth-ctl reconfigure

Ubuntu

dpkg -i hth-db_X.X.X_amd64.deb
sudo hth-ctl reconfigure

Perforce TeamHub and P4 DAM Web

Upload the hth-web package to the server designated for Web application role and install the package:

RHEL and CentOS

rpm -Uvh hth-web-X.X.X-stable.elX.x86_64.rpm
sudo hth-ctl reconfigure

Ubuntu

dpkg -i hth-web_X.X.X_amd64.deb
sudo hth-ctl reconfigure