Skip to main content

About Backup and Restore

This topic provides conceptual information about backup and restore.

Overview

An important part of the lifecycle of an application is backup and restore. The Replicated admin console can be used to create and manage your storage destination and schedule, and to perform and monitor the backup and restore process.

The admin console backup and restore feature is called snapshots. The snapshots feature is available only for licenses that have the Allow Snapshots feature enabled. Velero and restic are the underlying technologies for snapshots.

There are two types of snapshots:

  • Full snapshots (Recommended): Backs up the admin console and all application data. For embedded clusters, this also backs up the Docker registry, which is required for air gapped installations.

    Object-stored data that does not use PVCs, such as Rook and Ceph, require custom hooks for backups. Custom hooks are configured by your vendor. See Full Snapshots in Creating Backups.

  • Partial snapshots: Backs up the application volumes and manifest files only. See Partial Snapshots in Creating Backups.

About Storage Destinations

You can use a storage provider that is compatible with Velero as the storage destination for backups created with the Replicated snapshots feature. For a list of the compatible storage providers, see Providers in the Velero documentation.

You initially configure backups on a supported storage provider backend using the kots CLI. If you want to change the storage destination after the initial configuration, you can use the the Snapshots page in the admin console, which has built-in support for the following storage destinations:

  • Amazon Web Services (AWS)
  • Google Cloud Provider (GCP)
  • Microsoft Azure
  • S3-Compatible
  • Network File System (NFS)
  • Host Path

Kubernetes installers that include the Velero add-on also include a locally-provisioned object store. By default, Kubernetes installer clusters are preconfigured in the admin console to store backups in the locally-provisioned object store. This object store is sufficient for only rollbacks and downgrades and is not a suitable configuration for disaster recovery. Replicated recommends that you configure a snapshots storage destination that is external to the cluster in the admin console for Kubernetes installer clusters.

Additional Resources