Possible to "mirror" backup data on Exagrid and AWS Glacier Deep Archive (without using Standard S3)

[hofmannb@cna.org]

We recently upgraded to 12.2 in order to test out the ability to backup directly to AWS S3 Glacier, without first needing to upload to S3 Standard. However, we are a bit confused on the best way to configure this.

We want to keep 6 months of data on both our Exagrid and AWS Glacier (the same backup data on both). The thinking being we would regularly restore from the Exagrid, and AWS Glacier would only be needed for Disaster Recovery, but we still want recent backup data on both.

Our confusion comes in the best way to essentially have 6 months of backup information on both the Exagrid and AWS. It seems like in setting up the job it just wants to age out from the Exagrid to AWS, but we want to keep it in both places.

We looked at a Backup Copy job, but we want to ensure we're not duplicating backup data on the Exagrid, and we were not sure how/if we can have the copy job immediately move the data to AWS, and then remove the copy job data from the Exagrid. But if we have to have duplicate data on the Exagrid for this to work that is a workable alternative, just not ideal, as it will limit overall storage capacity on the Exagrid.

[sfirmes]

I wrote this blog which might help: https://community.veeam.com/blogs-and- ... art-6-6123

It explains how to use GFS backups and the archive tier.

[veremin]

AWS S3 Glacier can only be used as an Archive Tier. In the Archive Tier, you can store only outdated standalone restore points (such as GFS, exported, VeeamZIP, etc.). In other words, you won't be able to achieve your scenario of having identical copies of data in both Exagrid and Glacier repositories.

If you are interested in making copies, you should use the Capacity Tier. As the Capacity Tier, you can utilize AWS S3. To save on storage costs, you can enable the Standard Infrequent Access or One Zone-Infrequent Access storage class in the repository settings.

Thank you.