Hi @yukihyou,
First, I’ll preface this by saying we don’t officially support syncing across symlinks/junctions . This post goes into more detail about that: Syncing symlinks/hardlinks/junctions/etc.. - how does it work?
Now that that’s out of the way, the idea you propose should be possible, although it is not something we’ve tested so you’d want to experiment with some test data beforehand. The key aspects to hit would be:
-
Ensure a full recursive sync:
Recursive sync will need to be done on each folder in the “proxy” system and it will need to done to completion. This can be an issue, at times, because the bulk recursive download operation can abort when certain types of errors, or multiple errors are encountered, leaving folders in a placeholder state. If this happens, then the rules you set on the structure will not affect existing folders that are in a placeholder state, so you will want everything exposed. You will probably want to use a basic script that will brute-force the recursive sync. See here for more details: Downloading my 3 TB+ Amazon Cloud Drive contents to my external drive -
Test behavior of a broken junction:
This will probably depend on the nature of the break, but if odrive’s scanning is able to enumerate the target folder and it looks empty, its going to think you purposely deleted data. With odrive’s trash functionality, remote deletes can be prevented, however, and once the junction is restored the detected deletes will be negated (since the data will be back). You would just want to make sure to not have any auto-trashing rules set.
You will probably want to conduct a fair amount of testing in this area.