Hi, I have a new computer and I’m trying to sync with a local sync store the files on my MacMini, which is due to retire, to the new computer. I set up the Local Sync Store on the new computer, enabled incoming connections, did the same on MacMini and started the sync on the new computer. This was the result:
On the new computer the statistics of the database are:
Groups: 285
Tags: 442
PDF/PS: 31
Total: 788 (15 indexed)
On the MacMini computer, those statistics are:
Groups: 284
Tags: 417
PDF/PS: 3580
Total: 10,906 (1 indexed)
Then I started the sync on the MacMini, which showed thousands of items being synced, but the statistics (and spot-checked contents of folders) on the new computer haven’t changed.
I’m at a loss now, feel like I’m stupidly missing something very obvious, but can’t find any other posts in the forum with a conclusion/solution approach that seems relevant.
Any help is greatly appreciated! I need to sync about 20 databases altogether.
You can have more than one method of syncing set up, so you may have Bonjour as well as a local sync store. You can sync to either or both.
A local sync store doesn’t have to be local to one computer. It can be on portable media or on shared storage. It’s a common ground between two or more computers. Each computer using it can sync with it.
That seems reasonable for indexed files. But why aren’t the files ‘inside’ the Research database’s directory tree on the MacMini not part of the synchronisation to the new computer’s Research database? According to help, “Using a Bonjour sync, in which you’d import and sync directly between devices.”
I understood it would move all files mapped in the Research database on the MacMini to the new Research database on the new computer. Now what do I do? Delete the Research database on the MacMini and run the Bonjour sync again. Copy the Research database in its entirety from the MacMini to the new computer and delete it from the MacMini.
Questions from a perplexed DevonThink user…
Thanks for the thoughts.
Files are not mapped but either imported or indexed. Two different approaches, thoroughly explained in the manual and discussed here often. You do one or the other, but you don’t “map” files.
I’d suggest copying the indexed files from the old Mac to the same location(s) on the new Mac and then repair and verify the database on the new one. And take some time to read the manual to dive deeper into the concepts of DT.
No external drive, no cloud drive used for these files. Occasionally files were synced, but files in the same group, stored in the same directory (as shown with the command “Show in Finder”) below the database.
: are the files INDEXED or IMPORTED? (it does not matter what group).
: If INDEXED, are the files in the same macOS path location (exact)? If you pick “Show in Finder” in the Log, does Finder find the files on both machines? INDEXED files are not in the database–only “pointers” to where they exist somewhere external to DEVONthink database.
Actually yes they are. Anytime you have a graphic presentation of a symbolic relationship you have a map: A graphic device used to show relationships. I do not know how the imported and indexed files are maintained logically or physically in the database. A graphic map, produced in Finder, and two lists of database contents are what I have to work from.
I can say it in different ways, but to be clear for you: both indexed files and imported files in a DevonThink Database are mapped when their location in a directory tree is shown in Finder.
I may also respond to your Driver’s Education level remark about reading manuals in the sense of desiring meaningful exchanges. We should all remember: different people, different concepts. Accounting for that can help people find solutions instead of editorialising their problems. This also helps retain the positive and helpful engagements of a community.
The main point with this problem is that not all files from a DevonThink database are being synced to a new database on a new computer. With a focus on this pragmatic issue in the exchange, I hope we’re moving towards a solution.