UPDATE - I was about to launch a support ticket thru CCC and decided I would try one more time to create a task that would copy FCP libraries. Since you can dissect your backups to your like, Chronosync doesn’t eat up your RAM. Best of all, you will never feel the pressure on your mac. You can tell it to backup individual folders just once in a day (say the FCPX Cache folder) while versioning the most active, working folder, Projects files, every X minutes.
One Carbon Copy Cloner is slow very slow and as the App title stats it is a cloner.Ĭarbon Copy Cloner is not really useful to keep track of changes in a file.ĬhronoSync on the other hand is an all-in-one app with tools for synchronizing, backups, bootable backups and cloud storage backups.Ĭhronosyc allows a more fine-tuned backup and versioning. I have used both and I strongly recommend ChronoSync. Old thread but maybe someone else has the same question. From just playing with their demos for a few days they both seem to have their pluses and minuses but wonder about real world experience backing up the FCPX, Motion, Logic, Aperture and Lightroom files that we us in projects. I was wondering if there was any advantage to using Carbon Copy Cloner or ChronoSync. I've just changed our backup strategy on one of our machines from Time Machine and Backups for FCPX to just Time Machine for the system files and am thinking of using either ChronoSync or Carbon Copy Cloner plus Backups for FCPX for the production drives.
0 kommentar(er)
