Configuring a read-only replica
To support warm standby servers, a replica server requires an up-to-date copy of both the master server’s metadata and its versioned files.
To help the standby server stay as current as possible with the master server, consider setting the rpl.journalcopy.location configurable. The value of 1 could keep the standby server's journalcopy more current with the master server's journal by writing the journalcopy to a faster device than the device in the journalPrefix configurable defined for the standby server.
Replication is asynchronous, and a replicated server is not recommended as the sole means of backup or disaster recovery. We recommend that you maintain a separate set of database checkpoints and depot backups.
In addition, see the Failover topic in Helix Core Server Administrator Guide: Fundamentals.
Disaster recovery and failover strategies can be complex and site-specific, in which case Perforce Consultants are available to assist organizations in planning and deployment.
The following extended example configures a replica as a warm standby server for an existing Helix Core server with some data in it. For this example, assume that:
- Your master server is named
Masterand is running on a host calledmaster, using port 11111, and its server root directory is/p4/master. - Your replica server will be named
Replica1and will be configured to run on a host machine namedreplica, using port22222, and its root directory will be/p4/replica. - The service user name is
service.
You cannot define P4NAME using the p4
configure command because a server must know its own
name to use values set by p4 configure.
You cannot define P4ROOT using the p4
configure command because it is important to avoid the risk of specifying an
incorrect server root.
Your search for returned result(s).
