> Expert > Storage > Libraries > Cloud Storage > Planning for Cloud Storage > Planning Archive Storage Tiers

Archive Storage Tier

Commvault supports direct storage to the native archive cloud storage services provided by cloud vendors.

Supported Storage Classes

  • Amazon S3 Glacier Flexible and Deep Archive

  • Alibaba Cloud Object Storage Service Archive

  • Google Cloud Storage Archive

  • Huawei Object Storage Archive

  • Microsoft Azure Storage Archive

  • Oracle Cloud Infrastructure Archive Storage and Archive Storage Classic

Backups

All data is stored in the archive storage tier.

Restores

Recalls from Archive storage tiers are slower as both the metadata (index and deduplication metadata), as well as the actual data, resides in the Archive storage tier. As a result, multiple passes for metadata and the actual data recalls, is initiated. With each pass taking up to 4 to 12 hours, depending on the storage vendor and the amount of recalled data, recalls will be considerably slower.

For more information, see Restoring Data from Archive Cloud Storage.

Copies

Archive storage as a source copy to create a secondary copy is not recommended. But you can create a secondary copy on archive storage using a non-archive storage tier or another data source as the source copy. However, automatic recall is not supported from a secondary copy and data must be manually recalled using the On-Demand recall method.

For this reason, the following agents are not recommended on archive storage: (For a comprehensive list of agents supporting automatic and on-demand recalls, see Restoring Data from Archive Cloud Storage Using a Workflow - Supported Agents.)

  • Exchange Compliance Archiver

  • Exchange Database

  • Exchange Mailbox

  • Exchange Mailbox (Classic)

  • OnePass for Exchange Mailbox (Classic)

  • Active Directory

  • Office 365

    • Exchange Online

    • OneDrive for Business

    • SharePoint Online

    • Teams

Deduplication

Both deduplicated and non deduplicated backups supported.

Deduplication sealing is done automatically to ensure that the data is pruned. By default, DDB will be sealed every 365 days.

Note

For longer retention periods, this value can be manually setup to be half of the retention days. For example, if the retention is set to 4 years, this value can be set to 2 years or 730 days.

Deduplication sealing is set using the following options available in the Deduplication tab in Storage Policy Copy Properties dialog box:

  • Seal and Start new DDB automatically on detection of inconsistency

  • Create new DDB every n days

Loading...