Restoring Full Snapshots

In order to set up disaster recovery snapshots, backups should be configured to use a store that exists outside of the cluster. This is especially true for installations on cluster created with the Replicated Kubernetes installer.

Restore on Existing Cluster

1. Begin with installing a version of Velero compatible with the one that was used to make the snapshot.

   • If restoring from an NFS or a host path storage destination, see Configuring an NFS Storage Destination or Configuring a Host Path Storage Destination for the configuration steps and how to set up Velero.
   • Otherwise, see Basic Install and Plugins in the Velero documentation.

   Note: Restic is required and --use-restic flag must be used with velero install command.

2. Use the kots CLI to list backups and create restores. See backup ls and restore in the kots CLI documentation.

Restore on Online Kubernetes Installer-created Clusters

1. Set up the embedded cluster. See Installing with the Kubernetes Installer.
2. Use the kots CLI to configure the pre-installed Velero setup to point at the snapshot storage destination. Consult the relevant CLI documentation for your provider:
   • AWS S3 Configuration: See velero configure-aws-s3.
   • Azure Configuration: See velero configure-azure.
   • GCP Configuration: See velero configure-gcp.
   • S3-Other (e.g. MinIO) Configuration: See velero configure-other-s3.
   • NFS Configuration: See velero configure-nfs and Configuring an NFS Storage Destination.
   • HostPath Configuration: See velero configure-hostpath and Configuring a Host Path Storage Destination.
3. Use the kots CLI to list backups and create restores. See backup ls and restore in the kots CLI documentation.

Restore on Air Gapped Kubernetes Installer-created Clusters

An air gapped Kubernetes installer-created cluster can be restored only if the store backend used for backups is accessible from the new cluster.

The Kubernetes installer must also be able to assign the same IP address to the embedded private image registry in the new cluster.

The Kubernetes installer must be provided with the correct registry IP address:

cat install.sh | sudo bash -s airgap kurl-registry-ip=<ip>

The registry from the old cluster does not need to be (and should not be) accessible.

1. Set up the cluster in accordance with the above guidance as well as the guidance in the air gap installation documentation. See Install in an Air Gapped Environment.
2. Use the kots CLI to configure the pre-installed velero setup to point at the snapshot storage destination. Consult the relevant CLI documentation for your provider:
   • AWS S3 Configuration: See velero configure-aws-s3.
   • Azure Configuration: See velero configure-azure.
   • GCP Configuration: See velero configure-gcp.
   • S3-Other (e.g. Minio) Configuration: See velero configure-other-s3.
   • NFS Configuration: See velero configure-nfs and Configuring an NFS Storage Destination.
   • HostPath Configuration: See velero configure-hostpath and Configuring a Host Path Storage Destination.
3. Use the kots CLI to list backups and create restores. See backup ls and restore in the kots CLI documentation.

Additional Resources

Troubleshooting Backup and Restore