In order to increase the reliability and security of HSM operations, Etere highly suggest including MD5 actions in your archive/restore T-workflows, Etere is able to generate and verify the security file hash of media files at every transfer, thus protecting media consistency against corruptions, modifications or substitutions. As explained in Archive workflows and Restore workflows chapters, MD5 actions can be used as follows:
Archive Workflow:
MD Archive (generate a MD5 before file is archived)>>HSM Cache>>HSM(check the MD5 on cache after file is archived)
Restore Workflow:
HSM>>HSM Cache>>MD Archive(check the MD5 on cache after file is archived)
Defining custom MD5 actions is possible from the "Etere Configuration > Configuration Editor" module, going to the "Data Mover > Copy" section, creating a new action with a "MD5 Checksum" process type and selecting one of the following options:
Generate MD5 file hash - Calculate the MD5 checksum of a media file and store it in the database.
For instance, generate a MD5 file hash when archiving files on HSM (see HSM Archive, HSM Archive LTFS).
Check MD5 file hash - Verify the actual MD5 checksum against that stored in the Etere's database; to pass the check the file's MD5 checksum should be equal to the one of the currently processing file (or any other file associated to the same asset).
For instance, check a MD5 file hash when restoring files from HSM (see HSM Restore, HSM Mount LTFS).
Note
For detailed information on this MD5 actions please refer to the "MD5 Checksum" chapter of the Configuration Editor manual.