VEEAM VMCE_V12 Practice Test - Questions Answers, Page 3

To meet the stringent Recovery Time Objective (RTO) of 4 hours and Recovery Point Objective (RPO) of 1 hour for the two critical applications, the most suitable approach is to use a combination of backup copy jobs and hourly VM replication, which corresponds to answer C. Backup copy jobs can ensure that backups are available offsite for disaster recovery purposes, while VM replication provides the ability to quickly failover to a replica VM in case of a primary VM failure, thereby minimizing downtime. Veeam's replication capabilities are designed to create exact copies of VMs at regular intervals, which can then be rapidly activated in case of a failure. This strategy ensures that the applications can be brought back online within the 4-hour RTO, with data loss not exceeding the 1-hour RPO, thus meeting the company's stringent data protection requirements for these critical applications.

Veeam Cloud Service Providers (VCSPs) are equipped to offer a range of services designed to extend Veeam's data protection capabilities to the cloud, enhancing the flexibility and reliability of backup and disaster recovery strategies for Veeam's customers. The two service offerings that align with VCSP capabilities are:

A) Backup as a Service (BaaS) - This service allows Veeam customers to offload their on-premises backup operations to the cloud, leveraging cloud resources for storage and management of backups. BaaS simplifies backup processes, reduces the need for extensive on-premises infrastructure, and provides an added layer of data protection and accessibility.

E) Disaster Recovery as a Service (DRaaS) - DRaaS extends beyond basic backup services to offer a more comprehensive disaster recovery solution. It ensures not only the availability of backups but also the capability to rapidly restore and run critical workloads in the cloud in the event of a disaster, minimizing downtime and ensuring business continuity.

These services leverage the robust capabilities of Veeam Backup & Replication, tailored for cloud environments, to offer scalable, efficient, and secure data protection solutions.

When moving the Veeam Backup & Replication server and its configuration database to new hardware or servers, the appropriate process to undertake is a configuration restore, denoted by option A: Restore. This process involves using the Veeam Backup & Replication Configuration Backup utility, which regularly backs up the configuration of the Veeam Backup & Replication server. In the event of a hardware migration or significant system change, this utility allows administrators to restore the server's configuration, including all settings, job configurations, and inventory, onto the new server setup. This ensures a seamless transition with minimal disruption to the backup operations and policies that were previously in place.

The correct approach for backing up Hyper-V VMs to tape in a ransomware protection strategy is to create media pools first and then configure backup to tape jobs. This method ensures organized and efficient tape management while securing VM backups on tape media.

Reference: Veeam Backup & Replication User Guide, Veeam Tape Backup Configuration Guide

Veeam Data Platform can achieve image-level backups for Solaris workloads. This means it can create a complete backup of the system at the image level, capturing the entire state of the Solaris system, including the operating system, applications, and data.

Reference: Veeam Data Platform Documentation, Veeam Solaris Backup Guide

To ensure that the VM data remains encrypted throughout the backup process, the job should be configured to use the proxies with the NBDSSL (Network Block Device SSL) transport mode. This mode encrypts data transferred over the network, adhering to the company policy that prioritizes data security. While DirectSAN Access is fast, it does not provide encryption of in-flight data.

Reference:

Veeam Backup & Replication User Guide: Transport Modes

Veeam Best Practices: Securing Backup Traffic

To grant MS SQL DBAs the ability to restore their databases without giving access to other operations, the appropriate action is to give the DBA group Restore Operator access specifically to MS SQL databases within Veeam Enterprise Manager. This role-based access control allows DBAs to perform the needed restores while restricting access to other functionality.

Reference:

Veeam Backup & Replication User Guide: Role-Based Access Control

Veeam Enterprise Manager Guide: Delegating Restore Operations

Given the proxy load of 68% and all other loads (source, network, target) at 0%, the bottleneck is at the proxy. To decrease the backup processing time and accommodate the growth of the environment, adding additional Windows or Linux machines as backup proxies would help distribute the load. This would enable parallel processing and reduce the time taken to complete the backup jobs, thereby helping to meet the RPOs.

Veeam Backup & Replication User Guide: Backup Proxy

Veeam Help Center: Managing Backup Proxies

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.

Reference: Veeam Backup & Replication Documentation, Veeam Backup & Replication Best Practices Guide