NBServerMigrator Update: Rename operation - communication failing between the media/client and the primary server after performing the rename

Article: 100071789
Last Published: 2024-11-11
Ratings: 0 0
Product(s): Appliances, NetBackup & Alta Data Protection

Problem

Communication issues between the media/client and the primary server after the rename.

Error Message

a) client hostname could not be found (48)

b) client backup EXIT STATUS 58: can't connect to client

Cause

N/A

Solution

1) Check if the new_name has been updated in the DNS or the hosts file of the media/cleint server.

2) Restart NetBackup services on the media/client server.

3) Clear the cache using the command:
For Linux:
/usr/openv/netbackup/bin/bpclntcmd -clear_host_cache

For Windows:
<install_path>\veritas\netbackup\bin\bpclntcmd -clear_host_cache

4) confirm that the communication is happening by running the command:
For Linux:
/usr/openv/netbackup/bin/admincmd/bptestbpcd -host <new_name> -verbose

For Windows:
<install_path>\veritas\netbackup\bin\admincmd\bptestbpcd -host <new_name> -verbose

Was this content helpful?