Deployment includes installing, configuring, upgrading, downgrading, migration from other DBMSs, and automated deployment options. Here's an overview of what you can find in this section.

Available deployment methods are component-specific.

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

A MariaDB ID is a free account that provides:

• Customer access to MariaDB database product downloads

Create A MariaDB ID

You can register for a MariaDB ID with a social login or a traditional email/password.

Create a using one of the following Single sign-on methods:

• Sign up using your Google Account

• Sign up using your GitHub Account

• Sign up using your LinkedIn Account

Or use your email address:

• Enter your email address and press next.

• Click the reset button. A password link will appear in your email.

• Once you set a new password, the MariaDB account page will appear.

Obtaining Support

MariaDB Corporation provides commercial support and services for MariaDB database products.

To contact us with questions, or if you need assistance:

• If you are able to login to your MariaDB ID,

• If you do not have a MariaDB ID or are unable to login,

\

MariaDB RPM packages since are signed.

For MariaDB Community Server, see the MariaDB Community Server RPM / Source Keys section of the GPG page for details on how to import the key used by those repositories.

For MariaDB Enterprise Server, see the MariaDB Enterprise GPG Keys section of the GPG page for details on how to import the key used by those repositories.

To check the signature you first need to import the public part of the key like so:

gpg --keyserver hkp://pgp.mit.edu --recv-keys 1BB943DB

Next you need to let pgp know about the key like so:

You can check to see if the key was imported with:

Once the key is imported, you can check the signature of the MariaDB RPM files by running the something like the following in your download directory:

The output of the above will look something like this (make sure gpg shows up on each OK line):

See Also

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

Unsupported Versions of Windows

Recent versions of MariaDB may not install on unsupported Windows versions. See to find the final supported versions.

Systems with User Account Control

Running mysql_install_db.exe from a standard command prompt might cause the error:

To get rid of it, use the elevated command prompt, for example on Windows 7 start it via 'Run as administrator' option.

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

MariaDB Server does not currently provide a .pkg installer for macOS. For information about how to install MariaDB Server on macOS using Homebrew, see Installing MariaDB Server on macOS Using Homebrew.

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

How to create a source tar.gz file.

First Setup your build environment.

Then use automake/configure/make to generate the tar file:

BUILD/autorun.sh
./configure --with-plugin-xtradb
make dist

This creates a source file with a name like mysql-5.3.2-MariaDB-beta.tar.gz

See also the generic build instructions.

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

Users need to run mariadb-install-db.exe, without parameters to create a data directory, e.g

C:\zip_unpack\directory> bin\mariadb-install-db.exe

Then you can start server like this

C:\zip_unpack\directory> bin\mariadbd.exe --console

If you like to customize the server instance (data directory, install as service etc), please refer to mariadb-install-db.exe documentation

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

MariaDB is in Gentoo, so the steps to build it are:

1. Synchronize your tree with\

   Copy

   emerge --sync

2. Build MariaDB using\

   Copy

   emerge mariadb

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

This article lists some typical errors that may happen when you try to use an incompatible MariaDB binary on a linux system:

The following example errors are from trying to install MariaDB built for SuSE 11.x on a SuSE 9.0 server:

and

If you see either of the above errors, the binary MariaDB package you installed is not compatible with your system.

The options you have are:

• Find another MariaDB package or tar from the

If you are using DirectAdmin and you encounter any issues with , then the directions below may help. The process is very straightforward.

Or:

Buildroot

is a way to cross compile MariaDB and other packages into a root filesystem. In the menuconfig you need to enable "Enable C++ Support" first under "Toolchain". After C++ is enabled MariaDB is an option under "Target Packages" ->"Libraries" -> "Databases" -> "mysql support" -> "mysql variant" -> "mariadb". Also enable the "mariadb server" below the "mysql support" option.

After running apt-upgrade mariadb, it's possible that apt shows a fail in trying to start the server, but in fact the database is up and running, which then provokes apt to remain in a non finished state.

For example:

This situation could occur if the timeout for the init script was too short. For example, see , a situation where the timeout was 30 seconds, but the server was taking 48 seconds to start.

To overcome this, the timeout needs to be increased. This can be achieved as follows:

The following article is about different issues people have encountered when installing MariaDB on RHEL / CentOS.

