MENU
An engineer is using Veeam Backup and Replication v12.
The only backup repository is a Microsoft Windows server with direct attached Fibre Channel storage array.
The engineer realizes that none of their backups are immutable. A second copy of the backup on a different site and a different media is required.
Which option should be used to provide immutable backups on a secondary site with a different media?
To provide immutable backups on a secondary site with a different media, the best option given the context is B: Create a Scale Out Backup Repository (SOBR) with the existing Microsoft Windows Server as the performance tier and an AWS S3 bucket with immutability enabled as the capacity tier.
This approach involves leveraging the existing backup infrastructure (Microsoft Windows Server with direct-attached storage) as the performance tier of the SOBR, where the most recent backups are stored for fast access. For long-term storage and immutability, backups can be offloaded to an AWS S3 bucket configured with Object Lock. The Object Lock feature in AWS S3 provides an additional layer of data protection by making the backup data immutable, meaning it cannot be deleted or modified for a specified duration. This setup ensures that backup data is protected against accidental deletion, ransomware, and other malicious activities.
By implementing this configuration, the engineer can achieve the desired level of data protection and immutability, utilizing cloud storage as a secure and scalable secondary backup location, distinct from the primary on-premises storage media.