Verifying replica integrity

Multi-server installations are accessed through the p4 journaldbchecksums command, and their behavior is controlled by three configurables: rpl.checksum.auto, rpl.checksum.change, and rpl.checksum.table.

When you run p4 journaldbchecksums against a specific database table (or the set of tables associated with one of the levels predefined by the rpl.checksum.auto configurable), the upstream server writes one or more journal notes Entries added to journals and checkpoints that provide information for subsequent users of the journal or checkpoint. For example, replica servers might take action based on the journal notes they process. containing table checksum information. Downstream replicas, upon receiving such journal notes, verify these checksums and record their results in the structured log for integrity-related events. To learn more, see Journal notes.

These checks are also performed whenever the journal is rotated. In addition, triggers allow you to take action when journals are rotated. See Triggering on journal rotation.

Administrators who have one or more replica servers deployed should enable structured logging for integrity events, set the rpl.checksum.* configurables for their replica servers, and regularly monitor the logs for integrity events.