Storage

Updated

Cloud Storage

Adding a Secondary Credential to Access the Cloud Library Mount Path

You can add a secondary cloud storage credential, which can be used by clients that have the Storage Accelerator package, to access the cloud library mount path. You can use the secondary credential to prevent clients that have the Storage Accelerator package from gaining full access to the cloud storage library by creating the secondary credential with only read and write permissions to the mount path. (Delete permission can be omitted for the Storage Accelerator.) Also, when you set up the MediaAgent with a secure access role (such as AWS IAM role) to access the cloud storage library, you can create this secondary access credential for clients that have the Storage Accelerator package.

For more information, see the following:

Automatically Installing the Storage Accelerator Package on a Client Computer

The software automatically installs the Storage Accelerator package if the package is not present on the client computer that is associated with the storage policy configured for a cloud storage library or a HPE Catalyst Storage Library. However, if the client computer already has MediaAgent installed, then the backup data is sent directly to the library from the client computer.

For more information, see the following:

You can now use AWS PrivateLink for Amazon S3 to create S3 cloud libraries that are directly accessible from within your VPC, from on-premises or within the region. AWS PrivateLink provides private connectivity between VPCs, AWS services, and your on-premises networks, without exposing your traffic to the public internet.

When you create an Amazon S3 interface endpoint, Amazon S3 generates two types of endpoint-specific, S3 DNS names: regional and zonal. You may now add a new Commvault cloud library using the Interface VPC endpoint regional or zonal hostname as the S3 service host.

Privatelink for Amazon S3 libraries may use existing authentication methods - Access Key, IAM role, STS:AssumeRole, and C2S Access.

For more information, see Amazon S3.

Distributed Storage

Syncing Distributed Storage Clusters

You can update the CommCell with any new configured storage nodes or proxies in the registered distributed storage cluster.

For more information, see Syncing Distributed Storage Clusters.

Indexing

Changing the Indexing MediaAgent Using the CommCell Console

You can change the MediaAgent used for indexing operations on the following entities:

  • A backup set or subclient on a client computer

  • A backup set on a virtual server

  • A database instance

For more information, see Changing the Indexing MediaAgent Using the CommCell Console.

Changing the Location of the Index Log Cache Directory

You can change the location of the index log cache directory on a MediaAgent, in order to help distribute the MediaAgent's disk resources.

By default, the IndexCache directory stores all index databases and all index action logs.

After you change the location of the index log cache directory, content is stored as follows:

  • IndexCache directory: Stores only the index databases

  • New index log cache directory: Stores the index action logs and other non-essential index data

For more information, see the following: