This page includes details for upgrading from MariaDB 10.6 to the subsequent long-term maintenance version, MariaDB 10.11. It is currently incomplete.
How to Upgrade
Before you upgrade, it would be best to take a backup of your database. This is always a good idea to do before an upgrade. We would recommend Mariabackup.
The suggested upgrade procedure is:
1. Modify the repository configuration, so the system’s package manager installs MariaDB 10.11. For example,
2. Stop MariaDB.
3. Uninstall the old version of MariaDB. * On Debian, Ubuntu, and other similar Linux distributions, execute the following: sudo apt-get remove mariadb-server * On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following: sudo yum remove MariaDB-server * On SLES, OpenSUSE, and other similar Linux distributions, execute the following: sudo zypper remove MariaDB-server
4. Install the new version of MariaDB.
5. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.
6. Start MariaDB.
7. Run mariadb-upgrade. * mariadb-upgrade does two things: 1. Ensures that the system tables in the mysql database are fully compatible with the new version. . Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .
Incompatible Changes Between 10.6 and 10.11
On most servers upgrading from 10.6 should be painless. However, there are some things that have changed which could affect an upgrade:
If a non-zlib compression algorithm was used in InnoDB or Mroonga before upgrading to 10.11, those tables will be unreadable until the appropriate compression library is installed. See Compression Plugins#Upgrading.
Options That Have Been Removed or Renamed
The following options should be removed or renamed if you use them in your option files:
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.