To migrate the credentials

1. Contact NetBackup Technical Support and ask for new credentials.
2. Log into NetBackup web UI and add the new credentials to Credential management.

   • On the left, click Credential management.

   • On the Named credentials tab, click Add and provide the following properties:

     • Credential name

     • Tag

     • Description

   • Click Next.

   • In the drop-down, select FortKnox.

     Note:

     For NetBackup 11.0 and earlier releases, select Veritas Alta Recovery Vault in the drop-down list.

   • Click FortKnox Azure, FortKnox Amazon, or FortKnox Google.

     Note:

     For NetBackup 11.0 and earlier releases, select Veritas Alta Recovery Vault Azure or Veritas Alta Recovery Vault Amazon in the drop-down list.

   • Add the Storage account and Refresh token.

   • Select or add a role that can access this credential.

   • Review the information and click Finish.

3. Update the -ntr option with the csconfig cldinstance command.

   Example:

   /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -us -in  
   <instance name> -sts <alias name> -ntr 1

   Confirm the change by making sure that the need token renew option -ntr is set to 1 for enabling this option on the storage server:

   <install path>/netbackup/bin/admincmd/csconfig cldinstance -i

4. Update the credentials using nbdevconfig.

   Create a configuration file with cmsCredName as the credential name that you created using the Credential management.

   Example of the configuration file:

   V7.5 "operation" "update-lsu-cloud" string
   V7.5 "lsuName" "myvolume" string
   V7.5 "cmsCredName" "RVLT-creds" string
   V7.5 "lsuCloudBucketName" "mybucket" string
   V7.5 "lsuCloudBucketSubName" "myvolume" string

5. Use the new configuration file to update the credentials.

   <install path>/netbackup/bin/admincmd/nbdevconfig 
   -setconfig -stype PureDisk -storage_server <storage_server> 
   -configlist <config file path>

   Restart the services on the primary server and the media server for the changes to take effect.

6. Verify the restore of the old backup and run a new backup. Restore the new backup.