It is highly recommended to where possible.

In RHEL/ CentOS it is also possible to install a or a . The RPM is the preferred version, except if you want to install many versions of MariaDB or install MariaDB in a non standard location.

Replacing MySQL

mariadb-install-db initializes the MariaDB data directory and creates the in the database, if they do not exist. MariaDB uses these tables to manage , , and . It also uses them to provide the data for the command in the client.

works by starting MariaDB Server's mysqld process in mode and sending commands to create the and their content.

There is a version specifically for Windows, .

To invoke mariadb-install-db

If you see the error message:

...then you are probably trying to use the mysql command-line client from MariaDB with libmysqlclient.so from MySQL.

The symbol mysql_get_server_name() is something present in the MariaDB source tree and not in the MySQL tree.

If you have both the MariaDB client package and the MySQL client packages installed this error will happen if your system finds the MySQL version oflibmysqlclient.so first.

To figure out which library is being linked in dynamically (for instance, the wrong one) use the 'ldd' tool.

PHP5 may give an error if used with the old connect method:

This is because the library wrongly checks and expects that the client library must be the exact same version as PHP was compiled with. You would get the same error if you tried to upgrade just the MySQL client library without upgrading PHP at the same time.

Ways to fix this issue:

1. Switch to using the in PHP (Recommended solution).

By default all plugins are enabled and built as dynamic .so (or .dll) modules. If a plugin does not support dynamic builds, it is not built at all.

Use PLUGIN_xxx cmake variables. They can be set on the command line with -DPLUGIN_xxx=value or in the cmake gui. Supported values are

Below are instructions for creating your own Debian repository. The instructions are based on

Using the Debian repository you just created

One needs to add a new file to the /etc/apt/sources.list.d/ directory. For instance a new file called mariadb.list

In the event that you are using the Linux-based operating system Fedora or any of its derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB build in the official repositories.

Installing Build Dependencies

MariaDB requires a number of packages to compile from source. Fortunately, you can use the package in the Fedora repository to retrieve most of the relevant build dependencies through DNF.

Running DNF in this way pulls the build dependencies for the release of MariaDB compiled by your version of Fedora. These may not be all the dependencies you need to build the particular version of MariaDB you want to use, but it will retrieve most of them.

For some distributions you can build MariaDB from a source RPM. (See also ).

You can build it as follows:

using dnf

On RHEL8 you might need to start with:

MariaDB source RPMs (SRPMs) are not packaged on all platforms for which MariaDB RPMs are packaged.

The reason is that MariaDB's build process relies heavily on for a lot of things. In this specific case, MariaDB's build process relies on to build RPMs. The specific package generator that it uses to build RPMs is called .

Support for source RPMs in became usable with MariaDB's build system starting from around . This means that we do not produce source RPMs on platforms where the installed version is older than that.

See also .

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

The following two articles should help you get your Solaris machine prepared to build MariaDB (just ignore the parts about installing buildbot):

MariaDB Corporation provides package tarballs for some MariaDB database products.

Package tarballs provide multiple benefits:

• Package tarballs are compressed tar archives that contain software packages.

• Software packages can be installed using the operating system's package manager without relying on a remote repository.

• RPM (.rpm) files are distributed for CentOS, Red Hat Enterprise Linux (RHEL), and SUSE Linux Enterprise Server (SLES).

• DEB (.deb) files are distributed for Debian and Ubuntu.

If you want to deploy MariaDB database products without using a package tarball, are available. Available deployment methods are component-specific.

Use Cases

MariaDB database products can be deployed with package tarballs to support use cases, such as:

• Transfer the package tarball to an air-gapped network for installation without an internet connection

• Install software using a package manager without configuring a package repository

• Automatically install missing dependencies using a package manager

Compatibility

The following MariaDB database products can be deployed using package tarballs:

• MariaDB Community Server 10.5

• MariaDB Community Server 10.6

• MariaDB Enterprise Server 10.5

• MariaDB Enterprise Server 10.6

Download a Package Tarball

MariaDB Corporation provides package tarballs (.debs.tar, .rpms.tar) to support customers who leverage in-house package repositories to distribute software to their servers. Secure any such repository to prevent outside access.

MariaDB Corporation provides multiple interfaces to download package tarballs.

