NBServerMigrator update: rename operation - MSDP configured on the primary/media server with EKMS or KMS configured

Problem

After rename, backups on MSDP with EKMS on the primary/media server are failing.

Error Message

Error nbjm (pid=xxxx) NetBackup status: 2106, EMM status: Storage Server is down or unavailable

or

Critical bptm (pid=xxxxx) Storage Server Error: (Storage server: PureDisk:<storage server name>) _pdvfs_fcache_flushfile_norm_cleanup: Failed to write to spoold on storage server (incorrect crypto key supplied). Ensure storage server services are running and operational. V-454-8

or
Backups are in hung state
- granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=MSDP_KMS;Path=PureDiskVolume;StorageServer=iamnewname;MediaServer=iamnewname
- granted resource MSDP_KMS-stu
- estimated 0 kbytes needed
- Info nbjm (pid=37162) started backup (backupid=iamnewname_1741084726) job for client iamnewname, policy FS_primary, schedule FULL on storage unit MSDP_KMS-stu
- started process bpbrm (pid=41424)
 

Cause

N/A

Solution

When the MSDP with KMS is configured on the media server, update the contentrouter.cfg file on the media server.

1.  Make a copy of the file <storage_server_path>/etc/puredisk/contentrouter.cfg
    
2. Edit the file in the path <storage_server_path>/etc/puredisk/contentrouter.cfg
    
3. Search for the keyword: KMSServerName
    
4. a) Update the value from current_name to new_name
   where: current_name is the original hostname and the new_name is the new hostname of the NetBackup primary server.
   b) Remove the field: KMSSectionCrc (If it is present)
    
5. Example:
   
   Existing fields:
   [KMSOptions]
KMSEnable=true
KMSType=0
KMSServerName=current_name
KMSKeyGroupName=dl380g10-075-vm28_kms_kg
KMSSectionCrc=3461486082
   
   Updated fields:
   [KMSOptions]
KMSEnable=true
KMSType=0
KMSServerName=new_name
KMSKeyGroupName=dl380g10-075-vm28_kms_kg
    
6. Restart NetBackup services on the media server.
7. Open the contentrouter.cfg file to verify that the KMSSectionCrc field has been populated.

When the MSDP with KMS is configured on the Primary server, update the contentrouter.cfg file on the Primary Server:
 

1. Run the command <install_path>/netbackup/bin/admincmd/nbkmsutil -listkeys -all
2. Note down the KMSKeyGroupName for the MSDP configured on the primary server.
3. Make a copy of the file <storage_server_path>/etc/puredisk/contentrouter.cfg
4. Edit the file in the path <storage_server_path>/etc/puredisk/contentrouter.cfg
5. Search for the keyword: KMSServerName and KMSKeyGroupName
6. a) Update the value of KMSServerName from current_name to new_name (Ignore if already updated).
   where: current_name is the original hostname and the new_name is the new hostname of the NetBackup primary server.
   b) Update the value of KMSKeyGroupName to the existing KMSKeyGroupName obtained from the point 2.
   c) Remove the field: KMSSectionCrc (If it is present)

       Example:

        Existing fields:
        [KMSOptions]
        KMSEnable=true
        KMSKeyGroupName=iamnewname:key1
        KMSServerName=iamnewname
        KMSType=0
        KMSSectionCrc=2239367674

        Updated fields:
        [KMSOptions]
        KMSEnable=true
        KMSKeyGroupName=<original_key_group_name>:<key_name>
        KMSServerName=iamnewname
        KMSType=0

    7. Restart NetBackup services on the Primary server.
    8. Open the contentrouter.cfg file to verify that the KMSSectionCrc field has been populated.