Configuration to limit backup storage on S3 (and keep backups on Exagrid and Glacier Archive)

[hofmannb@cna.org]

We have been testing out different backup strategies for the past few months, which led to the following backup configurations:

1. SOBR: Performance Tier - Exagrid, Capacity Tier - AWS S3, Archive Tier - AWS Glacier Archive
2. Standard Backup Job to Exagrid, then Backup Copy job: Performance Tier - AWS S3, Archive Tier - AWS Glacier (no Capacity Tier)

However in both instances the S3 storage is holding weeks worth of backups, which is racking up massive costs. Our end goal is to have 6 months of backups on our Exagrid, 1 year of backups on our AWS Glacier Archive, and the minimal amount of backups on S3 (ideally we only want backups there long enough to move to Glacier, then be removed).

Is someone able to provide documentation, or other assistance, on the best way to accomplish this goal? We have entered a ticket, which led to us trying the Backup Copy job method, but as that is not working I wanted to posted on here to see if anyone has found a better solution. Thank you in advance!

[HannesK]

Hello,
and welcome to the forums.

I would recommend to wait for the next version (12.2) instead of trying to optimize something with any other V12 version. Watch out for the release notes once they are published

Best regards,
Hannes

[hofmannb@cna.org]

Hi Hannes,

Thank you for the reply, I am now quite interested to see what 12.2 has in store. Would you happen to have any estimate as to when it may be coming out? Having a timeline will definitely help us determine how much time/effort to spend getting things working in our current version. Thank you again!

[HannesK]

ah sorry... yes Q3 is the plan.

In 12.1 you can only move "as fast as possible" from capacity tier. There is no way to go directly from performance tier to Archive tier except for within Azure / AWS

[hofmannb@cna.org]

Thank you again!

One question, you state "There is no way to go directly from performance tier to Archive tier except for within Azure / AWS", is there documentation on how that can be done within AWS? If we need to do that manually as a hold-over until the next update that may still be better that our current situation.

[HannesK]

Hello,
there is some documentation here.

You just skip the "capacity tier" in the Scale-Out-Repository wizard.

Best regards,
Hannes