Existing SOBR with performance tier on a local NAS and capacity tier on an S3 compatible cloud provider. Upgraded from v10 to v11 for AWS Glacier archive tier functionality. When trying to add an archive tier extend there is no archive tier section when editing the SOBR.
Already added a Glacier repository including the required S3 bucket and the proxy appliance
How can I add an archive tier to the existing SOBR?
Is having capacity and archive tiers on different providers not supported?
You can only use archive tier with all amazon. Meaning your capacity tier has to be located on AWS S3 as well. We perform a process to combine the smaller objects stored in s3 to a larger object to store in archive when it’s being transferred to glacier or deep archive. This is done to save costs and improve performance.
Dustin Albertson | Director of Product Management - Cloud & Applications | Veeam Product Management, Alliances
Thanks for responding,
We are looking to have full independent backups archived to Glacier but keep S3 capacity backups on the current separate provider.
Considering that when creating the Glacier repository a S3 bucket is required, Can we upload the backup to the S3 bucket and from there immediately move it to Glacier?
As Dustin said, we change data format before moving backups to Glacier for archiving to make economical sense (otherwise it will be way too expensive due to API costs). So, just moving those millions of relatively small objects from S3 to Glacier is a really bad idea. If I understood you correctly and you wanted to do this yourself.
But if you want Veeam to do this, then we have to manage the whole process end to end (create backups in Performance Tier, then copy/move to Capacity Tier, then move to Archive Tier). You can't have Veeam moving what are effectively "imported" backups from an S3 bucket that you populate yourself via some process.
Thanks for the quick responses.
It seems we will have to go with AWS VTL for Glacier if we want to keep the non-amazon S3 provider. The experience with the AWS VTL in other deployments hasn't been very good so we were eager to implement the new Veeam Glacier integration