Installation From Package Tarball

Once downloaded and extracted, you can:

• Install .rpm packages (RHEL, CentOS, and SLES): rpm -i

• Install .deb packages (Debian, Ubuntu): dpkg -i

• Install from the simple package repositories included in the tarball. Missing dependencies will be resolved when using the apt, yum

Installation loads software to the system. This software requires configuration before the database server is ready for use.

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

In the event that you are using the Linux-based operating system Debian or any of its direct derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB source repository for the release that interests you. For Ubuntu and its derivatives, see Building on Ubuntu.

Before you begin, install the software-properties-common and devscripts packages:

Installing Build Dependencies

MariaDB requires a number of packages to compile from source. Fortunately, you can use the MariaDB repositories to retrieve the necessary code for the version you want. Use the tool to determine how to set up the MariaDB repository for your release of Debian, the version of MariaDB that you want to install, and the mirror that you want to use.

First add the authentication key for the repository, then add the repository.

The second command added text to the /etc/apt/sources.list file. One of these lines is the repository containing binary packages for MariaDB, the other contains the source packages. The line for the source packages is commented out by default. This can be scripted:

Alternately, open the file using your preferred text editor and uncomment the source repository.

Once the repository is set up, you can use apt-get to retrieve the build dependencies. MariaDB packages supplied by Ubuntu and packages supplied by the MariaDB repository have the same base name of mariadb-server. You need to specify the specific version you want to retrieve.

Building MariaDB

Once you have the base dependencies installed, you can retrieve the source code and start building MariaDB. The source code is available on GitHub. Use the --branch option to specify the particular version of MariaDB you want to build.

The source code includes scripts to install the remaining build dependencies. For Ubuntu, they're located in the debian/ directory. Navigate into the repository and run the autobake-deb.sh script. Then use

After Building

After building the packages, it is a good idea to put them in a repository. See the page for instructions.

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

Instructions on compiling MariaDB on musl-based operating systems (Alpine)

The instructions on this page will help you compile MariaDB from source. Links to more complete instructions for specific platforms can be found on the source page.

• First, .

• Next, .

Using cmake

and above is compiled using cmake. You can configure your build simply by running cmake using special option, i.e.

To build and install MariaDB after running cmake use

Note that building with MariaDB this way will disable tokuDB, till tokuDB becomes fully supported on musl.

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

To generate RPM packages from the build, supply the -DRPM=xxx flag to CMake, where the value xxx is the name of the distribution you're building for. For example, centos7 or rocky8 or fedora39 or sles15.

What these do are controlled in the following CMake files:

• cmake/cpack_rpm.cmake

• cmake/build_configurations/mysql_release.cmake

• cmake/mariadb_connector_c.cmake

To build the packages you should execute:

See Also

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

In the event that you are using the Linux-based operating system Ubuntu or any of its derivatives and would like to compile MariaDB from source code, you can do so using the MariaDB source repository for the release that interests you.

Before you begin, install the software-properties-common, devscripts and equivs packages.

Installing Build Dependencies

MariaDB requires a number of packages to compile from source. Fortunately, you can use the MariaDB repositories to retrieve the necessary code for the version you want. Use the tool to determine how to set up the MariaDB repository for your release of Ubuntu, the version of MariaDB that you want to install, and the mirror that you want to use.

First add the authentication key for the repository, then add the repository.

Once the repository is set up, you can use apt-get to retrieve the build dependencies. MariaDB packages supplied by Ubuntu and packages supplied by the MariaDB repository have the same base name of mariadb-server. You need to specify the specific version you want to retrieve.

Building MariaDB

Once you have the base dependencies installed, you can retrieve the source code and start building MariaDB. The source code is available on GitHub. Use the --branch option to specify the particular version of MariaDB you want to build.

The source code includes scripts to install the remaining build dependencies. For Ubuntu, they're located in the debian/ directory. Navigate into the repository and run the autobake-deb.sh script. Then use

Further Dependencies

In the event that there are still build dependencies that are not satisfied, use mk-build-deps to generate a build dependency deb to use in installing the remaining packages.

Then, call the autobake-deb.sh script again to build MariaDB.

After Building

After building the packages, it is a good idea to put them in a repository. See the page for instructions.

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

