For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upgrade MariaDB Enterprise Server from 11.8.X to 11.8.Y

Instructions for performing a minor release upgrade of MariaDB Enterprise Server within the 11.8 series, from an earlier 11.8.x release to a later 11.8.y release.

These instructions detail a minor release upgrade with MariaDB Enterprise Server 11.8 on a range of supported Operating Systems.

A minor release upgrade is a change from an earlier release of MariaDB Enterprise Server 11.8 to a later release in the same release series.

For example, it would be a minor release upgrade to upgrade from MariaDB Enterprise Server 11.8.2-0 to MariaDB Enterprise Server 11.8.3-1.

Data Backup

Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup before upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.

The instructions below show how to perform a backup using MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup:

sudo mariadb-backup --backup \
      --user=mariadb-backup_user \
      --password=mariadb-backup_passwd \
      --target-dir=/data/backup/preupgrade_backup

Confirm successful completion of the backup operation.

2. The backup must be prepared:

sudo mariadb-backup --prepare \
      --target-dir=/data/backup/preupgrade_backup

Confirm successful completion of the prepare operation.

3. Backups should be tested before they are trusted.

Stop the MariaDB Server Process

Before the new version can be installed, we first need to stop the current MariaDB Server process.

1. Set the innodb_fast_shutdown system variable to 1:

2. Use XA RECOVER to confirm that there are no external XA transactions in a prepared state:

Commit or roll back any open XA transactions before stopping the node for upgrade.

3. Stop the server process. For distributions that use systemd (most supported OSes), you can manage the server process using the systemctl command:

Install the New Version

MariaDB Corporation provides package repositories for YUM (RHEL, AlmaLinux, CentOS, Rocky Linux), APT (Debian, Ubuntu), and ZYpp (SLES).

For a minor release upgrade, the existing MariaDB Enterprise Server packages do not need to be uninstalled. The packages are updated in place.

Install via YUM (RHEL, AlmaLinux, CentOS, Rocky Linux)

1. Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.

2. Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.

To configure YUM package repositories:

Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.

3. Update MariaDB Enterprise Server and package dependencies:

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.

2. Configure the APT package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.

To configure APT package repositories:

Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.

3. Update MariaDB Enterprise Server and package dependencies:

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.

2. Configure the ZYpp package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.

To configure ZYpp package repositories:

Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.

3. Update MariaDB Enterprise Server and package dependencies:

Configuration

For platforms that use YUM or ZYpp as a package manager: MariaDB Enterprise Server's packages bundle several configuration files:

  • /etc/my.cnf

  • /etc/my.cnf.d/client.cnf

  • /etc/my.cnf.d/mariadb-enterprise.cnf

  • /etc/my.cnf.d/mysql-clients.cnf

  • /etc/my.cnf.d/server.cnf

If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back.

For example, to move server.cnf back in place:

Starting the Server

MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system's default process management system.

For distributions that use systemd, you can manage the Server process using the systemctl command:

Operation
Command

Start

sudo systemctl start mariadb

Stop

sudo systemctl stop mariadb

Restart

sudo systemctl restart mariadb

Enable during startup

sudo systemctl enable mariadb

Disable during startup

sudo systemctl disable mariadb

Status

sudo systemctl status mariadb

Upgrading the Data Directory

MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.

The utility is called mariadb-upgrade:

Testing

When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.

1. Connect to the server using MariaDB Client using the root@localhost user account. MariaDB Client is called mariadb:

2. You can also verify the server version by checking the value of the version system variable with the SHOW GLOBAL STATUS statement:

3. You can also verify the server version by calling the VERSION() function:

This page is: Copyright © 2025 MariaDB. All rights reserved.

spinner

Last updated

Was this helpful?