Merge pull request #72284 from CarmiWisemon/oadp3400-storage-mapping

OADP 3400 storage class mapping

Author: jeana-redhat

backup_and_restore/application_backup_and_restore/oadp-advanced-topics.adoc

@@ -25,14 +25,22 @@ include::modules/oadp-backing-up-opt-out.adoc[leveloffset=+3]
 include::modules/oadp-cluster-to-cluster-uid-and-gid-ranges.adoc[leveloffset=+2]
 include::modules/oadp-backing-and-restoring-from-cluster-to-cluster.adoc[leveloffset=+2]
 
+[id="oadp-storage-class-mapping"]
+== OADP storage class mapping
+
+include::modules/oadp-storage-class-mapping.adoc[leveloffset=+2]
+include::modules/oadp-storage-class-mapping-oadp.adoc[leveloffset=+3]
+
 [role="_additional-resources"]
 [id="additional-resources_oadp-advanced-topics"]
 == Additional resources
 
-For more information about API group versions, see xref:../../backup_and_restore/application_backup_and_restore/oadp-advanced-topics.adoc#oadp-different-kubernetes-api-versions[Working with different Kubernetes API versions on the same cluster].
+* xref:../../backup_and_restore/application_backup_and_restore/oadp-advanced-topics.adoc#oadp-different-kubernetes-api-versions[Working with different Kubernetes API versions on the same cluster].
+
+* xref:../../backup_and_restore/application_backup_and_restore/installing/oadp-using-data-mover-for-csi-snapshots-doc.adoc#backing-up-applications[Using Data Mover for CSI snapshots].
 
-For more information about OADP Data Mover, see xref:../../backup_and_restore/application_backup_and_restore/installing/oadp-using-data-mover-for-csi-snapshots-doc.adoc#backing-up-applications[Using Data Mover for CSI snapshots].
+* xref:../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-backing-up-applications-restic-doc.adoc#backing-up-applications[Backing up applications with File System Backup: Kopia or Restic].
 
-For more information about using Restic with OADP, see xref:../../backup_and_restore/application_backup_and_restore/backing_up_and_restoring/oadp-backing-up-applications-restic-doc.adoc#backing-up-applications[Backing up applications with File System Backup: Kopia or Restic].
+* xref:../../migration_toolkit_for_containers/advanced-migration-options-mtc.adoc#migration-converting-storage-classes_advanced-migration-options-mtc[Migration converting storage classes].
 
 :!oadp-advanced-topics:

modules/oadp-storage-class-mapping-oadp.adoc

@@ -0,0 +1,43 @@
+// Module included in the following assemblies:
+//
+// * backup_and_restore/application_backup_and_restore/advanced-topics.adoc
+
+[id="oadp-storage-class-mapping-oadp_{context}"]
+:_mod-docs-content-type: PROCEDURE
+
+[id=storage-class-mapping-oadp_{context}]
+= Mapping storage classes with OADP
+
+You can use OpenShift API for Data Protection (OADP)  with the Velero plugin v1.1.0 and later to change the storage class of a persistent volume (PV) during restores, by configuring a storage class mapping in the config map in the Velero namespace.
+
+To deploy ConfigMap with OADP, use the `change-storage-class-config` field. You must change the storage class mapping based on your cloud provider.
+
+.Procedure
+. Change the storage class mapping by running the following command:
++
+[source,terminal]
+----
+$ cat change-storageclass.yaml
+----
+. Create a config map in the Velero namespace as shown in the following example:
++
+.Example
+[source,yaml]
+----
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: change-storage-class-config
+  namespace: openshift-adp
+  labels:
+    velero.io/plugin-config: ""
+    velero.io/change-storage-class: RestoreItemAction
+data:
+  standard-csi: ssd-csi
+----
+. Save your storage class mapping preferences by running the following command:
++
+[source,terminal]
+----
+$ oc create -f change-storage-class-config
+----

modules/oadp-storage-class-mapping.adoc

@@ -0,0 +1,16 @@
+// Module included in the following assemblies:
+//
+// * backup_and_restore/application_backup_and_restore/advanced-topics.adoc
+
+[id="oadp-storage-class-mapping_{context}"]
+:_mod-docs-content-type: CONCEPT
+= Storage class mapping
+
+Storage class mapping allows you to define rules or policies specifying which storage class should be applied to different types of data. This feature automates the process of determining storage classes based on access frequency, data importance, and cost considerations. It optimizes storage efficiency and cost-effectiveness by ensuring that data is stored in the most suitable storage class for its characteristics and usage patterns.
+
+You can use the `change-storage-class-config` field to change the storage class of your data objects, which lets you optimize costs and performance by moving data between different storage tiers, such as from standard to archival storage, based on your needs and access patterns.
+
+[id=storage-class-mapping-mtc_{context}]
+== Storage class mapping with MTC
+
+You can use the Migration Toolkit for Containers (MTC) to migrate containers, including application data, from one {product-title} cluster to another cluster and for storage class mapping and conversion. You can convert the storage class of a persistent volume (PV) by migrating it within the same cluster. To do so, you must create and run a migration plan in the MTC web console.