-
Best archive workflow once project is delivered – to zip or not?
I recently had a bad incident involving media which corrupted during the transfer between a master drive and archive drive. Although it appeared the complete contents of the project folder had transfered successfully (the sum of files and file sizes matched between both folders), I later discovered that over half the media had not in fact been successfully transfered – and only AFTER I had already wiped the master drive.
Research indicates the only way to properly verify a successful, uncorrupted data transfer would be to run a md5 checksum on every file within the folder. I’ve searched high and low for an app that would calculate the checksum of all files within a directory+subdirectories automatically, but that doesn’t seem to exist – you can only do one file at a time.
So my thought is this:
Once a project has been delivered and is ready for archive, I compress the entire project into a zip file. I can then transfer this zip file to the archive drive, and run a checksum on just the zip file to determine a successful and uncorrupted transfer.Does anybody see any problems with doing this? Are there concerns regarding archiving projects into a single .zip file? Does that introduce more risk for corruption (overall corruption of the zip file)?
Thanks.