Forum Discussion

madmax00's avatar
madmax00
Level 3
10 years ago

Connectivity problems (err 58)

I'm running NBU 7.6.0.2 on a Linux server and getting a 58 error while backing up a Windows 2000 client.

The client is accesible from master and media servers via ping, and telnet to bpcd and vnetd ports works as well. From client the ping to master and media servers works too.

The backups failed before with status 13 (I've an open case with support for that) and started fail with status 58 without any change in config.

From master:


 bptestbpcd -host onms -verbose -debug
14:15:44.976 [23631] <2> bptestbpcd: VERBOSE = 0
14:15:44.981 [23631] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:1998] VN_REQUEST_SERVICE_SOCKET 6 0x6
14:15:44.981 [23631] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2012] service nbrntd
14:15:46.088 [23631] <8> vnet_do_socks5_client_protocol: [vnet_connect.c:2426] bad status 2 0x2
14:15:46.088 [23631] <8> async_connect: [vnet_connect.c:1677] do_service failed 24 0x18
14:15:47.107 [23631] <2> vnet_version_connect: vnet_vnetd.c.1681: 0: Function failed: 24 0x00000018
14:15:47.107 [23631] <8> do_vnetd_service: [vnet_connect.c:1952] vnet_version_connect failed 24 0x18
14:15:47.107 [23631] <8> async_connect: [vnet_connect.c:1677] do_service failed 24 0x18
14:15:47.107 [23631] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (24) BAD_VERSION; system: (115) Operation now in progress; FROM 0.0.0.0 TO onms 172.31.192.91 bpcd VIA vnetd
14:15:47.107 [23631] <8> vnet_connect_to_bpcd: [vnet_connect.c:297] connect_to_service() failed 18 0x12
14:15:47.107 [23631] <2> local_bpcr_connect: Can't connect to client onms
14:15:47.107 [23631] <2> ConnectToBPCD: bpcd_connect_and_verify(onms, onms) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(onms) failed: 25
14:15:47.107 [23631] <16> bptestbpcd main: Function ConnectToBPCD(onms) failed: 25
<16>bptestbpcd main: cannot connect on socket
14:15:47.113 [23631] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
14:15:47.114 [23631] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
14:15:47.114 [23631] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

[root@backup00 bpcd]# bpclntcmd -hn onms
host onms: onms at 172.31.192.91
aliases:     onms     172.31.192.91
 

From client

C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -server backup00
host backup00: backup00 at 172.17.5.53 (0x350511ac)
checkhname: aliases:

C:\Program Files\VERITAS\NetBackup\bin>


Any ideas will be welcome!!

TIA

Agents
Backing Up
Backup and Recovery
Error messages
Linux
NetBackup
Troubleshooting
  • Marianne's avatar
    Marianne
    10 years ago
    Resilient network is for 7.x only. Not for 6.5. Not much can be done about problematic/archaic Windows 2000 TCP stack. Actually nothing, as you already know. All you can do is to enable checkpoints and keep on restarting failed backups. Please close off this discussion as your status 58 issue has been solved.

12 Replies

Sort By
Replies have been turned off for this discussion
  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

     NBU 7.6.0.2  ..... backing up a Windows 2000 client.

     

    Sorry, NOT supported.

     NBU 6.x was the last version to support W2000.

    If you really want to keep on trying, verify that NBU Client Service is running on Windows client and check with 'netstat -a' that bpcd and vnetd are LISTENING.

    Confirm that server and client can ping one another using hostnames.

    Test name lookup from client as follows:

    bpclntcmd -hn backup00

    bpclntcmd -ip 172.17.5.53 

    Check that Windows Firewall is disabled and verify that port 13724 (vnetd) is open in both directions between server and client.
    Use telnet to test connectivity on port 13724.

  • madmax00's avatar
    madmax00
    Level 3
    10 years ago

    Hi Marianne, thanks for answering. The NBU server is 7.0.6.2 and the old windows 2000 client is 5.1MP3... I know it's out of support but I cannot do anything about that... :-(

    The vnetd and bpcd ports are Listening in the client and both of them are accesibles via telnet from the master and media servers.

    I can ping one another using hostnames correctly

    Thats the result of bpclntcmd from client:

    C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -server backup00
    host backup00: backup00 at 172.17.5.53 (0x350511ac)
    checkhname: aliases:

    C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -ip 172.17.5.53
    checkhaddr: host   : backup00: backup00 at 172.17.5.53 (0x350511ac)
    checkhaddr: aliases:

    Thanks for your interest

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    10 years ago

    14:15:44.981 [23631] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2012] service nbrntd

    has me wondering if resilient network is configured for this client on the master. Don't think resilient network was introduced before one of the 7.X versions ...

    Also think the 0.0.0.0 address might be an issue, think there was an technote about it, albeit for 7.0

    If you havn't already create the bpcd and vnetd log folders on the onms client

    Have some times experienced that a repair of the netbackup client solved issues like this. But would recommend to only use it the second last option, the last being a total uninstall/install of the client with reboot between each step.

     

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    Client should be on 6.5 minimum. Forget about 5.1. 2 versions lower will not work. 5.1 needed some special config to make it connect on bpcd and connect back on vnetd. Without this special config it needed connect back on a whole range of ports. 6.5 will only use vnetd to connect and connect back. You are absolutely under no obligation to make anything work that is not supported. Not supported by Symantec, not by Microsoft.
  • watsons's avatar
    watsons
    Level 6
    10 years ago

    bptestbpcd needs to be successful for a backup to work fine. In your case, it failed with network error.

    You can spend time trying to update your NIC driver, or set your NIC duplex setting or troubleshoot the network side of problem. But is it worth the effort? 

    Could be the client is just too old for Netbackup to support, and at the end you still need to move the data somewhere else onto a supported machine to be backup. I would rather spend time convincing your management to "refresh/renew" that Win2000 client. Justification? Time & effort to enable backup, not to mention troubleshooting.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    Justification? Support. Support from Symantec. Support from Microsoft.
  • madmax00's avatar
    madmax00
    Level 3
    10 years ago

    Yes, resilient network was configured for the client, just for try...

  • madmax00's avatar
    madmax00
    Level 3
    10 years ago

    They use an application that only runs in Windows 2000, so they don't want to upgrade de OS version. We're planning to upgrade NBU to 6.5 to see if it help...

    Thanks

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    @madmax, Resilient client will not work with this old client. NBU 5.1 will also not work - too old. Your only hope to get it working is NBU 6.5 where vnetd is used for connection.
  • madmax00's avatar
    madmax00
    Level 3
    10 years ago

    The client upgrade is planned for next wednesday... let's see what happens next...