MD5 (Base64)

Checker name

MD5 checksum check (base64)

Description

Calculates the MD5 checksum of a restored file and supports comparison with either a configured checksum value or the checksum stored in the Bacula Catalog.

This checker is useful for Catalog comparison because Bacula stores file checksums in Base64 form.

Attribute

MD5 checksum (Base64)

Selecting this attribute in Verification Rules causes Bacularis to execute the MD5ChecksumBase64Check checker.

Supported operators

• == - equal to

• != - not equal to

• C== - equal to the value stored in the Bacula Catalog

C== is the user-facing Catalog comparison operator. Its internal checker identifier is Equal Catalog Value.

Expected value

For manual comparisons, provide the expected MD5 checksum in Base64 format.

When C== is used, the expected checksum is read automatically from the Bacula Catalog. The Catalog-compatible value is compared in Base64 form without trailing = padding.

Capabilities

This checker requires a Restore Destination with the File restore checks capability enabled.

Requirements

No additional requirements.

Examples

Compare a restored file with a manually supplied checksum:

/srv/data/example.bin  MD5 checksum (Base64)  ==  <Base64 checksum>

Compare the restored file with the checksum stored in the Bacula Catalog:

/srv/data/example.bin  MD5 checksum (Base64)  C==  Catalog value

Notes and limitations

For regular files, Catalog comparison requires a corresponding checksum to be available in the Bacula Catalog for the selected backup.

For regular files, the selected path must exist and be readable. If the file does not exist or cannot be read, the check fails.

Bacula does not calculate file-content checksums for symbolic links and stores 0 as the checksum value. For Catalog comparison, Bacularis handles this value without following the symbolic link to its target.

Manual checksum comparison is not supported for symbolic links. The checker does not follow symbolic links to calculate the checksum of their targets.