Hey @budowski,
I’ll need to look more into it, but if you are syncing the same remote location with the same client, but in two different local locations, the client may be filtering out the “redundant” remote add event for the item you just uploaded (in order to prevent feedback loops). Typically if a user is using “sync to odrive” they would unsync the corresponding location in the default odrive folder, so that the client is not syncing the same remote location twice.
This doesn’t mean that it will never refresh, but it won’t be a quick “optimized” refresh, and will depend on either the periodic background scanning, browsing into the folder (as you said), or issuing a “refresh” on the folder. Note that using “sync” will use the existing information and not perform folder refreshes unless you tick the option to force refreshes. That is why you are not seeing the items picked-up when you use folder syncing.
Can you run through the this scenario and then send a diagnostic, when you get a chance?
Add a new file within the default odrive folder
Wait 10 minutes
Add a new file using the Dropbox web client
Wait 10 minutes
Send a diagnostic
What I think you may see in the above scenario is that the file added in 1. will not be processed yet by the client (the remote event will be filtered out), but the item in 3. will.
Hey @budowski,
After taking a look, here is the explanation.
The corresponding remote events for a local upload have a good chance of being filtered-out because the desktop was the one responsible for creating the remote event. This is why you are likely to not get quick reflection on your external HD for a change made locally.
The remote events process is not started until an initial, full scan is done, which starts shortly after the software starts-up. In the diagnostic I saw that you had recently started odrive. It began with scanning on the external drive, which takes quite a while to get through because of the amount of data being synced (about an hour and 10 minutes, it looks like).
Once odrive is initialized and has completed all remote scans, the expectation is the following:
A local change in the odrive default folder will likely not reflect quickly to the external HD because of the feedback filtering.
A remote change, like one made from the Dropbox web client, should reflect quickly (within 5 minutes) in both the default folder and the external drive. You will see these events as “(RCR)” refreshes in the sync activity log.
odrive will eventually pick-up all changes with the background periodic remote scan, which happens 1-2 times a day.
Hi @budowski,
Yes. For 1. you could technically use the Windows odrive agent to sync to the external HD on the same computer, if you don’t need the Windows Explorer integration extras (right-click options and icon overlays).
Are you using the external drive strictly as a backup?
Yeah, I’m using the external drive as backup only (since I can’t keep the entire copy of my Dropbox on my computer - too big (about 6TB).
Another issue - I have a MacOS, not Windows