mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
17 lines
1.4 KiB
Plaintext
17 lines
1.4 KiB
Plaintext
// 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-full}
|
|
|
|
You can use the {mtc-first} 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-short} web console.
|