Backup of Hyper-V Virtual Machines using the Backup Exec Hyper-V Agent with its files residing inside Mount Points fail with "access denied " error.

Problem

Backup of Hyper-V Virtual Machines using the Backup Exec Hyper-V Agent with its files residing inside Mount Points fail with "access denied " error.

Error Message

Access denied to directory User?Data\Microsoft Hyper-V\VM1\G:\MountPoint\.
Directory VRTSRV::\\HYPV.domain.local\Hyper-V?Virtual?Machine\VM1\User?
Data\Microsoft Hyper-V\VM1\G:\MountPoint was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed

A backup of a Virtual Machine hosted in a Hyper-V setup may fail with the above error if the files for the Virtual Machine (*.Vhd, *.aVhd etc ) are hosted inside mount points. In the error shown above the files related to VM1 are hosted on a disk that has been mounted as a mount point in the location G:\MountPoint

The beremote debug log on the Hyper-V server reports the following error during the backup. Please refer to the Related Documents section for more information on how to enable debugging:

==============================================================================================
 
[2052] 03/19/09 13:29:35 brUtil::OpenObject() Current object is 'G:\MountPoint'
 
[2052] 03/19/09 13:29:35 brUtil::OpenObject Error: 0xE0008488 Could not open the object 'G:\MountPoint'
 
[2052] 03/19/09 13:29:35 Status FS_ACCESS_DENIED (0xE0008488) for DDB pass thru object 1 in SHADOW::OpenObj
 
[2052] 03/19/09 13:29:35 LP_ENV::MsgError: error 0xe0008488 processing object User?Data\Microsoft Hyper-V\VM1\G:\MountPoint
 
=================================================================================================

Solution

Workaround:
 
Ensure that none of the files related to the Virtual Machine are hosted inside Mount Points.
 
Or
 
Backup the Virtual Machines using the Backup Exec Remote Agent for Windows (RAWS). See Related Documents for instructions on how to install (RAWS) inside the Virtual Machines..
 
Resolution:
 
The above mentioned issue has now been fixed in Backup Exec 2010. 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)