Recalling Index Data from Archive Cloud Storage

When you browse and restore data from an archive cloud storage, if the browse operation fails with index errors, the software automatically recalls the index data using the Cloud Storage Archive Recall workflow, and then continues with the restore operation.

The automated index recall applies to all Commvault hypervisor, file-system, and application agents (using v1 or v2 indexing). Additionally, recall functions for deduplication and non-deduplicated cloud libraries.

The recall is performed by requesting the relevant index data from the copy in an existing archive cloud library, when all the MediaAgents associated with the primary copy are offline and as a result the index cannot be restored from the primary copy.

This applies to the following cloud storage data:

  • Backup data stored in archive tiers, such as Glacier.

  • Backup data stored in combined storage tiers prior to Feature Release 11.23.

Combined storage tier cloud libraries will receive indexes faster from warm tier. Direct to Cloud Archive Storage recalls will incur the archival recall delay, based on the cloud storage service being used.


From Feature Release 11.23 onwards, for combined storage tiers, index data is stored in the warmer tiers. As a result separate index recalls are not required as the data is readily accessible from the warmer tiers.

Prior to Feature Release 11.23, use the CloudTestTool to recall the metadata and the .idx file permanently to the standard tier. To move existing data, see Permanently Moving Data From One Cloud Storage Tier To Another. You can also change the Storage Class from Archive to Combined Tier for future backups. For more information, see Modifying the Storage Class for an Existing Cloud Library.

To recall the index data, the MediaAgent associated with the Cloud Archive Storage libraries must 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.

If the Index Server is on a different host, make sure that the MediaAgent associated with the Index Server has access to the Cloud Storage library. For more information about adding the Index Server MediaAgent to an existing cloud storage library, see Adding a MediaAgent to an Existing Cloud Storage.