Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Server Administration Documentation | 2025.1

# General guidelines

Follow these guidelines:

- Read the Requirements for replication systems for replication.
- Assign a unique `serverID` to every server by using the p4 server command to identify each server in your network. (If the deprecated P4NAME is configured, set the serverID to match it.)
- 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 strong passwords to the service users. To learn more, 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. To learn more, see Verifying replica integrity.
- Make sure that each standby server and replica that might be required to take over from its target server The immediately upstream server for replica servers, edge servers, standby servers, proxies and brokers. See also 'upstream server' and 'central server'. during Failover have their own license file. Fill out the form at P4 Duplicate Server Request.

Your search for returned results