From 2019.1 or later to latest (single server)
These instructions assume you have a single server. If not, see From 2019.1 or later to latest (multi-server environment).
Note
- A proxy or broker only needs to get the latest binary.
- You do NOT need to run p4d -xu against offline db.* files (a set of db.* files periodically brought current by replaying the journal files from the production server).
Prerequisites
- To upgrade Helix Core Server to a newer version, your Helix Server license file must be current.
- We strongly recommend that you take a checkpoint so that you know you can recover if something goes wrong during the upgrade. (See Checkpoint files.) It is best to take the checkpoint at a time when the end-users are not active.
-
Make sure that journaling is enabled.
Upgrade Steps
In the following steps, replace
- [P4ROOT] with the path to the P4ROOT directory
- [P4JOURNAL] with the directory path and name of the journal file
-
Shut down the server by running p4 admin stop
- Install the new version of the p4d binary on the system.
- As the OS account owner of the Helix Core Server, run p4d -r [P4ROOT] -J [P4JOURNAL] -xu
- Wait until you see this message:
Upgrades will be applied at server startup.
- Start the server.
- Inform your users that they can resume work.