Helix Core Server Administrator Guide: Multi-Site Deployment (2019.1)

Starting the replica

To name your server Replica1, set P4NAME or specify the -In option and start the replica as follows:

$ p4d -r /p4/replica -In Replica1 -p replica:22222 -d
Important

To avoid configuration problems, the value of serverID should always match the value of P4NAME if both are set. We recommend setting serverID, but support P4NAME for backward compatibility. Use the p4 serverid command to set the serverID.

When the replica starts, all of the master server’s configuration information is read from the replica’s copy of the db.config table (which you copied earlier). The replica then spawns three p4 pull threads: one to poll the master server for metadata, and two to poll the master server for versioned files.

Note

The p4 info command displays information about replicas and service fields for untagged output as well as tagged output.

Next step

Testing the replica