I’ve just successfully upgraded my server from 11.4 (via 12.1) to 42.1 (at least in my VMware testing environment^^).
What I’m now looking for is information on what’s changed exactly? I mean, I’m coming from a pretty old (but stable) openSuse version and I’m wondering if an upgrade is even recommendable… like SystemD replacing the script based SystemV.
Are there any things I need to be aware of if I do upgrade? Things to consider/change in my old environment?
I know it’s a pretty broad question, but hopefully a lot of you already did upgrade and could point out a thing or two
I do not know what you exactly mean with “upgrade”. When you mean using the option of that name on the installation medium, then IMHO that is only realy supported when doing one step at the time (11.4 > 12.1 > 12.2 > 12.3 > 13.1 > 13.2 >42.1) and then I assume it would be advisable to realy use those intermediate steps, because several applications (mostly the desktops) will possibly adapt their configurations in an upward compatible way on first login in the newer version. And I am not sure they will cope when jumping versions.
Several people seem to have been able using this way of “upgrade” jumping versions (but I never saw as many as you plan to do), but that does of course not guarantee anything as everbodies system usage is differnt.
My advice would be to do a fresh installation, while of course keeping the user’s data (as in /home and maybe on other places). A backup of /etc in a way that enables you to consult your original configurations when configuring the new installed system might be handy (but never simply copy old config files to the new system, use the old ones as hints).
My experience with SuSE Linux since 8.1 is, that the general rule of “install as new” generally causes less issues than an upgrade.Caveat: upgrading “point releases” (for example: 9.2 to 9.3; 13.1 to 13.2) are usually free of major issues but, upgrading from one major release to another is often “adventurous” (see the issues I experienced with a dual-boot Laptop upgrade from 13.2 to Leap 42.1 . . . ) :shame: .
[HR][/HR]Given that you are migrating server hardware from an older major release to newer one, hcvv’s point regarding System and User’s data is absolutely the most important work-to-be-done with respect to the migration.
[HR][/HR]
The changes you may/could/possibly see as a result of the upgrade to Leap 42.1:
The Linux Kernel is much newer: you could expect much better support for you server’s hardware especially in the area of power control/saving.
The applications are mostly much newer: you can expect much better security (holes where attacks may occur have been patched); very much application dependent but, in an awful amount of cases GUI applications start faster and are more pleasant to use.
System applications are often faster: the time needed for a reboot is possibly reduced (especially if the server has a multiple core CPU).
System applications often change their behaviour and their input parameters: a careful inspection of the start-up parameter values has to be performed to ensure that “everything works as expected”.
It might have not been clear by my post, but I’ve already successfully upgraded a VMware **copy **of my server. And although previous releases did indeed ask of you to install one intermediate release after the other, Leap actually lets you upgrade from 12.1 (not 11 though!).
I’m currently trying out several things after the (virtual) upgrade to know beforehand what works and what doesn’t (my Apache config seems to be broken for instance).
After that I’ll try it with my real server…
But of course, a fresh install is always preferred, even by me^^
Btw: is anyone actually using btrfs on a new install?
Seems to be mightily over-complicating things with all these volumes (that you apparently need for snapshots)…
You should inventory your Server apps.
It would give you a clearer picture the various things you will need to account for both cleaning up an in-place upgrade or if disaster strikes what you will need to install if you need to re-build.
Of course, besides at least one one known working backup of your original system,
You should also identify and perhaps make additional backups of your data.
You mentioned Apache, is it a LAMP?
If so, then in almost all cases, MySQL/Mariadb data stores cannot be automatically upgraded with the system upgrade, you’ll need to create a new database in the upgraded MySQL/Mariadb and import the data.
There have been major changes in PHP since 11.4 if you are using it, your website code may break, your Apache config won’t likely be the only issue that would need to be manually addressed.
Bottom line, if you’re running LAMP, you’ll need to evaluate its upgrade issues separately from the system upgrade.
Keep in mind that VMware virtualized hardware isn’t likely going to cause as many problems as real hardware.
In fact, many companies in your position decide to “upgrade” to a virtualized deployment and leave it at there, operating that way in Production. The penalty might be approx 2% overhead (general estimate) but the benefits can be great, from easier and better backups, testing backups, easier maintenance, etc. There are many documents that describe this, if you decide to virtualize permanently, if your hardware supports you can consider VMware ESXi (it’s free), or other virtualization running on a minimal HostOS.
