As an Edge Administrator, you can use this procedure to recover your data and restore Edge site functionality if your managed Kubernetes cluster fails while Edge is running.
While you can follow the steps in Reinstall an Edge site, in the case of a disaster, you must reinstall the Edge site on a new cluster as shown in this use case.
This procedure applies only when your Edge site is installed on a managed Kubernetes cluster.
Use Case Scenario
Below is an example scenario which demonstrates when this procedure would be used and how to initiate it.
In this scenario, an Edge site has already been installed on Cluster A. You should backup your Edge site data regularly to avoid losing your Edge site configurations.
The process of recovering from a disaster requires the following steps:
- Set up a periodic backup of Edge on Cluster A.
- Uninstall the Edge site running on Cluster A.
- Install the new Edge site and restore a backup on Cluster B.
- If you use the Helm chart method, the restore backup command must be run before you reinstall the Edge site.
-
Run the following command to verify the status of the installation.
Copy
kubectl get pods -n collibra-edge
Tip All steps require that the kubectl utility can connect to the cluster.
- Review Edge jobs.
- Create new connections or capabilities.