Helix Core Server Administrator Guide: Fundamentals (2018.2)

Upgrading the Perforce service

You must back up your Helix Server installation (see Backup procedures) as part of any upgrade process.

Important

In replicated and distributed environments (see Helix Core Server Administrator Guide: Multi-Site Deployment), all replicas must be at the same release level as the master. Any functionality that requires an upgrade for the master requires an upgrade for the replica, and vice versa.

Warning

Before you upgrade the Perforce service, always read the release notes associated with your upgraded installation.

Note

Helix Server requires two executables:

  • the Helix Core Server, also referred to as the Perforce service (p4d)
  • at least one Helix Server application, such as the Command-Line Client ( p4)

The Perforce service and applications are available on the Perforce web page for Downloads.

To upgrade from 2013.2 (or earlier) to 2013.3 (or later), you must restore the database from a checkpoint. See Checkpoints for database tree rebalancing for an overview of the process and Upgrading Helix Server - between 2013.2 and 2013.3 for instructions specific to this upgrade.