cancel
Showing results for 
Search instead for 
Did you mean: 

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.

Tags (2)
2 Solutions

Accepted Solutions
Accepted Solution!

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

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.

View solution in original post

Accepted Solution!

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

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.

View solution in original post

Tags (2)
12 Replies

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

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

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

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

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

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)

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

Run this command on both master/media and client and see if it helps.

bpclntcmd -reverse_name_lookup prohibited

This will disable reverse name lookup verfication (IP to name).

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

Thank you!

If I run this command on Master will this prevent the backups that are configured with the IP address in NBU?

Accepted Solution!

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

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.

View solution in original post

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

As SDO say, use of IP adresses is not supported, but it may work.

bptestbpcd -client work from the client to the maste/media as well, saves you some typing.

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

One thing more, from where do you run the console. From the master server or from a terminal server not part of the Netbackup domain ?

If run from a terminal server, the name of the terminal server need to be a the server list as well. It's because the java console connect direct to the client, command are not passing the master server first.

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

@tyadagiri 

A Windows Client does not have bp.conf. 
SERVER entries are in the registry. 

Easiest way to see why you are seeing Status 59 is to create bpcd log folder on the client (under ....\Veritas\netbackup\logs).

Try the connection again, then check the log file in bpcd folder.
You will see connection request from an IP address, followed by client's attempt to resolve the IP address to a hostname, that is then compared with the SERVER entries in the registry. 

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

I am running the Console from my Desktop machine that is within the Domain.

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

Then your desktop should be listed in the Netbackup client server list (the server list can also be found in the Netbackup BAR gui).

 

Accepted Solution!

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

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.

View solution in original post

Tags (2)