Skip to content

Backup#

Mirantis strongly recommends that you regularly back up your MKE 4 clusters. In particular, you should backup your clusters anytime you make a configuration change.

Info

The MKE 4 backup operation does not impact normal cluster function.

Limitations#

  • You can only restore an MKE 4 cluster from a backup that was derived from the exact same version of the software.

  • You cannot run two backups of an MKE 4 cluster at the same time.

  • Initiating an upgrade while a backup operation is in progress can lead to unpredictable results.

  • MKE 4 may not be able to back up a cluster that has crashed.

  • MKE 4 does not support scheduled backups.

Create a backup#

Info

MKE 4 backups are saved as local tarballs.

To create an MKE 4 backup and save it to a local path, run:

unset KUBECONFIG
mkectl backup -f <config_file_path>

You can provide a name for the backup using the --name flag. If this flag is not specified, the system will apply backup.tar as the tarball file name. If a backup with the same name already exists, the backup process will immediately fail. To use the same name, please rename the earlier backup tarball or move it to a different location.