Restoring DevOps Loop data

You can restore DevOps Loop from a backup created with Velero and Helm values after a disaster recovery event or a failed upgrade.

You must have completed the following tasks:

Ensured that the Kubernetes environment hosting DevOps Loop is running and accessible.
Gained administrative privileges
Installed Velero and configured with an S3-compatible storage backend (MinIO or AWS S3). See Tools supporting backup and restoration.
Locally saved the Helm values for your current DevOps Loop deployment.

DevOps Loop utilizes both block and file storage, allowing the restore process to support CSI snapshots and fs-volume backups.

Important:If DevOps Loop pods that use file storage were not labeled during backup, their data will not be restored, which could result in incomplete or inconsistent recovery.

Run the following command to restore the DevOps Loop namespace from the Velero backup:
```
velero restore create --from-backup devops-loop-backup
```
Verify that the restore is completed successfully by running the following command:
```
velero restore describe devops-loop-backup --details
```
Reinstall or upgrade DevOps Loop using the saved Helm values if necessary:
```
helm upgrade --install devops-loop devops-loop-chart -n devops-loop -f devops-loop-values-backup.yaml
```
Note: If persistent volumes are larger than the default Helm chart sizes, override them using --set options during reinstall.
Optional: Restore any external databases used by DevOps Loop using their native restore tools to ensure data consistency.
Restart DevOps Loop to ensure all services reflect the restored state:
```
kubectl rollout restart deployment devops-loop -n devops-loop
```

Optional: Check the status and logs of your restore jobs to troubleshoot any issues:

# Check all restores
velero get restore

# Describe a specific restore
velero describe restore <RESTORE_NAME>

# View restore logs
velero restore logs <RESTORE_NAME>

You have restored the DevOps Loop namespace, including all CSI snapshots and fs-volume backups, and any external databases (if applicable).