Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions modules/virt-about-storage-class-migration.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
// Module included in the following assemblies:
//
// * virt/managing_vms/virtual_disks/virt-migrating-storage-class.adoc

:_mod-docs-content-type: CONCEPT
[id="virt-about-storage-class-migration_{context}"]
= About storage class migration

[role="_abstract"]
A persistent volume claim (PVC) requests storage with specific attributes, such as size and performance, defined by its storage class. You cannot change a PVC's storage class after you create it.

The VM's data remains on the original storage backend that provisioned the PVC. The target storage class might use a different backend that does not contain the VM's data.

To move a VM disk to a new storage class, you create a migration plan. The migration plan creates a new PVC in the target storage class and copies the data from the original PVC to the new PVC.
Original file line number Diff line number Diff line change
Expand Up @@ -11,5 +11,6 @@ toc::[]
[role="_abstract"]
You can migrate one or more virtual disks to a different storage class to optimize storage performance or reduce costs without stopping your virtual machine (VM) or virtual machine instance (VMI).

include::modules/virt-about-storage-class-migration.adoc[leveloffset=+1]
include::modules/virt-migrating-storage-permissions.adoc[leveloffset=+1]
include::modules/virt-migrating-storage-class-ui.adoc[leveloffset=+1]