Autor: Redaktion

Data security in workflows

Different stages in a production workflow require specific tactics to protect filmic data from loss or damage.

Recording: When recording, it is often impossible to create backup copies automatically. If the recording media fail, there is a risk of data loss. In addition, most professional cameras do not store their own checksums for recorded files so that data changes might remain undetected. Some professional cameras record to a second recording drive or allow data to be transferred live to external devices via a network or SDI interface. If re-shooting of scenes is not possible, both internal and external recording devices should be operated at the same time. In addition to that, the condition of the recording media should be checked regularly in order to detect media errors at an early stage and to exclude faulty media.
[justify]Dubbing: At the latest when recording media are copied for the first time, checksums should automatically be created for each file. Recording media should not be deleted until quality control confirms perfect copies. It is best to use software especially designed for copying that creates checksums and copy reports (Pomfort Silverstack, Shotput Pro or Carbon Copy Cloner). The checksums should later be used to verify the originals when making further copies or editing, as this is the only way to find undetected data changes.[/justify] 
Ongoing work: Creating backup copies of running projects can be challenging because workflows extend across multiple computers and applications and changes to project files are quite common. The best strategy is to automatically save the project files of used applications and create version them if necessary. If all files are located on a central network storage (NAS/SAN), snapshots can be used to freeze certain points in time across all files and thus back up the entire file system completely or incrementally. Modern file systems like BTRFS and ZFS, but also some NAS/SAN systems support snapshots directly. Snapshots are also suitable as a starting point for a complete average backup. If the work is distributed, each computer should be backed up individually and regularly (one backup per hour) (e.g. by OSX TimeMachine). Central snapshots and individual backups are also suitable if individual files have been accidentally deleted.
Archives: All media data and business data that need to be stored for a longer period of time should be backed up with a complete 3-2-1 backup. It is also important to back up all software and operating system versions that have been used for the work on the projects. This is because future software updates may no longer include support for old file formats or individual features. In addition, a backup of software licenses must exist, because it should always be assumed that the recovery will take place on new hardware or a fresh installation of the operating system. Recommendable places for archives are the cloud or offline media (LTO). If the confidentiality of content is important, backups should be completely encrypted. In this case, the keys for decrypting the backup must be kept separately, preferably printed on paper in the vault of the house bank.

Related Articles: