MariaDB is designed to allow easy upgrades. You should be able to trivially upgrade from ANY earlier MariaDB version to the latest one (for example MariaDB 10.3.x to MariaDB 10.11.x), usually in a few seconds. This is also mainly true for any MySQL version < 8.0 to MariaDB 10.4 and up.

Upgrades are normally easy because:

• All MariaDB table data files are backward compatible

• The MariaDB connection protocol is backward compatible. You don't normally need to upgrade any of your old clients to be able to connect to a newer MariaDB version.

• The MariaDB replica can be of any newer version than the primary.

MariaDB Corporation regularly runs tests to check that one can upgrade from MariaDB 5.5 to the latest MariaDB version without any trouble. All older versions should work too (as long as the storage engines you were using are still around).

Note that if you are using MariaDB Galera Cluster, you have to follow the Galera upgrading instructions!

Requirements for Doing an Upgrade Between Major Versions

• Go through the individual version upgrade notes (listed below) to look for any major changes or configuration options that have changed.

• Ensure that the target MariaDB version supports the storage engines you are using. For example, in 10.5 TokuDB is not supported.

• Back up the database (just in case). At least, take a copy of the mysql system database directory under the data directory with mariadb-dump --add-drop-table mysql (called mysqldump in MariaDB 10.3 and earlier) as most of the upgrade changes are done there (adding new fields and new system tables etc).

• Cleanly shutdown the server. This is necessary because even if data files are compatible between versions, recovery logs may not be.

  • Ensure that the innodb_fast_shutdown variable is not 2 (fast crash shutdown). The default of this variable is 1.

  • innodb_force_recovery must be less than 3.

Note that rpms don't support upgrading between major versions, only minor like 10.4.1 to 10.4.2. If you are using rpms, you should de-install the old MariaDB rpms and install the new MariaDB rpms before running mariadb-upgrade. Note that when installing the new rpms, mariadb-upgrade may be run automatically. There is no problem with running mariadb-upgrade many times.

Recommended Steps

• If you have a primary-replica setup, first upgrade one replica and when you have verified that the replica works well, upgrade the rest of the replicas (if any). Then upgrade one replica to primary, upgrade the primary, and change the replica to a primary.

• If you don't have a primary-replica setup, then take a backup, shutdown MariaDB and do the upgrade.

Step by Step Instructions for Upgrades

• Upgrade MariaDB binaries and libraries, preferably without starting MariaDB.

• If the MariaDB server process, mariadbd was not started as part of the upgrade, start it by executing mariadbd --skip-grant-tables. This may produce some warnings about some system tables not being up to date, but you can ignore these for now as mariadb-upgrade will fix that.

• Run mariadb-upgrade

• Restart MariaDB server.

Work Done by mariadb-upgrade

The main work done when upgrading is done by running mariadb-upgrade. The main things it does are:

• Updating the system tables in the mysql database to the newest version. This is very quick.

• mariadb-upgrade also runs mariadb-check --check-upgrade to check if there have been any collation changes between the major versions. This recreates indexes in old tables that are using any of the changed collations. This can take a bit of time if there are a lot of tables or there are many tables which used the changed collation. The last time a collation changed was in MariaDB/MySQL 5.1.23.

Post Upgrade Work

Check the MariaDB error log for any problems during upgrade. If there are any warnings in the log files, do your best to get rid of them!

The common warnings/errors are:

• Using obsolete options. If this is the case, remove them from your my.cnf files.

• Check the manual for new features that have been added since your last MariaDB version.

• Test that your application works as before. The main difference from before is that because of optimizer improvements your application should work better than before, but in some rare cases the optimizer may get something wrong. In this case, you can try to use explain, optimizer trace or optimizer_switch to fix the queries.

If Something Goes Wrong

• First, check the MariaDB error log to see if you are using configure options that are not supported anymore.

• Check the upgrade notices for the MariaDB release that you are upgrading to.

• File an issue in the MariaDB bug tracker so that we know about the issue and can provide a fix to make upgrades even better.

• Add a comment to this manual entry for how we can improve it.

Disaster Recovery

In the unlikely event something goes wrong, you can try the following:

• Remove the InnoDB tables from the mysql data directory. They are:

  • gtid_slave_pos

  • innodb_table_stats

  • innodb_index_stats

  • transaction_registry

• Move the mysql data directory to mysql-old and run mariadb-install-db to generate a new one.

• After the above, you have to add back your old users.

