Google Cloud Storage - OAuth 2.0 (Service Account)

Use this dialog box to add (or modify) Google Cloud Storage, with OAuth 2.0 (Service Account) authentication, as a storage target.

Option

Description

Additional Information

Name

The name of the Cloud library.

Device Name

A unique device name generated by the system when the library is added.

Type

Select Google Cloud Storage from the list.

MediaAgent

The name of the MediaAgent to which the device is attached. Select a MediaAgent from the list to add to the cloud storage device. The list contains the names of all the MediaAgents configured in the CommCell.

Access Information

Add the credentials and other details required to access the cloud storage space.

Authentication

Select OAuth 2.0 (Service Account).

Make sure to setup the necessary permissions needed to access the library, before configuring the library in a MediaAgent. For more information about the required permissions, see https://cloud.google.com/storage/docs/access-control/iam-permissions.

Service Host

The URL of the host providing the cloud storage service. (Commvault transfers data using HTTPS protocol to the service host.)

Default: storage.googleapis.com

Multiple hosts can be added in the Service Host field using commas to separate them. For example servicehost1, servicehost2, servicehost3. (For local cloud servers with multiple IP addresses, the list of IP addresses can be added. For example, 192.xxx.0.100,192.xxx.0.101, 192.xxx.0.102. )

Note

All the hosts (or IP addresses) in the list must point to the same storage. Adding a host or IP address to a different storage will result in data loss.

Project ID

The Google Cloud Platform Project ID.

Service Account EMail

The email ID associated with the private account.

P12 Key Filename

The file name for the P12 private key.

Make sure that the P12 key file is copied and available in all the MediaAgents using the library under the <software install folder>/Base/Certificates folder.

Private Key's Password

The password for the private key.

Bucket

Click the Detect button to detect an existing bucket.

Sometimes, existing bucket list may not get populated while detecting the buckets, as some vendors may not support this operation, or if there are no permissions to complete the operation. In such cases, type the name of the existing bucket that you want to use. The system will automatically use the existing bucket if it is available.

The following permissions must be enabled for the bucket:

storage.buckets.create
storage.buckets.delete
storage.buckets.get
storage.buckets.getIamPolicy
storage.buckets.list
storage.buckets.setIamPolicy
storage.buckets.update
storage.objects.create
storage.objects.delete
storage.objects.list

Storage Class

Use this option to add an existing bucket.

The following storage classes are supported:

  • Use bucket's default storage class

  • Standard

  • Nearline

  • Coldline

  • Archive

  • Durable Reduced Availability

  • For more information on Google storage classes, see https://cloud.google.com/storage/.

  • If the bucket does not already exist, a new bucket will be created using the options selected in the Storage Class Settings for Creating a New Bucket section.

Storage Class Settings for Creating a New Bucket

Use this option to create a new bucket.

Storage Class

The following storage classes are supported:

  • Standard

  • Nearline

  • Coldline

  • Archive

For more information on Google storage classes, see https://cloud.google.com/storage/.

Location

The endpoint location for the bucket.

Performing a Space Reclamation Operation on Deduplicated Data

Loading...