We recommend that you go through our “Automated Backup” guide and set it up.
Once that is done take a manual backup of the cluster state (the whole Reach namespace as a minimum) using Velero and also take a manual backup of the databases that we list using our provided solution.
velero backup create reach-$(date +"%m-%d-%Y")\
--include-namespaces $REACH_NAMESPACE \
After a while, all the -triggered-backup- jobs should show up as Completed
kubectl get pods -n "$REACH_NAMESPACE" | grep triggered-backup
Query the list of snapshots
kubectl get snapshot -n "$REACH_NAMESPACE"
The output should look something like this with the status of all snapshots showing as Completed
Once you are happy to move on, delete the completed job pods
kubectl delete jobs -n $REACH_NAMESPACE -l app=backup-restore-triggered-backup