Combined Storage Tier

Commvault's combined storage tier stores a small portion of the frequently accessed indexing and metadata in the warm tiers, while storing a major portion of the actual data in the cold tiers, to provide a simplified, cheaper, and quicker data recalls when needed. By placing frequently accessed indexing and metadata in warm tiers, a recall is as simple as a Browse and Restore operation.

Key Benefits

Combined Storage tier is recommended as it has the following key benefits:

  • Restores using Browse and Restore occur faster, with no index recall delay.

  • Index data can be managed (created, removed) without early deletion charges. (Note that Index data does not follow storage policy retention, so it can be aged sooner.)

  • Recalls are faster on Combined Storage Tier, as the metadata (index and deduplication metadata) resides in the warmer tier. As a result, only one pass for data recall is initiated from the Archive tier.

Supported Storage Classes

Amazon S3

  • S3 Standard / S3 Glacier Instant Retrieval (combined storage tiers)

  • S3 Intelligent-Tiering / S3 Glacier Instant Retrieval (combined storage tiers)

  • S3 Standard-Infrequent Access / S3 Glacier Instant Retrieval (combined storage tiers)

  • S3 One Zone-Infrequent Access / S3 Glacier Instant Retrieval (combined storage tiers)

  • S3 Standard / S3 Glacier Flexible Retrieval (combined storage tiers)

  • S3 Intelligent-Tiering / S3 Glacier Flexible Retrieval (combined storage tiers)

  • S3 Standard-Infrequent Access / S3 Glacier Flexible Retrieval (combined storage tiers)

  • S3 One Zone-Infrequent Access / S3 Glacier Flexible Retrieval (combined storage tiers)

  • S3 Standard / S3 Glacier Deep Archive (combined storage tiers)

  • S3 Intelligent-Tiering / S3 Glacier Deep Archive (combined storage tiers)

  • S3 Standard-Infrequent Access / S3 Glacier Deep Archive (combined storage tiers)

  • S3 One Zone-Infrequent Access / S3 Glacier Deep Archive (combined storage tiers)

Microsoft Azure Storage

  • Hot/Archive (combined storage tiers)

  • Cool/Archive (combined storage tiers)

Alibaba Cloud Object Storage Service

  • Standard/Archive (combined storage tiers)

  • Infrequent Access/Archive (combined storage tiers)

Huawei Object Storage Cloud

  • Standard/Archive (combined storage tiers)

  • Infrequent Access/Archive(combined storage tiers)

Oracle Cloud Infrastructure Object Storage

  • Standard/Archive (combined storage tiers)

  • Infrequent Access/Archive (combined storage tiers)

Backups

Commvaults combined storage tiers works by placing Commvault metadata used in both deduplication and non-deduplicated backups in the warmer or frequent access tiers. This allows you to perform a simple Browse and Restore of the archival data, without the delay of a cloud archive storage recall.

As a result, more than 90% of the backup data gets stored in the Archive tier, while only up to 10% of the data is stored in the warmer tiers.

  • Deduplicated and non-deduplicated data is supported in Commvault combined storage tiers.

  • For deduplicated data, the backup indexes and deduplication metadata is stored in the warmer tier.

  • For non-deduplicated data, the backup index is stored in the warmer tier.

Backup Sizing

While Cloud Storage services typically grow forever, for planning purposes, the following ratios can be used when sizing your cloud storage for archival use-cases:

  • 10% of backup data stored will reside in warm tier

  • 90% of backup data store will reside in cold tier

These figures refer to data after deduplication and compression (if used).

Restores

Restores from combined storage tiers require no additional steps. Simply Browse your data, select the data to restore, and then click Restore.

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

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.

You can set Deduplication sealing using the Create new DDB every n days option available in the Deduplication tab in Storage Policy Copy Properties dialog box.

Loading...