Backups using the Agent for VMWare Virtual Infrastructure (AVVI) fails with error: "0xe0009585 - Unable to open a disk of the virtual machine." and 'Error: '16064' when a particular licensed version of ESX does not contain the vStorage API.
|Article:TECH148510|||||Created: 2011-01-19|||||Updated: 2014-04-25|||||Article URL http://www.symantec.com/docs/TECH148510|
Backup Exec 2010 and Backup Exec 2010 R2 will fail with the error: "0xe0009585 - Unable to open a disk of the virtual machine." and 'Error: '16064' when a limited license is installed on ESX.
Backup Exec 2010’s Agent for VMware natively incorporates VMware’s latest backup technology, vStorage API’s for Data Protection. If an AVVI agent backup is initiated and no vStorage API's exist on the licensed version of the ESX server, the above error can occur.
- 0xe0009585 - Unable to open a disk of the virtual machine.
Beremote debug will contain the following information:
VDDK-Warn: VixDiskLibVim: Not licensed to use this function.
VMDKRemoteImage::Open()Could not open the disk '[Datastore] <Name of VMDK>' Error Text: 'Host is not licensed for this feature 'Error: '16064'
VMWare has several different licensing options for ESX and some can contain all necessary components, while others are limited.
In ESX 3.5 the 'Licensed Features' option will show 'VMWare Consolidated Backup' and will contain the vStorage API as long as the appropriate license has been installed. (See Figure 1)
In ESX 4.0 and higher, the vStorage API is listed in 'Licensed Features' if the appropriate license has been installed. (See Figure 2)
To confirm the vStorage API has been installed for a particular license of ESX, check the following:
1. Select the ESX Server from the list of servers in VMware VirtualCenter.
2. Click the Configuration tab.
3. Click the Licensed Features link
1. Obtain an ESX license key that installs the VStorage API
2. Backup the Virtual Machine using the Backup Exec Remote Agent for Windows Servers.
Unable to open a disk of the virtual machine
Article URL http://www.symantec.com/docs/TECH148510