About installing and configuring the new MSDP direct cloud tier server
You need a new MSDP direct cloud tier server with no existing disk pools for the Cloud Catalyst migration. This section assumes that the primary server has been upgraded to the latest version of NetBackup (10.0 or later) which supports migration. Also, this section also assumes that the latest version of NetBackup (10.0 or later) has been installed on the media server or appliance to be used for migration.
Configure an MSDP direct cloud tier server on the media server to be used for migration. Do not configure any disk pools for that storage server. You must use the same KMS settings when configuring the new MSDP direct cloud tier server as were used for Cloud Catalyst. If the Cloud Catalyst storage server type ends in _cryptd (for example: PureDisk_amazon_cryptd) then KMS needs to be enabled. If the Cloud Catalyst storage server type ends in _rawd (for example: PureDisk_azure_rawd) then KMS may or may not need to be enabled. This information should be compiled before migration as noted in the About beginning the direct migration section.
Note:
If KMS needs to be enabled then all three KMS-related checkboxes on the MSDP server configuration screen in the web UI need to be checked. Also, the KMS key group name from Cloud Catalyst needs to be entered. Mismatched KMS settings can cause problems attempting to access any of the data that Cloud Catalyst uploaded. You must verify that all KMS-related information matches.
The new MSDP direct cloud tier server must have at least 1 TB free disk space. You can migrate to a system with less free disk space. However, an extra step is required after you create the new MSDP direct cloud tier server and before you run the Cloud Catalyst migration. This extra step involves modifying the default values for CloudDataCacheSize and CloudMetaCacheSize in contentrouter.cfg file.
See About the configuration items in cloud.json, contentrouter.cfg, and spa.cfg.
The new MSDP server should be set to the correct time and you can set the time by using an NTP server. If the time is incorrect on the MSDP server, some cloud providers may report an error (for example: Request Time Too Skewed) and fail upload or download requests. Refer to your specific cloud vendor documentation for more information.
Note:
After configuring the new MSDP server and before continuing, run a manual backup of the catalog backup policy (policy type ). Do not skip this step as it is very important to run this manual backup. This backup establishes a point in time to return to if the migration does not complete successfully.