Restoring to newly named resources - issue with PVC #8786
Unanswered
dippydocus
asked this question in
Community support Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I originally posted this on the #velero-users Slack channel but maybe here is a better place to ask these questions? 🙂
Hi!,
I'm using Velero as a means to backup and restore VirtualMachines using the kubevirt-velero-plugin.I'd like to be able to restore these resources from a backup while changing the names of the resources to create what will essentially be a new instance.
Changing the names should avoid conflicts with the existing resources as specified in the backup. The way that I'm trying to achieve this is via a plugin that on RestoreItem will change the names and any references that also need changing.
PVCs and the underlying DataVolume will be restored from a VolumeSnapshot.
The problem that I'm having is that the plugin is running which is renaming the PVC and then as soon as it's renamed, the restore logs show that it's reset to allow dynamic allocation.
Does anyone know how I can achieve what I'm trying to do? The restored resources need to remain in the same namespace as the resources that were backed up. Remapping unfortunately isn't an option. Thanks in advance.
My idea to get around this is to get the
VolumeSnapshotContent
in the plugin and manually create a PVC using aVolumeSnapshot
with the above content as the source and then marking the backed-up PVC asWithoutRestore
.If anyone has a better suggestion on how to achieve this I would be super grateful.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions