Learn more about Replicated to operationalize your KOTS app
Logo

Admin Console Docs

Disaster Recovery

In order to setup disaster recovery snapshots, backups should be configured to use a store that exists outside of the cluster. This is especially true for embedded kURL installs.

Existing Cluster Restore

  1. Begin with installing a version of Velero compatible with the one that was used to make the snapshot.
    1. If restoring from an NFS or a Host Path storage destination, please refer to the Configuring NFS or Configuring a Host Path documentation for the configuration steps and how to set up Velero.
    2. Otherwise, please refer to Velero documention for installing and configuring the plugins.
    3. Note that Restic is required and --restic flag must be used with velero install command.
  2. Use the KOTS CLI to list backups and create restores.

Online Embedded Cluster Restore

  1. Setup the embedded cluster,
  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:
  3. Use the KOTS CLI to list backups and create restores.

Airgapped Embedded Cluster Restore

An airgapped embedded kURL cluster can be restored only if the store backend used for backups is accessible from the new cluster. kURL installer must also be able to assign the same IP address to the embedded private image registry in the new cluster. kURL installer must be provided with the correct registry IP address:

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

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

  1. Setup the cluster in accordance with the above guidance and airgap cluster install documentation
  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:
  3. Use the KOTS CLI to list backups and create restores.