Scheduling backups using Schedule CR

The schedule operation allows you to create a backup of your data at a specified time, defined by a Cron expression.

You schedule backups by creating a Schedule custom resource (CR) instead of a Backup CR.

Prerequisites

• You must install the OpenShift API for Data Protection (OADP) Operator.

• The DataProtectionApplication CR must be in a Ready state.

Procedure

1. Retrieve the backupStorageLocations CRs:

   $ oc get backupStorageLocations -n openshift-adp

   Example output

   NAMESPACE       NAME              PHASE       LAST VALIDATED   AGE   DEFAULT
   openshift-adp   velero-sample-1   Available   11s              31m

2. Create a Schedule CR, as in the following example:

   $ cat << EOF | oc apply -f -
   apiVersion: velero.io/v1
   kind: Schedule
   metadata:
     name: <schedule>
     namespace: openshift-adp
   spec:
     schedule: 0 7 * * * (1)
     template:
       hooks: {}
       includedNamespaces:
       - <namespace> (2)
       storageLocation: <velero-sample-1> (3)
       defaultVolumesToFsBackup: true (4)
       ttl: 720h0m0s
   EOF

   1	cron expression to schedule the backup, for example, 0 7 * to perform a backup every day at 7:00.
   2	Array of namespaces to back up.
   3	Name of the backupStorageLocations CR.
   4	Optional: In OADP version 1.2 and later, add the defaultVolumesToFsBackup: true key-value pair to your configuration when performing backups of volumes with Restic. In OADP 1.1, add the defaultVolumesToRestic: true key-value pair when you back up volumes with Restic.

3. Verify that the status of the Schedule CR is Completed after the scheduled backup runs:

   $ oc get schedule -n openshift-adp <schedule> -o jsonpath='{.status.phase}'