Deploy with Binary Tarballs
MariaDB Corporation provides binary tarballs for some MariaDB Enterprise components.
Binary tarballs provide multiple benefits:
Binary tarballs are compressed
tararchives that contain pre-compiled executables, libraries, and other deployment dependencies.
Binary tarballs can be installed to any path by extracting the contents to the desired path.
After performing a component-specific configuration procedure, the files can be used in-place.
If you want to deploy MariaDB Enterprise components without using a binary tarball, alternative deployment methods are available. Available deployment methods are component-specific.
MariaDB Enterprise components can be deployed with binary tarballs to support use cases, such as:
Transfer the binary tarball to an air-gapped network for installation without an internet connection
Install software without using a package manager
Install software to a custom path
Simultaneously install multiple versions of software at different paths
Install software as a non-root user
Build your own packages
The following MariaDB Enterprise components can be deployed using binary tarballs:
MariaDB Community Server 10.2
MariaDB Community Server 10.3
MariaDB Community Server 10.4
MariaDB Community Server 10.5 (excluding ColumnStore 5)
MariaDB Community Server 10.6 (excluding ColumnStore 6)
MariaDB Enterprise Server 10.2
MariaDB Enterprise Server 10.3
MariaDB Enterprise Server 10.4
MariaDB Enterprise Server 10.5 (excluding Enterprise ColumnStore 5)
MariaDB Enterprise Server 10.6 (excluding Enterprise ColumnStore 6)
MariaDB MaxScale 2.4
MariaDB MaxScale 2.5
MariaDB MaxScale 6
MariaDB Xpand 5.3
MariaDB Xpand 6
MariaDB Xpand Storage Engine 5.3 (included with MariaDB Enterprise Server 10.5)
MariaDB Xpand Storage Engine 6 (included with MariaDB Enterprise Server 10.6)
Download a Binary Tarball
MariaDB Corporation provides multiple interfaces to download binary tarballs.
Download a Binary Tarball with a Web Browser
Steps to download a binary tarball with a web browser:
Installation from Binary Tarball
Many of the configuration steps handled by repository deployment and package tarball deployment must be performed manually when installing from a binary tarball.
Installation from binary tarball requires you to account for steps typically handled by the package manager, including:
Copying files to desired locations
Changing file ownership
Changing file permissions
Configuring system policies, if applicable
Rebuilding OS caches
Creating the default
/etc/mysql/my.cnfconfiguration file, and using the
!includedirdirective to include the provided
Initializing and hardening the data directory by executing
mariadb-install-db(ES10.4 and later) or
Installation loads software to the system. This software requires configuration before the database server is ready for use.