Netbackup Master server still attempting to contact decommissioned clients

Question

I am currently running Netbackup Server 7.7.2 on RedHat Linux and&nbsp;a mix of&nbsp;media servers (HP-UX, AIX, RedHat).&nbsp;

Several years ago many clients were taken off the list of servers to backup.&nbsp; They were/are running Out-dated operating systems; hence had Netbackup client 4, 5, or 6 installed.&nbsp; I am monitoring output from the Master server and noticed these client servers are still attempted to be contacted over a range of ports.&nbsp; I added the clients to a test policy and deleted them.&nbsp; No longer is the range of ports being contacted, only a single port 13782.

I have verified the clients are not in a policy.&nbsp; I am finding some of the clients in /db/client/&lt;client&gt; and in /db/images/&lt;client&gt;.&nbsp; I understand images are past backups and do not wish to touch that directory.

These clients may no longer exist and I would like my master server to stop attempting to contact them on port 13782.&nbsp; My thought is that during upgrade processes through the years did not update the database tables properly.&nbsp;

Has anyone else run into this?&nbsp; Any idea how to fix.

nbutech · Accepted Answer

Run the command to identify the clients

bpplclients -allunique -l &gt; output.txt

&nbsp;

If they are not listed anywhere and you see it in logs you might then gather logs and send to Veritas support for the sql script to remove those client

revarooo · Answer

Shouldn't need the clients that are deleted in netbackup/db/clients directory.
You can delete those or move them.
Obviously do NOT delete anything from db/images

areznik · Answer

If you go to the Clients screen in the GUI, are they still there?&nbsp;

Run this command for a few of the clients and see if you get anything back:&nbsp;

nbemmcmd -listhosts -display_server -machinetype client -machinename &lt;clientname&gt;

&nbsp;

sdo · Answer

Or perhaps keep the Client Attributes, i.e. keep the contents of /db/client, and "offline" the no longer existing client name, and maybe this will cease the reach out?

How often was the reach out to old client names? &nbsp;Hourly? &nbsp;Every 12 hours? &nbsp;Every 24 hours? &nbsp;Maybe image cleanup is causing something deep inside NetBackup to attempt to resolve the name.

In fact, this rings a bell...

...I think you may need to create a load of dummy hosts file name entries like:

192.168.200.200 &nbsp;oldclientname

...and point the many old client names at an unused IP address... and I think this will stop the errors when internal NetBackup tries to resolve a name to an address when trundelling over the /db/images set.

gdyr_mpd · Answer

Result from command posted

&nbsp;

NBEMMCMD, Version: 7.7.2
	The function returned the following failure status:
	invalid host name (136)
	Command did not complete successfully.
	&nbsp;

gdyr_mpd · Answer

I used the Java GUI to remove the items from the clients&nbsp;directory, just incase additional items are being performed in the background.

Netbackup Management -&gt; Host Properties -&gt; Master Servers -&gt; (double click) &lt;server&gt;

Select the Client Properties and removed the old visible hosts from the list.

&nbsp;

Will see in the next 24 hours if an attempt is made to contact the client and post the result.

Forum Discussion

Netbackup Master server still attempting to contact decommissioned clients

12 Replies

Related Content

Decommissioning a NetBackup media server

Decommission Enterprise vault server

Decommissioning Enterprise Vault

netbackup retry attempt

Decommission a client from NetBackup

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date