one of our customers (running CV11.24.43) is interested in configuring a Selective Copy to Amazon S3 Standard-IA/Deep Archive (Combined Storage Tier). So far, no problem.
We intend to copy Monthly Fulls. Basic retention will be 365 days and Yearly Fulls will get extended retention set to 10 years.
Also, they want to lock the objects to prevent them from being deleted before the retention is met. The “Enable WORM Storage” workflow should take care of that.
But it does raise a few questions:
- Would you recommend using Deduplication in this scenario, or not?
- If we use Dedupe, I suppose a DDB seal will take place automatically ever 365 days, right?
- In this combined storage tier, metadata is written to Standard-IA, and actual backup data is stored in the Deep Archive tier, right? Do we set the object-level retention on both tiers?
- Retention of Index V2 backups does not follow the Storage Policy settings, and might be pruned earlier than the configured retention on the Storage Policy. What object-level retention does the software set on Index V2 backups if they are written to the same Storage Policy as the backup data?
- If we would write Index V2 backups to the Standard-IA tier, should we expect early-deletion fees because we’re only keeping the last (3, I believe) backups of each Index? Or is there any way to alter the Index V2 backup retention?
Thanks in advance for any answers!
Best answer by OrazanView original
Good morning. I will attempt to answer your questions in order:
@Orazan, thanks for your quick reply. And they do answer some of my questions.
In SP26 we will set the retention on each object, prior to that, it is relying on the bucket default retention set to 2x the Storage Policy retention.
If they would like to get these jobs to age quicker, they can set the Additional Setting to increase the frequency of backups:
Name : CHKPOINT_ENFORCE_DAYS Category: Indexing Type: Integer Value : Name : CHKPOINT_ENFORCE_DAYS Category: Indexing Type: Integer Value :