Add note to 'Scheduling Backup' section to set backup every 10 minutes

backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-scheduling-backups-doc.adoc

@@ -61,10 +61,22 @@ spec:
     ttl: 720h0m0s
 EOF
 ----
+
 <1> `cron` expression to schedule the backup, for example, `0 7 * * *` to perform a backup every day at 7:00.
++
+[NOTE]
+====
+To schedule a backup at specific intervals, enter the `<duration_in_minutes>` in the following format:
+[source,terminal]
+----
+  schedule: "*/10 * * * *"
+----
+Enter the minutes value between quotation marks (`" "`).
+====
+
 <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.
+<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 version 1.1, add the `defaultVolumesToRestic: true` key-value pair when you back up volumes with Restic.
 
 . Verify that the status of the `Schedule` CR is `Completed` after the scheduled backup runs:
 +

modules/oadp-scheduling-backups.adoc

@@ -1,71 +0,0 @@
-// Module included in the following assemblies:
-//
-// * backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.adoc
-
-:_mod-docs-content-type: PROCEDURE
-[id="oadp-scheduling-backups_{context}"]
-= Scheduling backups
-
-You schedule backups by creating a `Schedule` custom resource (CR) instead of a `Backup` CR.
-
-[WARNING]
-====
-Leave enough time in your backup schedule for a backup to finish before another backup is created.
-
-For example, if a backup of a namespace typically takes 10 minutes, do not schedule backups more frequently than every 15 minutes.
-====
-
-.Prerequisites
-
-* You must install the OpenShift API for Data Protection (OADP) Operator.
-* The `DataProtectionApplication` CR must be in a `Ready` state.
-
-.Procedure
-
-. Retrieve the `backupStorageLocations` CRs:
-+
-[source,terminal]
-----
-$ oc get backupStorageLocations -n openshift-adp
-----
-+
-.Example output
-+
-[source,terminal]
-----
-NAMESPACE       NAME              PHASE       LAST VALIDATED   AGE   DEFAULT
-openshift-adp   velero-sample-1   Available   11s              31m
-----
-
-. Create a `Schedule` CR, as in the following example:
-+
-[source,yaml]
-----
-$ 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 version 1.1, add the `defaultVolumesToRestic: true` key-value pair when you back up volumes with Restic.
-
-. Verify that the status of the `Schedule` CR is `Completed` after the scheduled backup runs:
-+
-[source,terminal]
-----
-$ oc get schedule -n openshift-adp <schedule> -o jsonpath='{.status.phase}'
-----

virt/backup_restore/virt-backing-up-vms.adoc

@@ -37,8 +37,6 @@ include::modules/oadp-backing-up-pvs-csi.adoc[leveloffset=+2]
 include::modules/oadp-backing-up-applications-restic.adoc[leveloffset=+2]
 include::modules/oadp-creating-backup-hooks.adoc[leveloffset=+2]
 
-include::modules/oadp-scheduling-backups.adoc[leveloffset=+1]
-
 [id="additional-resources_virt-backing-up-vms"]
 == Additional resources