• When done, delete the mysql-old data directory.

Downgrading

MariaDB server is not designed for downgrading. That said, in most cases, as long as you haven't run any ALTER TABLE or CREATE TABLE statements and you have a mariadb-dump of your old mysql database , you should be able to downgrade to your previous version by doing the following:

• Do a clean shutdown. For this special case you have to set innodb_fast_shutdown to 0,before taking down the new MariaDB server, to ensure there are no redo or undo logs that need to be applied on the downgraded server.

• Delete the tables in the mysql database (if you didn't use the option --add-drop-table to mariadb-dump)

• Delete the new MariaDB installation

• Install the old MariaDB version

• Start the server with mariadbd --skip-grant-tables

• Install the old mysql database

• Execute in the mariadb client FLUSH PRIVILEGES

See Also

• Upgrading from MySQL to MariaDB

• Upgrading from MariaDB 10.11 to MariaDB 11.4

• Upgrading from MariaDB 10.6 to MariaDB 10.11

• Upgrading from MariaDB 10.6 to MariaDB 10.7

• Upgrading from MariaDB 10.5 to MariaDB 10.6

• Upgrading from MariaDB 10.4 to MariaDB 10.5

• Galera upgrading instructions

• innodb_fast_shutdown

_{This page is licensed: CC BY-SA / Gnu FDL}

For Windows, see Upgrading MariaDB on Windows instead.

Before you upgrade, it would be best to take a backup of your database. This is always a good idea to do before an upgrade. We would recommend mariadb-backup.

To upgrade between minor versions of MariaDB on Linux/Unix (for example from MariaDB 10.11.4 to MariaDB 10.11.5), the following procedure is suggested:

1. Stop MariaDB.

2. Uninstall the old version of MariaDB.

3. Install the new version of MariaDB.

• On Debian, Ubuntu, and other similar Linux distributions, see Installing MariaDB Packages with APT for more information.

• On RHEL, CentOS, Fedora, and other similar Linux distributions, see Installing MariaDB Packages with YUM for more information.

• On SLES, OpenSUSE, and other similar Linux distributions, see Installing MariaDB Packages with ZYpp for more information.

1. Make any desired changes to configuration options in option files, such as my.cnf.

2. Start MariaDB.

To upgrade between major versions, see the following:

• Upgrading Between Major MariaDB Versions

• Upgrading from MariaDB 11.1 to MariaDB 11.2

• Upgrading from MariaDB 11.0 to MariaDB 11.1

• Upgrading from MariaDB 10.11 to MariaDB 11.0

• Upgrading from MariaDB 10.6 to MariaDB 10.11

• Upgrading from MariaDB 10.5 to MariaDB 10.6

• Upgrading from MariaDB 10.4 to MariaDB 10.5

• Upgrading from MariaDB 10.3 to MariaDB 10.4

_{This page is licensed: CC BY-SA / Gnu FDL}

For incompatibilities such as removed features, and changes to variables, see the pages describing changes by version on Upgrading MariaDB.

Minor Upgrades

To install a minor upgrade, e.g 10.1.27 on top of existing 10.1.26, with MSI, just download the 10.1.27 MSI and start it. It will do everything that needs to be done for minor upgrade automatically - shutdown MariaDB service(s), replace executables and DLLs, and start service(s) again.

The rest of the article is dedicated to major upgrades, e.g 10.1.x to 10.2.y.

General Information on Upgrade and Version Coexistence

This section assumes MSI installations.

First, check everything listed in the Incompatibilities section of the article relating to the version you are upgrading, for example, Upgrading from MariaDB 10.1 to MariaDB 10.2, to make sure you are prepared for the upgrade.

MariaDB (and also MySQL) allows different versions of the product to co-exist on the same machine, as long as these versions are different either in major or minor version numbers. For example, it is possible to have say MariaDB 5.1.51 and 5.2.6 to be installed on the same machine.

However only a single instance of 5.2 can exist. If for example 5.2.7 is installed on a machine where 5.2.6 is already installed, the installer will just replace 5.2.6 executables with 5.2.7 ones.

Now imagine, that both 5.1 and 5.2 are installed on the same machine and we want to upgrade the database instance running on 5.1 to the new version. In this case special tools are requied. Traditionally, mysql_upgrade is used to accomplish this. On Windows, theMySQL upgrade is a complicated multiple-step manual process.

Since MariaDB 5.2.6, the Windows distribution includes tools that simplify migration between different versions and also allow migration between MySQL and MariaDB.

Note. Automatic upgrades are only possible for DB instances that run as a Windows service.

General Recommendations

Important: Ignore any statement that tells you to "just uninstall MySQL and install MariaDB". This does not work on Windows, never has, and never will. Keep your MySQL installed until after the database had been converted.

The following install/upgrade sequence is recommended in case of "major" upgrades, like going from 5.3 to 5.5

• Install new version, while still retaining the old one

• Upgrade services one by one, like described later in the document (e.g with mysql_upgrade_service). It is recommeded to have services cleanly shut down before the upgrade.

• Uninstall old version when previous step is done.

Note. This recommendation differs from the procedure on Unixes, where the upgrade sequence is "uninstall old version, install new version"

Upgrade Wizard

This is a GUI tool that is typically invoked at the end of a MariaDB installation if upgradable services are found. The UI allows you to select instances you want to upgrade.

mysql_upgrade_service

This is a command line tool that performs upgrades. The tool requires full administrative privileges (it has to start and stop services).

Example usage:

mysql_upgrade_service --service=MySQL

mysql_upgrade_service accepts a single parameter — the name of the MySQL or MariaDB service. It performs all the steps to convert a MariaDB/MySQL instance running as the service to the current version.

Migration to 64 bit MariaDB from 32 bit

Earlier we said that only single instance of "MariaDB ." version can be installed on the same machine. This was almost correct, because MariaDB MSI installations allow 32 and 64-bit versions to be installed on the same machine, and in this case it is possible to have two instances of say 5.2 installed at the same time, an x86 one and an x64 one. One can use the x64 Upgrade wizard to upgrade an instance running as a 32-bit process to run as 64-bit.

Upgrading ZIP-based Installations.

Both UpgradeWizard and mysql_upgrade_service can also be used to upgrade database instances that were installed with theZIP installation.

_{This page is licensed: CC BY-SA / Gnu FDL}

Overview

These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 11.8 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 What's New in MariaDB Enterprise Server 11.8.

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. On MariaDB Enterprise Server 11.8 and later:

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.8"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.8"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.8"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 11.8.2-0-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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 11.8.2-0-MariaDB-Enterprise |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 11.8.2-0-MariaDB-Enterprise |
+-----------------------------+

Overview

These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 11.4 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 What's New in MariaDB Enterprise Server 11.4.

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. On MariaDB Enterprise Server 11.4 and later:

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.4"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.4"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="11.4"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome 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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 11.4.5-3-MariaDB-Enterprise |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 11.4.5-3-MariaDB-Enterprise |
+-----------------------------+

Overview

These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.6 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 What's New in MariaDB Enterprise Server 10.6.

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. On MariaDB Enterprise Server 10.6 and later:

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.6"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.6"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.6"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.6.21-17-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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 10.6.21-17-MariaDB-Enterprise |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 10.6.21-17-MariaDB-Enterprise |
+-----------------------------+

Overview

These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.5 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 What's New in MariaDB Enterprise Server 10.5.

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. On MariaDB Enterprise Server 10.5 and later:

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.5"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.5"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.5"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.5.28-22-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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 10.5.28-22-MariaDB-Enterprise  |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 10.5.28-22-MariaDB-Enterprise |
+-----------------------------+

Overview

These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.4 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 What's New in MariaDB Enterprise Server 10.4.

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

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.4"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.4"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.4"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.4.34-24-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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 10.4.34-24-MariaDB-Enterprise |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 10.4.34-24-MariaDB-Enterprise |
+-----------------------------+

Overview

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 What's New in MariaDB Enterprise Server 10.3.

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

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. On the MariaDB Enterprise Server 10.4 and later:

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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Uninstall the Old Version

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.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

SET GLOBAL innodb_fast_shutdown = 1;

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

XA RECOVER;

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:

sudo systemctl stop mariadb

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

1. 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:

sudo yum remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:

2. 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:

sudo yum remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Uninstall via APT (Debian, Ubuntu)

1. 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:

sudo apt-get remove "mariadb-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo apt remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

apt list --installed | grep -i -E "mariadb|galera"

Uninstall via ZYpp (SLES)

1. 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:

sudo zypper remove "MariaDB-*"

Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.

2. 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:

sudo zypper remove galera-enterprise-4

3. Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:

rpm --query --all | grep -i -E "mariadb|galera"

Install the New Version

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

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

1. Retrieve your Customer Download Token atand 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:

sudo yum install curl 

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.3"

3. Install MariaDB Enterprise Server and package dependencies:

sudo yum install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

Install via APT (Debian, Ubuntu)

1. Retrieve your Customer Download Token atand 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:

sudo apt install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.3"

sudo apt update

3. Install MariaDB Enterprise Server and package dependencies:

$ sudo apt install mariadb-server mariadb-backup

4. 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.

Install via ZYpp (SLES)

1. Retrieve your Customer Download Token atand 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:

sudo zypper install curl

curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup

echo "4d483b4df193831a0101d3dfa7fb3e17411dda7fc06c31be4f9e089c325403c0  mariadb_es_repo_setup" \
    | sha256sum -c -

chmod +x mariadb_es_repo_setup

sudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
   --mariadb-server-version="10.3"

3. Install MariaDB Enterprise Server and package dependencies:

sudo zypper install MariaDB-server MariaDB-backup

Installation of additional packages may be required for some plugins.

4. Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.

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:

sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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:

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

sudo 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 (ES 10.4 and later):

sudo mariadb

Welcome 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)]>

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

