#Chronosync mac

I have used ChronoSync for many years to sync a database between my work mac and my home mac, using an USB stick. On the other hand, if neither machine ever leaves the office, I usually run bidirectional syncs scheduled during the night. Do the first job before I leave the office with the laptop and the second job when I return. If I’m moving database between a desktop and a laptop, I usually use the backup option and have an A -> B job and a separate A <- B job. When it became available to test I evaluated it in the same manner it did not meet my needs and performance requirements so I don’t use it.ĭo you use bidirectional sync or the backup (copy from a to b) option in Chronosync?ĭepends on circumstances. DEVON Sync did not exist when I chose ChronoSync. I needed a safe, reliable, proven trustworthy backup solution for the data on which my income relies. I recommend writing down, prioritizing, and evaluating your needs and comparing them to the available options, which you test and judge based on your needs. So you would actually recommend Chronosync instead of the built in sync option in DTPO? There are many fine competitors of ChronoSync, so it is not the only alternative. For me, none if this is time consuming because I’ve used ChronoSync’s scheduler to run these jobs when I’m out of the office or at night, and I’ve worked out a method of tracking which machine has the current copy of data, to avoid using the wrong instance of a database.

If ChronoSync fails it is always because a target machine or drive went offline, and all I have to do is start over.

So, it’s just easier to copy entire databases among machines. In addition to the difficulty of error-shooting DEVONthink databases, when I evaluated ChronoSync’s dissect packages I found that if not configured precisely date/time stamps in packages can introduce subtle errors in databases that cannot be repaired with tools provided by DEVON or others. Whereas, Chrono Sync and it’s competitors were designed for backing up data.) In fairness, DEVON Sync is not for backups, and should never be used for that purpose. (That daunting task, not easily possible with DEVON Sync, is the main reason I’ll never use DEVONthink Sync. I don’t use “dissect packages” mainly because I’d rather not troubleshoot things like that – if bits and pieces of a database go missing it is very difficult, time consuming, and therefore costly (unbillable time) to sort the problem, regardless of logs or any other aid. On one machine I have had ChronoSync sync and clone jobs running automatically several times daily for years, unattended. It has never failed me, is reliable, and easy to configure and administer. I have used ChronoSync for years to sync databases (and other material) between machines on my LAN.