Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise Server 15 SP1

1 Upgrade Paths and Methods Edit source

SUSE® Linux Enterprise (SLE) allows to upgrade an existing system to the new version, for example, going from SLE 12 SP4 to the latest SLE 15 service pack. No new installation is needed. Existing data, such as home and data directories and system configuration, is kept intact. You can update from a local CD or DVD drive or from a central network installation source.

This chapter explains how to manually upgrade your SUSE Linux Enterprise system, be it by DVD, network, an automated process, or SUSE Manager.

1.1 Supported Upgrade Paths to SLES 15 SP1 Edit source

Before you perform any migration, read Chapter 3, Preparing the Upgrade.

Important
Important: Cross-architecture Upgrades Are Not Supported

Cross-architecture upgrades, such as upgrading from a 32-bit version of SUSE Linux Enterprise Server to the 64-bit version, or upgrading from big endian to little endian are not supported!

Specifically, SLE 11 on POWER (big endian) to SLE 15 SP1 on POWER (new: little endian!) is not supported.

Also, since SUSE Linux Enterprise 15 is 64-bit only, upgrades from any 32-bit SUSE Linux Enterprise 11 systems to SUSE Linux Enterprise 15 and later are not supported.

To make a cross-architecture upgrade, you need to perform a new installation.

Note
Note: Skipping Service Packs

Consecutively installing all Service Packs is the easiest upgrade path. For the SUSE Linux Enterprise 15 product line (GA and the following Service Packs) it is supported to skip one service pack when upgrading. For example, it is supported to upgrade from SLE 15 GA to 15 SP2 or from SLE 15 SP1 to 15 SP3.

Note
Note: Upgrading Major Releases

We recommend to do a fresh install when upgrading to a new Major Release, for example from SUSE Linux Enterprise 12 to SUSE Linux Enterprise 15.

Overview of Supported Upgrade Paths
Figure 1.1: Overview of Supported Upgrade Paths
Supported Upgrade Paths per Version
Upgrading from SUSE Linux Enterprise Server 11 GA / SP1 / SP2 / SP3

Upgrading from SLES 11 SP3 or older service packs directly is not supported. You need at least SLES 11 SP4 before you can proceed to SLES 15 SP1.

If you cannot do a fresh installation, first upgrade your installed SLES 11 service pack to SLES 11 SP4. This upgrade is described in the SLES 11 Deployment Guide.

Upgrading from SUSE Linux Enterprise Server11 SP4

Upgrading from SLES 11 SP4 is only supported via an offline upgrade. Refer to Section 1.2, “Online and Offline Upgrade” for details.

Upgrading from SUSE Linux Enterprise Server 12 GA / SP1 / SP2

Upgrading from SLES 12 SP2 or older service packs directly is not supported. You need at least SLES 12 SP3 before you can proceed to SLES 15 SP1.

If you cannot do a fresh installation, first upgrade your installed SLES 12 service pack to SLES 12 SP3. This upgrade is described in the SLES 12 Deployment Guide .

Upgrading from SUSE Linux Enterprise Server 12 SP3 / SP4

Upgrading from SLES 12 SP3 / SP4 is only supported via an offline upgrade. Refer to Section 1.2, “Online and Offline Upgrade” for details.

Upgrading SUSE Linux Enterprise Public Cloud Guests

See https://documentation.suse.com/suse-distribution-migration-system/1.0/single-html/distribution-migration-system/ for instructions on upgrading SLE guests in public clouds.

Upgrading from SUSE Linux Enterprise Server 15 GA

Upgrading from SLES 15 GA is supported both online and offline. Refer to the following for details:

Upgrading from openSUSE Leap 15

Upgrading from openSUSE Leap 15 is supported. See Section 5.9, “Upgrading from openSUSE Leap to SUSE Linux Enterprise Server. Only the server installation of Leap is supported for an upgrade.

1.2 Online and Offline Upgrade Edit source

SUSE supports the following upgrade and migration methods. For more information about the terminology, see Section 2.1, “Terminology”. The methods are:

Online

Upgrades that are executed from the running operating system itself (system up and running state). Examples: online update with Zypper or YaST, connected through SUSE Customer Center or Repository Mirroring Tool (RMT), Salt Policy via SUSE Manager.

For details, see Chapter 5, Upgrading Online.

When migrating between Service Packs of the same major release, we suggest following Section 5.4, “Upgrading with the Online Migration Tool (YaST)” or Section 5.5, “Upgrading with Zypper”.

Offline

Upgrading offline implies that the operating system to be upgraded is not running (system down state). Instead, the installer for the target operating system is booted (for example, from the installation media, via network or via local boot loader), and performs the upgrade.

For details, see Chapter 4, Upgrading Offline.

Important
Important: SUSE Manager Clients

If your machine is managed by SUSE Manager, update it as described in the SUSE Manager documentation. The Client Migration procedure is described in the SUSE Manager Upgrade Guide, available at https://documentation.suse.com/suma/.

Print this page