Auditing a (somewhat) dynamic archive

[Paul Dougherty]

Hi,

I work for large nonprofit with the 27 TB archive of video files that we’re constantly adding new projects to. While I value Fixity to audit the foundation of the archive we just created, it doesn’t seem as though the an existing Fixity project can accommodate new folders that get added to a given directory.

Correct me if I’m wrong but this is the missing functionality I seek… if fixity were to encounter a new folder added to a given directory after the original scan it would report it (as new), and then (ideally) go about computing checksums, such that on the next scan there would be no need to report this folder as new, instead it’s just another nested folder to audit.

As a rule we would never add to or tinker with folders that have been submitted to the archive, but since we serve a production environment, the archive is not fixed but somewhat dynamic.

Thanks in advance for feedback.

Paul Dougherty

International Rescue Committee

[Pamela Vizner]

Hi Paul,

Thank you for your feedback on Fixity! The application does in fact function the way you are describing it: Fixity will identify any new folders placed in the directories set for scanning and report all files within them as "new". In the subsequent scheduled scans, if the folder and all its files remain the same, files will be identified as "confirmed". Would this functionality serve your needs?

Let us know if you have further questions about the application and its functionalities, we are happy to help.

Best,

Pamela

[Paul Dougherty]

Hi Pamela, that is great news and what I was hoping for:)