Thanks Wei - don't be worried - i kept my old config files and indeed it works out well. Sometimes "lazyness" might have it's benefits ;-) Beside the topic from the other letter regarding my cpu-core count isn't present at the dashboard anymore.
Am Mi., 17. Nov. 2021 um 13:04 Uhr schrieb Wei ZHOU <ustcweiz...@gmail.com>: > Hi Chris, > > When you upgrade, do NOT overwrite existing configuration files. Normally > it should work with the new version as well. > > The backup of configs and databases are used only when you face some > issues in upgrading (for example config files are overwritten by mistake, > some DB exceptions) , then you have to rollback to the older version or > recover the config files. > > -Wei > > On Wed, 17 Nov 2021 at 12:51, vas...@gmx.de <vas...@gmx.de> wrote: > >> Hi Wei, >> >> thanks for your suggestions. >> Regarding the database - that's what i did (in addition to the usual >> back-up of the dabase during normal operation). And this "step" is >> explicit >> mentioned in the upgrade instructions. >> How ever regarding the configuration files, there i was a bit "suprised". >> It seems there have been quiet some changes regarding the actual values / >> nameing inside the configurations. >> Not that there have been changes, but that this topic wasn't mentioned >> in >> the upgrade guide or some recommadations on how to deal with it. >> >> As far as i understand - and please correct me here if i am wrong - the >> workflow would be to backup the current config, install the new version of >> the config files during upgrade and then go through the configs and try to >> merge the settings / values by hand? >> >> Regards, >> Chris >> >> Am Mi., 17. Nov. 2021 um 12:23 Uhr schrieb Wei ZHOU < >> ustcweiz...@gmail.com>: >> >> > Hi Chris, >> > >> > It would be good to backup all the folder /etc/cloudstack/management/ >> and >> > database before upgrade. >> > >> > -Wei >> > >> > On Wed, 17 Nov 2021 at 11:54, vas...@gmx.de <vas...@gmx.de> wrote: >> > >> >> Thank you Rohit for your answer, will keep that in mind for further >> >> upgrades ahead! >> >> Regards, >> >> >> >> Chris >> >> >> >> Am Mi., 17. Nov. 2021 um 11:04 Uhr schrieb Rohit Yadav < >> >> rohit.ya...@shapeblue.com>: >> >> >> >> > Hi Chris, >> >> > >> >> > That's typical of a Linux package manager to ask questions when >> during >> >> an >> >> > upgrade the config files change. You most likely want to keep the >> >> original >> >> > config than package maintainers, esp for db.properties, >> >> server.properties. >> >> > It's a good idea to backup them before upgrading, and then manually >> >> > reconcile the config files if necessary. >> >> > >> >> > >> >> > Regards. >> >> > >> >> > ________________________________ >> >> > From: vas...@gmx.de <vas...@gmx.de> >> >> > Sent: Wednesday, November 17, 2021 02:00 >> >> > To: users@cloudstack.apache.org <users@cloudstack.apache.org> >> >> > Subject: Questions regarding config-files during upgrade to CS4.16 >> >> > >> >> > Hi everyone, >> >> > >> >> > currently I am trying myself on upgrading my cloudstack environment >> from >> >> > 4.15.2 to 4.16. >> >> > >> >> > I am a bit puzzeled as, while upgrading via repositorys i get the >> >> > notification / question, if i want to use my "old" configuration >> files >> >> on >> >> > the Management Server. Or use the newly provided from the maintainer. >> >> > As the "newly" provided seem to inherit the values from the old >> config >> >> > files, i currently choose to keep and use the old ones. >> >> > Is this the correct way for upgrading=? Didn't found something >> >> mentioned in >> >> > the upgrade-guide regarding this. >> >> > >> >> > Regards, >> >> > Chris >> >> > >> >> > >> >> > >> >> > >> >> >> > >> >
