Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup Exec 2010 backup of Hyper-V Virtual Machine to USB RDX drive completes with V-79-57344-38721 - Failed to mount one or more virtual disk images: Error mounting disk(s): UNKNOWN_ERROR (0xe00084af).

Created: 24 Jun 2010 • Updated: 26 Jul 2010 | 1 comment
This issue has been solved. See solution.

I am trying to use Backup Exec 2010 to backup a Microsoft Hyper-V Virtual Machine to a local USB RDX drive configured as a Removable Backup-To-Disk folder on the Backup Exec 2010 server. The Backup Exec 2010 server is running Windows Server 2008 R2 and also acts as the Hyper-V Server.  I have one guest virtual machine running Windows Server 2008 R2 on this backup Exec 2010 server.  The backup works just fine when I write to a regular Backup-To-Disk folder.  When I try to backup using the Remvable backup-To-Disk folder, I keep getting the following error that the virtual disk cannot be mounted:

===============================================================================

Backup- VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL

V-79-57344-38721 - Failed to mount one or more virtual disk images:

Error mounting disk(s): UNKNOWN_ERROR (0xe00084af).

================================================================================

I found the following 2 entries on the support forum, but they did not help for the reasons listed:

http://seer.entsupport.symantec.com/docs/355319.htm - I don't see the "Not Found" error in the debug log http://seer.entsupport.symantec.com/docs/350675.htm - I was able to mount and online the VM

Looking through the Debug Monitor, this is one of the few places where an error is listed.  I don't see any of the failed mount commands that I see in other posts with a similar error ( V-79-57344-38721  ).  I did check the HCL (Hardware Compatibility List) for BE2010 and it says that "Note: Granular Restore Technology (GRT) is not supported on Removable B2D devices if the backup spans media".  My backups are not spanning media, so this should not be the reason the backups don't work.  I am also ataching the complete Debug Monitor log to see if there is something else I am missing.  Any help is appreciated.

Thanks,
Paul

