Permanently Moving Data Between Google Cloud Storage Tiers

You can permanently move all the data residing in Google cloud storage tier to another Google cloud storage tier.

The process involves the following steps:

Contact the storage vendor and create the new storage class in cloud storage.
Recall the existing data from the current storage tier to the new tier. For example, from Archive to Nearline, Coldline or Standard tier.
Next, you need to run a command to permanently move the data to the appropriate new class.
For new data, change the storage class in the cloud storage library as described in Migrating Data Between the Storage Classes in a Cloud Storage Library.

Procedure

Identify the bucket name and mount path base folder for the data that must be moved.

You can view the BucketName and the MountPathBaseFolder from the Mount Path Properties (General) dialog box in the CommCell Console.
Create text file with the path to the data residing in the cloud depending on the number of mount paths that must be moved:
- If you have multiple mount paths on the same bucket, then add the bucket and the mount path base folder as follows:
```
 
<BucketName>\<MountPathBaseFolder>\
```
  Example:
```
MyBucket\E3TLWT_11.01.2017_03.09\
```
- If you have just one mount path, than add only the bucket name as follows:
```
 
<BucketName>\
```
  Example:
```
MyBucket\
```
  Note
  
  Make sure to include the backslash (\) at the end.

Navigate to the following folder:

<software installation directory\Base

Example:

c:\Program Files\Commvault\ContentStore\Base

From the command prompt, run the CloudTestTool with the following parameters, to restore the data from the current storage to the desired storage:

 
CloudTestTool.exe -u "<ServiceHost//ProjectID|-|Service_Account_Email|-|P12_Key_Filename>" -p <Private_Key's_Password> -b <bucket_name> -f "<InputFileName>" -m <#> -o changeTier -T <#>

Options	Description
-u	Service Host, Project ID, Service Account Email, and P12 Key Filename
-p	Private key password.
-b	Bucket name.
-f	Full path and name of the input file created in step 1.
-T	Storage Class to which the data must be recalled. Valid values are: 0 – Standard 1 – Durable Reduced Availability 2 – Nearline 3 – Coldline 4 – Regional 5 – Multi-Regional
-m	Recall metadata options. Valid values are: 1 – Chunk Meta Data only 2 – SFILE only 3 – non SFILE 0 – All

Example:

CloudTestTool.exe -u "storage.googleapis.com@9#5us//expense-12345|-|myemailid@developer.gserviceaccount.com|-|mykeyfile-99c999f99g.p12" -p myprivatekey -b mybucket -f "C:\Program Files\Commvault\ContentStore\Base\Temp\googlelist.txt" -m 0 -o changeTier -T 0

This will start the process of recalling the data from the current storage tier to the target tier specified in the command.

Note

Depending on the amount of data, this process will take some time to complete.

Once the data is recalled, the list.txt.ChangeList.txt file will be created, with a complete list of files that was recalled. This file will be saved in the same folder specified for the input file.

Permanently convert the storage class using the following command:

 
CloudTestTool.exe -u  -u "<ServiceHost//ProjectID|-|Service_Account_Email|-|P12_Key_Filename>" -p <AccessKey> -b <Container> -f "<InputFileName>" -o changeTier -o changeTierFullList -f <full path>\list.txt.RestoringList.txt

Example:

CloudTestTool.exe -u "storage.googleapis.com@9#5us//expense-12345|-|myemailid@developer.gserviceaccount.com|-|mykeyfile-99c999f99g.p12" -p myprivatekey -b mybucket -f "C:\Program Files\Commvault\ContentStore\Base\Temp\googlelist.txt" -o changeTierFullList -f C:\Program Files\Commvault\ContentStore\Base\Temp\list.txt.RestoringList.txt

Once the command is completed successfully, you can view the storage tier for the data using the Cloud Storage Explorer tool. For more information about this tool, see Starting the Cloud Storage Explorer Tool.

What to Do Next

Once you move the existing data, you must also modify the storage class in the library and point it to the new storage tier. This will ensure that the new data writes to the new storage tier. For more information see Modifying the Storage Class for an Existing Cloud Library.