Failed to get VM Server Info List: cannot connect on socket. (25)

Problem

Using a Windows NetBackup Administration Console to manually Browse and select Virtual Machine in a policy fails with a console dialog box:

Failed to get VM Server Info List:

cannot connect on socket. (25)

Error

cannot connect on socket. (25)

NBSL - (OID 132):

6/14/2011 12:26:36.015 nbsl 132 PID:4424 TID:5104 [PolicyQueryFacetImpl::getVMVirtualServerInfoList()#10] No. of vmVirtualServers:0(../PolicyQueryFacetImpl.cpp:678)
6/14/2011 12:26:36.015 nbsl 132 PID:4424 TID:5104 [PolicyQueryFacetImpl::getVMVirtualServerInfoList()#10] Overriding return code of getVMVirtualServerInfoSeq:-1(../PolicyQueryFacetImpl.cpp:682)
6/14/2011 12:26:36.015 nbsl 132 PID:4424 TID:5104 [NBUErrorTranslator::getErrorDetails()] NB error code: 25 NB localized Error text: cannot connect on socket(../NBUErrorTranslator.cpp:47)
6/14/2011 12:26:36.015 nbsl 132 PID:4424 TID:5104 [ExceptionManager::fillExceptionObject()] Error:PolicyQueryFacetImpl::getVMVirtualServerInfoList()#10:../PolicyQueryFacetImpl.cpp(685): errNo:25 localizedStr:cannot connect on socket additionalStr:(../ExceptionManager.cpp:94)
 

NBPROXY:

12:26:36.015 [5844.3608] <2> read_guest_tree: server type has to be ESX server or vApp
12:26:36.015 [5844.3608] <2> dblibFacadeImpl::getAllVMs(): bpcr_get_virtual_names_rqst returned:-1(dblibFacadeImpl.cpp:3119)
12:26:36.015 [5844.3608] <2> dblibFacadeImpl::getAllVMs(): bpcr_disconnect_rqst returns -1(dblibFacadeImpl.cpp:3125)
12:26:36.015 [5844.3608] <2> dblibFacadeImpl::getVMVirtualServerInfoSeq(): getAllVMs call failed. Return code:-1(dblibFacadeImpl.cpp:3264)
 

BPCD:

12:26:35.765 [1468.4860] <2> run_VMutil_cmd: cmd = C:\Program Files\Veritas\NetBackup\bin\bpVMutil.exe
12:26:35.765 [1468.4860] <2> createProcessWithOutput: CreateProcess of >"C:\Program Files\Veritas\NetBackup\bin\bpVMutil.exe" 0 "0" "_NONE_"<
12:26:36.015 [1468.4860] <2> run_VMutil_cmd: exit code for the process is h_errno = 0 - The operation completed successfully.
12:26:36.015 [1468.4860] <2> run_VMutil_cmd: reading temp file C:\WINDOWS\TEMP\VMutl-04640308068795796580000000000-a05580
12:26:36.015 [1468.4860] <2> put_string: cannot write data to network:  An established connection was aborted by the software in your host machine.
12:26:36.015 [1468.4860] <16> putLinesToSocket: couldn't put string
12:26:36.015 [1468.4860] <4> putLinesToSocket:    h_errno = 10053 - An established connection was aborted by the software in your host machine.
12:26:36.015 [1468.4860] <2> put_string: cannot write data to network:  An established connection was aborted by the software in your host machine.
12:26:36.015 [1468.4860] <16> run_VMutil_cmd: couldn't put string
12:26:36.015 [1468.4860] <4> run_VMutil_cmd:    h_errno = 10053 - An established connection was aborted by the software in your host machine.
12:26:36.015 [1468.4860] <2> process_requests: VMutil command failed: 24
 

BPVMUTIL:

12:26:35.905 [4640.5580]  read cache file = C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\vcbnames_virtual_center_server_Any
12:26:35.905 [4640.5580] read_guests returned 0 and 0
 

Cause

The virtual machine on the VMware ESX host did not properly register on the Virtual Center Server.

The virtual image(s) or (templates in this example) did not properly register when either copied or imported from a previous system.

1. Check file, \install_path\NetBackup\online_util\fi_cntl\vcbnames_virtual.center.server_Any file. (Note: The name of the virtual.center.server will vary per environment).

• In this error condition the vcbnames.virtual.center.server_Any file appears corrupt per example below:
  • DC: HRO_NBU_DC
  • DP: \(DC)HRO_NBU_DC(DC)
  • GUEST
  • HN: 10.10.10.10
  • DN: DAYTONA
  • VD: DAYTONA
  • MO: vm-150
  • VX: 1_LOCAL_DATA
  • DS: HROAPPS
  • DS: 1_LOCAL_DATA
  • DT: 1308071180
  • ID: 420af98b-8af2-9b16-0c43-16efcca89aca
  • IP: 10.66.16.24
  • PS: 2
  • FL: 4401
  • VE: vmx-07
  • GI: windows7Server64Guest
  • VP: vm
  • RP: Resources
  • NT: HRO_NBU_Lab_VLAN
  • CS: connected
  • EH: esx_server.domain.com

 

• Note the location of the EH: record above.
• When the virtual machine inventory is incomplete or incorrect the EH record does not appear in the correct location and the manual browse will fail.

 

• In this example the vcbnames_virtual_center_server_Any file contains the correct entries:
  • DC: HRO_NBU_DC
  • DP: \(DC)HRO_NBU_DC(DC)
  • EH: esx_server.domain.com
  • GUEST
  • HN: 10.10.10.10
  • DN: DAYTONA
  • VD: DAYTONA
  • MO: vm-150
  • VX: 1_LOCAL_DATA
  • DS: HROAPPS
  • DS: 1_LOCAL_DATA
  • DT: 1308071180
  • ID: 420af98b-8af2-9b16-0c43-16efcca89aca
  • IP: 10.10.10.10
  • PS: 2
  • FL: 4401
  • VE: vmx-07
  • GI: windows7Server64Guest
  • VP: vm
  • RP: Resources
  • NT: HRO_NBU_Lab_VLAN
  • CS: connected

 

Solution

The virtual images or templates in this example did not completely register on the ESX server.

Note: Intelligent policy (Select automatically through query) is not affected by this condition.

To correct the condition for manual selection:

1. Remove the templates out of ESX server inventory.
2. Add them back into the ESX server inventory.
3. Force a client refresh in the NetBackup Administration Console.

• From the NetBackup Administration Console:
  • Open the VMware policy, go to clients.
  • Virtual machine selection:
  • Select manually.
  • Click New
  • Then select Browse and select Virtual Machine
  • Note: Error 25 will occur.
  • Then select Refresh List.

After the successful refresh the client list is available to select a client for backup.

Note the examples of the vcbnames_virtual.center.server_Any file above.

 

Article URL