There may be some throttling from Apple’s servers, so the initial sync should be done one database at a time.This is a single stage sync, writing to Apple’s servers.iCloud can stall (which is beyond our control or detection).This is a two-stage sync: syncing locally first then iCloud does its own syncing.Questions of privacy, but can be offset using an encryption key.Any cloud service can have slow/unresponsive servers, limit maximum connections, and throttle bandwidth.Requires access to the volume or machine where the sync store is locaterd.They can sync when they’re on and running DEVONthink. Can be located on an external drive or a shared resource, like an NAS.Firewalls must allow exceptions for DEVONthink traffic.Only works on LANs permitting Bonjour or non-standard port traffic.Requires devices to be on and our app(s) to be running.Direct machine-to-machine syncing with no intermediary.Here is a simple matrix with things to consider when choosing a sync method… If you intend to sync with DEVONthink To Go on an iOS device, option 2 cannot be used. Like the Dropbox option, a remote sync store is created on the server. WebDAV server (such as macOS Server, ownCloud, some NAS drives) or a WebDAV-enabled cloud service (like CloudMe). This requires DEVONthink 3.6.2 or later and DEVONthink To Go 3.x or later. Another iCloud mechanism but, similar to Dropbox syncing, it’s a single-stage sync, writing directly to Apple’s servers. This requires DEVONthink 3.x and DEVONthink To Go 2.6 or later. Using Apple’s servers as a storage location, this is a two-stage sync, writing to the local machine quickly, then iCloud itself transfers the data to Apple’s servers and between machines. NOTE: This is NOT the same as “putting my database in my Dropbox folder”, which you should never do. NOTE: While neither Google Drive nor OneDrive is specifically supported, you can use a local sync store in your local Google Drive or OneDrive folder.ĭropbox Sync location This creates a remote sync store in a private folder on the Dropbox servers. This does not require Machine A to be running for Machine B to sync. It can also be stored on a connected external drive or thumb drive. This is a file that can reside on a commonly accessible location, like a drive on your network. Note 2: If you have a firewall On or an application like Little Snitch monitoring your network, you must put in exceptions to allow DEVONthink’s network traffic. This is controlled by the network administrators, not DEVONtechnologies. Note: Public and corporate WiFi often disallow Bonjour connections. Mac to Mac:īonjour (Direct Connection) Syncing between two Macs that are on the same local network that are On and running DEVONthink with the particular Syncing database(s) open. It just means there are some stumbling blocks that can occur when using them - blocks caused by the conditions mentioned, not our sync engine - and they can inhibit proper syncing. This doesn’t mean you can’t successfully use a remote solution. account does not make it an optimal solution for all situations. These are limitations sync cannot overcome, any more than your web browser can.įor the optimal experience, you should use a remote sync option when you need to. Bandwidth throttling measures employed by cloud services.Maximum concurrent connection limitations imposed by the service.Remote server reachability and response times.However, you should still consider whether quick updates are needed in this situation.Īny remote sync location has inherent weaknesses due to: Or you may have a colleague, assistant, or significant other accessing a device while you’re away. It would be impractical to move one machine to be able to sync. For example, you may have an iMac at home and an iMac at work. We suggest using a remote sync option when it is needed, not merely because the option is available. Sync is simple but you need to choose the type of sync method to use. Syncing Mac-to-mac or Mac-to-mobile is done via our Sync plugin (see DEVONthink’s Preferences > Sync or DEVONthink To Go’s Settings > Sync: Locations).
0 Comments
Leave a Reply. |