SHOW GLOBAL VARIABLES LIKE 'version';

+---------------+-----------------------------+
| Variable_name | Value                       |
+---------------+-----------------------------+
| version       | 11.4.5-3-MariaDB-Enterprise |
+---------------+-----------------------------+

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

SELECT VERSION();

+-----------------------------+
| VERSION()                   |
+-----------------------------+
| 11.4.5-3-MariaDB-Enterprise |
+-----------------------------+

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

A minor release upgrade is a change from an earlier release of MariaDB Enterprise Server 11.4 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.4.4-2 to MariaDB Enterprise Server 11.4.5-3.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb

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

• /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:

$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

$ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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

$ sudo mariadb-upgrade

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

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

   Copy

   $ sudo mariadb

   Copy

   Welcome 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)]>

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

   Copy

   SHOW GLOBAL VARIABLES LIKE 'version';

   Copy

   +---------------+-----------------------------+
   | Variable_name | Value                       |
   +---------------+-----------------------------+
   | version       | 11.4.5-3-MariaDB-Enterprise |
   +---------------+-----------------------------+

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

   Copy

   SELECT VERSION();

   Copy

   +-----------------------------+
   | VERSION()                   |
   +-----------------------------+
   | 11.4.5-3-MariaDB-Enterprise |
   +-----------------------------+

