our documentation around combined storage tiers in cloud could be a bit misleading around sizing for Warm and archive tier storage requirements.
See in red below.
what’s the ideal ratio to size? (or do we need to just go 10% on warm tier to be safe?)
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.
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:
3% of backup data stored will reside in warm tier
97% of backup data store will reside in cold tier
These figures refer to data after deduplication and compression (if used).
It’s advised to follow the Backup Sizing ratio guidelines, 3% for data residing in Warm and 97% in Cold.
For some individual jobs we can see indexes/metadata consuming more data than others in the warm tier, but the overall average for all jobs in the bucket should follow the above ratio.