Restoring Data from Archive Cloud Storage Using Command Line
If your data is moved or stored in an archive cloud, you must recall the data to the main storage location before you can restore the data. Use the following procedure to manually recall the data from the storage location.
- The recommended method for restoring such data is by configuring a workflow. See Restoring Data from Archive Cloud Storage Platforms for more information.
- For deduplicated data, all the volumes associated with the Deduplication Database (DDB) will be recalled.
- The command line method may recall more data from the Archive Cloud storage platform, which may result in additional costs incurred on cloud storage.
Before You Begin
To recall data from Amazon Glacier to S3, make sure that the user associated with the bucket has the
RestoreObject permission. For more information on POST Object restore, see https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOSTrestore.html.
- Run a List Media operation and list the media required for performing the restore. For more information on list media operations, see List Media: Getting Started and List Media: Advanced.
A file called ChunkList_mount_path_ID.txt is created on the CommServe computer in the <software installation path>\Base\Temp folder.
Note: If we have multiple mount paths configure, you will see multiple chunk files with multiple mount path ids.
- From either the CommServe computer or any MediaAgent associated with the cloud library, open the command prompt and navigate to the <software installation path>\Base folder.
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 in the CloudTestTool.
- Depending on the vendor, initiate the recall process as described in one of the following pages:
- Amazon S3 Glacier Using Life Cycle Rule
- Amazon Glacier
- Microsoft Azure Storage
- Oracle Cloud Infrastructure Archive Storage
- Oracle Cloud Infrastructure Archive Storage Classic
The data will be recalled to the main storage location.
Note: This process might take several hours to complete. You can use the CloudTestTool to view the progress and to confirm whether all the data has been recalled successfully.
- Once the recall is complete, perform one of the following tasks:
- If the previous restore job is displayed as Failed in the Job Controller window, resubmit the restore the job. For more information on resubmitting a job, see Resubmitting a Job in the Job Controller.
- If the previous restore job is displayed as Pending in the Job Controller window, resume the job. For more information on resuming a job, see Resuming a Job in the Job Controller.
Last modified: 1/14/2019 2:51:48 PM