PersistentVolumeClaim
of the rootdisk and datadisk-0 PVC.rootdisk
PVC at a time:datadisk-0
PVC from the Objects listrootdisk
PVC yaml to learn a bit about why specific transformations are added. Follow the below transformations for the rootdisk
PVC.cdi.kubevirt.io/storage.populatedFor
exists in the PVC, then don’t need to add the annotation, but if the PVC does not have the annotation then the user needs to add the annotation as below: /metadata/annotations/cdi.kubevirt.io~1storage.populatedFor : "rhel8-korean-leopard-rootdisk-i27do
"cdi.kubevirt.io/ownedByDataVolume
exists in the PVC, then remove the annotation using remove
operation and value /metadata/annotations/cdi.kubevirt.io~1ownedByDataVolume
Remove
the path /spec/volumeName
Remove
the ownerReferences
/metadata/ownerReferences/0
Replace
the dataSource
name - /spec/dataSource/name
with the VM name rhel8-korean-leopard
datadisk-0
PVC yaml to learn a bit about why specific transformations are added. Follow the below transformations for the datadisk-0 PVCcdi.kubevirt.io/storage.populatedFor
exists in the PVC, then don’t need to add the annotation, but if the PVC does not have the annotation then the user needs to add the annotation as below: /metadata/annotations/cdi.kubevirt.io~1storage.populatedFor : "rhel8-korean-leopard-datadisk-0-f92h1"
datadisk-0
PVC the annotation cdi.kubevirt.io/ownedByDataVolume
does not exist, so don’t need to perform any transformation.Remove
the path /spec/volumeName
Remove
the ownerReferences
- /metadata/ownerReferences/0
/spec/dataSource
path is not present in the datadisk-0
PVC spec, don’t need to perform any transformation for the dataSource name.Add
button to save the datadisk-0
PVC transformation to see the details of the PVC transformation components.Save
button to start the Restore operation. It will take a few minutes to complete the restore depending on the size of PVCs being restored.