Restore data stores to a previous point in time or recover a lost cluster.

If you are recovering from a complete loss of the Kubernetes cluster, complete the following tasks before restoring:

  • Create a new cluster.
  • Install any drivers or controllers you had installed on the lost cluster.

Scaling Down Services

Scale down Deployments and StatefulSets to prevent conflicts during restoration.

kubectl scale --replicas=0 $(kubectl get deployment -o name -n <namespace>)
kubectl scale --replicas=0 $(kubectl get statefulset -o name -n <namespace>)
Table 27. Scale Down Parameters
Parameter Description
namespace The namespace created for the application.

Restoring Velero

Reinstall Velero and ensure the backup configuration points to the backup storage location you used previously.

Restoring Data Stores

Restore PostgreSQL, MongoDB, Elasticsearch (if deployed), and S3-compatible data stores. NI recommends restoring all data stores to a similar point in time to avoid data inconsistencies.

Restoring Kubernetes Objects

Use Velero to restore the Kubernetes objects. Refer to Restore Reference for more information.
Note Restoring the Kubernetes objects also restores the following to the status at the time of the backup:
  • Application configuration settings
  • The scale of your Deployments and StatefulSets
Run the helm upgrade command with the updated values to reapply changes made since the time of the backup. Refer to Updating SystemLink Enterprise for the appropriate commands for each component.