BEREMOTE: [06/23/10 15:53:12] [3240]     FS_BlowOutMachine: entered -->VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL<--
BEREMOTE: [06/23/10 15:53:12] [3240]     ******************************************************************************
BEREMOTE: [06/23/10 15:53:12] [3240]     Initial DLE Tree
BEREMOTE: [06/23/10 15:53:12] [3240]     -->C:<-- address 0x000000D86D80 type 5 subtype 0 feature bits 0x0B111579 0x00000000 dataId 14 bedsId 14 bedsVer 3
BEREMOTE: [06/23/10 15:53:12] [3240]     -->D:<-- address 0x000000D86750 type 5 subtype 0 feature bits 0x0B111579 0x00000000 dataId 14 bedsId 14 bedsVer 3
BEREMOTE: [06/23/10 15:53:12] [3240]     -->E:<-- address 0x000000D85D00 type 5 subtype 0 feature bits 0x0B111579 0x00000000 dataId 14 bedsId 14 bedsVer 3
BEREMOTE: [06/23/10 15:53:12] [3240]     -->F:<-- address 0x000000D86330 type 5 subtype 0 feature bits 0x00100135 0x00000000 dataId 14 bedsId 14 bedsVer 3
BEREMOTE: [06/23/10 15:53:12] [3240]     -->Microsoft Terminal Services<-- address 0x000000D9A850 type 7 subtype 0 feature bits 0x00000082 0x00000000 dataId 0 bedsId 0 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     -->Microsoft Windows Network<-- address 0x000000D9A9F0 type 7 subtype 0 feature bits 0x00000082 0x00000000 dataId 0 bedsId 0 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     -->VICTOR\BKUPEXEC<-- address 0x00000522A440 type 16 subtype 1 feature bits 0x0022C000 0x00001004 dataId 43 bedsId 43 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     -->Shadow?Copy?Components<-- address 0x000000DA0BE0 type 18 subtype 0 feature bits 0x03020109 0x00000000 dataId 47 bedsId 47 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     -->System?State<-- address 0x000000D96B30 type 30 subtype 0 feature bits 0x00000000 0x00000000 dataId 59 bedsId 59 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     -->VRTSRV::\\VICTOR.lablan.net\Microsoft?Hyper-V<-- address 0x000000D96F80 type 38 subtype 4 feature bits 0x00020002 0x00100000 dataId 75 bedsId 73 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     --><-- address 0x000000D8CE40 type 43 subtype 0 feature bits 0x0002C000 0x00000000 dataId 79 bedsId 79 bedsVer 0
BEREMOTE: [06/23/10 15:53:12] [3240]     End of List
BEREMOTE: [06/23/10 15:53:12] [3240]     FS_ResolveDevName: [VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL]
BEREMOTE: [06/23/10 15:53:12] [3240]     MB2-Resolve returned 1
BEREMOTE: [06/23/10 15:53:12] [3240]     Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [06/23/10 15:53:12] [3240]     ADC_ResolveDeviceName: pid = 1068, checking VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL
BEREMOTE: [06/23/10 15:53:12] [3240]     ApplyRegExp(): Invalid input (VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL). Parsing Failed.
BEREMOTE: [06/23/10 15:53:12] [3240]     GoodEvName(): Invalid EV device (VRTSRV::\\VICTOR.lablan.net\Hyper-V?Virtual?Machine\W2K8 USB RDX DELL).
BEREMOTE: [06/23/10 15:53:12] [3240]     FS_BlowOutMachine: FS_ResolveDevName returns -->VICTOR.lablan.net<-- as the machineName
BEREMOTE: [06/23/10 15:53:12] [3240]     FS_BlowOutMachine: processing as local machine
BEREMOTE: [06/23/10 15:53:12] [3240]     FS_BlowOutMachine: failed to find machine DLE in DLE tree, attempting DLE create
BEREMOTE: [06/23/10 15:53:12] [3240]     FS_CreateTempDLE
BEREMOTE: [06/23/10 15:53:12] [3240]     11 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     12 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     Notes Agent:CLNFileSystem::CreateTempDLE
BEREMOTE: [06/23/10 15:53:12] [3240]     Notes Agent:CLNFileSystem::CreateTempDLE Exiting[-536805853]
BEREMOTE: [06/23/10 15:53:12] [3240]     13 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     RMAN_CreateTempDLE: Function called
BEREMOTE: [06/23/10 15:53:12] [3240]     14 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     16 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     17 = 0xE000FE23
BEREMOTE: [06/23/10 15:53:12] [3240]     18 = 0x00000001
BEREMOTE: [06/23/10 15:53:12] [3240]     19 = 0xE00084AF
BEREMOTE: [06/23/10 15:53:12] [3240]     20 = 0xE00084AF
BEREMOTE: [06/23/10 15:53:12] [3240]     21 = 0xE00084AF
BEREMOTE: [06/23/10 15:53:12] [3240]     OFF_HOST_FS::OpenOHMetadataFile( ): error Opening the file (C:\Program Files\Symantec\Backup Exec\Data\)
BEREMOTE: [06/23/10 15:53:12] [3240]     OFF_HOST_FS::GetDLEDetailsFromMDSrc() Status E_FS_OFF_HOST_DATA_CREATE_ERROR (E0000301) Opening the metadata source
BEREMOTE: [06/23/10 15:53:12] [3240]     OFF_HOST_FS::CreateTempDLE( ) Status E_FS_OFF_HOST_DATA_CREATE_ERROR (E0000301) creating Dle when creating temp Dle for device \\VICTOR.lablan.net
BEREMOTE: [06/23/10 15:53:12] [3240]     23 = 0xE0000301
BEREMOTE: [06/23/10 15:53:12] [3240]     26 = 0x00000001

Comments 1 CommentJump to latest comment

PWBratach's picture

I contacted Symantec support and they suggested I apply the patch listed below and amazingly it works!  Now I am able to backup my VM (both the complete VM and even the individual files) and restore  either the complete VM or individual files to the VM.

64-bit

http://seer.entsupport.symantec.com/docs/355984.htm

32-bit

http://seer.entsupport.symantec.com/docs/355983.htm

Paul

SOLUTION