# Recalling Index Data from Archive Cloud Storage On-Demand

The Cloud Storage Archive Recall workflow can be run on-demand to recall data from the archive cloud storage libraries, for a restore job.

## Before You Begin

- Verify the following support information before running the workflow:

  - Supported Archive Cloud Storage Platforms

  - Supported Agents

  - Feature Support

- Make sure that the MediaAgent associated with the Cloud Archive Storage libraries have the same Service Pack level as the CommServe server.

- Install the Workflow Engine on a Windows server, and then deploy the Cloud Storage Archive Recall workflow on the server. The workflow is not supported if the Workflow Engine is hosted on Linux operating system. For more information on deploying the workflow, see Deploying a Workflow.

  - This workflow is included in the Commvault software and will be listed under the Workflows node in the CommCell Browser.

  - Ensure that the workflow is deployed by a user with the necessary permissions needed to deploy and execute a workflow. For more information on user permissions, see User Security Permissions - Workflow.

  - If the workflow is already deployed, verify that the latest version of the workflow is deployed. For more information on the workflow version, see Viewing Workflow Version History.

    If the workflow is an older version, re-deploy the workflow. For more information on deploying a workflow, see Deploying a Workflow.

- To perform the Browse from the Archive tier operation, run the index recall first. By default, the browse operation will initiate the Index Restore job and the Cloud Storage Archive Recall workflow job is initiated if there is any index data is to be recalled. Once the Cloud Storage Archive Recall workflow job is complete, you can perform the browse operation again.

- For VSA clients with V1 indexing, while performing VM recalls from cold storage for synthetic full backup jobs, run the index recall first. Verify that the VM browse works after the index restore before running Cloud Storage Archive Recall workflow. For more information on running the index restore, see Recalling Index Data from Archive Cloud Storage.

  See Also: Restoring Data from Archive Cloud Storage Using a Workflow - Feature Support

## Procedure

1. From the Command Center navigation pane, go to Manage > Integration > Developer tools.

2. Click the Workflows tile.

3. On the Workflows page, go to the Cloud Storage Archive Recall workflow.
4. Click the action button , and then click Execute.

5. On the Cloud Storage Archive Recall dialog box, enter the following information:

   - Backup JobId: Enter one of the following:

     - If the agent supports automatic recalls, enter the Restore Job ID.

     - If the agent does not support automatic recalls, then enter the Backup Job ID.

       Note

       This action recalls the entire job back from archive storage and may incur additional charges.

       For information about supported agents, see Restoring Data from Archive Cloud Storage Using a Workflow - Supported Agents.

   - Recall Monitoring Interval: Select the monitoring frequency from the list.

     For the Default option, the workflow uses an appropriate value based on the storage vendor and storage class.

   - Retention Days: Enter number of days to access the recalled data after the recall.

   - Retrieval option (AWS): Select the recall mode that must be used to recall data for AWS.

     Note

     Expedited mode will incur additional costs. Also note that Expedited recall mode requires provisioned capacity as described in https://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive-two-steps.html#api-downloading-an-archive-two-steps-retrieval-expedited-capacity.

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

   - Retrieval Option (Azure): Select the recall mode that must be used to recall data for Azure.

     Note

     If High Priority is selected, the re-hydration request will be prioritized over the Standard requests, and may finish in under 1 hour.

     For more information about the recall options, see https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-rehydration.

   - Recall only index files: If enabled, only index files (metadata) are recalled.

6. Click OK.

The recall process may take some time, depending on the Archive Cloud Storage platform from which the recall is initiated.

## What to Do Next

When data is recalled from Microsoft Azure Storage, it will be recalled from archive to hot storage class. Data will be copied from the Archive tier to the Hot tier under the `cvshadowcopy-do-not-use-or-delete-folder` subfolder, and the original data will be still present on the Archive tier.

Once the cloud recall workflow is complete, perform a Browse and Restore operation using the Job ID.

Note

You must configure a lifecycle policy to delete recalled data after 7 days. This applies to both:

- the standalone `cvshadowcopy-do-not-use-or-delete` container used in earlier versions
- the `cvshadowcopy-do-not-use-or-delete-folder` subfolder structure used in newer versions across any container

Use this sample json file to configure the lifecycle policy. Ensure that you update the `prefixMatch section` with the appropriate container or folder paths specific to your environment before applying the policy. For more information, see Azure Blob Storage lifecycle management overview.

×

Loading...