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

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

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

For example, it would be a minor release upgrade to upgrade from MariaDB Enterprise Server 10.5.27-21 to MariaDB Enterprise Server 10.5.28-22.

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 prior to 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 . For more information about backing up and restoring the database, please see the .

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   On MariaDB Enterprise Server 10.3 and earlier:

   Confirm successful completion of the backup operation.

2. The backup must be prepared.

   On MariaDB Enterprise Server 10.4 and later:

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 system variable to 1:

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

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

3. Stop the server process:

Install the New Version

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

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

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 default process management system.

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

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 in MariaDB Enterprise Server 10.4 and later:

And the utility is called in MariaDB Enterprise Server 10.3 and 10.2:

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 (ES10.4 and later) or mysql (ES10.3, ES10.2):

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

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