Installation of a newer minor version of a package, which usually contains security or bug fixes. Installation of a newer major version of a package or distribution, which brings new features. For a distinction between the upgrade options, see Section 1. SUSE Linux Enterprise Server has a year lifecycle: 10 years of general support and three years of extended support.
SUSE Linux Enterprise Desktop has a year lifecycle: seven years of general support and three years of extended support. SUSE supports previous service packs for six months after the release of the new service pack. Figure 2. If you need additional time to design, validate and test your upgrade plans, Long Term Service Pack Support can extend the support you get by an additional 12 to 36 months in month increments.
This gives you a total of 2 to 5 years of support on any service pack. For details, see Figure 2. SUSE Linux Enterprise Server can regularly check for changes in the support status of all installed products and send the report via e-mail in case of changes. To generate the report, install the zypper-lifecycle-plugin with zypper in zypper-lifecycle-plugin. The report displays changes in the support status after the change occurred and not in advance. If the change occurs right after the generation of the last report, it can take up to 14 days until you are notified of the change.
Take this into account when setting the DAYS option. Change the following configuration entries to fit your requirements:. The file contains two sections. The first section informs about the end of support for used products. The second section lists packages with their support end dates and update availability. The range for extended support levels starts from year 10 and ends in year These contain continued L3 engineering level diagnosis and reactive critical bug fixes.
With these support levels, you will receive updates for trivially exploitable root exploits in the kernel and other root exploits directly executable without user interaction. Furthermore, they support existing workloads, software stacks, and hardware with limited package exclusion list.
Find an overview in Table 2. The repository names map to specific URIs in the customer center. To list all available repositories on your system, use zypper as follows:. This gives you a list of all available repositories on your system. Each repository is listed by its alias, name and whether it is enabled and will be refreshed. The option -u gives you also the URI from where it originated.
Before starting the upgrade procedure, make sure your system is properly prepared. Among other things, preparation involves backing up data and checking the release notes. The following chapter guides you through these steps. Upgrading the system is only supported from the most recent patch level.
Make sure the latest system updates are installed by either running zypper patch or by starting the YaST module Online-Update. Find a list of all changes, new features, and known issues in the release notes. You can also find the release notes on the installation media in the docu directory. The release notes usually only contain the changes between two subsequent releases.
If you are skipping one or more Service Packs, check the release notes of the skipped Service Packs as well. Before upgrading, back up your data by copying the existing configuration files to a separate medium such as tape device, removable hard disk, etc. Back up all data as root. Only root has sufficient permissions for all local files. If you have selected Update an Existing System as the installation mode in YaST, you can choose to do a system backup at a later point in time.
However, this is not a complete backup, as all the other important directories mentioned above are missing. You can save a list of installed packages, for example when doing a fresh install of a new major SLE release or reverting to the old version. Be aware that not all installed packages or used repositories are available in newer releases of SUSE Linux Enterprise.
Some may have been renamed and others replaced. It is also possible that some packages are still available for legacy purposes while another package is used by default.
Therefore some manual editing of the files might be necessary. This can be done with any text editor. Create a file named repositories. Also create a file named installed-software. Back up both files. The repositories and installed packages can be restored with the following commands:. Reasons for this are:. Packages were split to allow a more fine-grained package selection. When a package has been split, all new packages are installed in the upgrade case to retain the same functionality as with the previous version.
Legacy packages from SLE X may be kept for compatibility reasons. In addition, make sure to check the other sections of this chapter for further required preparations.
For more information, see Section 3. Before you start any upgrade, it is highly recommended to back up your database. Configure your MariaDB database to your needs.
Do not use the former configuration file and directory, but use it as a reminder and adapt it. If you have certificates created as MD5, re-create your certificates with the following steps:. If you want a stronger key, replace with a higher number, for example, Place the files server. While version 13 is the default, versions 10 and 12 are still provided through the Legacy module for upgrades from earlier versions of SUSE Linux Enterprise Server.
Because of the required migration work of the database, there is no automatic upgrade process. As such, the switch from one version to another needs to be performed manually. The program files for each PostgreSQL version are stored in different, version-dependent directories. Note that the versioning policy of PostgreSQL has changed between the major versions 9.
When upgrading from SLE 11, postgresql94 will be uninstalled and cannot be used for the database migration to a higher PostgreSQL version. Therefore in this case make sure to migrate the PostgreSQL database before you upgrade your system.
The procedure below describes the database migration from version 12 to When using a different version as start or target, replace the version numbers accordingly. If not already done, upgrade any package of the old PostgreSQL version to the latest release through a maintenance update. Install the packages of the new PostgreSQL major version. If space is tight, try to reduce size with the following SQL command on each database can take very long!
Initialize your new database instance either manually with initdb or by starting and stopping PostgreSQL, which will do it automatically:.
If you have changed your configuration files in the old version, consider transferring these changes to the new configuration files. This may affect the files postgresql. Note that copying the old configuration files is not recommended, because this may overwrite new options, new defaults and changed comments.
Check if the migration was successful. The scope of the test depends on your use case and there is no general tool to automate this step. Otherwise you may not be able to access the guests after the update. If the machine you want to upgrade is registered as a client against an SMT server, take care of the following:. Check if the version of the clientSetup4SMT.
Afterward, restart the upgrade process. Check if the client has successfully been deregistered by listing all client registrations:. If the client's host name is still listed in the output of this command, get the client's Unique ID from the first column.
The client might be listed with multiple IDs. If the client is listed with multiple IDs, repeat the step above for each of its unique IDs. Software tends to grow from version to version. Therefore, take a look at the available partition space before updating. If you suspect you are running short of disk space, back up your data before increasing the available space by resizing partitions, for example. There is no general rule regarding how much space each partition should have.
Space requirements depend on your particular partitioning profile and the software selected. During the update procedure, YaST will check how much free disk space is available and display a warning to the user if the installation may exceed the available amount.
In that case, performing the update may lead to an unusable system! Only if you know exactly what you are doing by testing beforehand , you can skip the warning and continue the update.
Use the df command to list available disk space. For example, in Example 3. On a Btrfs file system, the output of df can be misleading, because in addition to the space the raw data allocates, a Btrfs file system also allocates and uses space for metadata.
Consequently a Btrfs file system may report being out of space even though it seems that plenty of space is still available. In that case, all space allocated for the metadata is used up. If you use Btrfs as root file systems on your machine, make sure there is enough free space.
Check the available space on all mounted partitions. For all file systems including Btrfs you need enough free disk space to download and install big RPMs. For Btrfs with snapshots, you need at minimum as much free space as your current installation takes.
We recommend to have twice as much free space as the current installation. If you do not have enough free space, you can try to delete old snapshots with snapper :. However, this may not help in all cases. Before migration, most snapshots occupy only little space. A server running SMT requires a special upgrade procedure.
Support for this feature needs to be temporarily disabled to upgrade to a service pack. When the update has successfully finished, multiversion support can be re-enabled.
The result should look similar to:. To re-activate this feature after a successful update, remove the comment signs. The YaST installer can, for example, be started from a DVD, over the network, or from the hard disk the system resides on.
Before upgrading your system, read Chapter 3, Preparing the upgrade first. To upgrade your system, boot from an installation source, as you would do for a fresh installation.
However, when the boot screen appears, you need to select Upgrade instead of Installation. The upgrade can be started from:. Removable media. For more information, see Section 4. Network resource. You can either boot from the local medium and then select the respective network installation type, or boot via PXE. A Welcome screen is displayed, followed by the boot screen.
Start up the system by selecting Upgrade in the boot menu. Proceed with the upgrade process as described in Section 4. To start an upgrade from a network installation source, make sure that the following requirements are met:. Both the installation server and the target machine must have a functioning network connection.
Required network services are:. The way to select the boot method and to start up the system from the medium depends on the system architecture and on whether the machine has a traditional BIOS or UEFI. For details, see the links below. Usually you get this choice by pressing F4 , but in case your machine is equipped with UEFI instead of a traditional BIOS, you may need to manually adjust boot parameters.
To perform an upgrade from a network installation source using PXE boot, proceed as follows:. Initiate the boot of the target system and use VNC to remotely connect to the installation routine running on this machine. Before you upgrade your system, read Chapter 3, Preparing the upgrade first.
To perform an automated migration, proceed as follows:. If the system you want to upgrade is registered with the SUSE Customer Center, make sure to have an Internet connection during the following procedure.
After you have booted either from an installation medium or the network , select the Upgrade entry on the boot screen. Make sure you selected Upgrade at this point. If you select Installation by mistake, your data partition will be overwritten with a fresh installation. On the Welcome screen, choose Language and Keyboard. Proceed with Next. On the Select for Upgrade screen, select the partition to upgrade and click Next.
YaST mounts the selected partition and displays the license agreement for the upgraded product. To continue, accept the license.
On the Previously Used Repositories screen, adjust the status of the repositories. By default all repositories are removed. If you have not added any custom repositories, do not change the settings. The packages for the upgrade will be installed from DVD, and you can optionally enable the default online repositories in the next step.
Leave the repository in state Removed. Software that was installed from this repository will be removed during the upgrade. Use this method if no version of the repository that matches the new release is available. Update and enable the repository if it matches the new release. Change its URL by clicking the repository in the list, and then click Change. Enable the repository by checking Toggle Status until it is set to Enable. Do not keep repositories from the previous release, as the system may be unstable or not work at all.
Then proceed by clicking Next. If you do not have that medium, the system cannot be upgraded without registration. Select one migration target from the list and proceed with Next. In the next dialog you can optionally add an additional installation medium. If you have additional installation media, activate the I would like to install an additional Add On Product option and specify the media type.
If all settings are according to your wishes, start the installation and removal procedure by clicking Update. If the machine to upgrade is an SMT client, and the upgrade fails, see Procedure 3. After the upgrade process has finished successfully, perform post-upgrade checks as described in Section 4. During an upgrade procedure, packages may be renamed, removed, merged, or split.
As a result, certain packages can become orphaned and unsupported. Orphaned packages are not automatically removed. The following command gives you a list of these:. Use the list to determine which packages are still needed and which packages can be safely removed. When an upgrade includes changes to a default configuration file, instead of overwriting the configuration file, the package will write one of these file types. Use the following command to list them:.
The upgrade process can be executed automatically. It comes with a set of tools and a Web-based user interface for management tasks. With the integrated AutoYaST technology, upgrades from one major version to the next are possible.
When performing a service pack upgrade, it is necessary to change the configuration on the registration server to provide access to the new repositories. If the upgrade process is interrupted or reverted via restoring from a backup or snapshot , the information on the registration server is inconsistent with the status of the system.
This may lead to you being prevented from accessing update repositories or to wrong repositories being used on the client. When a rollback is done via Snapper, the system will notify the registration server to ensure access to the correct repositories is set up during the boot process. If the system was restored with another method, or the communication with the registration server failed, trigger the rollback on the client manually.
An example for manually triggering a rollback can be that the server was not accessible because of network issues. To do a rollback, execute:. We suggest always checking that the correct repositories are set up on the system, especially after refreshing the service using:. This functionality is available in the rollback-helper package. If the system was not registered before running the upgrade you can register your system at any time using the Product Registration module in YaST.
Provide the E-mail address associated with the SUSE account you or your organization uses to manage subscriptions. If one or more local registration servers are available on your network, you can choose one of them from a list. After successful registration, YaST lists extensions, add-ons, and modules that are available for your system. SUSE offers an intuitive graphical and a simple command line tool to upgrade a running system to a new service pack.
This chapter explains how to do a service pack upgrade step by step with these tools. To make it easy for customers to migrate to a new service pack and minimize downtime, SUSE supports migrating online while the system is running. This has the following advantages:.
The online migration is only supported for migrating between service packs. Online migration is not supported for upgrading to new major releases. For details, see Chapter 1, Upgrade paths and methods.
Use the offline migration to upgrade to a new major release. Use the Client Migration procedure instead. SUSE Manager can also be used. Merchandise Store. Communications Preferences. Don't panic: This document is quite long and detailed, but don't be afraid. In fact the update procedure is very simple, straight-forward and in most cases self-explaining.
Just pick the method that suits your needs best and start with it. This file contains a list of configuration files that could not be updated automatically. These files must be checked and the configurations adjusted manually.
Refer to the SLES9 documentation for details. See the respective section below. This is the only way it has been tested. You have to perform an update to Service Pack 1 first. You can either update to SP2 by using the online update tools to download patches or update using an SP2 installation media.
There is no automatic way to revert changes. Furthermore, the server has to be connected online during the whole update process. Prerequisites: You have to make sure to have your system registered. This will add an update source to your system. Press 'Accept' to apply updates with 'package management' flag set. After installing those, YOU will restart itself.
Press 'Accept' to apply all available updates that are available for SP1. This may also install a new kernel, so you should reboot the system after applying this one. Do not select any other patch at the same time - except for for additional migration patches for add-on products.
If an add-on product e. The migration of the add-on product should be done at the same time as the base product, otherwise there would be rpm dependency conflicts. After the patch is installed, YOU will close. Apply these patches to bring the system to SP2 level. Reboot the system. At this point, an ' rczmd restart ' and a restart of the zen-updater application might be necessary. Apply all maintenance updates that are available up to this point.
This may also install a new kernel a subsequent reboot is recommended. Select the ' move-to-slessp2 ' patch or ' move-to-sledsp2 ' accordingly. Enable these channels if you need to install libraries with debug information in case of an issue. Not in use, yet. Supposed to contain packages for future add-on products. This specific channels require an LTSS contract. Any previous channels from SP2 are visible, but not enabled. These disabled channels are only needed for users who have particular needs.
On registration, the system receives channels from the Customer Center. To list all available channels on your system, use zypper as follows:. This gives you a list of all available channels on your system. Each channel is listed by its alias, name and whether it is enabled and will be refreshed. The option -u gives you also the URI from where it originated.
If you want to remove old channels for example, from SP1 , use zypper removerepo and the name s of the channel s.
For example, to remove the old SP1 and SP2 channels, use the following command:. There you can see a list of URIs; Only channels from this list of products can be added. For example, to add the SP2 Extension Store, use the following command one line, without the backslash :.
There is no supported direct upgrade path from these versions. Instead it is recommended to perform a new installation. In order to avoid dependency conflicts during upgrade, enable this repository before performing the actual upgrade.
On SLES this extra step is not needed. Proceed with Section 7. Refer to Section 7. Before starting the update procedure, make sure your system is properly prepared. Among others, preparation involves backing up data and checking the release notes.
Before updating, copy existing configuration files to a separate medium such as tape device, removable hard disk, etc. Back up this data as root. Only root has read permissions for all local files. If you have selected Update an Existing System as the installation mode in YaST, you can choose to do a system backup at a later point in time. However, this is not a complete backup, as all the other important directories mentioned above are missing.
Before starting your update, make note of the root partition. In Example 7. Therefore, take a look at the available partition space with df before updating. If you suspect you are running short of disk space, secure your data before updating and repartitioning your system.
There is no general rule regarding how much space each partition should have. Space requirements depend on your particular partitioning profile and the software selected. Otherwise you may not be able to access the guests after the update. Support for this feature needs to be disabled for updating to a service pack. Once the update has successfully finished. The result shoul look like this:. For version specific requirements, refer to the release notes coming with the update product. In the release notes you can find additional information about upgrade procedures.
Start the update process by booting from the physical Service Pack media or a network installation source. Updating your system via online migration is done from within the running system. You only need to reboot once, after the update is completed.
In order to do an online update, the following requirements must be met. Make sure to also read Section 7. In order to be able to connect to the update channels, your product has to be registered. Make sure the currently installed version has the latest patches installed. Run an Online Update prior to the Online Migration. On the command line, run the following commands the last command needs to be run twice :.
If your setup involves third-party software or add-on software, test this procedure on another machine to make sure that the dependencies are not broken by the update. The online migration always has to be completed from beginning to end. If an online migration is interrupted in between, the system is corrupted beyond recovery. The following procedure applies to an online migration from SP1 to SP2.
If add-ons are installed on your system, you might need to enter your registration key in order to update the system. Be prepared to have the key available. When all requirements are met see Section 7. Click it to start YaST Wagon. Confirm the Welcome dialog with Next. If Wagon finds that the requirements are not met required maintenance updates are available but not yet installed it will do an automatic self-update, which may require a reboot.
Follow the on-screen instructions. Choose the update method in the following dialog. Choose Customer Center to use the default setup recommended. Click Custom URL to manually choose the software channels used for the online migration. A list of channels will be displayed, providing the opportunity to manually enable, disable, add, or delete channels.
Add the SP2 update source s. Click OK to return to the Update Method dialog. If you want to review changes to the channel setup caused by the update process, select Check Automatic Repository Changes. The system will be re-registered. Confirm the addition of the channels.
If you have selected Check Automatic Repository Changes in the Update Method dialog, the list of repositories will be displayed, providing the opportunity to manually enable, disable, add, or delete channels. Proceed with OK when finished. Click Advanced to manually select the repositories used for upgrading. The Distribution Upgrade Settings screen opens, presenting a summary of the update configuration.
The following sections are available:. Lists the actions that will be performed during the update. You can choose whether to download all packages before installing them default, recommended , or whether to download and install packages one by one. Click Next and Start The Update to proceed. It is safe to abort the online migration on this screen prior to clicking Start The Update and on all previous screens.
Click Abort to leave the update procedure and restore the system to the state it was in prior to starting YaST wagon. Follow the instructions on screen and perform a re-registration before leaving Wagon to remove the SP2 channels from your system. Get a list of these products by running the following command:. Depending on the scope of your installation, more products may be listed.
Register the products installed in the previous step in order to get the respective update channels:. Check the list of repositories you can retrieve with zypper lr. At least the following repositories need to be Enabled :. Depending on the scope of your installation, further repositories for add-on products or extensions need to be enabled. Make sure to list all needed repositories with --from , for example:. Upon completion of the distribution upgrade from the previous step, a Minimal Migration has been performed a minimal set of packages has been updated to the latest SP2 level.
Skip this step if you do not intend to do a Full Migration. In order to do a Full Migration updates all packages to the latest SP2 level , run the following command:. Now that the upgrade to SP2 has been completed, you need to re-register your product:. As an alternative to the Online Migration see Section 7. The update will start like a normal installation.
Either burn it to a DVD or prepare a network installation source as described in Section A network installation source is setup according to Section Please refer to Chapter 14, Remote Installation for in-depth information on starting the upgrade from a remote server. Provide the appropriate path information or select SLP as the installation source. Select the appropriate installation server from those offered or use the boot options prompt to provide the type of installation source and its actual location as in Section 6.
YaST starts. Finish the installation as outlined in Section 7. Initiate the boot of the target system and use VNC to remotely connect to the installation routine running on this machine. See Section Once you have successfully booted from installation medium or the network, proceed as follows to start the update:. On the Welcome screen choose Language and Keyboard and Accept the license agreement.
Proceed with Next.
0コメント