Configuring the forwarding replica

Important

The steps on this page assume you have logged into the master server as the Helix Core user with the access level of super. See Permission levels and access rights in the p4 protect topic of Helix Core Command-Line (P4) Reference. That user can have any name, but for convenience the examples use super:

p4 -u super login

Create a checkpoint of the master server.
p4 -u super admin checkpoint or p4d -jc
For more information, see Backup and recovery concepts and Checkpoint files.
Restore from that checkpoint on the machine that the forwarding replica will run on.
p4d -jr checkpoint_file
Copy the versioned files from the master server to the forwarding replica.

On Linux, cp -R /master/depot /replica/depot/

On Windows, Xcopy /E /I C:/master/depot C:/replica/depot

Versioned files include both text (in RCS format, ending with ,v) and binary files (directories of individual binary files, each directory ending with ,d). Ensure that you copy the text files in a manner that correctly translates line endings for the forwarding replica’s filesystem.

If your depots are specified using absolute paths on the master, use the same paths on the forwarding replica. (Or use relative paths in the Map: field for each depot, so that versioned files are stored relative to the server’s root.)
Start the Helix Core (p4d) server on the forwarding replica using the P4PORT value of forward:1667 and both the -n and -d options:

$ p4d -p forward:1667 -n -d

Note
Ignore the warning about topologyRegistration.
The -n option is necessary until we set the serverid to correspond to a type of server that does not need a license.
Set the serverid to fwd-1667 for the forwarding replica:
$ p4 -u super -p forward:1667 serverid fwd-1667
Confirm that the serverid is correctly set at the server address of forward:1667.

$ p4 -u super -p forward:1667 serverid

The output should be:

Server ID: fwd-1667
Log the service user into the master server using the location of the tickets file specified in the Spec configuration section of Configuring the master server for the forwarding replica:
$ p4 -u super -p master:1666 -E P4TICKETS=/p4/.p4tickets login service
On the forwarding replica, stop the server:
$ p4 -u super -p forward:1667 admin stop
Restart the server on the forwarding replica:

$ p4d -p forward:1667 -d

Confirm that the p4 pull commands specified in the fwd-1667 startup.N configurations are running:
$ p4 -u super -p forward:1667 monitor show -a
The output should be similar to this:
```
18835 R service00:04:46 pull -i 1
18836 R service00:04:46 pull -u -i 1
18837 R service00:04:46 pull -u -i 1
18926 R super 00:00:00 monitor show -a
```

Confirm that the forwarding replica is replicating.

$ p4 -u super -p forward:1667 pull -l -j

The output should be in this format, with the replica sequence matching (or being close to) that of the master.

Current replica journal state is:    Journal 511,    Sequence 29233313
Current master journal state is:    Journal 511,    Sequence 29233313.
The  statefile was last modified at:    2019/10/22 15:19:55.
The replica server time is currently:    2019/10/22 15:19:59 +0100 BST