Sometimes, one needs to have MariaDB compiled with Vanilla XtraDB. This page describes the process to do this. The process is rather crude, as my goal was just a once-off compile for testing (that is, not packaging or shipping) purposes.

The process is applicable to and XtraDB from Percona Server 5.1.61.

wget http://s.petrunia.net/scratch/make-vanilla-xtradb-work-with-mariadb.diff

bzr branch /path/to/mariadb-5.3 5.3-vanilla-xtradb-r3

cd 5.3-vanilla-xtradb-r3/storage/
tar czf innodb_plugin.tgz innodb_plugin/
rm -rf innodb_plugin
tar czf xtradb.tgz xtradb/
rm -rf xtradb
cd ../../

tar zxvf ~/Percona-Server-5.1.61.tar.gz
cp -r Percona-Server-5.1.61/storage/innodb_plugin 5.3-vanilla-xtradb-r3/storage/
patch -p1 -d 5.3-vanilla-xtradb-r3/storage/innodb_plugin/ < make-vanilla-xtradb-work-with-mariadb.diff

cd 5.3-vanilla-xtradb-r3/

BUILD/autorun.sh
./configure --with-plugin-innodb_plugin
make

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

MariaDB uses InnoDB as the default storage engine.

If you want to use Oracle's InnoDB plugin, then you need to compile MariaDB andnot specify --without-plugin-innodb_plugin when configuring. For example, a simple ./configure without any options will do.

When the InnoDB plugin is compiled, the innodb_plugin test suite will test the InnoDB plugin in addition to xtradb:

./mysql-test-run --suite=innodb_plugin

To use the innodb_plugin instead of xtradb you can do (for ):

See Also

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

How to generate binary tar.gz files.

• Setup your build environment.

• Build binaries with your preferred options/plugins.

If the binaries are already built, you can generate a binary tarball with

make package

Prior to , the following steps were required:

• Use make_binary_distribution to generate a binary tar file:

This creates a source file with a name like mariadb-5.3.2-MariaDB-beta-linux-x86_64.tar.gz in your current directory.

The other option is to use the bakery scripts. In this case you don't have to compile MariaDB source first.

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

MariaDB Corporation customers can use a Customer Download Token to download MariaDB database products using command-line tools or automation. This page provides instructions on how to retrieve and use the Customer Download Token.

Alternatively, customers can download MariaDB database products using a web browser from the without a Customer Download Token if they are logged in with their MariaDB ID.

Retrieve Customer Download Token

MariaDB Corporation customers can retrieve their Customer Download Token through the MariaDB Customer Portal.

This guide provides the detailed steps for installing MariaDB 10.1.21 via individual RPM packages on CentOS 7. The process involves installing dependencies, then the main packages, and resolving potential conflicts as they appear.

The RPMs needed for the installation are available from the MariaDB website. The required packages for this guide are:

Step-by-Step Installation

1. Install Basic Dependencies

The MariaDB project signs their MariaDB packages for Debian, Ubuntu, Fedora, and Red Hat. This page documents information about the keys that we use and have used.

MariaDB Community Server Debian / Ubuntu key

Our MariaDB Community Server repositories for Debian "Sid" and the Ubuntu 16.04 and beyond "Xenial" use the following GPG signing key. As detailed in MDEV-9781, APT 1.2.7 (and later) prefers SHA2 GPG keys and now prints warnings when a repository is signed using a SHA1 key like our previous GPG key. We have created a SHA2 key for use with these.

Information about this key:

• The short Key ID is: 0xC74CD1D8

• The long Key ID is: 0xF1656F24C74CD1D8

• The full fingerprint of the key is: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8

• Usage of the apt-key command is deprecated in the latest versions of Debian and Ubuntu, and the replacement method is to download the keyring file to the /etc/apt/trusted.gpg.d/ directory. This can be done with the following:

Prior to Debian 9 (Stretch), and Debian Unstable (Sid), and Ubuntu 16.04 LTS (Xenial), the id of our GPG public key was 0xcbcb082a1bb943db. The full key fingerprint is:

MariaDB Community Server RPM / Source Keys

MariaDB Enterprise GPG Keys

MariaDB MaxScale GPG Keys

Configuring Repositories

