Verifying files by signature

Helix Server administrators can use the p4 verify filenames command to validate stored MD5 digests of each revision of the named files. The signatures created when users store files in the depot can later be used to confirm proper recovery in case of a crash.

If the signatures of the recovered files match the previously saved signatures, the files were recovered accurately.

If a new signature does not match the signature in the Helix Server database for that file revision, Helix Server displays the characters BAD! after the signature, and you should contact Perforce Technical Support.

See also Recommended weekly verify in the Backup procedure.