If your data is moved or stored in an archive cloud storage, you must first recall the data to be accessible, before restoring the data.
Before a user recalls data from any Amazon S3 Glacier Storage platform, make sure that the user associated with the bucket has the
s3:RestoreObjectpermission. This permission may not be added by default to JSON and IAM roles permissions.
Restoring data from any Amazon S3 Glacier Storage platform involves latency, especially when large amounts of data have to be restored.
Life Cycle Policies are not recommended to move the data to archive storage. If Life Cycle Policies are already configured to move the data to archive storage during recall, we recommend that you disable the Life Cycle Rule Policy till the data is successfully recalled and restored.
You can use any one of the following methods to recall data from Archive Cloud Storage platform:
Automatic Recall: For Agents that support automatic recalls, the software automatically recalls the data from the Archive Cloud storage platform using the Cloud Storage Archive Recall workflow, and then continues with the restore operation.
On Demand Recall: For Agents that do not support automatic recalls, you must manually run the Cloud Storage Archive Recall workflow on-demand using the backup job ID. For more information on this method, see Running the Cloud Storage Archive Recall Workflow On-Demand.
When a browse operation fails with index errors, you must run the Cloud Storage Archive Recall workflow to restore only the index to continue with the browse and restore operation. For more information on performing index restores, see Recalling Index Data from Archive Cloud Storage.