Backup and Restoration of DevOps Loop
You must back up HCL DevOps Loop data before you uninstall the current version of DevOps Loop. You must back up the data to avoid data loss or inaccessibility.
A backup creates a copy of your data and stores it in secondary storage. You can use this copy to recover if the original data is lost or becomes inaccessible.
A restore copies backed-up data from secondary storage back to its original location, making it available again.
You must back up and restore the data when you perform the following tasks:
-
Move the existing environment to a new system.
-
Change the name of the release or namespace that you used during the installation of DevOps Loop.
-
Minimize the downtime of DevOps Loop during disaster recovery.
Tools supporting backup and restoration
DevOps Loop uses the following open source tools to perform backup and restore operations:
-
Velero: It is a Kubernetes native backup and restore tool that captures and restores Kubernetes resources, persistent volumes, and application state. Velero also supports disaster recovery and migration scenarios between clusters.
-
MinIO: It is an S3 compatible object storage system used as the backup storage target for Velero. MiniO stores the backups created by Velero and enables you to retrieve them for restore operations.
./ibm-devops-loop/scripts/backup-restore/install-minio.sh
./ibm-devops-loop/scripts/backup-restore/install-velero.sh```bash
kubectl port-forward --address 0.0.0.0 pod/minio -n loops-minio 9000:9000 9090:9090Then, use the MinIO Web UI (http://localhost:9090) to create a bucket (for example, "loops-backup") to store Velero backups.
