Ensuring system integrity after any restoration

After any restoration, use the command:

$ p4 counter lastCheckpointAction

to confirm that the lastCheckpointAction counter has been updated to reflect the date and time of the checkpoint completion.

You should also run p4 verify to ensure that the versioned files are at least as new as the database:

$ p4 verify -q //...

This command verifies the integrity of the versioned files. The -q (quiet) option tells the command to produce output only on error conditions. Ideally, this command should produce no output.

If any versioned files are reported as MISSING by the p4 verify command, you’ll know that there is information in the database concerning files that didn’t get restored. The usual cause is that you restored from a checkpoint and journal made after the backup of your versioned files (that is, that your backup of the versioned files was older than the database).

If (as recommended) you’ve been using p4 verify as part of your backup routine, you can run p4 verify after restoration to reassure yourself that the restoration was successful.

If you have any difficulties restoring your system after a crash, request Support.