Importing exisiting Seafile libraries into new instance

I had Seafile Pro installed on my server and working reasonably well on the admittedly old hardware. Using docker, the library (just me as a user) is in /mnt/user/seafile. I ran into an issue where Elasticsearch was running away with too much RAM on my server. Now I don’t fault Seafile or Elasticsearch for this at all. I just have older hardware trying to do too many things at once. RAM limit for ES is set to 2G.

I tried first to comment out Elasticsearch in the docker-compose, which worked, but now no search function works. I was hoping the basic file title search would work, but I now understand that if ES is in place, it is the search engine for the server. Take that away and you’re left with nothing.

I then realized I’m not really making too much use of the Pro features now and would like to add additional users down the road which would exceed the free 3 user limit.

I downloaded and installed the Seafile 12 CE docker template in Unraid and spun that up. It wants to put the data also in /mnt/user/seafile. I wasn’t sure if this would overwrite the existing seafile folder so I made a backup and then let it go. The files are still in the “new” /mnt/user/seafile, but aren’t appearing in Seafile itself. My question then is how can I import these already existing and chunked files into this new instance? I do have a rclone remote configured for Seafile, but that seems silly to “reassemble” the chunks only to chunk them up again, if that makes sense.

Any tips or suggestions would be great! I suppose it wouldn’t be the end of the world to reimport everything, but I’d prefer to not have to turn off a bunch of the other docker containers while my poor server wheezes as Seafile indexes the new data.

P.S. Pre-existing libraries are not encrypted, so hopefully that’ll smooth out the data transfer if at all possible.

Did you also move the database over from the old to the new setup? Also you might need to run the upgrade scripts to modify the database to work with new versions (add new columns and tables and such). The scripts like
upgrade/upgrade_9.0_10.0.sh.

Not moved over, but I realized the db is in an entirely different location than what the new container is looking for.

Trying to figure that one out now.