My remote syncing (via Dropbox) has become much less reliable in recent months.
I regularly find databases have stopped syncing - even though there are no errors logged at either side. The sync progress indicator completes, and all looks good. However, the files have not been synced. There is no particular database/s always affected, or pattern that is discernible. It happens at least every 2-3 weeks and sometimes as many as 3 or 4 databases have stopped syncing. The problem is it may be a couple of weeks before anyone realises they are out of sync.
Shut down reboot, verify & repair, (on both side) no errors, try again, still no success. Verify remote syncstore “Quickly" or "Thoroughly” also does not help.
In the end only a “Clean” of the syncstore fixes the issue. When the databases are 10-15GB in size, cleaning is a major data usage problem!
It happens so often I have had to put a text file with a colour label in the inbox of every database, and a smart group shows all the colour labels. I added a second Mac in my office, and all databases are on both machines. Every week I change the label colour and wait to see if the change propagates through. This obviously only proves the syncstore is ok, but it has helped.
We have 13 DEVONthink users around the world, and each share between 4-8 databases via Dropbox. The files that change in the various databases would probably average between 100k to 1MB in any one day, and maybe up to 100MB if a lot changed.
Up until few months back the sync was absolutely bullet proof for a very long time. If any sync did stop (very rare), a verify and repair would fix the issue and sync would restart itself.
It feels like something in a more recent DT3 build has made the sync process more fragile, but with no error shown, there is no way to know.
My location has has always had problems with the internet connection occasionally being dropped mid sync, but it always picks up again and continues when the connection comes back.
Likewise Dropbox has thrown glitches and error messages on odd occasions, but again, the sync always picked back up again.
One last oddball thought. One database did stop syncing more noticeably than others. It had RSS feeds which no longer were live and always errored in the log. I deleted those feeds and that database syncs much the same as the others. That was the only database with RSS feeds.
Any suggestion what to look for next time the sync fails?