Running the Cloud Storage Archive Recall Workflow 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:
Make sure that the MediaAgent associated with the Cloud Archive Storage libraries have the same Service Pack level as the CommServe server. For more information on viewing the version information, see Viewing the Service Pack Details for One or More Clients.
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.
To recall data from Amazon Glacier Glacier/Deep Archive or Combined Tier Storage Classes, 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.
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

From the navigation pane, click Workflows.
Right-click the Cloud Storage Archive Recall workflow and then click All Tasks > Execute.

The Cloud Storage Archive Recall dialog box appears.
From the Run workflow on list, select the engine to use to execute the workflow and then provide values for the workflow inputs.

If you select Any, the workflow engine with the latest deployed version of the workflow is used.
In the Backup JobId box, 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.
Optionally, from the Recall Monitoring Interval list, 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.)
Optionally, modify the following options for different storage vendors:

For Amazon S3 Glacier, Deep Archive, and Combined Tier Storage Class:
- Retention Days: No. of days to keep the recalled data in Amazon S3 after the recall.
  
  This option applies to Glacier, Deep Archive, and Combined Tier storage class only.
  
  Note
  
  Amazon Glacier (Direct) does not honor the Retention Days option. The recalled data will be available for 24 hours, after which it will be moved back to Glacier. For more information about the move back option, see https://docs.aws.amazon.com/amazonglacier/latest/dev/downloading-an-archive-two-steps.html.
- Retrieval option: 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
  
  2 - Bulk
  
  For more information about the recall modes, see http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOSTrestore.html.
  
  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. If the Expedited mode is selected, the re-hydration request will be prioritized over the Standard requests, and may finish in under 1 hour.
  
  Note
  
  Deep Archive does not support the Expedited recall mode.
  
  For Azure Archive Storage:
- Retrieval option: The recall mode that must be used to recall data. Default is set to Standard Priority. Valid values are:
  
  Standard Priority
  
  High Priority
  
  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.
  
  For Oracle Archive Storage: For information about the recall options, see https://docs.oracle.com/en-us/iaas/Content/Archive/Concepts/archivestorageoverview.htm.
Click OK.

The User Inputs dialog box will be displayed.
From the Select Copy/Copies list, select the storage policy copy from which the data must be recalled and click OK.

The Note dialog box will be displayed with information on the Total Files to be recalled and the list of MediaAgents used for performing the recall.
Click Yes to continue.

If required, click the Change MediaAgent button to select the MediaAgent from which the recall must be initiated.

A Cloud Storage Archive Recall job will be started and displayed in the Job Controller window. The job will complete once all the required files are recalled.

Note

Job may not complete if there is a service restart on the CommServe computer. Make sure to re-submit the job if there is a service restart.

The recall process may take some time, depending on the Archive Cloud Storage platform from which the recall is initiated. For example, Amazon S3 may take 8+ hours, Microsoft Azure 12+ hours, Oracle 1 hour, etc.

What to Do Next

For Azure Archive Storage, modify the Auto-archive recalled files on restore job completion option.

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 container, and the original data will be still present on the Archive tier.

If you execute the workflow with restore job as input, data will be moved back to archive automatically once the restore job completes.
If you execute the workflow with backup job as input, execute the workflow again and select the Move back data from Hot to Archive option when prompted. Data will be deleted from the cvshadowcopy-do-not-use-or-delete container.

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