I have just implemented some AWS Combined Tier copies for LTR data to move away from data being retained Long Term on Standard Tier. Everything working as expected and looks to be tiering fine. The V2 Index backups get selected to the new copies which I believe from the documentation it is meant to do when more than one copy is available. My question is however do/should these ‘Big Data Apps’ jobs get tagged to the Standard-IA tier as under most circumstances (3 index backup copies available criteria has been met), the jobs will age off in a short period breaking the minimum retention for the class. From the view I get in the Cloud Explorer Tool it does seem to be held on ‘Standard-IA’ but I can’t find any specific reference or confirmation in Documentation.
For Combined Tier Storage we keep Index and Metadata in the hot tier for easy and fast access. Data blocks are transferred to the Archive Tier to save on costs and only retrieved only when needed for a restore.
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.
For Combined Tier Storage we keep Index and Metadata in the hot tier for easy and fast access. Data blocks are transferred to the Archive Tier to save on costs and only retrieved only when needed for a restore.
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.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