© 2025 MariaDB. All rights reserved.

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

A minor release upgrade is a change from an earlier release of MariaDB Enterprise Server 10.6 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.6.20-16 to MariaDB Enterprise Server 10.6.21-17.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb

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

• /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:

$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

$ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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

$ sudo mariadb-upgrade

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

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

   Copy

   $ sudo mariadb

   Copy

   Welcome to the MariaDB monitor.  Commands end with ; or \g.
   Your MariaDB connection id is 9
   Server version: 10.6.21-17-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)]>

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

   Copy

   SHOW GLOBAL VARIABLES LIKE 'version';

   Copy

   +---------------+-------------------------------+
   | Variable_name | Value                         |
   +---------------+-------------------------------+
   | version       | 10.6.21-17-MariaDB-Enterprise |
   +---------------+-------------------------------+

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

   Copy

   SELECT VERSION();

   Copy

   +-------------------------------+
   | VERSION()                     |
   +-------------------------------+
   | 10.6.21-17-MariaDB-Enterprise |
   +-------------------------------+

© 2025 MariaDB. All rights reserved.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb

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

• /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:

$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

$ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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

$ sudo mariadb-upgrade

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

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

   Copy

   $ sudo mariadb

   Copy

   Welcome to the MariaDB monitor.  Commands end with ; or \g.
   Your MariaDB connection id is 9
   Server version: 10.5.28-22-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)]>

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

   Copy

   SHOW GLOBAL VARIABLES LIKE 'version';

   Copy

   +---------------+-------------------------------+
   | Variable_name | Value                         |
   +---------------+-------------------------------+
   | version       | 10.5.28-22-MariaDB-Enterprise |
   +---------------+-------------------------------+

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

   Copy

   SELECT VERSION();

   Copy

   +-------------------------------+
   | VERSION()                     |
   +-------------------------------+
   | 10.5.28-22-MariaDB-Enterprise |
   +-------------------------------+

© 2025 MariaDB. All rights reserved.

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

