93.2.1.9 MMS - MD5 Checksum

MMS - ETERE MD5 CHECKSUM is the action used by ETERE system to generate or check the MD5 hash file.

MMS---MD-Checksum---General-Tab

MMS---MD-Checksum---MD5-checksum-Tab

To create this action, the following fields must be filled.

GENERAL TAB

Name: Give a short name to identify the action.

Operation: Select "Etere MD5 CHECKSUM" option.

SOURCE

Current metafile: Select this option to use the current metafile.

Device/Codec: Select the source device and codec. If the meta device contains multiple versions (codecs) of the file, select the codec you wish to copy or delete.

OPTIONS

Do not use media folders even if configured: Enable this option to ignore the translated path, even if it's configured.

Concurrent processes: Indicate the maximum number of actions that can be taken at the workstation simultaneously.

Never update DB files: The file won't be updated in the Database.

Update all assets linked to the source file: If enabled (default), the copied file will be associated with all the asset forms linked to the source file.
Enabling this option is useful, for instance, when a single file is used by multiple assets (e.g. which transmit it overlaid with different logos); in this case, every time the file is copied, the new copy will be updated across all linked assets.
If disabled, the copied file will be associated only with the asset form for which the T-workflow has been launched.
Disabling this option is useful, for instance, when a single big file (e.g. a live feed recording) is used by multiple assets which partially retrieve a smaller file; in this case, only the support from which the partial retrieve has been executed will be updated.

Use SSL: Enable this option to use SSL (Secure Socket Layer) when saving the file in a destination path over the network. If enabled, the service media manager would attempt to complete the action using the following authentication steps in sequential order:

- FTP over TLS (Transport Layer Security)
- FTP over SSL (Secure Socket Layer)
- Plain FTP (without encryption)

If the FTP server supports SSL encryption, the Media Manager service will use a new set of libraries for copying files. Else, Plain FTP would be used.

Use passive mode: If checked, the FTP client will try to use passive mode for all file transfers (upload/download/move); otherwise (if disabled), the standard active way will be used.

Use "passive server to server" when moving between FTP servers: Enable this option if both source and destination devices use the FTP protocol and support 'passive mode'.

Check the file size with db value: If enabled, an additional check would be performed to compare the size of the copied physical file and the file size stored on db. This is useful to signal if the file has not been copied entirely into the destination folder. In this case, its file size differs from the original one, and this check can alert the operator by signalling an error in the wf.

Skip media check: Allow to avoid checking if the source file's device and codec match with the ones defined in the action. This is mandatory in the case of the Memory cut action because the Memory cut wf is attached to a new empty asset with no meta file, so the action would end in error if this parameter is disabled.

Maximum Bandwidth: The max. The bandwidth option is only supported for copies to limit the bandwidth used for data transfers.

MD5 CHECKSUM TAB

Generate MD5 file hash: Calculate the MD5 file hash of a media file and store it in the database.

Check MD5 file hash: Calculates the MD5 file hash of a media file and compares this value to the one stored in the database.

In case the MD5 HASH does not exist: Specify the behaviour in case the MD5 hash is missing for a metafile, that is, when at least one of the metafiles has an MD5 hash that is NULL:

• Exit with ERROR status (default) -> Exit the action with the "error" status.
• Exit with ABORTED status -> Exit the action with "aborted" status.
• Generate the MD5 HASH -> Generate a new MD5 hash for the metafile.

This parameter is useful to define the route the wf should follow, once this action is completed and to correct all the assets which have one or more metafiles without MD5 hash.

How to verify if the MD5 hash file has already been generated or checked?

The presence of the MD5 hash for a metafile is visible in the Media data tab under the MD5 Checksum column.

The possible MD5 Checksum results are listed below:

Green icon - The MD5 Checksum hash value has been calculated and stored but is still present in the file, or, the MD5 Checksum hash value was calculated and matched the stored value.

Red icon - The MD5 Checksum hash value does not match the stored. The archived file might have been corrupted.

Additional notes

• Please note that the MD5 checksum actions can be performed only for files stored on path-based meta devices (e.g. disk volumes). Using this action against files stored in video servers (e.g. ETX, Omneon) is NOT supported.

• When an asset file is removed, its md5 hash checksum is also removed.

It is impossible to remove the MD5 checksum from the asset without deleting it. However, it's possible to overwrite the existing MD5 checksum by creating a new one on the asset. The assets must be restored to disk to create a new checksum on assets in LTO tapes.

• Every time a file with an MD5 checksum is transferred, the existing checksum is also copied along with the file into the target metadevice.

• It is not recommended to copy the zipped files containing MD5 checksum files from the source to the destination folder; it could result in discrepancies in checksum value when files are uncompressed at the destination folder. Zip archive has its own checksum, different from the MD5 checksum.