![]() Sure your workflow is safe enough?įrom a “Tech Tip” perspective you may roll your eyes and not heed the advice but trust us, no matter how safe you think your workflow is, it can likely stand to be a little bit safer. Here are a few suggestions to improve your security.ġ. Use a dedicated Backup system, NOT JUST a RAID system. RAIDs are great to keep you working if a drive goes down, but separate sources dedicated to backup are a MUST for redundant and safe storage.A typical RAID system isn’t smart enough to know if a file is corrupt, but it will do a fine job of making sure you never lose that corrupt file! Should a file become corrupt, a RAID system will just perpetuate the existence of that corrupt file, not provide you with a backup of the viable data.Separate, dedicated backup drives are the only way to ensure the safety of your files going forward.Ģ. You don’t always remember to back up and you can’t always find the time to do it manually. Spend the $50 on professional software that will routinely backup files and check data for changes. Something like Chronosync (pictured below), Superduper or even Apples Time Machine are necessary parts of a safe workflow.ģ. Using features in Capture One Pro 7 like the Catalog workflow can do wonders to streamline a backup workflow. Even if you are dedicated to the Session workflow, it doesn’t hurt to create new Catalogs on a routine basis, referencing RAW files already edited in the Session and importing their adjustments into the backup Catalog.Ĥ. This will result in a Catalog that contains all the adjustments for your RAW data in one, easy to copy/store/archive file.The available “Backup” Catalog feature will not only create a copy of the Catalog that contains your changes since the last backup, but it will also guilt you into remembering by noting the last time you backed up.The backups of your Catalog are easily available in their default location or in a specific location you can choose (perhaps an external and dedicated backup drive would be best)ĥ.When considering the best solution to protecting your data, don’t cheapen out. Consider the real cost of a single lost image. If you’re a traveling photographer, should the hero shot reside in only one location, losing it is the same as losing the whole job. Always backup CF cards while on the road to at least 2 separate sources and, if it all possible, don’t format the CF card until you’re home safe and sound.ĭavid, just purchased C1Pro and transitioning from Aperture referenced images. I recently set up my Aperture organization as a yearly ‘Projects’. These are then broken down into thematic Albums, i.e. Family, Travel, Friends and then sub albums by event. ![]() I was leaning towards using the Catalog structure by creating one Catalog per year with all the sub folders (This would significantly reduce the size of the Catalog that I would use each year and speed up my workflow). While reviewing backup scenarios, I noticed that many C1 users create Catalogs for events (similar to Aperture Projects). ![]() So two questions: Is there a significant benefit to organizing my CP1 library(ies) by event versus by year with sub folders? My plan is to use a 4TB Thunderbolt external drive to hold my raw files, local drive on MBPro to hold my Catalogs, SuperDuper or CCC to backup all to Drobo 5N, and CP1 to backup Catalogs to 4TB drive and Drobo 5N. Does this make sense?ītw, I will only import my current year Aperture library to CP1 and start working from there.
0 Comments
Leave a Reply. |