A minor release upgrade is a change from an earlier release of MariaDB Enterprise Server 10.4 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.4.33-23 to MariaDB Enterprise Server 10.4.34-24.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb

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

• /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:

$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

$ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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

$ sudo mariadb-upgrade

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

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

   Copy

   $ sudo mariadb

   Copy

   Welcome to the MariaDB monitor.  Commands end with ; or \g.
   Your MariaDB connection id is 9
   Server version: 10.4.34-24-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)]>

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

   Copy

   SHOW GLOBAL VARIABLES LIKE 'version';

   Copy

   +---------------+-------------------------------+
   | Variable_name | Value                         |
   +---------------+-------------------------------+
   | version       | 10.4.34-24-MariaDB-Enterprise |
   +---------------+-------------------------------+

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

   Copy

   SELECT VERSION();

   Copy

   +-------------------------------+
   | VERSION()                     |
   +-------------------------------+
   | 10.4.34-24-MariaDB-Enterprise |
   +-------------------------------+

© 2025 MariaDB. All rights reserved.

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

A minor release upgrade is a change from an earlier release of MariaDB Enterprise Server 10.3 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.3.38-19 to MariaDB Enterprise Server 10.3.39-20.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Enterprise Server 10.4 and later:

   Copy

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

   On MariaDB Enterprise Server 10.3 and earlier:

   Copy

   $ 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:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb

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

• /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:

$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original

$ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf

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

$ sudo mariadb-upgrade

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

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

   Copy

   $ sudo mysql

   Copy

   Welcome to the MariaDB monitor.  Commands end with ; or \g.
   Your MariaDB connection id is 9
   Server version: 10.3.39-20-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)]>

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

   Copy

   SHOW GLOBAL VARIABLES LIKE 'version';

   Copy

   +---------------+-------------------------------+
   | Variable_name | Value                         |
   +---------------+-------------------------------+
   | version       | 10.3.39-20-MariaDB-Enterprise |
   +---------------+-------------------------------+

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

   Copy

   SELECT VERSION();

   Copy

   +-------------------------------+
   | VERSION()                     |
   +-------------------------------+
   | 10.3.39-20-MariaDB-Enterprise |
   +-------------------------------+

© 2025 MariaDB. All rights reserved.

These instructions detail the upgrade from MariaDB Community Server to MariaDB Enterprise Server 11.4 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.

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 MariaDB Backup. For more information about backing up and restoring the database, please see the Recovery Guide.

1. Take a full backup.

   On MariaDB Community Server 10.4 and later:

   Copy

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

   On MariaDB Community Server 10.3 and earlier:

   Copy

   $ 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.

   On MariaDB Community Server 10.4 and later:

   Copy

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

   On MariaDB Community Server 10.3 and earlier:

   Copy

   $ 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.

Audit Plugin Considerations

If you have the MariaDB Audit Plugin 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 MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later.

It can be removed by using the UNINSTALL SONAME statement:

UNINSTALL SONAME 'server_audit';

And if you load the plugin in a configuration file using the plugin_load_add option, then the option should also be removed.

The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.

Convert InnoDB Row Format

MariaDB Enterprise Server 11.4 changes the COMPRESSED row format to read-only. Before upgrading, modify any compressed InnoDB tables to use the DYNAMIC row format.

1. Use the information\_schema.INNODB\_SYS\_TABLES to identify any InnoDB tables that use the COMPRESSED row format:

   Copy

   SELECT NAME, ROW_FORMAT
   FROM information_schema.INNODB_SYS_TABLES
   WHERE NAME NOT LIKE 'SYS_%'
      AND ROW_FORMAT = 'COMPRESSED';

2. Execute an ALTER TABLE statement for each table, changing its row format from COMPRESSED to DYNAMIC:

   Copy

   ALTER TABLE accounts.hq_sales
   ROW_FORMAT = DYNAMIC
   PAGE_COMPRESSED = 1;

Uninstall the Old Version

When upgrading to MariaDB Enterprise Server, it is necessary to remove the existing installation of MariaDB Community Server, before installing MariaDB Enterprise Server. Otherwise, the package manager will refuse to install MariaDB Enterprise Server.

Stop the MariaDB Server Process

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

1. Set the innodb_fast_shutdown system variable to 1:

   Copy

   SET GLOBAL innodb_fast_shutdown = 1;

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

   Copy

   XA RECOVER;

   Commit or rollback 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:

   Copy

   $ sudo systemctl stop mariadb