Backup of a virtual machine using the Backup Exec Agent for VMware Virtual Infrastructure (AVVI) fails with the error:
Final error: 0xe0009578 - Unable to copy the virtual machine disk using the VMware VixDiskLib
Final error category: Resource errors
For additional information regarding this error refer to link V-79-57344-38264
V-79-57344-38264 - Unable to copy the virtual machine disk using the VMware VixDiskLib. VixDiskLib_Read() reported the error: You have requested access to an area of the virtual disk that is out of bounds
Currently 2 causes have been identified against this error condition:
- Multiple Extended Partitions exist in a disk in the affected Virtual Machine where the last extended partition is larger than the earlier ones.
- Under "normal" circumstances VMware will only create VMs with disks that have an even number of sectors. However, some Physical to Virtual (P2V) tools create virtual disks that can have an odd number of sectors (matching the original physical disk). This is the second known cause of the problem
This issue has been resolved in Backup Exec 2010 R3 Service Pack 2
If the issue is caused by an odd number of sectors because the Virtual Machine was converted from a physical system, then after installing Backup Exec 2010 R3 with SP1 the problem can be solved with the following steps:
- Use regedit on the media server to locate HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\
- Create a Key called SymVmTools
- Inside the Key create a REG_DWORD value called SymVmToolsValidateDiskSizeAtBrowse and set the value data to 1
- Inside the Key create a REG_SZ value called SymVmToolsDataPath and set the value data to a valid path on the server e.g. C:\Program
Files\Symantec\Backup Exec\Data (Note this is a temporary repository for the disk descriptor files which are removed once the information is extracted)
- Restart the Backup Exec services.
NOTE: the above steps should solve the problem, but could have an effect on performance as such we recommend using the registry modification provided above in order to perform one or more valid backups of the affected system. Then shutdown the original system and run a redirected restore from the backup. Then verify the restore of the restored virtual machine and if operational use this copy as the production machine and then remove the registry modification. The restored VM will have disks with an even number of sectors should no longer experience the problem.
An alternative solution could be to expand the vmdk disk using the tools provided by VMWARE (Vmware Infractructure Client or VSphere). It would force Vmware itself to fix the issue with the odd blocks
Hotfixes are now available to address both causes of this issue in the current version(s) of the product(s) mentioned at the end of this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.
This issue is currently seen with:
- Backup Exec 2010 SP1
- Backup Exec 2010 R2
- Backup Exec 2010 R3