-
CatDV to Cache-A archive inconsistencies
Hi all,
I have been establishing our CatDV/Cache-A archive system over the past few months, and I think I have good handle on the best workflow etc. I have recently upgraded to CatDV Pro 9 with Archive and MXF options. The upgrade has solved one particular issue I was having with my JVC MXF (equivalent to XDCAM format) media, but I am still experiencing inconsistencies in the actual archive to data tape. More on the specific issue in a bit, but first a little information on the system I have established to track my archives as I go.
I have established a spreadsheet data base system to track which original media (2 Different types)has been logged and sorted into category specific catalogs. I also have another spreadsheet tracking the category catalogs themselves, when a catalog is first archived to CacheA, which LTO tape it was archived to, and eventually any dates on which the archive is updated.
After lots of trial and error, back and forth between CacheA and CatDV support (both seem to playing a bit of a blame game) I still don’t have a successful transfer from a CatDV catalog to CacheA tape as every transfer I’ve attempted results in errors logged in the CacheA transfer log, which CacheA indicates are never good.
I have carefully archived media using the command provided in CatDV with one category catalog at a time or if the catalog is large, in chunks of 20 to 30 GB within a catalog. During these archives, I do nothing else with the computer and wait until the CacheA browser based user interface indicates a successful transfer in the transfer log before attempting anything else.
The two media types in question are P2 MXF and JVC/XDCAM MXF which are both imported into the catalogs as ‘Metaclips’ not ‘movies’ to ensure all of the MXF data is packaged into a single clip and can be successfully restored after dumping to the CacheA.
After upgrading to CatDV 9, I erased all of my LTO tapes and started fresh as much of what I had already archived all contained transfer log errors. (It’s a long story, but to a degree I had been ignoring the errors during the first archive transfers because CacheA had indicated another issue with the CacheA UI I was experiencing was not something to worry about) CacheA indicated that the CatDV upgrade should clear that up, but upon my first post-upgrade test the same errors were replicated, specifically an issue with P2 media.
The transfer logs seem to indicate that while some P2 media in a particular directory transfer successfully other metaclips result in a transfer error that indicates the media is not accessible on the disk. I’ve attached the transfer logs of my most recent catalog archives. I have touched base with CacheA on this matter again, but am still waiting on a response after they deemed it necessary to perform a support connect.
I realize this is a CatDV forum, but perhaps folks out there are also using CatDV to catalog and archive their media via CacheA and hopefully have some insight.
Any thoughts or suggestions are sincerely appreciated. And if you require more information, please let me know I am happy to provide. This issue is one of many I have experienced over a period of months as I work to establish a manageable, efficient and organized catalog/archive system for the long term.
Here are links to the logs from the recent transfer:
3895_321transfersummaryallmountainlioncatalog.docx.zip
3896_321transfersummaryerrorsonlymountainlioncatalog.docx.zip
Thanks,
Lindsay