Agent for VMware Virtual Infrastructure (AVVI) based backup of VMware ESX virtual machine fails with error "0xe0009599 - The virtual machine has a physical disk"

Article:TECH124365  |  Created: 2010-01-19  |  Updated: 2012-11-13  |  Article URL http://www.symantec.com/docs/TECH124365
Article Type
Technical Solution



Issue



Agent for VMware Virtual Infrastructure (AVVI) based backup of VMware ESX virtual machine fails with error "0xe0009599 - The virtual machine has a physical disk"


Error



Common Errors for this problem are as : 

1. V-79-57344-38297 - The virtual machine has a physical disk.

2. VixDiskLib_Open() reported the error: You do not have access rights to this file

3. V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib.

4. VixDiskLib_Read() reported the error: Unknown error


Cause



Backup of VMware ESX virtual machine fails with above mentioned error if the Virtual Machine being backed up has one or more RDM (RAW Device Mapping) disks in physical compatibility mode connected.

The above error is caused because, as per VMWare: "snapshots of raw disks, RDM physical mode disks, and independent disks are not supported". For more information, refer to the vSphere Basic System Administration guide, Section 17.  http://www.vmware.com/pdf/vsphere4/r40_u1/vsp_40_u1_admin_guide.pdf 

This behavior is different from earlier versions of Backup Exec where the backup job for virtual machine with RDM or independent disk completes with exception. This change has been added in Backup Exec 2010 to ensure that the backup administrator is aware that these type of disks are not being backed up by the AVVI agent but need to be protected by an alternate method [backing up using RAWS separately or in same job].

Solution



For BE 2010 The following workaround can be used to remove the error by excluding the RDM disks. This is NOT supported by Symantec. 
For BE 2012 This option is removed as the resulting backup is not supported and could result in a restored machine that cannot function as one or disks were excluded.
The supported solution is to run a backup of the VM as a physical backup using the Remote Agent.

Warning: Symantec does not support excluding RDM or independent disks from the backup of a virtual machine.  These steps should only be performed after reviewing the risks of excluding the disk(s) from the backup.  It is recommended to completely protect virtual machines with RDM or independent disks to install a Remote Agent on the virtual machine and back it up as a physical server.

1. In the Backup job selections select the virtual machine (VM) with RDM or independent disk.
2. Highlight the VM and click on Include/Exclude button.
3. Select Exclude.
4. Next to File type the name of the vmdk file corresponding to the RDM or independent disk as shown in figure below and click OK.
Note: Make sure to leave "Include subdirectories" checked
 



Note: It is recommended to configure a separate job [ or in a same job ]  to backup these type disks using Backup Exec Remote Agent for Windows Server.

Supplemental Materials

SourceUMI
ValueV-79-57344-38297
Description

The virtual machine has a physical disk. (VixDiskLib_Open() reported the error: You do not have access rights to this file.)


SourceError Code
Value0xe0009599
Description

The virtual machine has a physical disk.


SourceETrack
Value2005502
Description

AVVI: In BE 2010 the backup of a VM with an RDM disk in physical compatibility mode fails with error ?0xe0009599 - The virtual machine has a physical disk?



Legacy ID



347485


Article URL http://www.symantec.com/docs/TECH124365


Terms of use for this information are found in Legal Notices