The Veeam Certified Engineer v12 (VMCE_v12)

When starting an on-demand lab from backup files for mission-critical VMs, the appropriate SureBackup feature to configure is A: Application Group. An Application Group in Veeam Backup & Replication is a predefined group of VMs that are started together in the SureBackup job. This feature is designed to ensure that interdependent VMs, such as those comprising a multi-tier application, are started in a sequence that respects their operational dependencies, allowing for comprehensive verification and testing. The Application Group can include the mission-critical VMs and any associated VMs required for the application environment to function correctly, ensuring that all components are available and interact as expected within the isolated on-demand lab environment. This setup facilitates effective testing or troubleshooting in a manner that closely mirrors the production environment without impacting live operations.

Recovery Point Objective (RPO) refers to the maximum acceptable amount of data loss measured in time. It is essentially the age of the files that must be recovered from backup storage for normal operations to resume after a failure or disaster. In other words, it defines the data loss tolerance of a business unit or organization. If an RPO is set to one hour, the system must back up at least every hour to meet the RPO. References:

Veeam Documentation: Recovery Point Objective (RPO)

Veeam Backup & Replication User Guide: RPO and Recovery Time Objective (RTO) Definitions

A failover plan in Veeam Backup & Replication allows you to define the order in which VMs are started during a failover operation. It can include startup delays for certain VMs, ensuring that some VMs can be configured to start after a defined time delay. This meets the requirement of having some replicated VMs start on a time delay. References:

Veeam Backup & Replication User Guide: Failover Plans

Veeam Help Center: Creating Failover Plans

To meet the requirements of setting up a Scale-Out Backup Repository (SOBR) with immutability for malware protection and specific retention policies, the most fitting configuration is D: Copy and move mode with a Performance Tier configured on a Linux Hardened Repository using the XFS file system and immutability set for 21 days, and a Capacity Tier on Amazon S3 with immutability set for 60 days. This setup utilizes the copy and move mode to ensure that backups are first stored on the on-premises Linux Hardened Repository with an immutability setting that prevents modifications to backups, providing protection against malware for the most recent 21 days of backups. As this on-premises server has limited capacity, older backups beyond 21 days are moved to the Capacity Tier in Amazon S3, where they are also protected with immutability for the entire 60-day retention period. This configuration leverages the strengths of both on-premises and cloud storage while ensuring that all backups are protected from modification or deletion by immutability, aligning with the customer ' s malware protection concerns and retention requirements.

In Veeam Backup & Replication, to meet the business requirements of having both the database backup and transaction logs stored at a secondary location, a Backup Copy Job can be configured. The Backup Copy Job can be set to include both the VM backup and the transaction logs, ensuring that the database ' s recovery points are consistent and available at the DR site. The transaction logs backup every 30 minutes can be specified as the source for the Backup Copy Job, ensuring that the transaction log backups are also copied to the secondary repository.

To meet the 1-hour RPO for the databases within the VM, while only being able to snapshot the VM once per day, the best strategy is to enable regular transaction log backups (option A) and process transaction logs with the job (option E). This setup allows the system to capture changes in the SQL Server transaction logs at intervals less than the RPO requirement, without needing to snapshot the entire VM more frequently. References: Veeam Backup & Replication Documentation, Veeam Backup & Replication Best Practices Guide

To meet the specified requirements, configuring a backup copy job in periodic copy (pruning) mode with 62 days of retention and six monthly Grandfather-Father-Son (GFS) restore points is the best approach. This setup allows for daily backups for up to two months and weekly backups for up to six months, aligning with the desired restore capabilities. References: Veeam Backup & Replication User Guide, Veeam GFS Retention Policy Explanation

For Hyper-V environments where VMs are stored on local storage, the On-host backup proxy should be used. This type of proxy processes jobs directly on the host where the Hyper-V role is enabled, allowing it to interact directly with the local VM storage. It is suitable for infrastructures with multiple Hyper-V servers storing VMs locally. References:

Veeam Backup & Replication User Guide: Hyper-V On-Host Proxy

Veeam Best Practices: Hyper-V Backup Proxies

To enable backup from storage snapshots with a Nimble Array, it is necessary to add the storage system to the Veeam Backup & Replication console ' s Storage Infrastructure. This allows Veeam to interact with the Nimble Array and orchestrate the creation of storage snapshots, which can then be used for backups. Simply enabling the backup from storage snapshots option in the job is not enough; the array itself must be integrated into the Veeam infrastructure. References:

Veeam Backup & Replication User Guide: Integration with Storage Systems

Veeam Best Practices: Nimble Storage Snapshot Integration