Steps to reproduce: OADP demo. backup & restore Pacman application with DataMover.

NOTE: OADP version 1.1 is needed for this Demo to work.

WARN: This is just an example to show how the DataMover feature works in OADP is not official documentation of the product.

Deploy OCP 4.11
Deploy ODF 4.11. Example. Deploying ODF with ArgoCD
Create the openshift-adp namespace and operator-group

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/01_namespace_and_operatorgroup.yaml

Deploy OADP v1.1 Operator

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/02_oadp-operator.yaml

Deploy the Volsync Operator

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/03_volsync-operator.yaml

Create the Restic repository secret that contains the repo encryption key, by default OADP consumes a secret with the name: dm-restic-secret

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/04_restic-secret.yaml

Create a cloud-secret file with the credentials for your S3 backup target. Our example:

$ cat aws-oadp-creds.txt
[default]
aws_access_key_id = AKIAVS4L7GDXXXXXX
aws_secret_access_key = 4amiqN9pw3cy/uXXXXXXXvieXqkkJgSLF1r

Create the cloud-secret from the previous file

$ oc create secret generic cloud-credentials --namespace openshift-adp --from-file cloud=aws-oadp-creds.txt

Create the AWS S3 target bucket that you are going to use for your OADP backups/restores, using an S3 client and the AWS creds from the aws-oadp-creds.txt file to create the bucket. In this example we will use oadp-store as the name for the bucket:

$ aws s3 mb s3://oadp-store/

Create the Data protection application. in this DPA yaml, we are using AWS S3 us-east-1 region with a bucket called oadp-store as the storage location for OADP, the S3 access and secret keys will be read from the cloud-credentials secret created previously, we are also enabling the DataMover feature that is TP in OADP v1.1

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/05_dpa.yaml

Once the DPA is created you should have three pods in the openshift-dpa namespace, the volume-snapshot-mover will be available only when the DataMover the feature is enabled:

$ oc get pods
NAME                                                READY   STATUS    RESTARTS   AGE
openshift-adp-controller-manager-6f45cf8766-6nnhj   1/1     Running   0          14m
velero-8c6c879fc-tm9nk                              1/1     Running   0          65s
volume-snapshot-mover-78d694d4b5-7bztf              1/1     Running   0          65s

Also the Backup Storage Location should be in the Available state:

oc get backupstorageLocations
NAME          PHASE       LAST VALIDATED   AGE     DEFAULT
oadp-demo-1   Available   41s              6m18s   true

Setting a DeletionPolicy of Retain on the VolumeSnapshotClass will preserve the volume snapshot in the storage system for the lifetime of the Velero backup and will prevent the deletion of the volume snapshot

$ oc patch volumesnapshotclass ocs-storagecluster-rbdplugin-snapclass --type=merge -p '{"deletionPolicy": "Retain"}'
$ oc patch volumesnapshotclass ocs-storagecluster-cephfsplugin-snapclass --type=merge -p '{"deletionPolicy": "Retain"}'

$ oc label VolumeSnapshotClass  ocs-storagecluster-cephfsplugin-snapclass velero.io/csi-volumesnapshot-class=true
$ oc label VolumeSnapshotClass ocs-storagecluster-rbdplugin-snapclass velero.io/csi-volumesnapshot-class=true

Deploy the PACMAN application.

$ git clone git@github.com:likid0/oadp-demo.git
$ oc new-project pacman
$ oc apply -k oadp-demo/pacman/

Play Pacman!!! and create High Scores
Take a backup of Pacman, via a normal backup:

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/06_backup-pacman.yaml

or scheduling a planned time for the backup:

$ oc create -f https://github.com/likid0/oadp-demo/blob/main/07_schedule-pacman.yaml

Confirm your backup has finished successfully without errors, for example using the velero cli

$ alias velerocli='oc -n openshift-adp exec deployment/velero -c velero -it -- ./velero'
$ velerocli backup get

Delete the Pacman Namespace, or drop the full OCP cluster

$ oc delete ns pacman

Restore the Pacman Application.

$ oc create -f https://raw.githubusercontent.com/likid0/oadp-demo/main/08_restore-pacman.yaml

Check the restore has finished successfully

$ velerocli restore get

moorrode/oadp-demo

Steps to reproduce: OADP demo. backup & restore Pacman application with DataMover.