We are planning to start sending our secondary copies to the AWS Cloud and it was recommended that we use a combined storage class, consisting of S3-IA/Glacier storage to accomodate all our data. We have several hundred TBs of data that will need to be copied and we will very infrequently have a need to restore from it. The mass majority of our restores will be satisfied by the primary on-premise copy. It was also recommended that we host the MA/DDB in the Cloud to help with lowering costs. Does this sound like a reasonable configuration based on our needs?
Commvault recommends that we seal the DDB every 8-12 months. Can someone please explain in simple terms why the DDB seal is necessary? I am concerned because with each seal, we will be forced to re-baseline all our data (100's of TBs) and this could take a very long time.
According to the documentation, micro-pruning is supported with a combined storage class. Does this mean that the jobs will be aged/pruned from the Glacier storage object? I thought that was one of the reasons why we had to perform the DDB seal was to help facilitate the pruning as it wouldn't occur without the seal?