An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.3 on a range of supported Operating Systems.
When MariaDB Enterprise Server is upgraded, the old version needs to be uninstalled, and the new version needs to be installed.
See .
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 . For more information about backing up and restoring the database, please see the .
Take a full backup. On MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the backup operation.
The backup must be prepared. On the MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
If you have the installed and if you are upgrading to MariaDB Enterprise Server 10.4 or later, then the audit plugin should be removed prior to the upgrade to prevent conflict with the that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the statement:
And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.
When upgrading to a new major release of MariaDB Enterprise Server, it is necessary to remove the existing installation of MariaDB Enterprise Server before installing the new version of MariaDB Enterprise Server. Otherwise, the package manager will refuse to install the new version of MariaDB Enterprise Server.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external in a prepared state:
Commit or roll back any open before stopping the node for upgrade.
Stop the server process: For distributions that use systemd (most supported OSes), you can manage the server process using the systemctl command:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
MariaDB Corporation provides package repositories for YUM (RHEL, AlmaLinux, CentOS, Rocky Linux), APT (Debian, Ubuntu), and ZYpp (SLES).
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
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 section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
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 section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins. Configure MariaDB. Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
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 section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
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:
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:
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 in MariaDB Enterprise Server 10.4 and later:
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.
Connect to the server using MariaDB Client using the root@localhost user account. MariaDB Client is called mariadb (ES 10.4 and later):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
/etc/my.cnf.d/mysql-clients.cnf/etc/my.cnf.d/server.cnf
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
sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backupsudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;sudo systemctl stop mariadbsudo yum remove "MariaDB-*"sudo yum remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo apt-get remove "mariadb-*"sudo apt remove galera-enterprise-4apt list --installed | grep -i -E "mariadb|galera"sudo zypper remove "MariaDB-*"sudo zypper remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo yum install curl curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo yum install MariaDB-server MariaDB-backupsudo apt install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo apt update$ sudo apt install mariadb-server mariadb-backupsudo zypper install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo zypper install MariaDB-server MariaDB-backupsudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.originalsudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnfsudo mariadb-upgradesudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 11.4.5-3-MariaDB-Enterprise MariaDB Enterprise Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------------------+
| Variable_name | Value |
+---------------+-----------------------------+
| version | 11.4.5-3-MariaDB-Enterprise |
+---------------+-----------------------------+SELECT VERSION();+-----------------------------+
| VERSION() |
+-----------------------------+
| 11.4.5-3-MariaDB-Enterprise |
+-----------------------------+This page is: Copyright © 2025 MariaDB. All rights reserved.