Requirement by Netflix
The redundancy of original camera files (OCF) and audio files throughout a production is crucial. Data loss can be a huge financial burden and creative loss.
There are multiple ways to backup and verify production assets. Below are our minimum expectations followed by best practices.
MINIMUM EXPECTATIONS
3:2:1 Principle
RAID 5, 6, or 10 (or above) storage (RAID 0 is only acceptable for temporary transfer/shuttle drives, and not for backup purposes.)
LTO (6, 7, 8 or 9 written in LTFS format)
- Hold at least three copies of all original camera files (OCF) and audio.
- Store the OCF and audio copies on at least two different types of media.
- Keep at least one of these backups in a different geographical location from the others.
* Production is responsible for ensuring 3:2:1 practice is maintained through final delivery to Netflix.
If considering cloud storage options, including Content Hub, please contact Netflix to discuss.
Checksum Verification:
- If using MHL, a single MHL should be at the root of every camera and sound roll. One MHL per roll.
During the checksum process, a unique machine-readable checksum manifest (e.g., MHL) should be generated with every offload and accompany the files through all the transfers, including final delivery.
All copies of original camera and audio files should be offloaded using checksum verification, either MD5 or xxHash64be. Checksum verification is built into most professional offload software.
MD5 and xxHash64be are checksum formats
MHL (Media Hash List) is a manifest format (i.e., listing of file names and checksum values of those files)
Visual inspection of camera files during offload:
Whether you’re shooting scripted or nonfiction content, the best time to check for any image or sound file irregularities is during the offload. The visual inspection should cover any possible major recording or data transfer issues and serves as a technical check.
Example method: Scrubbing through the material to perform a spot check of all captured media.
Scripted Fiction Full QC of camera files:
- Providing feedback to key production personnel to discuss a solution to a technical problem.
- Minimizing possible problems in the future.
- The primary purpose of Full QC is to catch correctable technical issues where there is value in finding those issues up-front.
- Full QC is ideally done at real-time playback
- Full QC should be performed at a minimum image resolution of 3840x2160 to best identify visual artifacts (e.g., dead pixels, moire, etc.)
- Full QC should be done in a controlled environment like a lab. If color evaluation is part of the process the monitor should be professionally calibrated.
- Full QC should be done from a checksum-verified safety copy and not a camera mag
Scripted Fiction Editorial Rushes Sign-off
Editorial has access to reports from multiple departments such as Script Supervisor, camera loader and the DIT, and can cross-reference all of these reports with the lab report to confirm they have received every piece of shot material and potentially flag image inconsistencies or possible problems when reviewing.
How to deliver with nodeum?
The process is simply :
- Create 3 task to copy files on TAPE 1 - TAPE 2 & Cloud
- For each task activate the Checksum Verification (MD5-Hash or XXHASH-64be)
- Compare the file MD5 Report to validate the copy is conform to the original file
- Check the report on the processed files see for each file the status (done, failed, ....) Download the report for the package to Netflix
- Make Etiquette easier with the browser to know quickly which number of tape media is used in the delivery Netflix
