Back up and restore a management cluster¶
This section contains a backup and restore procedure for the OpenStack or AWS-based Container Cloud clusters. A management cluster backup consists of backing up MKE and MariaDB.
The backup and restore procedure for other supported cloud providers is on the testing stage and will be published in one of the following Container Cloud releases.
The procedures below imply backup and restore of a management cluster to the same hardware nodes.
The restore procedure below implies that the MCR swarm is healthy. If the MCR swarm is not operational, first recover it as described in MKE documentation: Swarm disaster recovery.
The restore procedure below implies usage of the same MKE Docker version of the image that was used during backup. Restoring of an MKE cluster to an MKE version later than the one used during backup is not supported.
To back up an OpenStack or AWS-based management cluster:
Back up MKE as described in MKE Operations Guide: Back up MKE.
Update the root permissions of the backup archive created in the previous step for
sudo chown mcc-user:mcc-user <backup-archive-name>.tar
Verify that the MKE cluster backup has been created as described in MKE Operations Guide: Back up MKE: Verify an MKE backup.
Back up MariaDB as described in Configure periodic backups of MariaDB for AWS and OpenStack providers.
Verify that the backup has been created as described in Verify operability of the MariaDB backup jobs.
To restore an OpenStack or AWS-based management cluster:
If MKE is still installed on the swarm, uninstall MKE as described in MKE documentation: Recover an MKE cluster from an existing backup.
Restore MKE as described in MKE documentation: Restore MKE.
Restore MariaDB as described in Restore MariaDB databases.