Upgrading from a previous version of Reach

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 \

 --storage-location=reach-velero

./trigger-database-backup.sh


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


NAME

STATUS

ID

CREATIONDATE

artifact-binary-store-minio-1614596088

Completed

62e1a3a3

2021-03-01T10:54:48Z

artifact-store-neo4j-core-1614596081

Completed

6ae45b16

2021-03-01T10:54:41Z

job-db-mysql-master-1614596084

Completed

944321c7

2021-03-01T10:54:44Z

keycloak-db-mysql-master-1614596084

Completed

468e81a1

2021-03-01T10:54:44Z

vrdb-binary-store-minio-1614596088

Completed

729ae219

2021-03-01T10:54:48Z

vrdb-store-neo4j-core-1614596083

Completed

1c2e7bee

2021-03-01T10:54:43Z

Once you are happy to move on, delete the completed job pods


kubectl delete jobs -n $REACH_NAMESPACE -l app=backup-restore-triggered-backup

T
Tom is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.