See the page for details on using the mariadb_repo_setup and mariadb_es_repo_setup scripts to configure repositories that use these keys.

See the on configuring MariaDB Foundation repositories that use these keys.

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

This article describes how to download the RPM files and install them using therpm command.

It is highly recommended to Install MariaDB with yum where possible.

Navigate toand choose the desired database version and then select the RPMs that match your Linux distribution and architecture.

Clicking those links takes you to a local mirror. Choose the rpms link and download the desired packages. The packages will be similar to the following:

For a standard server installation you will need to download at least the client, shared, and server RPM files. See About the MariaDB RPM Files for more information about what is included in each RPM package.

After downloading the MariaDB RPM files, you might want to check their signatures. See for more information about checking signatures.

Prior to installing MariaDB, be aware that it will conflict with an existing installation of MySQL. To check whether MySQL is already installed, issue the command:

If necessary, you can remove found MySQL packages before installing MariaDB.

To install MariaDB, use the command:

You should see output such as the following:

Be sure to follow the instructions given in the preceding output and create a password for the root user either by using or by running the /usr/bin/mysql_secure_installation script.

Installing the MariaDB RPM files installs the MySQL tools in the /usr/bin directory. You can confirm that MariaDB has been installed by using the client program. Issuing the command mariadb should give you the MariaDB cursor.

See Also

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

The mariadb-install-db.exe utility is the Windows equivalent of mariadb-install-db.

Functionality

The functionality of mariadb-install-db.exe is comparable with the shell script mariadb-install-db used on Unix, however it has been extended with both Windows specific functionality (creating a Windows service) and to generally useful functionality. For example, it can set the 'root' user password during database creation. It also creates the my.ini configuration file in the data directory and adds most important parameters to it (e.g port).

mariadb-install-db.exe is used by the MariaDB installer for Windows if the "Database instance" feature is selected. It obsoletes similar utilities and scripts that were used in the past such as mysqld.exe --install,mysql_install_db.pl, and mysql_secure_installation.pl.

Example

will create the database in the directory C:\db, register the auto-start Windows service "MyDB", and set the root password to 'secret'.

To start the service from the command line, execute

Removing Database Instances

If you run your database instance as service, to remove it completely from the command line, use

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

These best practices warrant consideration, but are not expected to apply to every business or in every situation. Recommendations here are not mandatory.

General Recommendations

We recommend that you:

• Understand business requirements before deployment.

• Adapt deployment practices to align to business requirements.

• Consider to what extent deployed systems should integrate with existing business systems and practices.

Backups

Addition, removal, and change of database systems are types of production changes. Before undertaking any production changes:

• Perform a backup of existing data and database configurations.

• Establish a plan for data restoration for use in reverting a change.

• Perform a test to confirm your backup is complete and viable.

Irreversible Changes

Installation of new database servers, change of server configuration, migrations, upgrades, and downgrades can produce irreversible changes which may require you to restore from the last good backup.

Changes to data format on disk, including from upgrades and downgrades, are generally irreversible. A fault during the upgrade or downgrade process may corrupt data. Confirm you have a recent, full, complete, and tested backup before any upgrade or downgrade operation.

When are in use, downgrade operations will generally require migration of data between servers or restore from a backup made pre-upgrade.

Full and Complete Backup

Before proceeding with an upgrade, perform a full and complete backup. Confirm successful completion of the backup operation and test the backup.

Business requirements may require you to retain backups made to support upgrade and downgrade operations.

Additional information regarding backing up and restoring MariaDB database products can be found in "".

Change Management

Change Management, Automation, Orchestration

Server configuration changes should be done through change management. Accurate records of the time of change and reason for change can enable faster issue diagnosis.

Automation can enable repeatability of change deployment, and can aid Pre-Production and Post-Production testing.

Automation or orchestration can enable repeatability of server deployment, including system provisioning.

Production Controls

Dedicated Servers

Database servers exist to run database server software. Database servers should not also run web server software, act as a file server, or run other workloads.

Understand workload and data isolation requirements before server deployment. Isolation requirements are often defined through business requirements, including:

• Data and application security requirements that trigger isolation of one workload from other workloads.

• Separation of Development and Testing environments from Production environments.

Production Controls

Understand control requirements before server deployment, including records of control implementation needed to support audits.

