Pass VMCE_v12 Exam Guide

In a scenario where backups need to be sent from Site B to a repository at Site A and the direct backup cannot complete within the backup window due to connection limitations, a Backup Copy Job is the most suitable type of job. The Backup Copy Job can transfer data efficiently and with reduced impact on the production environment. The components involved would be:

• 6 (Repository at Site B): Where the initial backups are stored.
• 4 (WAN Accelerator at Site A): To optimize the data transfer over the WAN.
• 3 (WAN Accelerator at Site B): To prepare the backup data for transfer.
• 2 (Repository at Site A): The target repository for the backup copies. This configuration leverages the WAN Accelerators to reduce the amount of data that needs to travel over the WAN, thus allowing the backup copy job to complete within the available window.

When implementing a backup copy strategy for unstructured data backups with additional retention, a File Share Copy job is the correct configuration. This type of job is designed to copy backups of file shares to a secondary location, which in this case would be the alternate site. It allows for the setting of additional retention days beyond the original backup retention policy.References:

• Veeam Backup & Replication User Guide: File Share Backup and Copy
• Veeam Knowledge Base: Configuring File Share Copy Jobs

The Veeam Plug-in for Oracle RMAN is designed specifically for efficient backup and recovery of Oracle databases. It allows for direct integration with Oracle RMAN (Recovery Manager), ensuring that the backups are consistent and reliable. For a photography company that relies heavily on an Oracle database with new photos being continuously added, this feature provides an ideal solution. The daily backup of the database ensures that all new content is secured regularly, while the 15-minute interval for archived redo logs ensures that any recent transactions are also protected. This approach aligns well with the company's requirement to protect only the database.References:

• Veeam Documentation: Veeam Plug-in for Oracle RMAN
• Veeam Help Center: Oracle RMAN Backup and Recovery

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.References:

• Veeam Documentation: Scale-Out Backup Repository
• Veeam Help Center: AWS S3 as Capacity Tier and Archive Tier Configuration