Search <book_title>...

NetBackup™ Web UI Administrator's Guide

Last Published: 2024-01-16

Product(s): NetBackup (10.3.0.1)

Integrating MSDP Cloud and CMS

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, click Disk storage, click the Disk pools tab, and then click Add.
- In 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 left cleared, the default value is Unlimited and may cause performance issues.
  - After all required information is added, click Next.
  - In Volumes, use the Volume drop down and select Add volume.
    Provide a unique volume name that gives adequate description of the volume.
    In the Cloud storage provider section, select Microsoft Azure, Amazon, or any other cloud provider of S3 and Azure types.
- In the Region section, select the appropriate region.
- In the Associate Credentials section, 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 NetBackup™ Deduplication Guide.
- In Access details for the 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 bucket section, you can create a cloud bucket by clicking Retrieve list to select a predefined bucket from the list. If the cloud credentials in use do not have the permissions to list buckets, use Enter an existing cloud bucket name.
- 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 Change option to adjust any settings.

In the Volumes step, you can now use Retrieve List (list buckets) or create a bucket depending on what you want to accomplish.

Note:

CMS is now supported for all S3 and Azure cloud vendor types.

Updating credentials

To update 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.
Click on the Actions menu to the right of the Credential name.
Click Edit and in the Edit credential screen, make the changes as necessary.
In the Permissions window, add or change as necessary and click Save.
Finish adding the disk pool.

nbcldutil changes

The CLI now has a new parameter cmscredname that should be used instead of username from 10.3 and newer. However, the support for username is not removed, you can still use username for older media servers.
Validate credentials - nbcldutil -validatecreds -storage_server mystorage_server -cmscredname mycmscredentialname
Create bucket - nbcldutil -createbucket -storage_server mystorage_server -cmscredname mycmscredentialname -bucket_name bucketname

nbdevconfig changes

You need to provide lsuCmsCredName in the configuration file for Veritas Alta Recovery Vault Azure and Veritas Alta Recovery Vault 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 either on the primary server, media server, or 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 CMS with credentials the browser saves. You must to turn off a setting in Firefox so that the credentials do not auto-populate.