Restore Virtual Machine to Kubernetes Cluster

CommunityEnterprise

The virtual machines are KubeVirt resources with manz dependencies (e.g., Config Maps, Secrets, PVCs, and others). To restore a virtual machine successfully, you must also restore all of its required dependent resources.

We recommend select all resources from the backup. If you need a more targeted (advanced) restore, you can select individual dependencies along with the virtual machine YAML definition.

Note

Some dependencies may be shared by multiple virtual machines. If you select all resources and replace restore option is set to Always, you can modify the configuration of these dependencies and apply an older one. This can affect other virtual machines in the environment.

The plugin can handle different restore scenarios:

  • Same name and in the same namespace: the restore creates its dependencies (if needed) with the same name.

  • Different name but in the same namespace: the restore creates Persistent Volume Claims in the format restore-{UUID}-{PVC Name}.

  • Same name but in a different namespace: the restore creates its dependencies with the same name.

  • Different name and in a different namespace: the restore creates the dependencies with the same name.

Note

When restoring a Network Attachment Definition resource into a different namespace, the plugin creates it with a different bridge name in its configuration. It is because the bridge name must be unique on the nodes. You can change this value after the restore if needed.

See also

Previous articles:

Next articles:

Go back to: Restore.