Control requirements typically follow data:

• Both production and non-production systems may require production-level controls based on the presence of data subject to control.

• Database servers, backup servers, and other systems may require production-level controls based on the presence of data subject to control.

Testing

Servers should be validated before exposure to production workloads and production data.

It may be appropriate to prevent access to an unconfigured server until configured and validated. Load balancer configuration, firewall rules, or database server configuration are often used to prevent unintended traffic to new servers.

Details assessed during Pre-Production validation can include:

• Server capacity, including performance of disk systems

• Server security configuration and hardening

• Tuning for initial data load vs production workloads

• Alignment to business requirements

Updates

MariaDB Product Notifications allow you to keep aware of new releases, including security fixes. Customers can manage MariaDB Product Notifications through the .

Additionally, MariaDB Enterprise Server follows an enterprise lifecycle, that provides a .

Obtaining Support

MariaDB Corporation provides commercial support and services for MariaDB database products.

New customers can for more information.

Existing MariaDB Subscription customers can access technical support via the as detailed in .

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

Prelude

Building MariaDB on macOS relies on the Apple-provided toolchain and Homebrew for dependencies.

You can install the toolchain without XCode (suggested, unless you have XCode installed already) with:

Homebrew is a package manager for macOS which you can install from https://brew.sh

Install Dependencies

First, install the upstream dependencies, then clone MariaDB.

Second, clone MariaDB from the GitHub repository: see the page for options.

Set Up the Environment

CMake should find the dependencies automatically, but we may need to set several environment variables to explicitly point at locations of dependencies installed by Homebrew to avoid conflicts with system-native versions that aren't suitable for building MariaDB. In the worst case scenario, use the following (but you can try building MariaDB first by skipping to the "Run CMake" section below to see if these are necessary in your setup):

The installation location of Homebrew depends on the processor type. Apple Silicon macs will have Homebrew in /opt/homebrew while Intel macs will have Homebrew in /usr/local.

Run CMake

By default, macOS uses a case-insensitive filesystem. When building, we can't create a build subdirectory because BUILD already exists, and all the CMake output will end up mixed in with BUILD. Instead, create a mariadb-build directory as that is unique. cd into mariadb-build and, from there, run CMake with the following flags:

(You can vary the values of these flags depending on what you need to do.)

If CMake runs successfully, you can then run the build itself:

This produces a mariadbd binary at mariadb-build/sql.

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

Shortly after the release we became aware of some installation issues with the Debian and Ubuntu repositories. These issues were fixed in , but due to how apt works, steps need to be taken to solve the broken dependencies before upgrading.

We know of three scenarios when dependencies were broken. The steps to fix each of them are pretty much the same, only the list of broken dependencies and hence the list of packages to take care of them differs. The basic idea is to downgrade those certain packages to 5.5.32 temporarily before upgrading them to 5.5.33a.

If you ran into issues when moving from to , look through each of the three scenarios to see which one applies to you and then follow the steps to apply that fix.

Applying the fix

To get your system ready to apply the fix, do the following:

• Comment out the standard repo in the /etc/apt/sources.list or /etc/apt/sources.list.d/mariadb.repo file (or wherever you have the repositories configured).

• Add a repository to the sources.list. The easiest way is to add the following. Just replace '{os}' and '{dist}' with the appropriate values.

For example, on Debian Wheezy the line would be:

And on Ubuntu Raring the line would be:

• Then run 'sudo apt-get update'

• Then 'sudo apt-get install' the list of packages to downgrade as given in the applicable section below.

• Next, modify our sources.list to remove the 5.5.32 repo and switch back to the normal 5.5 repo

5.5.32 server + 5.5.32 client upgraded to the initial (17 Sep 2013) release of 5.5.33

In this first scenario, both client and server were partially upgraded to 5.5.33 before the process aborted. The problem looks like this:

To fix it, the following server and client packages need to be temporarily downgraded to 5.5.32 (replace 'wheezy' with the name of whatever distribution you are using):

5.5.32 Galera server and 5.5.32 MariaDB client upgraded to 5.5.33

In this scenario, the client upgraded, but Galera-server did not. The problem looks like this:

To fix it, only the client packages need to be temporarily downgraded to 5.5.32 (replace wheezy with whatever your distribution is):

5.3.12 server + 5.3.12 client + 5.5.32 libmariadbclient18 upgraded to 5.5.33

In this scenario, only the library upgraded. The problem looks like this:

To fix it, the library needs to be downgraded to 5.5.32 (replace wheezy with your distribution):

After switching back to the 5.5 repo, the libraries won't get upgraded, they will stay 5.5.32 until you upgrade the server to 5.5.33a.

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

MariaDB Corporation provides package repositories, including the MariaDB Enterprise Repository and the MariaDB Community Repository, that can be used to install MariaDB products using the operating system's package manager. Local mirrors of the package repositories can be used for local deployments.

Local package repository mirrors provide multiple benefits:

• MariaDB Corporation's official package repositories are the source for the local mirror.

• Tools provided by the operating system are used to create and maintain the local mirror.

• After a local mirror is created, the mirror can be used just like the MariaDB repositories to install MariaDB products using the operating system's package manager.

If you want to deploy MariaDB database products without using a local package repository mirror, are available. Available deployment methods are component-specific.

Use Cases

MariaDB database products can be deployed with local package repository mirrors to support use cases, such as:

• Install from the mirror on an air-gapped network that is not connected to the internet

• Remove packages from mirror for versions that are not used in the local environment

• Add packages to mirror for tools and clients that are used in the local environment

Compatibility

The following MariaDB database products can be deployed using package repositories:

• MariaDB Community Server 10.6

• MariaDB Community Server 10.11

• MariaDB Community Server 11.4

• MariaDB Community Server 11.8

Operating System Package Managers

The package manager depends on the operating system:

Create a Local Repository Mirror

Creating a local mirror of the MariaDB Enterprise Repository or the MariaDB Community Repository enables you to distribute MariaDB products to your servers from a local repository you support. Secure any such repository mirror to prevent outside access.

2. Set up a repository mirroring tool, for example:

   • YUM: reposync, available at:

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

MariaDB was originally designed as a drop-in replacement of MySQL, with more features, new storage engines, fewer bugs, and better performance, but you can also install it alongside MySQL. (This can be useful, for example, if you want to migrate databases/applications one by one.)

Here are the steps to install MariaDB near an existing MySQL installation.

• Download the compiled binary tar.gz file that contains the latest version.

• Extract the files in a directory of your choice. In the following, we assume you chose the

Required Tools

The following is a list of tools that are required for building MariaDB on Linux and Mac OS X. Most, if not all, of these will exist as packages in your distribution's package repositories, so check there first. See , , and pages for specific requirements for those platforms.

In the event that you are using the Linux-based operating system CentOS or any of its derivatives, you can optionally compile MariaDB from source code. This is useful in cases where you want use a more advanced release than the one that's available in the official repositories, or when you want to enable certain feature that are not otherwise accessible.

Installing Build Dependencies for

Before you start building MariaDB, you first need to install the build dependencies required to run the compile. CentOS provides a tool for installing build dependencies. The yum-builddep utility reads a package and generates a list of the packages required to build from source, then calls YUM to install them for you. In the event that this utility is not available on your system, you can install it through the

It is relatively straightforward to build MariaDB from source on FreeBSD. When working with an individual host, you can use Ports to compile particular or multiple versions of MariaDB. When working with multiple hosts, you can use Poudriere to build MariaDB once, then serve it as a package to multiple FreeBSD hosts.

Using Ports

The FreeBSD Ports Collection provides a series of Makefiles that you can use to retrieve source code, configure builds, install dependencies and compile software. This allows you to use more advanced releases than what is normally available through the package managers as well as enable any additional features that interest you.

A member of the MariaDB community, Mark <ms (at) it-infrastrukturen (dot) org>, has created some Debian "squeeze" 6.0.4 based, live iso images with or 5.3 pre-installed on them and some Debian "squeeze" 6.0.5 based, live iso images with pre-installed on them.

These live and install images can be used to quickly run a MariaDB server in live mode for learning or testing purposes, or to simplify and speed up off-line installations of Debian-based MariaDB servers onto harddisk.

To work in live mode the system boots from a usb stick (or CD/DVD) and runs in RAM without touching the system's harddisk drive.

