A Scale-out Backup Repository with one local extent has been configured as follows.
A daily VMware backup job retention is 31 days, keeping weekly GFS full backups for 14 weeks.
It is Mar, 20. A file from a backup that occurred the week of Jan, 1 must be recovered. Where is the data?
The backup from the week of January 1 must be recovered and today is March 20, which means the backup is older than 21 days but less than 60 days. Since the 'Move backups to object storage as they age out of the operational restore window' option is enabled and set to 21 days in the Capacity Tier, the backup will have already been moved to the capacity tier. The Archive Tier is not enabled, so the data cannot be there. Therefore, the data will be in the capacity tier.
It's A (performance tier) obviously. Archive Tier is not even enabled. It's not in the capacity either because it's not older than 21 day
It is 20/Mar and need the backup on 01/Jan, why it is not older than 21 days?
Oh my mistake, I misread i thought it was Jan...it's C then in the capacity tier
its C, Capacity . its mar 20 not jan 20
Data from 1 Jan on 20 March will be in the Capacity
March 20 is more than 21 days
C capacity tier
Archive tier is NOT EVEN ENABLED.
No comment.
C capacity tier there is no archive tier configured
C capacity tier
C capacity tier
Data from 1 Jan on 20 March will be in the Capacity
why is the answer D, archive tier is disabled.
Why answer is D?
Isn't it B because "copy backup to object storage" is not enabled in the capacity tier?
C capacity tier backups older than 21 days
C, there is no Archive Tier, and Mar 20 is over 21 day after Jan 1. So it moved to Capacity Tier
Answer: C Explanation: Based on the configuration shown in the image, backups older than 21 days are moved to the capacity tier. Since the VMware backup job retention is set for 31 days and keeps weekly GFS full backups for 14 weeks, the backup from the week of January 1st is older than 21 days but within the 14-week GFS retention policy. Therefore, as of March 20, the backup data you need to recover would be in the capacity tier, not on the local performance tier, because it has been offloaded to the object storage configured as the capacity tier to reduce long-term retention costs. Reference: Veeam Backup & Replication Documentation, Scale-Out Backup Repository Configuration
The listed "correct answer" says D. There is no archive tier however. Odd. It is C, as the SOBR is configured for "Move" and the content in question would have been rolled off and the GFS content is only available in the Capacity Tier.
The correct answer is: C. The Capacity Tier. Explanation: Daily retention is 31 days, which means that the daily backups from the week of January 1 have already been deleted. However, weekly GFS backups are retained for 14 weeks. Since it's March (March 20), the weekly backup from the week of January 1 should still be available. In a Scale-out Backup Repository setup, GFS backups are typically copied or moved to the Capacity Tier, which is typically cloud storage (e.g., Amazon S3, Azure Blob Storage). Therefore, the required archive should be in the Capacity Tier.