Back up MariaDB on a management cluster

Available since MCC 2.27.0 (Cluster release 16.2.0)

MOSK uses a MariaDB database to store data generated by the Container Cloud components. Mirantis recommends backing up your databases to ensure the integrity of your data. Also, you should create an instant backup before upgrading your database to restore it if required.

The Kubernetes cron job responsible for the MariaDB backup is enabled by default to create daily backups. You can modify the default configuration before or after the management cluster deployment.

Warning

A local volume of only one node of a management cluster is selected when the backup is created for the first time. This volume is used for all subsequent backups.

If the node containing backup data must be redeployed, first move the MySQL backup to another node and update the PVC binding along with the MariaDB backup job to use another node as described in Change the storage node for MariaDB.

Important

Mirantis highly recommends that you also back up MKE on management and MOSK clusters regularly, especially after any major action. For example, after the following operations:

  • Deployment of a management and its MOSK cluster

  • Updating a cluster to a major or patch version

  • Adding or redeploying nodes, including host operating system operations using HostOSConfiguration objects

  • Changing the operating system distribution

  • Reconfiguration of a cluster, for example:

    • Switching to a new container runtime

    • Configuring proxy

    • Updating MKE or Keycloak certificates

  • Minor cluster changes, for example:

    • Adding or removing node labels

    • Creating or removing UpdateGroup objects

For the backup procedure, see Mirantis Kubernetes Engine documentation: Back up MKE.