The same usb stick (or CD/DVD media) can be used to install a complete server installation onto the harddisk drive using the included Debian installer.

All required MariaDB packages are included on the media, so there is no need for an Internet connection.

Three types of images are provided, text (command line), LXDE, and Gnome. The text-based live images can be used for testing or server off-line installations. The two gui types, LXDE and Gnome, can be used for testing/learning in live mode or for off-line desktop installations. Debian live images with LXDE (gnome, KDE or awesome) are pretty comfortable for daily work as a replacement for whatever desktop OS is installed on the system.

There are three iso images for each type, one for 32-bit (i386) systems, one for 64-bit (amd64) systems, and one with both.

1. Live iso images (text) for i386, amd64 or multi architectures.

1. Live iso images (text) for i386, amd64 or multi architectures.

1. Live iso images with LXDE for i386, amd64 or multi architectures.

1. Live iso images with Gnome for i386, amd64 or multi architectures.

1. Live images

1. Live images demonstration video

The LXDE and Gnome images contain documentation under /srv/PDF. Including instructions on how to create your own Debian live images in live mode (you need 16GB RAM or more to be able to do this). See the README, README.live, and live-manual.en.pdf files under /srv/PDF for details.

Note: Some HP notebooks are not able to boot binary hybrid iso images from a USB stick.

Downloads

To get the iso images you can use rsync:

or just use the links above (or go to:).

Preparing of bootable media:

A USB stick or CD/DVD can be used as bootable media. The preferred way is a USB stick.

• for Linux: dd if=./<image_name_as_above.iso> of=/dev/<USB-stick-ID_like_sdb_or_sdc>

• for other systems: cygwin includes dd and some other linux/Unix tools.

The iso images have been successfully tested on:

• Acer ASPIRE @ne netbooks (1GB RAM)

• ThinkPad T60p and T61p notebooks (2 or 4GB RAM)

• Xeon E31270 / Asus P8BWS desktop (16GB ECC RAM)

• AMD FX-4100 / Asus M5A99X EVO desktop (16GB ECC RAM)

Notes

It is possible to add some options on the bootline for special purposes like, for example, the installation of additional packages from a local repository on the image or assigning a static IP address and running sshd.

1. To configure a static IP use "ip=". For example: "ip=eth0:192.168.1.53:255.255.255.0:192.168.1.1"

• The full format of "ip=" is: "ip=[interface]:[IP_address]:[netmask]:[gateway]"

1. If you use an empty "ip=" value the content of /etc/network/interfaces and /etc/resolv.conf will be used. Without the "ip=" option, dhcp will be used to get an IP address.

2. For installing and running sshd (so that the image can act as a server in a test environment) use: "sshd=on"

• The live user is "sql" and the password is "live". Please change the password immediately after first login!

1. Depending on the image or 5.3 server is installed. There is no root passord for the database set so please set a password immediately after first login!

2. Run repo-off-line.sh to activate local repositories on the image for apt-get (for off-line installations) or repo-on-line.sh for internet repositories.

3. The binary hybrid live iso images with multiple-choices inside the boot menu allow for the assignment of two different IPs. (e.g. for testing of clustered database operations)

Send any feedback or suggestions related to these images to:

• Mark <ms (at) it-infrastrukturen (dot) org>

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

The .deb packages provided by MariaDB Foundation's and MariaDB Corporation's repositories are not identical to the official .deb packages provided by Debian's and Ubuntu's default repositories.

The packages provided by MariaDB Foundation's and MariaDB Corporation's repositories are generated using the Debian packaging in MariaDB's official source code. The Debian packaging scripts are specifically in the debian/ directory.

The packages provided by Debian's and Ubuntu's default repositories are generated using the Debian packaging in Debian's mirror of MariaDB's source code, which contains some custom changes. The source tree can be found here:

As a consequence, MariaDB behaves a bit differently if it is installed from Debian's and Ubuntu's default repositories.

Option File Locations

• The located at /etc/mysql/my.cnf is handled by the mechanism when the mysql-common package is installed. It is a symbolic link that references either mysql.cnf or mariadb.cnf depending on whether MySQL or MariaDB is installed. Most of the MariaDB are therefore actually located in /etc/mysql/mariadb.d/.

System Variables

Since there is no system variable difference from the Standard MariaDB.