Upgrade Managed Databases to MariaDB 11.8 LTS via WHM & Plesk

Introduction

Many shared‑hosting and VPS users rely on the database management tools that ship with WHM (cPanel) or Plesk. MariaDB 11.8 LTS is the latest long‑term support release, adding new SQL features, improved performance, and continued security updates. This guide walks you through the upgrade of the managed user databases in WHM or Plesk, including the necessary command‑line steps on the underlying server.

1. Preparing the Server for the Upgrade

Before touching the database engine, make sure the system is ready. The steps are split into two blocks: one for Debian/Ubuntu (apt) and one for AlmaLinux/Rocky/RHEL (dnf). WHM/cPanel typically runs on AlmaLinux 9, while Plesk can be on either family, so follow the block that matches your host.

Debian/Ubuntu (apt)

# Update package lists
sudo apt update

# Install tools needed for the repository setup
sudo apt install -y curl gnupg

# Download and run the MariaDB repository setup script
curl -LsS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=11.8

# Refresh the package cache after adding the repo
sudo apt update

The script adds the official MariaDB 11.8 repository, ensuring you receive the correct packages and future security updates.

AlmaLinux / Rocky / RHEL (dnf)

# Install curl if it is not already present
sudo dnf install -y curl

# Download and run the MariaDB repository setup script
curl -LsS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version=11.8

# Clean old metadata and rebuild the cache
sudo dnf clean all
sudo dnf makecache

These commands add the official MariaDB 11.8 repository for the DNF package manager.

2. Backing Up Existing Databases

A backup is the single most important safety net. Both WHM and Plesk provide UI tools, but a command‑line dump guarantees you have a copy that can be restored on any server.

Creating a full dump (all users)

# Create a directory for the backup
mkdir -p ~/mariadb-backup/$(date +%F)

# Dump every database (excluding system schemas if desired)
mysqldump --all-databases --single-transaction --quick --lock-tables=false \
    --user=root --password="YOUR_ROOT_PASSWORD" \
    > ~/mariadb-backup/$(date +%F)/all-databases.sql

Replace YOUR_ROOT_PASSWORD with the actual root password, or use a .my.cnf file to avoid exposing it. Verify the dump size and optionally copy it to off‑site storage.

3. Stopping the Current MariaDB Service

The database engine must be stopped before the package can be replaced. Use the service manager that matches your OS.

Debian/Ubuntu

sudo systemctl stop mariadb

AlmaLinux / Rocky / RHEL

sudo systemctl stop mariadb

Confirm the service is not running:

sudo systemctl status mariadb

4. Upgrading MariaDB Packages

Now install the new version. The package name remains mariadb-server, but the repository points to 11.8.

Debian/Ubuntu

sudo apt install -y mariadb-server

AlmaLinux / Rocky / RHEL

sudo dnf install -y mariadb-server

The package manager will resolve dependencies, replace the old binaries, and keep your existing configuration files (usually /etc/my.cnf.d/server.cnf or /etc/mysql/mariadb.conf.d/).

5. Running the MariaDB Upgrade Script

After the binaries are in place, run the internal upgrade utility. It checks the data dictionary and applies any necessary system‑table changes.

# Start MariaDB in normal mode to run the upgrade tool
sudo systemctl start mariadb

# Run the upgrade utility (it will prompt for the root password)
sudo mysql_upgrade -u root -p

# When the tool finishes, restart the service to apply changes cleanly
sudo systemctl restart mariadb

If mysql_upgrade reports errors, review the log at /var/log/mariadb/mariadb.log (or /var/log/mysql/error.log on Debian) before proceeding.

6. Updating WHM/cPanel Integration

WHM detects the MariaDB version automatically, but you should refresh its internal cache and verify that the new version is recognized.

1. Log in to WHM as root.
2. Navigate to SQL Services → MySQL/MariaDB Upgrade. The page should now display “MariaDB 11.8”.
3. If the page still shows the old version, click Re‑Check Versions or run the following command from the shell:

whmapi1 list_mysql_versions

The JSON output will contain "version":"11.8" if the upgrade succeeded.

7. Updating Plesk Integration

Plesk also reads the server’s mysqld binary. After the upgrade:

1. Log in to the Plesk panel.
2. Go to Tools & Settings → Database Servers. The MariaDB entry should now show version 11.8.
3. If the version does not update, click the Refresh button or run:

# Plesk command‑line utility
sudo plesk bin database_server --list

The list will include the new version number. No further action is required for Plesk’s internal scripts.

8. Verifying User Databases

Log in to a few user databases through WHM’s phpMyAdmin or Plesk’s phpMyAdmin to ensure tables open without errors. Run a quick query to confirm the server version from the client side:

SELECT VERSION();

The result should be something like 11.8.0-MariaDB. Check the error log for any lingering warnings.

Conclusion

Upgrading managed user databases to MariaDB 11.8 LTS inside WHM or Plesk involves three core phases: preparing the repository and backup, swapping the server packages, and confirming that the control panel recognizes the new version. By following the OS‑specific commands above, you keep configuration files intact, minimise downtime, and ensure that all hosted sites continue to run on a supported, secure database engine. Regularly repeat the backup step and monitor the MariaDB changelog to stay ahead of future updates.