Ordered resources for PVCs not being respected #8859
-
|
I have noticed that when I set in the backup manifest the orderedResources for PVCs to be: ns1/pvc-B,ns1/pvc-A,ns1/pvc-C I do not see the backup volumesnaphosts are done in the sequence specified by the orderedResources. I checked backup logs and the Backup Item Operations when they are created/started and doesn't follow the sequence stated. However, I do see that Pods ordering are being respected. Is there a known issue with the PVC ordering, or is my expectation wrong? Note that Im using CSI snapshots for the backup. Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
@gmilamjr PVCs must be backed up with pods, since we have to coordinate the pod hooks. So the Pods are backed up in the specified order -- and then for each pod, the pod's backup item action returns a list of mounted PVCs -- and those are backed up right then before moving on with the pod backup. When velero gets to PVC backup, those are processed in order -- however, PVCs mounted by pods have already been backed up, so those actions become no-ops. If you had PVCs not mounted by pods, those would have probably been backed up according to the ordering. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
@gmilamjr PVCs must be backed up with pods, since we have to coordinate the pod hooks. So the Pods are backed up in the specified order -- and then for each pod, the pod's backup item action returns a list of mounted PVCs -- and those are backed up right then before moving on with the pod backup. When velero gets to PVC backup, those are processed in order -- however, PVCs mounted by pods have already been backed up, so those actions become no-ops. If you had PVCs not mounted by pods, those would have probably been backed up according to the ordering.