NBServerMigrator Update: Rename operation - issues and warnings in "Action Required"

Description

List of issues and warnings under "action required" in the rename operation:

1. Failed to make primary name as first entry in Media/Client bp.conf
   - There is a connectivity issue between the primary server and the media/client server.
   - Update the bp.conf/registry of the media/client server:
   On Linux:
   a) vi /usr/openv/netbackup/bp.conf
   b)Make the first entry to be:  SERVER = <new_name>
   On Windows:
   a) Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Server
   b) Make the first entry to be: <new_name>
    
2. Failed to append primary name to Media/Client bp.conf
   - There is a connectivity issue between the primary server and the media/client server.
   - Update the bp.conf/registry of the media/client server:
   On Linux:
   a) vi /usr/openv/netbackup/bp.conf
   b)Add the entry:  SERVER = <new_name>
   On Windows:
   a) Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\Server
   b) Make the entry : <new_name>
    
3. Failed to Update EMMSERVER with primary on Media/Client
   - There is a connectivity issue between the primary server and the media/client server.
   - Update the bp.conf/registry of the media/client server:
   On Linux:
   a) vi /usr/openv/netbackup/bp.conf
   b)Edit the entry:  EMMSERVER= <new_name>
   On Windows:
   a) Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\EMMSERVER
   b) Edit the entry : <new_name>
    
4. Database is not running.
   - run nbdb_ping to check if the NBDB is up.
   - If NBDB is not up, then restart NetBackup services.
   - If NBDB is still not up, then contact NetBackup Technical support.
    
5. Netbackup services are not up and running
   - Restart NetBackup services.
   - If the required NetBackup services are not up, contact NetBackup Technical support.
    
6. Primary Server is not able to ping itself, Please Check.
   - run the command on the primary server: bpclntcmd -pn -verbose
   Example:
   bpclntcmd -pn -verbose
   expecting response from server new_hostname
   10.xx.xx.xx:45213 -> 10.xx.xx.xx:13720
   PEER_IP = 10.xx.xx.xx
   PEER_PORT = 45213
   PEER_NAME = new_hostname
   POLICY_CLIENT = new_hostname
   
   - verify if the PEER_NAME value is equal to the new_name provided in the nbserver_update command during the rename operation.
   - If not, then:
   a) check the first entry of the bp.conf (or registries) on the primary server. It should be the new_name.
   b) Reverse and forward lookup should happen successfully for the new_name on the primary server. EIther the new_name entry should be present on the DNS or in the hosts file of the primary server.
   c) NetBackup services should be up and running.
   d) If the command is giving error or issue is still not resolved, then please contact NetBackup Technical support.
   Note: If doing rename with the following combination:
   i) current_name.domain.com -> current_name
   ii) current_name -> current_name.domain.com
   Then, update the DNS/hosts file on the primary server to have:
   <IP> <new_name> and clear the host cache and run the bpclntcmd -pn -verbose command to verify.
    

Note: After performing the above-mentioned steps, proceed with the rename steps mentioned in the administrator guide.