Command Line - Amazon S3 Glacier Using Life Cycle Rule

After generating the chunk files, the recall can be initiated from the command line. For more information on generating the chunk files, see Restoring Data from Archive Cloud Storage Using Command Line.


CloudTestTool.exe -h s3.[region].amazonaws.com -u <Access Key> -p <Secret Access Key> -b <bucket> -c 0 -f "C:\<software installation path>\Base\Temp\ChunkList_mount_path_ID.txt" -d <days>


.\CloudTestTool.exe -h s3.[region].amazonaws.com -u <Access Key> -p <Secret Access Key> -b <bucket> -c 0 -f "/opt/commvault/Base/Temp/ChunkList_mount_path_ID.txt" -d <days>




A valid endpoint name for the Amazon S3 region provided by the agency.

Default: s3.[region].amazonaws.com

Example: s3.us-west-1.amazonaws.com

To find the region, see https://docs.aws.amazon.com/general/latest/gr/rande.html.


Access Key


Secret Access Key


Bucket Name


Location of the chunk list file.

Note: If the CloudTestTool is run from any MediaAgent that has access to the Cloud library, make sure to copy the ChunkList_mount_path_ID.txt file to the MediaAgent and provide the appropriate location of the file.


No. of days to keep the recalled data in Amazon S3 after the recall.

Default is set to 3 days.


The recall mode that must be used to recall data. Default is set to 0, which is Standard mode. Valid values are:

0 - Standard

1 - Expedited

Note: Expedited mode will incur additional costs.

2 - Bulk

For more information on the recall modes, see http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOSTrestore.html.

Note: Deep Archive does not support the Expedited recall mode.




When the cloud storage is accessed using a proxy server then the proxy server name and credentials as follows:

-x <proxy server name>

-y <user name to access the proxy server>

-z <password for the user name>

Last modified: 10/14/2019 7:37:35 PM