That is not a sync, that is a one-directional, incremental back-up, it is everytime saving the changes from the database you worked with to it’s older adequate on the other Mac.
And there is no problem with that. That is the way I back-up my DT databases everyday - databases closed of course. No matter how many files and gb my databases hold, my back-up app only copies the changes: it copies new added files and the dtmeta-files that changed because of adding files. There is no way that it would ever copy the whole package/database just because I made small changes. I use Synchronize Pro X, but ChronoSync will do the same.
Now that would be a sync.
Problem is that DT on Mac1 with databaseA does not know what you do with databaseB on Mac2 booted from Mac2. And I would not expect a third party app to tell DT that by merging both databases’ indexes, at least I would not trust that concept. Synchronizing the files (no back up, bringing them together instead) that the database holds is one simple thing for any decent back-up application, but making DT aware of that changes is another thing which I would l leave to DT’s sync feature which is in the making and already in internal testing, see [url]Synchronizing on two Macs]
Kind regards,
Bernd