Forum Discussion

jayaram226's avatar
jayaram226
Level 4
12 years ago

Netbackup Master - Media

Hola All,

 

I wil explain the issue first, because I am not sure of what's happening in this particluar client.

I have a backup failure with 58 error.

I do know, it is because of connectivity.

But, in this case I have complete connectivity from either end,

Ping worked.

Telnet worked.

I Tried,

bpclntcmd also resolves.

Is there any other possibility for this failure to occur..??

Sorry if the question is too basic..but it kills me to see this error and do nothing about it.

 

 

Thanks and Regards,

.Jayaram Balasubramanian.

 

  • Did you do bpclntcmd with '-ip' and '-hn' from server and from client?
    Which port did you test telnet on? 
    Did you test from server to client as well as from client to server?

    Problem is normally with port connectivity or with reverse lookup from client side.

    Test with bptestbpcd - it tests forward and reverse lookup as well as port connectivity.

    1. Create bpcd log folder on the client

    2. Run bptestbpcd from the server:
    bptestbpcd -client <client-name> -verbose -debug

    Check output for errors.

    Check bpcd log on the client for errors - check if client can resolve server's IP address to hostname.
    Check if this hostname can be resolved to valid SERVER entry.
    If not, update DNS or client's hosts file.

  • I tried bpclntcmd with hostname, -hn and it resolved.

    I tested for the port 13782.

     

    I tested the connection from either side and it worked.

     

    Will check the bptest bpcd and update..

     

    thanks !

  • As from NBU 6.0, NBU uses vnetd (13724) for connection in both directions.

    As from NBU 7.0.1, NBU uses PBX (1556) in both directions. If PBX connectivity fails, NBU will fail back to vnetd.

     

    I tried bpclntcmd with hostname, -hn and it resolved.

    Important to check reverse lookup on client with '-ip'.
    The client needs to resolve server's incoming IP address to valid SERVER name as explained in my post above.

     

  • Port connectivity was okay..

    Master was Netbackup 7.5 and Client was Netbackup 6.0 MP4.

    Had an issue in bp.conf entry, Master server name was mentioned in last line.

    Mentioned master server name in first line, and restarted the job.

     

    Will update.

     

     

    Thanks and Regards,

    .Jayaram Balasubramanian.

     

  • Please take note that SERVER name in bp.conf must match exactly the name that is resolved by the client (bpclntcmd -ip <server-IP-address>).

    You will find evidence of name resolution in client's bpcd log.

     

    *** EDIT ***

    Any possibility that you can upgrade client's NBU software?

    Support for NBU 6.x ended in Oct 2012.

  • Hi,

     

    Similar issue in another server, and in this case, I tried bptestbpcd...however no response for a long time...and please let me know how to setup the bpcd logs.

     

     

     

    Thanks and Regards,

    .Jayaram Balasubramanian.

  • Create bpcd folder under ....netbackup/logs folder. Connection attempts will be recorded in log file in this folder. If it seems like bptestbpcd is hanging, it is actually waiting for the client to respond. If no response, it will wait for duration of Client Connect Timeout. Remember to add -verbose and -debug. If Client Connect Timeout is high, reduce it to 300 on the server where you are testing from. Wait until command returns with failure message. Check if log is created in client's bpcd log.
  • Port 13724, was not open from Master server as well as Client, Have requested my Communication team to open the ports.

    Waiting for their response.

     

    Will update.

     

     

    Thanks and Regards,

    .Jayaram Balasubramanian.