Back up MariaDB on a management cluster

Container Cloud 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.

After the management cluster deployment, the cluster configuration includes the MariaDB backup functionality for the OpenStack provider.

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

For bare metal and vSphere providers, 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 on bare metal and vSphere clusters.

For the OpenStack provider, a backup job is configured to work with the default csi-sc-cinderplugin storage class. With this class, a PV is created as a Cinder volume. This way, it is independent from any of the management cluster nodes.

• Configure periodic backups of MariaDB
• Verify operability of the MariaDB backup jobs
• Restore MariaDB databases
• Change the storage node for MariaDB on bare metal and vSphere clusters