Update Enterprise Manager

Instructions for updating an existing Enterprise Manager deployment.

Prerequisites

• Make a backup of Enterprise Manager data following instructions in Backup & Restore of Enterprise Manager

Enterprise Manager Update with Internet Access

1

Login to the MariaDB Enterprise Docker Registry

Login to the MariaDB Enterprise Docker Registry providing your MariaDB ID as a username and Customer Download Token as a password.

• Docker:

# Login
docker login docker.mariadb.com

• Podman:

# Login
podman login --compat-auth-file .docker/config.json docker.mariadb.com

2

Download the latest installer

This installer performs an in-place update of an existing Enterprise Manager deployment. Download and run it in the directory that contains the existing deployment’s enterprise-manager/ installation directory.

Insert your Customer Download Token into the download URL and download the latest installer in the same folder where you have folder enterprise-manager:

# Download installer
wget https://dlm.mariadb.com/<Customer_Download_Token>/enterprise-release-helpers/install-enterprise-manager.sh

3

Make the installer executable

# Make executable

chmod +x install-enterprise-manager.sh

4

Run the installer

Update Enterprise Manager by running the installer:

# Run installer

./install-enterprise-manager.sh

During this step, the installer renames the existing enterprise-manager/ directory to enterprise-manager.old/, downloads and extracts the new installation tarball into a new enterprise-manager/ directory, and copies the existing .env file and TLS certificates from enterprise-manager.old/ to preserve the current configuration. It then pulls the required container images and recreates the Enterprise Manager containers while reusing the existing container volumes.

When the update completes successfully, the message Enterprise Manager has been upgraded is displayed.

5

Verify containers

Run docker compose ps in the enterprise-manager directory to check that all of the constituent containers are running. The containers are:

• enterprise-manager-grafana

• enterprise-manager-nginx

• enterprise-manager-otelcol

• enterprise-manager-prometheus

• enterprise-manager-supermax

# Check containers

cd enterprise-manager
docker compose ps

Enterprise Manager Update in Air-Gapped Deployment

1

Copy new installer tarball and container images to a private registry

Copy the new installer tarball and container images to your private registry, exactly as during installation, using the versions from the Enterprise Manager release notes for the target release.

2

Update the image versions

Edit the existing enterprise-manager/.env file and update each IMAGE_* tag to the new version of container image you copied to your private registry in the previous step.

# Update image version in .env file

IMAGE_SUPERMAX=<private-registry>/mariadb/enterprise-manager-backend:<backend-version>
IMAGE_NGINX=<private-registry>/mariadb/enterprise-manager-frontend:<frontend-version>
IMAGE_GRAFANA=<private-registry>/mariadb/grafana:<grafana-version>
IMAGE_PROMETHEUS=<private-registry>/mariadb/prometheus:<prometheus-version>
IMAGE_OTELCOL=<private-registry>/mariadb/opentelemetry-collector-contrib:<otelcol-version>

3

Download the latest installer

This installer performs an in-place update of an existing Enterprise Manager deployment. Download and run it in the directory that contains the existing deployment’s enterprise-manager/ installation directory.

Download the latest version of installer, place it on the Enterprise Manager host in the same folder where you have folder enterprise-manager. Make it executable.

4

Run the installer

Update Enterprise Manager by running the installer:

# Run installer

./install-enterprise-manager.sh \
  --registry <private-registry> \
  --repository mariadb/enterprise-manager-distrib \
  --tag <release-version>

The flags tell the installer where to pull the new installation tarball from:

• --registry — your private registry hostname or IP address.

• --repository — the path to the tarball within your registry.

• --tag — the Enterprise Manager release version.

During this step, the installer renames the existing enterprise-manager/ directory to enterprise-manager.old/, downloads and extracts the new installation tarball into a new enterprise-manager/ directory, and copies the existing .env file and TLS certificates from enterprise-manager.old/ to preserve the current configuration. It then pulls the required container images and recreates the Enterprise Manager containers while reusing the existing container volumes.

When the update completes successfully, the message Enterprise Manager has been upgraded is displayed.

5

Verify containers

Run docker compose ps in the enterprise-manager directory to check that all of the constituent containers are running. The containers are:

• enterprise-manager-grafana

• enterprise-manager-nginx

• enterprise-manager-otelcol

• enterprise-manager-prometheus

• enterprise-manager-supermax

# Check containers

cd enterprise-manager
docker compose ps

Agent update

Update the mema-agent package on each monitored MariaDB Server and MaxScale node using the node's package manager. On air-gapped nodes, you can download the new package from the MariaDB Customer Downloads page, transfer it to the node, and update it locally. After updating, verify that the host continues to report to MariaDB Enterprise Manager.

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