Forum Discussion

tyadagiri's avatar
tyadagiri
Level 4
6 years ago
Solved

If the RDP is not functioning on a server will that impact NBU tape backup?

We have a Windows Client that we are unable to connect to that machine using RDP. Will this cause the NBU backup to fail?

This was due to the Microsoft bug fix for RDP needs to be installed and this server is critical which they can't reboot for the fix to be installed.

We got the error code as 59: Unable to connect to the client.

From the NBU Java console, I couldn't connect to the host properties. However, the services are up and running on the client machine.

  • sdo's avatar
    sdo
    6 years ago

    You need to logon to each of master and media and client and issue fifteen commands on each - to reveal if names are ok - and yes, you do need to issue each of those name check commands twice in order to rule out looping / double entries in DNS.

    The fifteen commands to issue on each of master, media and client are:

    nslookup mastername
    nslookup mastername
    nslookup medianame
    nslookup medianame
    nslookup clientname
    nslookup clientname

    bpclntcmd -clear_host_cache
    bpclntcmd -clear_host_cache

    bpclntcmd -hn mastername
    bpclntcmd -hn mastername
    bpclntcmd -hn medianame
    bpclntcmd -hn medianame
    bpclntcmd -hn clientname
    bpclntcmd -hn clientname

    UNIX:
    cat /usr/openv/netbackup/bp.conf
    ...and look at "client_name = " entry... is it correct ?
    ...and look at "server =" entries... are they correct ?
    (N.B: on all three hosts (master, media, client) the first "server =" entry must always be the master server name.
    On the client, the client needs to also have a server entry for the media server name.

    WINDOWS:
    reg query "hklm\software\veritas\netbackup\currentversion\config"
    ...and the checks are the same as for Unix.


    TOP TIP: It really really is best these days to use FQHN for any and all names, at all times, in all areas of NetBackup.

    TOP TIP: Also, use of underscores in names is not supported. And best to use lowercase at all times, to make your life simpler.

    TOP TIP:  Never use IP addresses as client names.

  • Finally, this is resolved as the Root cause for this issue is moving/decomm of DNS servers. Did nslookup and was unable to resolve the Master/Media servers. Ran bpclntcmd -pn the o/p of this command is empty. So we have added the entries of Master and Media servers in the Clients host file and triggered the backup which was successful.

12 Replies

  • Netbackup does not rely on RDP.

    Status 59 means the server list of the Netbackup clint isn't corretly configured. When a Netbackup master or media server contact a Netbackup client, the client validate the server is allowed to make the connection. So when e.g. deploying a new media server, the server list on clients need to be updated to include new media server, else all backups will fail that utilize thew new media server, but proceed on the existing servers.

    Please see this tech note to resolve the issue : https://www.veritas.com/content/support/en_US/article.100022203.html

    • tyadagiri's avatar
      tyadagiri
      Level 4

      Thank you for your response!

      I see that all the media servers are there in the bp.conf list in the client-server. All the NBU services are UP on the client machine. But still, I am unable to connect to the host from the host properties in the NBU Java console. bptest command is also successful

      • tyadagiri's avatar
        tyadagiri
        Level 4

        Here is the error from the Job log:

        Aug 7, 2019 8:25:00 AM - Info bpbrm (pid=16337) 	status: FAILED, (43) CONNECT_RESET; system: (104) Connection reset by peer; FROM 0.0.0.0 TO client.domain.com 10.xxx.xx.115 bpcd VIA pbx
        Aug 7, 2019 8:25:00 AM - Info bpbrm (pid=16337) 	status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO client.domain.com 10.xxx.xx.115 bpcd VIA vnetd
        Aug 7, 2019 8:25:00 AM - Info bpbrm (pid=16337) 	status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO client.domain.com 10.xxx.xx.115 bpcd
        Aug 7, 2019 8:25:00 AM - Error bpbrm (pid=16337) cannot connect to client.domain.com, Operation now in progress (115)