I’m just trying to set up the following, but from my initial attempt on the “master” pc, things were not going well, so I’ve read a few articles including:
If syncing to both Amazon (pictures) and Onedrive (mainly office365 files and pdf’s) (probably will include Google too), if users (only 2 of us at present, but accessing via web and via desktop and laptop pc’s, so potentially 5 PC’s plus 2 or 3 web clients concurrently active) are editing on local sync’d drives and directly via web browser, the same file will conflicts be reported or saved as copies/conflicts, or will the last user to save “win” and all other changes be lost?
The master machine already has the full dataset that is in all the cloud accounts, is the article above still correct, as all our data is currently in “good” sync?
How do you set up the initial sync to only pull down place holders, every time I’ve tried it defaults to “full files” which would take an age (300gb+ on each service)?
For the slave machines, that currently have partial sub sets of data, but we want access to all placeholders and only those files that in effect they already have, can we use the above method, and will it automatically select the files we move into the odrive file structure to be “offline” … and then we can go through and unselect those files we feel are not needed offline, to allow reversion to placeholders? (saving local space - but giving access to the FULL odrive file system (ie all of onedrive and amazon).
Does this multi editing multi cloud set up have any issues in Beta verse old odrive? What risks are we going to encounter and what steps should be take or precautions / working practices have in place?
- ie if a user on a train to the airport edits a file, it fails to sync, they go off for 2 weeks, the file is edited multiple times while they are away … they get back, open the file still in editing mode, do a bit more, and save it, will the system flag the conflicts?
thanks in advance