Forum Discussion

sxs's avatar
sxs
Level 2
7 years ago

Unable to connect to Netbackup host

Hello.

I have a 2012 Server with Netbackup 8 and a 2003 Server client with netbackup 7.6.1. When I try to create a policy and add the content to make the backup, the message always appears: "Unable to connect to Netbackup host"

I have tried almost everything.Add the corresponding entries in the different hosts files.Do a port scan.Test with different users.

...and nothing works.

Can someone help me?

7 Replies

  • sxs

    NBU master does not not normally try to connect to the client during policy creation.

    Can you show us screenshots of the steps that you are following to create the policy?

    Please also perform the following tests:

    From cmd on master and client:
    bpclntcmd -hn <remote-hostname>
    bpclntcmd -ip <remote-IP>

    On client: 
    bpclntcmd -pn

    Create bpcd log folder on the client, ensure NetBackup Client Service is running, then run this command on the master:
    bptestbpcd -client <client-name> -debug -verbose

    Show us output of commands as well as contents of bpcd log on the client.

    • Lowell_Palecek's avatar
      Lowell_Palecek
      Level 6

      If you browse to select backup items for the policy, NetBackup does connect to the client. There can be reasons on both sides of the connection attempt for failure. Try the test commands that Marianne gave you first. If you don't find the issue there, look at the bpcd log on the client to see how it may have responded to any commands from the server. On the server side, I think you will find evidence of the Java Console's attempts to browse the client in the nbsl log.

      • sxs's avatar
        sxs
        Level 2

        First of all thank you for your interest.

        The result of bptestbpcd command:

        09:28:02.450 [28864.31600] <2> bptestbpcd: VERBOSE = 009:28:32.857 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:28:33.747 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:03.748 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:04.764 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:14.748 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:44.749 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:46.765 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:29:55.765 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:30:25.766 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:30:29.781 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:30:36.766 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:31:06.767 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:31:14.782 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:31:17.767 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:31:38.767 [28864.31600] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10060 0x274c09:31:38.861 [28864.31600] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO xxxxxxxxx xxxxxxxxx bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO xxxxxxxxx xxxxxxxxx bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO xxxxxxxxx xxxxxxxxx bpcd09:31:38.861 [28864.31600] <8> vnet_connect_to_bpcd: [vnet_connect.c:305] connect_to_service() failed 18 0x1209:31:38.877 [28864.31600] <16> local_bpcr_connect: vnet_connect_to_bpcd(xxxxxxxxxx) failed: 1809:31:38.877 [28864.31600] <2> local_bpcr_connect: Can't connect to client xxxxxxxxxxx09:31:38.877 [28864.31600] <2> ConnectToBPCD: bpcd_connect_and_verify(xxxxxxxxx, xxxxxxxxx) failed: 25<16>bptestbpcd main: Function ConnectToBPCD(xxxxxxxxx) failed: 2509:31:38.939 [28864.31600] <16> bptestbpcd main: Function ConnectToBPCD(xxxxxxxxxxx) failed: 25<16>bptestbpcd main: cannot connect on socket09:31:39.002 [28864.31600] <16> bptestbpcd main: cannot connect on socket<2>bptestbpcd: cannot connect on socket09:31:39.064 [28864.31600] <2> bptestbpcd: cannot connect on socket<2>bptestbpcd: EXIT status = 2509:31:39.064 [28864.31600] <2> bptestbpcd: EXIT status = 25cannot connect on socket

         

         

  • you need a create a token file and copy the Token file to the agent while installation and paste the key.

    • Marianne's avatar
      Marianne
      Level 6

      RBuyyan wrote:

      you need a create a token file and copy the Token file to the agent while installation and paste the key.


      RBuyyan

      Really? 
      For a W2003 client running NBU 7.6.1? 

      Seems sxs has not been back since last post on 7 Feb...