vCenter Backup Failing

[Ben_Blackmore1]

Hi,

We're migrating from Backup Exec 12.5 to Backup Exec 2010 R3. I've migrated a number of jobs across, all of which work except the vCenter backup. The job fails and errors with the following message:

V-79-57344-38277 - Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: One or more required subsystems failed to initialize

However, I can't find any information in the support KBs on this 'One or more required subsystems failed to initialize' errors.

Can anyone help?

We're running Windows 2008 R2, vCenter 4.1, BE 2010 R2, SAN is a Dell/EMC DAE with fibre disks.

Any help appreciated!

Ben

[Dev_T]

 Hi,

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

[CraigV]

..have you tried to recreate the job and see if you get the same error?

[Ben_Blackmore1]

Hi,

Thanks for the replies.

I did read http://www.symantec.com/business/support/index?page=content&id=TECH129572 but the user account is domain admin, and ESX root admin. The error does not mention 'You do not have access rights to this file.', its the error 'One or more required subsystems failed to initialize' that threw me.

I tried to re-create the selection list, and the job, but it doesn't seem to help!

Ben

[ZeRoC00L]

What is the transport method you are trying to use ?
If it is SAN mode, your Backup Exec server needs access to the LUNs.
Try to use NBD (network) mode to test a backup.

[Ben_Blackmore1]

Hi,

The BE2010 server is attached directly to the SAN storage, but just to check I changed the job to use NBD, however this results in exactly the same error. I have deleted the selection list, policy & job again, and re-created from scratch, again, same error.

[ZeRoC00L]

Ben,

You can check this article:

http://www.symantec.com/business/support/index?page=content&id=TECH135858

[Colin_Weaver · Accepted solution]

If any of the following files exists in Progarm Files\Symantec\Backup Exec

Then remove/rename/move them to another folder for safety. Then restart the Backup Exec services and test your VMware Backup

vstor2-mntapi10.sys
vmware-vdiskmanager.exe
vmomi.dll
VmdkFilter.dll
vmacore.dll
vixMntapi.dll
vixDiskLibVim.dll
vixDiskLib.dll
gvmomi.dll

Note I would be interested in confirmation if this works for you.

[Ben_Blackmore1]

Hi,

Sorry for my delay in replying.

I have moved the files you listed above, and restarted the backup exec server, then tried to re-run the backup job, however, its still failing with the error.

VixDiskLib_Open() reported the error: One or more required subsystems failed to initialize
V-79-57344-38277 - Unable to open a disk of the virtual machine.

I've also read the article http://www.symantec.com/business/support/index?page=content&id=TECH135858 however, I'm not getting the "You do not have access rights to this file." error, and this isn't just happening on Windows 2008/2008 R2, but on Windows 2000 & 2003 as well.

This is getting quite urgent now, the new backup server is due to go live next week, but we can't currently backup our VM infrastructure.

Any help much appreciated

Ben
 

[Ben_Blackmore1]

Have also just removed the virtual infrastructure license key, rebooted, and re-added it again, then tried to perform the backup, but again, it failed.

[Ben_Blackmore1]

Anyone have any further thoughts on how to resolve this issue?

I have to have the new server in place and working by Friday.

[ZeRoC00L]

1. Does this error occur with all your VM's ?

2. Can you create quiesced snapshots manually ?

3. Did you contact Symantec Support about this issue ?

[Ben_Blackmore1]

1. Does this error occur with all your VM's ?

Yes, from the new backup server, trying to perform a backup of any of the VMs causes this error.

2. Can you create quiesced snapshots manually ?

We can perform quiesced backups from the older BE v12.5 server, which works fine, so this appears to be an issue between the new BE v2010 R3 server, and vCenter.

3. Did you contact Symantec Support about this issue ?

That's my next step today, I was hoping to get a quick solution from the forum, but will contact Symantec support once I've found our support contract details.

[Ben_Blackmore1]

After opening a support case with Symantec we found the server wasn't connecting to the storage group on the SAN correctly, so we opened a case with EMC-Dell and they connected in, and fixed the issue, so the server is now seeing the SAN disks correctly.

By all accounts, this should now be able to backup, but when running a test backup, the same 'Unable to open a disk of the virtual machine.' error is coming up. I'm trying to find some details on configuring vCenter 4.1 with Backup Exec 2010 R3 and found the following thread: http://communities.vmware.com/message/1481985 which I have checked through, and I think we have done everything correctly.

