I’ve done a search and this has been discussed in a few threads, but I couldn’t find a resolution of the problems of syncing two machines. I use Chronosync, and it works nicely for me. Here are the key points…
I use bidirectional sync for everything, but would never edit a DT database on one machine and then on the other machine without first synchronising them. This gets around the “opaque database” issue. So… NEVER work on a database on two machines at once.
Make sure that the “Dissect Packages” option is ticked in Chronosync. This will circumvent having the WHOLE .dtBase package copied every time you sync. My database is 1.7GB and growing (and I’ve only been using DT for a week or so). Full instructions below.
If you move a referenced file and then synchronise, the reference on the destination machine will still point to the old location, and so will be broken. I believe that if you equivalently move the file on the destination machine BEFORE syncing, all should be well (because Chronosync won’t copy from the source machine and thereby lose the locally-unique HFS+ file id), but I haven’t tested this yet (I’m away from my desktop). There’s a script here that you can use to find broken references: devon-technologies.com/phpBB … php?t=4073
I’m hoping to find an elegant solution to (3) one day
Hope this is useful to someone…
In Chronosync General preferences, tick “Display all files”, “Show package contents” and “Dissect packages”. This will only apply to NEW Synchronizer Documents; gets me every time, I tick a pref and it has no effect on the Synchronizer Document I’ve already created!
In the Synchronizer Document containing the .dtBase file, go to Options and tick “Dissect packages”. Go to Analyze and tick “Display: All” and then “Pkgs”.
Now it should just sync the changed files within the package (haven’t tested it because I’m away from my desktop and am writing this on my laptop; Chronosync displays the contents of the package as if it were a folder, so I’m 99% sure this will work).