we’re students at a German film school (Working on VFX) trying to collaborate over nextcloud that has been set up by the IT at our university. Since the past months have been unpredictable, we now have a unique situation where we need to migrate the sync content of 15 remote artists to a new sync (~400 gig total), and we don’t want everyone to have to re-download everything from scratch as this can take days for some of our artists.
----- Previously, our solution was to sync our entire project share (Server A) to a server where Nextcloud is set up (Server B). Unfortunately this meant duplicating our data tightening our storage space constraints. This folder was called “MNP_nextcloud”
----- Currently, our uni was fortunately able to set up mounting of our project share at Server A as external storage and thus saves us from duplicating the data to Server B. The new folder is called “MNP_nextcloud2” in order to allow a transition from the old server.
This now poses the serious issues that all our artists need to change their sync from “MNP_nextcloud” to “MNP_nextcloud2” (which have identical data, as they point to the same files on Server A). After some testing, this resulted in me having to re-download the entire share, even though all the data that is to be synced is already present. It would download the files and replace each existing file.
Is there any way around this? To do it cleanly? I thought about duplicating the ".sync****.db" file and renaming it to the new hash, but without success. The way it currently is, migrating would cause major issues for our production.
We are all on Windows 10 with the newest client version (.
Thank you for your help,