Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
A collection of upgrade guides for older, end-of-life versions of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
A collection of upgrade guides for older, end-of-life versions of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
A collection of upgrade guides for older, end-of-life versions of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
A collection of upgrade guides for older, end-of-life versions of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from MariaDB Community 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.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup prior to upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
If you have the installed and if you are upgrading to MariaDB Enterprise Server 10.4 or later, then the audit plugin should be removed prior to the upgrade to prevent conflict with the MariaDB Enterprise Audit Plugin that is present in MariaDB Enterprise Server 10.4 or later.
It can be removed by using the statement:
And if you load the plugin in a configuration file using the plugin_load_add option, then the option should also be removed.
The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.
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.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external XA transactions in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the systemctl
Uninstall via YUM (RHEL, AlmaLinux, CentOS, Rocky Linux)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
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)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3
For platforms that use YUM or ZYpp as a package manager:
MariaDB Community Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mysql-clients.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back. For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called in MariaDB Enterprise Server 10.4 and later:
And the utility is called mysql\_upgrade in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called (ES10.4 and later) or mysql (ES10.3 and earlier):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
Backups should be tested before they are trusted.
galera:Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
Uninstall via APT (Debian, Ubuntu)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called galera-3:
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
Uninstall via ZYpp (SLES)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called galera:
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
--mariadb-server-version10.5.To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.5.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Install via ZYpp (SLES)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.5.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
/etc/my.cnf.d/server.cnfOperation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt-get remove "mariadb-*"$ sudo apt remove galera-4$ sudo zypper remove "MariaDB-*"$ sudo zypper remove galera-4$ sudo yum install MariaDB-server MariaDB-backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ sudo yum remove "MariaDB-*"$ sudo yum remove galera-4$ 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$ sudo mariadb-upgrade$ sudo mysql_upgrade$ sudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.5.28-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------+
| Variable_name | Value |
+---------------+-----------------+
| version | 10.5.28-MariaDB |
+---------------+-----------------+SELECT VERSION();+-----------------+
| VERSION() |
+-----------------+
| 10.5.28-MariaDB |
+-----------------+$ sudo systemctl stop mariadb$ sudo yum remove galera$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 remove galera-3$ apt list --installed | grep -i -E "mariadb|galera"$ sudo zypper remove galera$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo apt install mariadb-server mariadb-backup$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 zypper install MariaDB-server MariaDB-backupAn upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
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.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup prior to upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
Before the new version can be installed, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external XA transactions in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the systemctl
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)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3
For platforms that use YUM or ZYpp as a package manager:
MariaDB Enterprise Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mariadb-enterprise.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back. For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called in MariaDB Enterprise Server 10.4 and later:
And the utility is called in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called (ES10.4 and later) or mysql (ES10.3, ES10.2):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
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.
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.
This page is: Copyright © 2025 MariaDB. All rights reserved.
Backups should be tested before they are trusted.
--mariadb-server-version11.4.To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 11.4.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
Install via ZYpp (SLES)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.5.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
/etc/my.cnf.d/mysql-clients.cnf/etc/my.cnf.d/server.cnf
Operation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
This page is: Copyright © 2025 MariaDB. All rights reserved.
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.
Take a full backup.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
Before the new version can be installed, we first need to stop the current MariaDB Server process.
Set the innodb_fast_shutdown system variable to 1:
Use XA RECOVER to confirm that there are no external XA transactions in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the systemctl command:
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)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.4.
To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4
Install via ZYpp (SLES)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4
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:
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:
Operation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
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:
And the utility is called mysql_upgrade in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called mariadb (ES10.4 and later) or mysql (ES10.3, ES10.2):
You can also verify the server version by checking the value of the version system variable with the SHOW GLOBAL STATUS statement:
You can also verify the server version by calling the VERSION() function:
This page is: Copyright © 2025 MariaDB. All rights reserved.
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.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 .
mysqld is now mariadbd: The server binary has been renamed.
Systemd services and mysqld_safe handle this automatically.
Impact: Monitoring scripts or custom startup scripts that explicitly look for a process named mysqld
SHOW SLAVE STATUS: This command now requires the REPLICATION SLAVE ADMIN or SUPER privilege. It previously required only REPLICATION CLIENT. Ensure your monitoring users have the correct grants.
innodb_checksums: Replaced by innodb_checksum_algorithm.
innodb_undo_logs: Deprecated/Replaced.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup before upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup. On MariaDB Enterprise Server 10.5 and later:
Confirm successful completion of the backup operation.
The backup must be prepared. On the MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
If you have the installed and are upgrading from MariaDB Enterprise Server 10.2 or 10.3, the audit plugin should be removed prior to the upgrade to prevent conflicts with the MariaDB Enterprise Audit Plugin, which that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the statement:
And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.
When upgrading to a new major release of MariaDB Enterprise Server, it is necessary to remove the existing installation of MariaDB Enterprise Server before installing the new version of MariaDB Enterprise Server. Otherwise, the package manager will refuse to install the new version of MariaDB Enterprise Server.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external in a prepared state:
Commit or roll back any open before stopping the node for upgrade.
Stop the server process: For distributions that use systemd (most supported OSes), you can manage the server process using the systemctl command:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
MariaDB Corporation provides package repositories for YUM (RHEL, AlmaLinux, CentOS, Rocky Linux), APT (Debian, Ubuntu), and ZYpp (SLES).
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository. Installable versions of MariaDB Enterprise Server are 11.8 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins. Configure MariaDB. Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
For platforms that use YUM or ZYpp as a package manager: MariaDB Enterprise Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mariadb-enterprise.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back.
For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system's default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called mariadb-upgrade in MariaDB Enterprise Server 10.4 and later:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account. MariaDB Client is called mariadb (ES 10.4 and later):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
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.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup prior to upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Enterprise Server 10.4 and later:
On MariaDB Enterprise Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
Before the new version can be installed, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the
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)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3
For platforms that use YUM or ZYpp as a package manager:
MariaDB Enterprise Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mariadb-enterprise.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back. For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called in MariaDB Enterprise Server 10.4 and later:
And the utility is called in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called (ES10.4 and later) or mysql (ES10.3, ES10.2):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from MariaDB Community Server to MariaDB Enterprise Server 10.4 on a range of .
When is upgraded, the old version needs to be uninstalled, and the new version needs to be installed.
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.
$ sudo yum update "MariaDB-*" "galera*"$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupSET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ 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$ sudo mariadb-upgrade$ sudo mysql_upgrade$ sudo mariadbWelcome 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)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-------------------------------+
| Variable_name | Value |
+---------------+-------------------------------+
| version | 10.5.28-22-MariaDB-Enterprise |
+---------------+-------------------------------+SELECT VERSION();+-------------------------------+
| VERSION() |
+-------------------------------+
| 10.5.28-22-MariaDB-Enterprise |
+-------------------------------+$ sudo systemctl stop mariadb$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupSET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ sudo mysqlWelcome 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)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-------------------------------+
| Variable_name | Value |
+---------------+-------------------------------+
| version | 10.3.39-20-MariaDB-Enterprise |
+---------------+-------------------------------+SELECT VERSION();+-------------------------------+
| VERSION() |
+-------------------------------+
| 10.3.39-20-MariaDB-Enterprise |
+-------------------------------+$ 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$ sudo mariadb-upgrade$ sudo mysql_upgrade10.3--mariadb-server-version10.3.To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
10.3--mariadb-server-version10.4.To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo apt install --only-upgrade "mariadb-*" "galera*"$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 zypper update "MariaDB-*" "galera*"$ sudo apt install --only-upgrade "mariadb-*" "galera*"$ sudo zypper update "MariaDB-*" "galera*"$ sudo systemctl stop mariadb$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 yum update "MariaDB-*" "galera*"$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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"mariadbd/etc/my.cnf.d/mysql-clients.cnf/etc/my.cnf.d/server.cnf
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
This page is: Copyright © 2025 MariaDB. All rights reserved.
Backups should be tested before they are trusted.
systemctl--mariadb-server-version10.4.To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
For users who have the Spider storage engine loaded who are upgrading from or earlier, Spider's new RPM package and dependencies must be manually installed after upgrading to or later.
In and earlier, Spider's components were installed with the server's RPM package.
Starting with , Spider adds unixODBC as a dependency, so Spider has been moved to a separate RPM package to avoid adding new dependencies to the server's RPM package.
To install Spider's new package and dependencies:
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.4.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
Install via ZYpp (SLES)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.4.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Update MariaDB Enterprise Server and package dependencies:
For users who have the loaded who are upgrading from or earlier, Spider's new RPM package and dependencies must be manually installed after upgrading to or later.
In and earlier, Spider's components were installed with the server's RPM package.
Starting with , Spider adds unixODBC as a dependency, so Spider has been moved to a separate RPM package to avoid adding new dependencies to the server's RPM package.
To install Spider's new package and dependencies:
/etc/my.cnf.d/mysql-clients.cnf/etc/my.cnf.d/server.cnf
Operation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
This page is: Copyright © 2025 MariaDB. All rights reserved.
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.
Take a full backup.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
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:
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.
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.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the innodb_fast_shutdown system variable to 1:
Use XA RECOVER to confirm that there are no external XA transactions in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the systemctl command:
Uninstall via YUM (RHEL, AlmaLinux, CentOS, Rocky Linux)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called galera:
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
Uninstall via APT (Debian, Ubuntu)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
Uninstall via ZYpp (SLES)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
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)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.4.
To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4
Install via ZYpp (SLES)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4
For platforms that use YUM or ZYpp as a package manager:
MariaDB Community Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.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:
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:
Operation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
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:
And the utility is called mysql\_upgrade in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called mariadb (ES10.4 and later) or mysql (ES10.3 and earlier):
You can also verify the server version by checking the value of the version system variable with the SHOW GLOBAL STATUS statement:
You can also verify the server version by calling the VERSION() function:
This page is: Copyright © 2025 MariaDB. All rights reserved.
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from MariaDB Community 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.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup prior to upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the backup operation.
The backup must be prepared.
On MariaDB Community Server 10.4 and later:
On MariaDB Community Server 10.3 and earlier:
Confirm successful completion of the prepare operation.
If you have the installed and if you are upgrading to MariaDB Enterprise Server 10.4 or later, then the audit plugin should be removed prior to the upgrade to prevent conflict with the that is present in MariaDB Enterprise Server 10.4 or later.
It can be removed by using the statement:
And if you load the plugin in a configuration file using the plugin_load_add option, then the option should also be removed.
The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.
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.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process:
For distributions that use systemd (most supported OSes), you can manage the Server process using the
Uninstall via YUM (RHEL, AlmaLinux, CentOS, Rocky Linux)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
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)
Retrieve your Customer Download Token at and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3
For platforms that use YUM or ZYpp as a package manager:
MariaDB Community Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mysql-clients.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back. For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called in MariaDB Enterprise Server 10.4 and later:
And the utility is called mysql\_upgrade in MariaDB Enterprise Server 10.3 and 10.2:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account.
MariaDB Client is called (ES10.4 and later) or mysql (ES10.3 and earlier):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
An upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backupsudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;sudo systemctl stop mariadbsudo yum remove "MariaDB-*"sudo yum remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo apt-get remove "mariadb-*"sudo apt remove galera-enterprise-4apt list --installed | grep -i -E "mariadb|galera"sudo zypper remove "MariaDB-*"sudo zypper remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo yum install curl curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.5"sudo yum install MariaDB-server MariaDB-backupsudo apt install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.5"sudo apt update$ sudo apt install mariadb-server mariadb-backup galera-enterprise-4sudo zypper install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.5"sudo zypper install MariaDB-server MariaDB-backupsudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.originalsudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnfsudo mariadb-upgradesudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 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)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------------------+
| Variable_name | Value |
+---------------+-----------------------------+
| version | 10.5.28-22-MariaDB-Enterprise |
+---------------+-----------------------------+SELECT VERSION();+-----------------------------+
| VERSION() |
+-----------------------------+
| 10.5.28-22-MariaDB-Enterprise |
+-----------------------------+$ sudo yum update "MariaDB-*" "galera*"$ sudo yum install MariaDB-spider-engine$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupSET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ 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$ sudo mariadb-upgrade$ sudo mysql_upgrade$ sudo mariadbWelcome 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)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-------------------------------+
| Variable_name | Value |
+---------------+-------------------------------+
| version | 10.4.34-24-MariaDB-Enterprise |
+---------------+-------------------------------+SELECT VERSION();+-------------------------------+
| VERSION() |
+-------------------------------+
| 10.4.34-24-MariaDB-Enterprise |
+-------------------------------+$ sudo systemctl stop mariadb$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupSET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ sudo yum remove "MariaDB-*"$ sudo yum remove galera-4$ sudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.4.34-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------+
| Variable_name | Value |
+---------------+-----------------+
| version | 10.4.34-MariaDB |
+---------------+-----------------+SELECT VERSION();+-----------------+
| VERSION() |
+-----------------+
| 10.4.34-MariaDB |
+-----------------+UNINSTALL SONAME 'server_audit';$ 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$ sudo mariadb-upgrade$ sudo mysql_upgradegalera-3:Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
galera:Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
10.3--mariadb-server-version10.4.To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
10.3--mariadb-server-version10.4.To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
$ apt list --installed | grep -i -E "mariadb|galera"$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt install mariadb-server mariadb-backup$ sudo zypper install MariaDB-server MariaDB-backup$ sudo systemctl stop mariadb$ sudo yum remove galera$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt-get remove "mariadb-*"$ sudo apt remove galera-4$ sudo zypper remove "MariaDB-*"$ sudo zypper remove galera-4$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 yum install MariaDB-server MariaDB-backup$ sudo apt remove galera-3$ sudo zypper remove galera$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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"Backups should be tested before they are trusted.
systemctlgalera:Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
Uninstall via APT (Debian, Ubuntu)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called galera-3:
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
Uninstall via ZYpp (SLES)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4 or later, the package is called galera-4:
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called galera:
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
--mariadb-server-version10.3.To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Install via APT (Debian, Ubuntu)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.3.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Install via ZYpp (SLES)
Retrieve your Customer Download Token at https://customers.mariadb.com/downloads/token/ and substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository.
Installable versions of MariaDB Enterprise Server are 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to . The following directions reference 10.3.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the section at the bottom of the page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB.
Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
/etc/my.cnf.d/server.cnfOperation
Command
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
This page is: Copyright © 2025 MariaDB. All rights reserved.
EXCEPT and INTERSECT: These are now reserved words. If used as identifiers (table/column names), they must be quoted.
VALUES() Function: Renamed to VALUE().
mysqldump Compatibility: A mysqldump binary from an older version cannot dump data from a MariaDB 10.3 server due to changes in the transaction registry tables. You must upgrade your client tools along with the server.
innodb_file_format: The Antelope file format is no longer supported. The default is Barracuda.
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.
Take a full backup. On MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the backup operation.
The backup must be prepared. On the MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
If you have the 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:
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.
When upgrading to a new major release of MariaDB Enterprise Server, it is necessary to remove the existing installation of MariaDB Enterprise Server before installing the new version of MariaDB Enterprise Server. Otherwise, the package manager will refuse to install the new version of MariaDB Enterprise Server.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the innodb_fast_shutdown system variable to 1:
Use XA RECOVER to confirm that there are no external XA transactions in a prepared state:
Commit or roll back any open XA transactions before stopping the node for upgrade.
Stop the server process: For distributions that use systemd (most supported OSes), you can manage the server process using the systemctl command:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
MariaDB Corporation provides package repositories for YUM (RHEL, AlmaLinux, CentOS, Rocky Linux), APT (Debian, Ubuntu), and ZYpp (SLES).
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure YUM package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository. Installable versions of MariaDB Enterprise Server are 11.8 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure APT package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins. Configure MariaDB. Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure ZYpp package repositories:
Checksums of the various releases of the mariadb_es_repo_setup script can be found in the Versions section at the bottom of the MariaDB Package Repository Setup and Usage page. Substitute ${checksum} in the example above with the latest checksum.
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
For platforms that use YUM or ZYpp as a package manager: MariaDB Enterprise Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mariadb-enterprise.cnf
/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:
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:
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called mariadb-upgrade in MariaDB Enterprise Server 10.4 and later:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account. MariaDB Client is called mariadb (ES 10.4 and later):
You can also verify the server version by checking the value of the version system variable with the SHOW GLOBAL STATUS statement:
You can also verify the server version by calling the VERSION() function:
This page is: Copyright © 2025 MariaDB. All rights reserved.
$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt-get remove "mariadb-*"$ sudo apt remove galera-4$ sudo zypper remove "MariaDB-*"$ sudo zypper remove galera-4$ sudo yum install MariaDB-server MariaDB-backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backup$ sudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;$ sudo yum remove "MariaDB-*"$ sudo yum remove galera-4$ 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$ sudo mariadb-upgrade$ sudo mysql_upgrade$ sudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 10.3.39-MariaDB MariaDB Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------+
| Variable_name | Value |
+---------------+-----------------+
| version | 10.3.39-MariaDB |
+---------------+-----------------+SELECT VERSION();+-----------------+
| VERSION() |
+-----------------+
| 10.3.39-MariaDB |
+-----------------+$ sudo systemctl stop mariadb$ sudo yum remove galera$ sudo yum install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backupsudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;sudo systemctl stop mariadbsudo yum remove "MariaDB-*"sudo yum remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo apt-get remove "mariadb-*"sudo apt remove galera-enterprise-4apt list --installed | grep -i -E "mariadb|galera"sudo zypper remove "MariaDB-*"sudo zypper remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo yum install curl curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo yum install MariaDB-server MariaDB-backupsudo apt install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo apt update$ sudo apt install mariadb-server mariadb-backupsudo zypper install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.3"sudo zypper install MariaDB-server MariaDB-backupsudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.originalsudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnfsudo mariadb-upgradesudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 11.4.5-3-MariaDB-Enterprise MariaDB Enterprise Server
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------------------+
| Variable_name | Value |
+---------------+-----------------------------+
| version | 11.4.5-3-MariaDB-Enterprise |
+---------------+-----------------------------+SELECT VERSION();+-----------------------------+
| VERSION() |
+-----------------------------+
| 11.4.5-3-MariaDB-Enterprise |
+-----------------------------+$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo apt install --only-upgrade "mariadb-*" "galera*"$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 zypper update "MariaDB-*" "galera*"$ sudo zypper install MariaDB-spider-engine$ sudo apt remove galera-3$ apt list --installed | grep -i -E "mariadb|galera"$ sudo zypper remove galera$ rpm --query --all | grep -i -E "mariadb|galera"$ sudo apt install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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$ sudo apt install mariadb-server mariadb-backup$ sudo zypper install curl$ curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setup$ echo "${checksum} 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 zypper install MariaDB-server MariaDB-backupAn upgrade guide for an older, end-of-life version of MariaDB Enterprise Server, kept for reference purposes for legacy systems.
These instructions detail the upgrade from a previous version of MariaDB Enterprise Server to MariaDB Enterprise Server 10.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 .
mysql.user Table: This table is now a View into mysql.global_priv.
Impact: Legacy scripts that attempt to manipulate users via INSERT INTO mysql.user ... will fail. You must use standard SQL commands (CREATE USER, GRANT, DROP USER
TLSv1.0: Disabled by default. Ensure your clients support newer TLS versions (TLS 1.1+).
wsrep_load_data_splitting: Default changed to OFF.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup before upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
The instructions below show how to perform a backup using . For more information about backing up and restoring the database, please see the .
Take a full backup. On MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the backup operation.
The backup must be prepared. On the MariaDB Enterprise Server 10.4 and later:
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
If you have the installed and are upgrading from MariaDB Enterprise Server 10.2 or 10.3, the audit plugin should be removed prior to the upgrade to prevent conflicts with the MariaDB Enterprise Audit Plugin, which that is present in MariaDB Enterprise Server 10.4 or later. It can be removed by using the statement:
And if you load the plugin in a configuration file using the plugin\_load\_add option, then the option should also be removed. The MariaDB Enterprise Audit Plugin will automatically be installed after installing MariaDB Enterprise Server 10.4 or later.
When upgrading to a new major release of MariaDB Enterprise Server, it is necessary to remove the existing installation of MariaDB Enterprise Server before installing the new version of MariaDB Enterprise Server. Otherwise, the package manager will refuse to install the new version of MariaDB Enterprise Server.
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the system variable to 1:
Use to confirm that there are no external in a prepared state:
Commit or roll back any open before stopping the node for upgrade.
Stop the server process: For distributions that use systemd (most supported OSes), you can manage the server process using the systemctl command:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications:
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
Uninstall all of the MariaDB Enterprise Server packages. Note that a wildcard character is used to ensure that all MariaDB Enterprise Server packages are uninstalled:
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well. The name of the package depends on the specific version of MariaDB Enterprise Server. When upgrading from MariaDB Enterprise Server 10.4 or later, the package is called galera-enterprise-4:
Before proceeding, verify that all MariaDB Enterprise Server packages are uninstalled. The following command should not return any results:
MariaDB Corporation provides package repositories for YUM (RHEL, AlmaLinux, CentOS, Rocky Linux), APT (Debian, Ubuntu), and ZYpp (SLES).
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the YUM package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure YUM package repositories:
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the APT package repository. Installable versions of MariaDB Enterprise Server are 11.8 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure APT package repositories:
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins. Configure MariaDB. Installation only loads MariaDB Enterprise Server to the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
Retrieve your Customer Download Token atand substitute for CUSTOMER_DOWNLOAD_TOKEN in the following directions.
Configure the ZYpp package repository. Installable versions of MariaDB Enterprise Server are 11.8, 11.4, 10.6, 10.5, 10.4, and 10.3. Pass the version to install using the --mariadb-server-version flag to mariadb_es_repo_setup. The following directions reference 11.8.
To configure ZYpp package repositories:
Install MariaDB Enterprise Server and package dependencies:
Installation of additional packages may be required for some plugins.
Configure MariaDB. Installation only loads MariaDB Enterprise Server onto the system. MariaDB Enterprise Server requires configuration before the database server is ready for use.
For platforms that use YUM or ZYpp as a package manager: MariaDB Enterprise Server's packages bundle several configuration files:
/etc/my.cnf
/etc/my.cnf.d/client.cnf
/etc/my.cnf.d/mariadb-enterprise.cnf
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the .rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back.
For example, to move server.cnf back in place:
MariaDB Enterprise Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system's default process management system.
For distributions that use systemd, you can manage the Server process using the systemctl command:
MariaDB Enterprise Server ships with a utility that can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory.
The utility is called mariadb-upgrade in MariaDB Enterprise Server 10.4 and later:
When MariaDB Enterprise Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the root@localhost user account. MariaDB Client is called mariadb (ES 10.4 and later):
You can also verify the server version by checking the value of the system variable with the statement:
You can also verify the server version by calling the function:
Unix Socket Auth: The unix_socket authentication plugin is now enabled by default on Linux. root access via sudo mariadb works without a password, which may affect scripts expecting password authentication for localhost root.
/etc/my.cnf.d/mysql-clients.cnf/etc/my.cnf.d/server.cnf
Start
sudo systemctl start mariadb
Stop
sudo systemctl stop mariadb
Restart
sudo systemctl restart mariadb
Enable during startup
sudo systemctl enable mariadb
Disable during startup
sudo systemctl disable mariadb
Status
sudo systemctl status mariadb
This page is: Copyright © 2025 MariaDB. All rights reserved.
sudo mariadb-backup --backup \
--user=mariadb-backup_user \
--password=mariadb-backup_passwd \
--target-dir=/data/backup/preupgrade_backupsudo mariadb-backup --prepare \
--target-dir=/data/backup/preupgrade_backupUNINSTALL SONAME 'server_audit';SET GLOBAL innodb_fast_shutdown = 1;XA RECOVER;sudo systemctl stop mariadbsudo yum remove "MariaDB-*"sudo yum remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo apt-get remove "mariadb-*"sudo apt remove galera-enterprise-4apt list --installed | grep -i -E "mariadb|galera"sudo zypper remove "MariaDB-*"sudo zypper remove galera-enterprise-4rpm --query --all | grep -i -E "mariadb|galera"sudo yum install curl curl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.4"sudo yum install MariaDB-server MariaDB-backupsudo apt install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.4"sudo apt update$ sudo apt install mariadb-server mariadb-backup galera-enterprise-4sudo zypper install curlcurl -LsSO https://dlm.mariadb.com/enterprise-release-helpers/mariadb_es_repo_setupecho "${checksum} mariadb_es_repo_setup" \
| sha256sum -c -chmod +x mariadb_es_repo_setupsudo ./mariadb_es_repo_setup --token="CUSTOMER_DOWNLOAD_TOKEN" --apply \
--mariadb-server-version="10.4"sudo zypper install MariaDB-server MariaDB-backupsudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.originalsudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnfsudo mariadb-upgradesudo mariadbWelcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9
Server version: 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)]>SHOW GLOBAL VARIABLES LIKE 'version';+---------------+-----------------------------+
| Variable_name | Value |
+---------------+-----------------------------+
| version | 10.4.34-24-MariaDB-Enterprise |
+---------------+-----------------------------+SELECT VERSION();+-----------------------------+
| VERSION() |
+-----------------------------+
| 10.4.34-24-MariaDB-Enterprise |
+-----------------------------+