Can anyone suggest anything that I might be missing?

[Ben_Blackmore1]

Re-opened our support case with Symantec, but the Symantec techie wasn't sure how to proceed further, so is escalating it to the next level.

The following errors were in the debug log file:

[4232] 07/13/11 14:45:36 [ndmp\ndmpsrvr]      - Going to perform pre backup dbcc.
[4232] 07/13/11 14:45:36 [fsys\vmvcb]         - VM_VCBPROXY_FS::GetSelectedObjInfo() Informational status FS_AT_ROOT (E000FE0A)
[4232] 07/13/11 14:45:38 [ndmp\loops]         - Windows Server 2003 (or higher) detected. No S2LP mapping required.
[4232] 07/13/11 14:45:38 [fsys\vmvcb]         - VM_VCBPROXY_FS::GetSelectedObjInfo() Informational status FS_AT_ROOT (E000FE0A)
[4232] 07/13/11 14:45:38 [fsys\vmvcb]         - VM_VCBPROXY_FS::GetSelectedObjInfo() Informational status FS_AT_ROOT (E000FE0A)
[4232] 07/13/11 14:45:38 [fsys\vmvcb]         - VM_VCBPROXY_FS::CloseObj() Could not delete the VMDKFSMAP file (0x2)
[4232] 07/13/11 14:45:38 [fsys\vmvcb]         - VM_VCBPROXY_FS::OpenObj() Could not open the disk '[High Perf #3] srvav01_1/srvav01.vmdk' DiskCompatibility: 'dependent' DiskMode 'persistent'  Error Text: 'One or more required subsystems failed to initialize' Error: '16053'
[4232] 07/13/11 14:45:38 [ndmp\loops]         - LP_ENV::MsgError: error 0xe0009585 processing object srvav01\srvav01.vmdk
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - TF xfer time = 1 seconds.
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - WRITE:  tpreceive_fail_count = 1
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - WRITE:  waiting_on_buffers_count = 0
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - WRITE:  buffers_written_count = 1
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - TF_CloseSet()
[4232] 07/13/11 14:45:38 [ndmp\tpfmt]         - FreeFormatEnv( cur_fmt=0 )
[4232] 07/13/11 14:45:38 [fsys\shared]        - Detach from VMVCB::\\srv03\VCGuestVm\(DC)OurSite(DC)\vm\srvav01
[4232] 07/13/11 14:45:38 [fsys\vmvcb]         - VM_VCBPROXY_FS::DisconnectVixDiskLib() Could not cleanup vixdisklib connection from the server 'srv03' VM 'srvav01'. Error Text: 'The operation is not supported' Error: '6' Cleanedup: '0' Remaining '0'
[4232] 07/13/11 14:45:38 [fsys\brfs]          - brUtil::brUtil Destructor
[4232] 07/13/11 14:45:38 [fsys\shared]        - vddkConnectToVMWareServer() GD: vmcConnect OK, vddkSession = 0000000004E19250
[4232] 07/13/11 14:45:38 [fsys\shared]        - vddkSetManagedTimeouts(): OK, vmwaretools LogLevel set to 1
[4232] 07/13/11 14:45:38 [fsys\shared]        - vddkConnectToVMWareServer() GD: status = 0X0
[4232] 07/13/11 14:45:38 [ndmp\loops]         - LP_ENV::removeVMWareSnapshot(): removing the snapshot 'SYMC-FULL 13-07-2011 14:45' for the VM '(DC)OurSite(DC)\vm\srvav01'

[JohnJohn]

Hi Ben,

After i upgrade BE 2010 R2 to BE 2010 R3 i have the same error of you.

Do you have solution ?

Thanks.

[Colin_Weaver]

Tech Support currently believe that Ben's issue after he fixed the SAN problem is now solved by making sure that none of the individual files listed directly in the ..\Symantec\Backup Exec\VMWare\VixDiskLib\bin folder are present in the ..\Symantec\Backup Exec folder.

However please note that this advice is specific to where the 16053 error code has been seen in debug or job logs.

Also note that you will have to stop the Backup Exec services to remove some of the files from ..\Symantec\Backup Exec and we obviously recommend moving them to a temp folder instead of a complete delete just in case you need to undo the removal.

[JohnJohn]

Hi Team Support,

I moved the files as to indicate higher in the post and it in resolved my problem ..

Thank you for you're reply.