Error while restoring Red Hat Virtualization virtual machines

The following table describes the problem that might occur when you restore an Red Hat Virtualization virtual machine.

Table: Error run into while restoring Red Hat Virtualization virtual machines

Error message or cause	Explanation and recommended action
VM recovery to alternate location fails on a Windows primary server.	For a Windows NetBackup primary server, ensure that the rename file ends with an empty line.
Pre-recovery check runs successfully when a VM with the same UUID exists in the Red Hat Virtualization cluster and the option to overwrite the VM is not enabled, but the VM restore fails. The following error message is seen: Info bpVMutil (pid=1196) FTL - Virtual machine exists and overwrite option not specified, can not proceed with restore. end Restore; elapsed time Hypervisor policy restore error. (2822)	Pre-recovery check compares the VM display name instead of UUID to find out if VM already exists, hence the check completes successfully. But if the overwrite option is not set, the restore job fails if a VM with the same UUID already exists. Workaround: Restore the VM with a new UUID Start the recovery process. On the Recovery Options page, click Advanced. Enable Create a new VM UUID. Proceed with the recovery process and click Start recovery to restore. Overwrite the existing VM that has the same UUID Start the recovery process. On Recovery Options page, enable the Overwrite existing virtual machine option. Proceed with the recovery process and click Start recovery to restore.
When you try to recover an Red Hat Virtualization VM image that is imported from a different domain using the Web UI, the pre-recovery check fails and displays that by default the recovery host is the same access host that was used during back up.	During the recovery of imported Red Hat Virtualization VM images, for the recovery host, select the access host in the target domain as a recovery host or select the target primary server.

Error message or cause

Explanation and recommended action

VM recovery to alternate location fails on a Windows primary server.

For a Windows NetBackup primary server, ensure that the rename file ends with an empty line.

Pre-recovery check runs successfully when a VM with the same UUID exists in the Red Hat Virtualization cluster and the option to overwrite the VM is not enabled, but the VM restore fails.

The following error message is seen:

Info bpVMutil (pid=1196) FTL - Virtual machine exists and overwrite option not specified, can not proceed with restore. end Restore; elapsed time Hypervisor policy restore error. (2822)

Pre-recovery check compares the VM display name instead of UUID to find out if VM already exists, hence the check completes successfully. But if the overwrite option is not set, the restore job fails if a VM with the same UUID already exists.

Workaround:

Restore the VM with a new UUID

Start the recovery process.
On the Recovery Options page, click Advanced.
Enable Create a new VM UUID.
Proceed with the recovery process and click Start recovery to restore.

Overwrite the existing VM that has the same UUID

Start the recovery process.
On Recovery Options page, enable the Overwrite existing virtual machine option.
Proceed with the recovery process and click Start recovery to restore.

When you try to recover an Red Hat Virtualization VM image that is imported from a different domain using the Web UI, the pre-recovery check fails and displays that by default the recovery host is the same access host that was used during back up.

During the recovery of imported Red Hat Virtualization VM images, for the recovery host, select the access host in the target domain as a recovery host or select the target primary server.

Error while restoring Red Hat Virtualization virtual machines

Feedback

Feedback