Integrating MSDP Cloud and CMS
Note:
CMS is now supported for all S3 and Azure cloud vendor types.
To integrate MSDP Cloud and CMS
- If you haven't already, create an MSDP storage server. See the Configuring MSDP server-side deduplication section in the NetBackup Deduplication Guide.
- Add a disk pool.
On the left, select Storage > Disk storage and select the Disk pools tab. Then select Add.
- In the Disk pool options, click Change to select a storage server.
Select a storage server from the list and click Select.
Enter the Disk pool name.
If Limit I/O streams is cleared, the default value is Unlimited and may cause performance issues.
After all the required information is added, click Next.
- In the Volumes properties, from the Volume list select Add volume.
Provide a unique volume name that gives adequate description of the volume.
For the Cloud storage provider, select Microsoft Azure, Amazon, or any other cloud provider of S3 and Azure types. The click Select.
- In the Region section, select the appropriate region.
- In the Associate Credentials section, select an authentication type, select Add a New Credential.
Enter a Credential name which should be a valid name and should only contain alphanumeric characters, hyphen, colon, and underscore.
Note:
For details of authentication types like AWS IAM Role Anywhere and Azure Service Principal, see the NetBackup Deduplication Guide.
- In Access details for type account, select AWS S3 compatible or Azure Blob and enter the access information.
Alternatively, you can use Select existing credential but the credentials must have a Category of MSDP-C and proper credentials for the chosen supported cloud provider.
- In the Cloud buckets section, select from the following options:
If the cloud credentials in use do not have the permissions to list buckets, click Enter an existing cloud bucket name.
To create a cloud bucket, click Select or add a cloud bucket. Then click Retrieve list to select a predefined bucket from the list.
- Click Next.
- In Replication, click Next.
- On the Details page, verify that all settings and information are correct. Click Finish.
The disk pool creation and replication configuration continue in the background if you close the window. If there is an issue with validating the credentials and configuration of the replication, you can use the option to adjust any settings.
In the Volumes step, you can now use (list buckets) or create a bucket depending on what you want to accomplish.
To update the credentials
- Create a disk pool.
After you have selected Add volume, Volume name, select Cloud storage, and select a Region then click Select existing credential.
- Locate Credential name. Then click Actions > Edit.
- Make any changes as necessary.
- In the Permissions, make any changes as necessary and click Save.
- Finish adding the disk pool.
nbcldutil changes(10.3 and later) Use the parameter cmscredname instead of username. However, username is still supported for older media servers.
Validate credentials. nbcldutil -validatecreds -storage_server mystorage_server -cmscredname mycmscredentialname
Create a bucket. nbcldutil -createbucket -storage_server mystorage_server -cmscredname mycmscredentialname -bucket_name bucketname
nbdevconfig changesYou need to provide lsuCmsCredName in the configuration file for FortKnox Azure and FortKnox Azure Gov.
Instead of using the storage account name for lsuCmsCredName, use the name of the credentials that are created when you use Credential management.
The configuration file for nbdevconfig CLI now uses a new Key cmsCredName instead of user lsuCloudUser and lsuCloudPassword. The file should look like the following:
[root@vramsingh7134 openv]# cat /add_lsu.txt V7.5 "operation" "add-lsu-cloud" string V7.5 "lsuName" "ms-lsu-cli" string V7.5 "lsuCloudBucketName" "ms-mybucket-cli" string V7.5 "lsuCloudBucketSubName" "ms-lsu-cli" string V7.5 "cmsCredName" "aws-creds" string V7.5 "requestCloudCacheCapacity" "4" string
Note:
For regular Azure and AWS from this 10.3 and newer: If you use the createdv option to create a cloud bucket on the primary server or media server or on an older media server, you see a message that tells you to use nbcldutil.
Note:
Some browsers like Firefox may auto-populate the fields to store the credentials in the CMS with credentials the browser saves. You must to turn off a setting in Firefox so that the credentials do not auto-populate.