General guidelines

Follow these guidelines:

  • Read the System requirements for replication
  • Assign a server ID to every server

    • if the server name (P4NAME) is configured, set the serverID to be the same as the server name

    • 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
    • make sure that each service user name is 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.
  • Failover licensing: make sure that any standby servers and replicas that might be required to take over from a master server have their own license file. Fill out the form at Helix Core Duplicate Server Request.