NBServerMigrator Update: Rename operation - ECA configured on Flex Appliance

Description

Rename steps to perform when ECA is configured on Flex Appliance:

Rename operation (ECA + NBCA is configured on the Flex instance)

1. Log into Flex Appliance host.
   Note: The Flex Appliance host must be in unrestricted and elevated mode.
2. Run the following command from the nbserverupdate directory:
   nbserver_update -operation rename -current_name <old Name> -new_name <new name>
    
3. Logon prompt is displayed for the Web UI.
   Note: Specify the username as admin and its password. The Rename logs is generated on the Flex Instance.
   
   Once the NBServerMigrator Update performs its operation, a message is displayed. It also displays the Action Required tasks in case the operation is partially completed due to some errors.

      Post rename tasks
 

1. Update the network configuration so that both the current name and the new name are resolved on the primary server as well as on the media and client servers. After this, clear the cache on the media and the client servers using the command: bpclntcmd -clear_host_cache
    
2. Run following commands on the Flex instance:
   a) /usr/bin/wmc/bin/install/configureWebServerCerts -removeExternalCert -all -force
   Note: if the above commands fail, please follow the technote: https://isearch.veritas.com/internal-search/en_US/article.100071793.html
   b) /usr/bin/netbackup/bin/nbwmc -stop
   c) /usr/bin/netbackup/bin/nbwmc -start
   d) /usr/bin/netbackup/bin/nbcertcmd  -removeEnrollment
    
3. Reconfigure ECA with a new certificate for the new_name with the following steps on the Flex instance.
   a) Remove/rename the old eca folder
   b) Copy ECA certificates of new_name in the eca folder.
   c) Set the appropriate ownership to the eca folder
       example:  chown nbsvc:bin -R /usr/eca   where nbsvc is service user
   d) Run the following commands
       i)/usr/openv/wmc/bin/install/configureWebServerCerts -addExternalCert -all -certPath <eca_folder_path>/cert_chain.pem -privateKeyPath <eca_folder_path>/private/key.pem -trustStorePath <eca_folder_path>/trusted/cacerts.pem
       ii) /usr/openv/netbackup/bin/nbwmc stop
       iii) /usr/openv/netbackup/bin/nbwmc start
       iv) /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate
   e) Run the following to check the status of eca
       /usr/openv/netbackup/bin/nbcertcmd -getSecConfig -caUsage
    
4. Pull new certificates on ECA deployed  clients/media
       /usr/openv/netbackup/bin/nbcertcmd -getCACertificate -server <new_name>
       /usr/openv/netbackup/bin/nbcertcmd -getCertificate  -force -server <new_name>
       /usr/openv/netbackup/bin/nbcertcmd -getCrl -server <new_name>
    
5. Run post rename report on the Flex Host:
   a) Validate that both the current name and the new name are pingable from the flex instance.
   c) Run the following command on the flex host:
       nbserver_update -operation rename  -current_name <hostname> -post_report
       Where the hostname is the new host name of the NetBackup primary server. That is the host name to which the NetBackup primary server has been renamed.
    
6. The post rename report post_rename_report.html will be present in the /mnt/nbdata/usr/openv/nbsm/nbserverupdate/report folder on the flex instance. Open it in a browser and analyze the report.
    
7. Take a restart of NetBackup services on the flex instance.

Rename operation (When Only ECA is configured on the Flex instance)

1. Enable NBCA on the Flex instance by using the command:
   /usr/openv/wmc/bin/install/configureWebServerCerts -addNBCert
    
2. Log into Flex Appliance host.
   Note: The Flex Appliance host must be in unrestricted and elevated mode.
    
3. Run the following command from the nbserverupdate directory:
   nbserver_update -operation rename -current_name <old Name> -new_name <new name>
    
4. Logon prompt is displayed for the Web UI.
   Note: Specify the username as admin and its password. The Rename logs is generated on the Flex Instance.
   
   Once the NBServerMigrator Update performs its operation, a message is displayed. It also displays the Action Required tasks in case the operation is partially completed due to some errors.

       Post rename tasks
 

1. Update the network configuration so that both the current name and the new name are resolved on the primary server as well as on the media and client servers. After this, clear the cache on the media and the client servers using the command: bpclntcmd -clear_host_cache
    
2. Run following commands on the Flex instance:
   a) /usr/bin/wmc/bin/install/configureWebServerCerts -removeExternalCert -all -force
   Note: if the above commands fail, please follow the technote: https://isearch.veritas.com/internal-search/en_US/article.100071793.html
   b) /usr/bin/netbackup/bin/nbwmc -stop
   c) /usr/bin/netbackup/bin/nbwmc -start
   d) /usr/bin/netbackup/bin/nbcertcmd  -removeEnrollment
    
3. Reconfigure ECA with a new certificate for the new_name with the following steps on the Flex instance.
   a) Remove/rename the old eca folder
   b) Copy ECA certificates of new_name in the eca folder.
   c) Set the appropriate ownership to the eca folder
       example:  chown nbsvc:bin -R /usr/eca   where nbsvc is service user
   d) Run the following commands
       i)/usr/openv/wmc/bin/install/configureWebServerCerts -addExternalCert -all -certPath <eca_folder_path>/cert_chain.pem -privateKeyPath <eca_folder_path>/private/key.pem -trustStorePath <eca_folder_path>/trusted/cacerts.pem
       ii) /usr/openv/netbackup/bin/nbwmc stop
       iii) /usr/openv/netbackup/bin/nbwmc start
       iv) Run the following commands:
           nbcertcmd -getCACertificate
           nbcertcmd -getCertificate -force
           Note: If a reissue token is requested, then follow: https://www.veritas.com/support/en_US/article.100044149
       v) /usr/openv/netbackup/bin/nbcertcmd -enrollCertificate
   e) Run the following to check the status of eca
       /usr/openv/netbackup/bin/nbcertcmd -getSecConfig -caUsage
4. Pull new certificates on ECA deployed  clients/media
       /usr/openv/netbackup/bin/nbcertcmd -getCACertificate -server <new_name>
       /usr/openv/netbackup/bin/nbcertcmd -getCertificate  -force -server <new_name>
       /usr/openv/netbackup/bin/nbcertcmd -getCrl -server <new_name>
    
5. Run post rename report on the Flex Host:
   a) Validate that both the current name and the new name are pingable from the flex instance.
   c) Run the following command on the flex host:
       nbserver_update -operation rename  -current_name <hostname> -post_report
       Where the hostname is the new host name of the NetBackup primary server. That is the host name to which the NetBackup primary server has been renamed.
    
6. The post rename report post_rename_report.html will be present in the /mnt/nbdata/usr/openv/nbsm/nbserverupdate/report folder on the flex instance. Open it in a browser and analyze the report.
    
7. Disable NBCA on the flex instance using the command:
   configureWebServerCerts -removeNBCert
   (use -force if the command requests it)
    
8. Take a restart of NetBackup services on the Flex instance.

Note: This technote includes the "Modify the host name of the primary server" and "Post rename tasks" topics of the NBServerMigrator Update: Rename operation administrator guide.