WIP - OADP-3617: Backing up and Restoring VMs - OADP

_topic_maps/_topic_map.yml

@@ -4188,14 +4188,14 @@ Topics:
   Topics:
   - Name: Backup and restore by using VM snapshots
     File: virt-backup-restore-snapshots
-  - Name: Installing and configuring OADP
-    File: virt-installing-configuring-oadp
+#  - Name: Installing and configuring OADP
+#    File: virt-installing-configuring-oadp
   - Name: Backing up and restoring virtual machines
     File: virt-backup-restore-overview
-  - Name: Backing up virtual machines
-    File: virt-backing-up-vms
-  - Name: Restoring virtual machines
-    File: virt-restoring-vms
+#  - Name: Backing up virtual machines
+#    File: virt-backing-up-vms
+#  - Name: Restoring virtual machines
+#    File: virt-restoring-vms
   - Name: Disaster recovery
     File: virt-disaster-recovery
 #  - Name: Collecting OKD Virtualization data for community report

_topic_maps/_topic_map_osd.yml

@@ -1655,14 +1655,14 @@ Topics:
   Topics:
   - Name: Backup and restore by using VM snapshots
     File: virt-backup-restore-snapshots
-  - Name: Installing and configuring OADP
-    File: virt-installing-configuring-oadp
+#  - Name: Installing and configuring OADP
+#    File: virt-installing-configuring-oadp
   - Name: Backing up and restoring virtual machines
     File: virt-backup-restore-overview
-  - Name: Backing up virtual machines
-    File: virt-backing-up-vms
-  - Name: Restoring virtual machines
-    File: virt-restoring-vms
+#  - Name: Backing up virtual machines
+#    File: virt-backing-up-vms
+#  - Name: Restoring virtual machines
+#    File: virt-restoring-vms
 #  - Name: Collecting OKD Virtualization data for community report
 #    File: virt-collecting-virt-data
 #    Distros: openshift-origin

_topic_maps/_topic_map_rosa.yml

@@ -1896,14 +1896,17 @@ Topics:
   Topics:
   - Name: Backup and restore by using VM snapshots
     File: virt-backup-restore-snapshots
-  - Name: Installing and configuring OADP
-    File: virt-installing-configuring-oadp
+#  - Name: Installing and configuring OADP
+#    File: virt-installing-configuring-oadp
   - Name: Backing up and restoring virtual machines
     File: virt-backup-restore-overview
-  - Name: Backing up virtual machines
-    File: virt-backing-up-vms
-  - Name: Restoring virtual machines
-    File: virt-restoring-vms
+#  - Name: Backing up virtual machines
+#    File: virt-backing-up-vms
+#  - Name: Restoring virtual machines
+#    File: virt-restoring-vms
+#  - Name: Collecting OKD Virtualization data for community report
+#    File: virt-collecting-virt-data
+#    Distros: openshift-origin
 #  - Name: Removed topics (Placeholder for topics removed from topic map)
 #    Dir: Removed_topics
 #    Topics:

modules/oadp-installing-dpa-1-3.adoc

@@ -19,7 +19,7 @@ You install the Data Protection Application (DPA) by creating an instance of the
 * You must configure object storage as a backup location.
 * If you use snapshots to back up PVs, your cloud provider must support either a native snapshot API or Container Storage Interface (CSI) snapshots.
 * If the backup and snapshot locations use the same credentials, you must create a `Secret` with the default name, `{credentials}`.
-ifdef::installing-oadp-azure,installing-oadp-gcp,installing-oadp-mcg,installing-oadp-ocs,virt-installing-configuring-oadp[]
+ifdef::installing-oadp-azure,installing-oadp-gcp,installing-oadp-mcg,installing-oadp-ocs,installing-oadp-kubevirt,virt-installing-configuring-oadp[]
 * If the backup and snapshot locations use different credentials, you must create two `Secrets`:
 
 ** `Secret` with a custom name for the backup location. You add this `Secret` to the `DataProtectionApplication` CR.
@@ -363,8 +363,8 @@ spec:
 <6> Specify how many minutes to wait for several Velero resources before timeout occurs, such as Velero CRD availability, volumeSnapshot deletion, and backup repository availability. The default is 10m.
 <7> The administrative agent that routes the administrative requests to servers.
 <8> Set this value to `true` if you want to enable `nodeAgent` and perform File System Backup.
-<9> Enter `kopia` or `restic` as your uploader. You cannot change the selection after the installation. For the Built-in DataMover you must use Kopia. The `nodeAgent` deploys a daemon set, which means that the `nodeAgent` pods run on each working node. You can configure File System Backup by adding `spec.defaultVolumesToFsBackup: true` to the `Backup` CR.
-<10> Specify the nodes on which Kopia or Restic are available. By default, Kopia or Restic run on all nodes.
+<9> Enter `kopia` as your uploader, to use the Built-in DataMover. The `nodeAgent` deploys a daemon set, which means that the `nodeAgent` pods run on each working node. You can configure File System Backup by adding `spec.defaultVolumesToFsBackup: true` to the `Backup` CR.
+<10> Specify the nodes on which Kopia are available. By default, Kopia run on all nodes.
 <11> Specify the backup provider.
 <12> Specify the correct default name for the `Secret`, for example, `cloud-credentials-gcp`, if you use a default plugin for the backup provider. If specifying a custom name, then the custom name is used for the backup location. If you do not specify a `Secret` name, the default name is used.
 <13> Specify a bucket as the backup storage location. If the bucket is not a dedicated bucket for Velero backups, you must specify a prefix.

modules/oadp-kubevirt-setting-resource-limits-and-requests.adoc

@@ -0,0 +1,48 @@
+// Module included in the following assemblies:
+//
+// * backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc
+
+
+:_mod-docs-content-type: CONCEPT
+[id="oadp-kubevirt-setting-resource-limits-and-requests_{context}"]
+= Velero CPU and memory resource allocations for {VirtProductName}
+
+You set the CPU and memory resource allocations for the `Velero` pod by editing the  `DataProtectionApplication` custom resource (CR) manifest.
+
+.Prerequisites
+
+* You must have the OpenShift API for Data Protection (OADP) Operator installed.
+
+.Procedure
+
+* Edit the values in the `spec.configuration.velero.podConfig.ResourceAllocations` block of the `DataProtectionApplication` CR manifest, as in the following example:
++
+[source,yaml]
+----
+apiVersion: oadp.openshift.io/v1alpha1
+kind: DataProtectionApplication
+metadata:
+  name: <dpa_sample>
+spec:
+...
+  configuration:
+    velero:
+      podConfig:
+        nodeSelector: <node selector> <1>
+        resourceAllocations: <2>
+          limits:
+            cpu: "1"
+            memory: 1024Mi
+          requests:
+            cpu: 200m
+            memory: 256Mi
+----
+<1> Specify the node selector to be supplied to Velero podSpec.
+<2> The `resourceAllocations` for backing up {VirtProductName} are most lkely to be more resource intensive than backing up containers. It is advisable to increase the memory and cpu limits.
+
+
+[NOTE]
+====
+Kopia is an option in OADP 1.3 and later releases. You can use Kopia for file system backups, and Kopia is your only option for Data Mover cases with the built-in Data Mover.
+====
+