Applies to: RHEV, OpenStack, and Nutanix Acropolis hypervisors
A backup can fail when the wrong GUID or UUID is returned during virtual machine discovery for the proxy VM that is performing the backup.
Symptom
Backup fails with a failure to attach a disk to the proxy VM.
The vsbkp.log includes the following error messages:
Failed to attach disk [$[disk_guid]] snapshotid [$[snapshot_guid]] to VMid [$[vm_guid]] Failed to attach disk [$[disk_guid]]. Error details: [Cannot attach Virtual Machine Disk. VM is not found.]
The vsdisovery.log displays the GUID that was returned for the proxy VM:
DetectLocalVMGuid() - Local VM Guid [$[proxy_guid]]
Cause
This error occurs when the GUID or UUID that is returned during VM discovery for a proxy does not match the actual GUID of the proxy VM.
Resolution
To resolve this issue, perform the following steps:
-
Verify that guest tools are up to date on the proxy VM.
-
To identify the correct UUID for the proxy VM, run the following command on the proxy VM that performed the backup:
dmidecode --type system dmidecode --type system | grep -i %s | awk -F: {'print $2'}| tr -d ' \t\r\n'This command returns information in the following format. The UUID entry identifies the actual GUID for the proxy VM.
System Information Manufacturer: Red Hat Product Name: RHEV Hypervisor Version: 7.1-20150420.0.el7ev Serial Number: vm_serial_number UUID: correct_uuid Wake-up Type: Power Switch SKU Number: Not Specified Family: Red Hat Enterprise Linux
For reference information on the dmidecode command, see the Linux man page.
-
To the proxy VM that is used to perform the backup, add the sProxyVMUUID additional setting as shown in the following table.
For instructions on adding additional settings from the CommCell Console, see Add or Modify an Additional Setting.
Property
Value
Name
Category
VirtualServer
Type
String
Value
correct_uuid
-
Run the backup again.