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

Backup Exev 2010 R3 GRT Failed to mount disk

Created: 23 Nov 2011 • Updated: 24 Nov 2011 | 3 comments
This issue has been solved. See solution.

Hi there,

We are trying to backup our VMs with GRT. When I use our ESX host as target the backup job completes without error but if I use our VCenter as target the job complete but failed to mount the virtual disk.

Our environment:

Media Server:

  • BE 2010 R3
  • OS - Win 2008 R2

ESX Host:

  • ESX 4.1 Update 2

VCenter Server:

  • VCenter Server 4.1 Update 2
  • OS- Win 2008 R2

Debug log from BE Media Server:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

BEREMOTE: [11/24/11 15:05:33] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVimResolveHostName: Resolving IP address for hostname 192.168.123.39.
BEREMOTE: [11/24/11 15:05:33] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVimResolveHostName: Resolved to 192.168.123.39.
BEREMOTE: [11/24/11 15:05:33] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: VixDiskLibVimLogin
BENGINE:  [11/24/11 15:05:33] [0412]     [server]             - Updating status for: 'Server2-Server2-FullBackUptoDisk' (0x1 0x10)
BENGINE:  [11/24/11 15:05:33] [0412]     [server]             - Status for: 'Server2-Server2-FullBackUptoDisk' updated
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: TicketFindVMByInvPath: vmxPath = -Host -
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Warn: VixDiskLibVim: TicketFindVMCb failure - VixError = 4000.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: VixDiskLibVimLogout
BEREMOTE: [11/24/11 15:05:34] [4556]     [mounter]            - VMDKRemoteImage::Open()  Could not open the disk '[vmshared8] server2/server2.vmdk' Error Text: 'The virtual machine cannot be found' Error: '4000'
BEREMOTE: [11/24/11 15:05:34] [4556]     [engidrapi]          - CDiskLayoutImplementation::DisableAutoMount: AUTOMOUNT is already disabled
BEREMOTE: [11/24/11 15:05:34] [4556]     [mounter]            - VMwareVirtualSystem::MountDisksUsingVddk() - Enter
BEREMOTE: [11/24/11 15:05:34] [4556]     [fsys\shared]        - vddkWrapper::createVDDkIniFile() using the ini file C:\Program Files\Symantec\Backup Exec\Data\vddk-0.ini for initialization
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Warn: Refusing to set temp directory second time 'C:\Users\ADMINI~1.DSH\AppData\Local\Temp\vmware-administrator-500' to 'C:\Users\ADMINI~1.DSH\AppData\Local\Temp\vmware-administrator-500'.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Warn: Mntapi_Init: Unable to set the driver name, volume mounting may not succeed.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: Mntapi_Init Asked - 1.0 Served - 1.0 was successful,TempDirectory: C:\Users\ADMINI~1.DSH\AppData\Local\Temp\vmware-administrator-500.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVimResolveHostName: Resolving IP address for hostname 192.168.123.39.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVimResolveHostName: Resolved to 192.168.123.39.
BEREMOTE: [11/24/11 15:05:34] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: VixDiskLibVimLogin
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: TicketFindVMByInvPath: vmxPath = -Host -
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Warn: VixDiskLibVim: TicketFindVMCb failure - VixError = 4000.
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Log: VixDiskLibVim: VixDiskLibVimLogout
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk [vmshared8] server2/server2.vmdk, openflags = 4 - VixError 0xfa0.
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Warn: DiskLibProvider_GetDisk: Open failed - index 0.
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Log: Error 2 opening disk 0.
BEREMOTE: [11/24/11 15:05:36] [1884]     [fsys\shared]        - VDDK-Log: VixMntapi: Operation failed with system error: The system cannot find the file specified.

     (2), translated to 4
BEREMOTE: [11/24/11 15:05:36] [4556]     [mounter]            - VMDKRemoteImage::mountDisks()  Could not open the diskset. Error Text: 'A file was not found' Error: '4'
BEREMOTE: [11/24/11 15:05:36] [4556]     [engidrapi]          - CDiskLayoutImplementation::SetAutoMount: Disabling AUTOMOUNT
BEREMOTE: [11/24/11 15:05:36] [4556]     [mounter]            - VDiskMounter::MountAllDisks:failed VirtualSystem::Initialize()
BEREMOTE: [11/24/11 15:05:36] [4556]     [mounter]            - Error mounting disks (0xe0009741)
BEREMOTE: [11/24/11 15:05:36] [4556]     [fsys\ntfs\img_pdi]  + img_pdi_attach.cpp (551):
BEREMOTE: [11/24/11 15:05:36] [4556]     [fsys\ntfs\img_pdi]  | Error mounting disk(s): E_IMG_FS_FAILED_TO_MOUNT_VIRTUAL_DISK (0xe0009741).
BEREMOTE: [11/24/11 15:05:36] [4556]     [mounter]            - CommonMounter::~CommonMounter called
BEREMOTE: [11/24/11 15:05:51] [4556]     | Exit point of IMG_PDI_FSYS::AttachToDLE hit: (0x00000000)

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Any ideas how to solve this?

Comments 3 CommentsJump to latest comment

pkh's picture

You have asked this same question question yesterday and there was only one reply.  If your problem is urgent, I would suggest that you open a formal support case with Symantec.

sbora's picture

This issue is caused by having the special character & in the password for the account used to backup the virtual machines or in the name of the virtual machine directory or name.

http://www.symantec.com/docs/TECH129185

SOLUTION
nhoj_O1's picture

After spending couple of hours troubleshooting on our problem we were able to solved it. It turns out that we put our ESX Host under a folder with a "&" character in it. That's the reason why BE can't mount the virtual disk.

Thanks everyone for the help.

---<<== nhoj_O1 ==>>---