Here is my “issue”. I have a NC server version 25 that I have to migrate to a new server and then upgrade NC to its latest version.
I have found out the path to go from 25 to the current version:
move 25 version to new server with PHP 7.4.3 then upgrade to PHP 8.1 then upgrade to NC26, then NC27, then upgrade php to 8.2 then upgrade to NC 28, then upgrade Maria DB to 10.5 then upgrade to NC30 and then NC31.
My main concern is that I don’t expect the upgrade to go very smoothly and I’m afraid that sync clients might make a mess in the process.
Should I delete all the unique passwords created in NC and change user account so nothing outside can connect at it while I’m handling the upgrade ? or is there an easier way to do ? or tell NC to answer only local requests (I can test the NC server from the server itself) and then reopen external access once all upgrades have been completed with success ?
No, during the upgrade, your instance is in maintenance mode and the clients won’t sync anything.
What I usually did when upgrading over multiple versions, after each major upgrade, I waited a bit, logged in, checked all the apps and the app data. E.g. sometimes some apps are disabled during upgrades and then if they are not updated and their data was changed between versions (and then again for the next upgrade).
And if you upgrade php and database, often people forget to install all required php modules for the new version.
Yeah but not during the migration and I wanted to check everything looks to work fine before sync clients reconnect to it
yeah same here, I wait that at least one cron job has runned without errors
Yep good question, I installed Nextcloud latest release on new server to check all dependencies are met before I start to migrate on that new server existing nextcloud instances
