Restore KOTS Admin Console and Jama Connect from a Replicated Snapshot (KOTS)
When you set up a new application server for Jama Connect, you can restore the KOTS Admin Console settings that you saved in a Replicated Snapshot.
Snapshots include the registry images and data for Jama Connect.
Requirements
If restoring to a new cluster, it must match these specifications and settings of the cluster where the backup was taken:
Number of nodes
Inbound and outbound traffic rules
Virtual memory settings for Elasticsearch
Connectivity to external services and resources (for example, AWS EFS, AWS S3)
To restore from a snapshot:
Configure servers for a new cluster:
After the servers for the cluster are provisioned, install KOTS on one node using the captured KOTS Installer. You must pass the same flags to the installation script that were passed to the original cluster.
Restoring an online cluster — Run the appropriate installation script that was generated from the captured KOTS installer.
Restoring an airgap cluster — Download the appropriate KOTS installer bundle, replacing <ip> with the IP address of the private registry from the original cluster:
cat install.sh | sudo bash -s airgap kurl-registry-ip=<ip>
When the installer has finished, run the command displayed on the screen so the other servers join the cluster. If required, label the nodes dedicated for Elasticsearch.
Install any add-ons that were manually installed in the cluster. For example, the EFS Driver.
Configure the storage destination: From the KOTS CLI, point the cluster to the storage destination where the Replicated Snapshots were saved.
AWS S3
See configure-aws-s3.
Azure
See configure-azure.
GCP
See configure-gcp.
S3-Other
See configure-other-s3.
NFS
See configure-nfs. If the cluster uses EFS or NFS, also see Configuring an NFS Storage Destination.
Note: If using EFS as an NFS server, Server field = DNS name of the EFS and Path field = a directory inside the EFS, writable by the user:group 1001:1001.
Locate the snapshot and restore it: From the KOTS CLI, run a backup ls and full restore.
backup ls
This can take a few minutes. If the snapshots don’t appear, rerun this command.
If you changed the host name for Jama Connect:
Update the Host Name field in the KOTS Admin Console and deploy the change.
From your browser, log in to Jama Connect and change your URL.
View scheduled jobs to verify that the list isn't empty.
If the Elasticsearch data wasn't included in the snapshot or if the snapshot isn't recent, reindex all search items.
Verify that you can locate your assets.