General guidelines

This topic assumes you have read System requirements.

Follow these guidelines to simplify the administration and maintenance of your multi-server environments:

  • Assign a server ID to every server
    • we recommend that the serverID be the same as the server name (P4NAME) if configured

    • use the p4 server command to identify each server in your network
  • Assign a service user name to every server by using the p4 server command (see Service users)
    • this simplifies the reading of logs and provides authentication and audit trails for inter-server communication
    • each service user name should be unique
    • assign service users strong passwords (see "strong passwords" at p4 password)
  • Configure each server to reject operations that reduce its disk space below the limits defined by that service’s filesys.*.min configurables, such as filesys.depot.min.
  • Monitor the integrity of your replicas by using the integrity.csv structured server log and the p4 journaldbchecksums command. See Verifying replica integrity.
Important

Licensing for replica, edge and standby servers:

Replica servers that are not going to be used for failover and edge servers do not require their own license for Helix Core Server (P4D) version 2014.1 or later.

Standby servers and replicas that might be required to take over from a master server do require their own license file. This can be obtained by filling out the form at https://www.perforce.com/support/duplicate-server-request.