A Veeam engineer creates a Scale-Out Backup Repository (SOBR) that uses AWS S3 as the Performance Tier. The backup job is configured to “Keep monthly full backups for: 12 months”. The engineer wants the backups to move to Glacier after 90 days.
What should the engineer do first to achieve this goal?
To move backups to Glacier after 90 days, the engineer should add an Archive Tier with the appropriate Bucket from S3. The Archive Tier is designed to facilitate the movement of data to long-term storage solutions such as AWS S3 Glacier. This tier can be added to a Scale-Out Backup Repository that already uses AWS S3 for the Performance Tier without needing to add a Capacity Tier first.
Correct Answer is C base on VEEAM Documentation: https://helpcenter.veeam.com/docs/backup/vsphere/archive_tier.html?ver=120 Archive tier is an additional tier of storage that can be attached to a scale-out backup repository. You can transport data to the archive tier for archive storage from the following extents: From performance extents that consist of Amazon S3, Microsoft Azure or S3 compatible with data archiving object storage repositories. From capacity extents. ************************* It is not required to have a capacity tier before using archive tier
I read Veeam Documentation and It seems correct
This is correct - tested in lab. You are able to enable archive tier without capacity tier when using S3 in the performance tier.
This is correct - tested in lab. You are able to enable archive tier without capacity tier when using S3 in the performance tier.
Definitivamente, C es la correcta. https://helpcenter.veeam.com/docs/backup/vsphere/archive_tier.html?ver=120
Quise decir B según la documentación https://helpcenter.veeam.com/docs/backup/vsphere/archive_tier.html?ver=120
Archive tier is an additional tier of storage that can be attached to a scale-out backup repository. You can transport data to the archive tier for archive storage from the following extents: From performance extents that consist of Amazon S3, Microsoft Azure or S3 compatible with data archiving object storage repositories. From capacity extents.
Archive tier is an additional tier of storage that can be attached to a scale-out backup repository. You can transport data to the archive tier for archive storage from the following extents: From performance extents that consist of Amazon S3, Microsoft Azure or S3 compatible with data archiving object storage repositories. From capacity extents.
Base on documentation C is correct
This is correct - tested in lab. You are able to enable archive tier without capacity tier when using S3 in the performance tier.
Keep monthly full backups for: 12 months and move to Glacier after 90 days Archive Tier can do it
Is B, expaantion; In Veeam Backup & Replication, to utilize AWS S3 Glacier for long-term storage, the AWS S3 must first be added as a Capacity Tier within the Scale-Out Backup Repository (SOBR). This step is necessary before backups can be moved to Glacier. Once S3 is established as the Capacity Tier, the policies for moving backups to Glacier can be configured based on the retention requirements (in this case, after 90 days). This approach ensures that the monthly full backups are initially stored in S3 and then offloaded to Glacier for cost-effective long-term retention. Reference: Veeam Documentation: Scale-Out Backup Repository Veeam Help Center: AWS S3 as Capacity Tier and Archive Tier Configuration
May be B
going for B
I think B, you need to first configure capacity tier to enable Archive tier in SOBR
No, you can go directly from performance to archive tier. From performance extents that consist of Amazon S3, Microsoft Azure or S3 compatible with data archiving object storage repositories. From capacity extents.
Add AWS S3 as a Capacity Tier: Before using Glacier
Capacity Tier is needed before you can enable Archive Tier
going for C
archive tier can be configured without need for capacity tier, so answer is C
Options A, B, and D are not the first steps necessary for achieving this goal: Option A: Creating a Vault in S3 Glacier is not directly managed from Veeam. Veeam interacts with Glacier through the Archive Tier in the SOBR. Option B: Adding AWS S3 as a Capacity Tier is a prerequisite but not the first action needed if the Capacity Tier is already set. You need the Archive Tier to facilitate moving data to Glacier. Option D: Reconfiguring the SOBR to use block storage as the Performance Tier is not relevant to the requirement of moving data to Glacier. Therefore, the correct initial step is: C. Add an Archive Tier with the appropriate Bucket from S3.
Glacier is an archive storage. You can not configure an SOR with Performance and Archive tier only. So you first need Capacity tier to use archive tier in the next step. So IMO the Answer is B
AWS S3 should be the first added as a capacity level within the Scalable Backup Repository (SOBR). This step is required before backups can be moved to Glacier.
S3 is already in place as perf tier. No capacity tier required to push to archive tier.
answer c is correct
C is what an VEEAM engineer needs to do. A is what a Cloud Engineer has to do
You don't require a capacity tier to move from performance to archive
C. Add an Archive Tier with the appropriate S3 bucket 🔹 Explanation: In Veeam, S3 is not used as a Performance Tier, but rather as a Capacity Tier. The Performance Tier must be local or cloud storage with fast access (such as a NAS or local disk).