Veeam VMCE_v12 Veeam Certified Engineer v12 Exam Practice Test

After completing a planned failover for VMs to the disaster recovery site, the typical actions available in Veeam Backup & Replication for a failover plan are:

• Undo: This allows you to reverse the failover and return the VMs to the original location.
• Start: This would be used to initiate the failover plan if it needs to be executed again.
• Edit: This option permits modifications to the failover plan.
• Delete: This allows the removal of the failover plan if it is no longer needed. There are no options for Copy in the context of a failover plan, and the Cancel option is typically available before and during the failover process, not after completion.

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

• Veeam Backup & Replication User Guide: Role-Based Access Control
• Veeam Enterprise Manager Guide: Delegating Restore Operations

To avoid running out of space when moving backups to a new repository, the "Move backup..." function in Veeam Backup & Replication should be used. This function allows you to relocate backup files to a new repository without duplicating data, which can save space. Unlike a simple copy action, the move function ensures that the backup chain remains intact and does not require additional space for a copy of the backups during the transfer. When the move is initiated, Veeam will also automatically update the configuration to point to the new backup location, thus preventing any disruptions in the backup chain.

Veeam provides agentless backup solutions for several public cloud infrastructures, among which AWS (Amazon Web Services) and Microsoft Azure are the prominent platforms supported. Thus, the correct answers are A: AWS and E: Microsoft Azure.

• For AWS, Veeam offers Veeam Backup for AWS, an agentless solution designed to protect AWS workloads by leveraging native AWS technologies. This solution allows for the backup and recovery of AWS EC2 instances without the need for agents inside the instances, providing efficient and flexible cloud-native data protection.
• In the case of Microsoft Azure, Veeam Backup for Microsoft Azure provides a similar agentless data protection capability, allowing for the backup and recovery of Azure VMs. This solution also utilizes native Azure technologies to facilitate seamless integration and management of backups within the Azure ecosystem.

These solutions are designed to provide comprehensive data protection for cloud workloads, simplifying management while ensuring robust backup and recovery capabilities in these public cloud environments.

The 3-2-1 backup strategy is a best practice that suggests having three total copies of your data, two of which are local but on different devices or media, and one copy offsite. In the described scenario, although there is an offsite component (SOBR with AWS S3 Performance Tier), and a local hardened immutable repository, there is no indication of a second local copy on a different device or media. This means that there is only one local copy of the backup data and one offsite copy. Therefore, the setup does not meet the 3-2-1 best practices requirement, which would involve having at least one more local copy on different media or device.

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

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.

Veeam Backup & Replication offers the capability to assign location tags to different components within the backup infrastructure, including vCenter servers. This feature is particularly useful for GDPR compliance, as it allows administrators to specify the physical location of the data processed and stored within vCenter servers, helping to ensure that data sovereignty and regulatory requirements are met.References:

• Veeam Backup & Replication User Guide: Location Tagging for GDPR Compliance
• Veeam Help Center: GDPR Compliance and Data Location Controls

The fastest way to bring a corrupted data drive back online with the least disruption in a VMware environment is through Instant Disk Recovery. This feature allows the administrator to quickly restore the specific affected disk from a backup, minimizing downtime and impact on business operations.References: Veeam Backup & Replication User Guide, Veeam Instant Disk Recovery Guide

In Veeam ONE, the remaining capacity of each backup repository server can be viewed under the Data Protection View. This section provides detailed information about the storage utilization and remaining capacity of backup repositories, allowing administrators to effectively monitor and manage storage resources.References: Veeam ONE User Guide, Veeam ONE Data Protection View Documentation

For backing up a 3-node Microsoft SQL Always On cluster running in a VMware environment with the specified Recovery Point Objectives (RPOs), the most suitable option is A: Veeam Backup and Replication - Create a VMware backup job, include the 3 nodes of the cluster. Use Application-Aware Processing to back up the transaction logs every 15 minutes. This approach allows for the entire SQL cluster nodes to be backed up as part of a regular VM backup job, which satisfies the 1-day RPO for the cluster nodes. The Application-Aware Processing feature of Veeam Backup & Replication ensures that the SQL databases are in a consistent state during backup. Moreover, this feature allows for the transaction logs to be backed up separately at a more frequent interval, in this case, every 15 minutes, meeting the 15-minute RPO requirement for the log files. This dual approach ensures comprehensive protection for both the SQL cluster nodes and the critical transaction logs, aligning with the specified RPOs.

To ensure that a backup job includes both the virtual machine's disk files and the Microsoft SQL database transaction logs, Application-aware processing should be used. This feature enables Veeam Backup & Replication to create transactionally consistent backups of VMs running VSS-aware applications like Microsoft SQL Server, ensuring that both the VM disks and the SQL transaction logs are properly backed up.References: Veeam Backup & Replication User Guide, Veeam Application-Aware Processing Guide

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

To dynamically include VMware VMs with a custom application installed in a backup job, the most efficient approach is C: Create a backup job based on vSphere tags. VMware vSphere tagging allows administrators to assign metadata to VMs, making it easier to categorize and manage them according to various criteria, such as application type, department, or any custom criteria relevant to the organization. Veeam Backup & Replication can leverage these tags to dynamically include VMs in backup jobs. By setting up a backup job to include VMs tagged with a specific identifier related to the custom application, any VM tagged accordingly will be automatically included in the backup job. This approach simplifies management, ensures consistency, and allows for the flexible and dynamic grouping of VMs based on changing criteria without the need for manual adjustments to the backup job configuration.

To meet the new regulatory requirements, enabling immutability on both the NAS and Amazon S3 is essential. Immutability prevents backup files from being deleted or modified, aligning with the requirement to protect the most recent 31 days of backup files. By enabling this feature on the NAS and Amazon S3, the business ensures that both local and offsite copies of their data are secure and compliant with the regulation. The other options do not directly address the new requirements of preventing deletion or modification of backup files.References:

• Veeam Documentation: Immutability Settings
• Veeam Help Center: Configuring Amazon S3 Immutability

In the context of disaster recovery, the Recovery Point Objective (RPO) is best defined by option B: The acceptable data loss measured in time that can be tolerated. RPO is a critical metric in disaster recovery and business continuity planning that specifies the maximum amount of data (measured in time) that an organization can afford to lose in the event of a disaster or system failure. It effectively sets the limit for how frequently data backups or replications should occur. For instance, an RPO of 4 hours means that the organization must be able to recover data from no more than 4 hours prior to the disaster, implying that backup or replication operations should occur at least every 4 hours. Establishing an RPO is essential for developing an effective data protection strategy, as it guides the choice of backup methodologies and technologies to meet the organization's tolerance for data loss.

Veeam ONE is a monitoring and reporting tool for Veeam Backup & Replication, as well as virtual environments like VMware vSphere and Microsoft Hyper-V. In Veeam ONE, you can monitor the capacity of VMware datastores by using the "Infrastructure View". Within this view, there is a specific group for "Datastores" which provides comprehensive information, including the capacity and free space available on each datastore. This feature is designed to help administrators manage storage effectively and ensure they are alerted before reaching critical capacity limits. The "Infrastructure View" provides a more direct and focused way to monitor resources like datastores compared to "Business View", which is typically used for categorizing and viewing the infrastructure based on business needs, rather than direct resource monitoring.

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

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.References: Veeam Backup & Replication User Guide, Veeam Tape Backup Configuration Guide

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.

To solve the space issue while enabling GFS retention, the engineer should add an Object Storage as a Capacity tier to the Scale-Out Backup Repository (SOBR) and set the policy to move backups that are older than 14 days. This approach allows for efficient use of local NAS storage for short-term retention and leverages object storage for long-term archival purposes.References: Veeam Backup & Replication User Guide, Veeam SOBR Configuration Guide

Veeam Plug-ins for Enterprise Applications provide a transactionally consistent backup of databases and their database logs. This ensures that the backup is not only complete but also consistent at a transactional level, capturing all transactions up to the point of the backup. This is crucial for databases to ensure data integrity and consistency when restored.References: Veeam Plug-ins for Enterprise Applications Guide, Veeam Database Backup Best Practices

The purpose of a Cache Repository when adding a file share in Veeam Backup & Replication is D: To store temporary metadata and track all objects that have changed. When Veeam Backup & Replication backs up data from file shares, it uses the Cache Repository to store metadata related to the files and directories on the share. This metadata includes information about file versions, change logs, and the structure of the file share, which is essential for efficient backup operations, incremental backups, and restore operations. The Cache Repository plays a crucial role in tracking changes between backup jobs, enabling Veeam to perform quick incremental backups by only processing the data that has changed since the last backup, thereby optimizing backup performance and reducing network and storage load.

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

• Veeam Backup & Replication User Guide: Transport Modes
• Veeam Best Practices: Securing Backup Traffic

Using the Veeam Guest OS File Restore wizard, files or folders can be restored to a valid UNC (Universal Naming Convention) path. This means that the director's folder can be restored to any network location that the Windows VM has access to, as long as it's specified in the UNC format, such as \\Server\SharedFolder. This allows for the flexibility of restoring the data to a different location than the original one.References:

• Veeam Backup & Replication User Guide: Guest OS File Recovery
• Veeam Help Center: Restoring Guest OS Files

When integrating a Data Domain deduplication appliance with Veeam Backup & Replication, it is typically used as a backup repository. The backup server may need to take on the gateway role, especially if the Data Domain is integrated over NFS or CIFS. This means that the backup server will be responsible for processing the data flow between the Veeam proxies and the deduplication appliance. If the gateway server (backup server) is not well-resourced, this additional workload can cause an increase in resource consumption on the backup server. The appliance's resources and the SSL certificate are not related to increased resource consumption on the backup server, and simply needing additional resources for deduplication (D) is not specific enough without indicating the gateway role.

In a scenario where a customer needs to recover from Wasabi's Cloud due to local backups becoming unavailable, the method that would provide the fastest Recovery Time Objective (RTO) while allowing users to interact with the recovered system as quickly as possible is D: Instant Recovery to local VMware VM. Veeam's Instant Recovery feature allows for the restoration of a backup directly into the production environment without the need to fully copy the backup data. When recovering from cloud storage like Wasabi, the backup data will be streamed on-demand to the local VMware environment, allowing the VM to start running immediately while the remaining data is transferred in the background. This method minimizes downtime and provides the quickest path to operational recovery, ensuring users can access the recovered system with minimal delay. It's important to note that the effectiveness of this approach depends on the available bandwidth and the size of the data being recovered.

Before creating a NAS backup job, an engineer must add the NAS file share to the Veeam Backup & Replication (VBR) console under the Inventory section. This involves specifying the NAS Filer and the particular file share to be protected. This step allows Veeam to recognize the file share as a valid source for backup operations.References:

• Veeam Backup & Replication User Guide: NAS Backup
• Veeam Help Center: Adding File Shares to Inventory

A planned failover is a process that allows for the seamless switching from the original VMs at Site A to their replicas at Site B with no data loss. This is the correct course of action when a power outage is expected, as it is a controlled process that ensures that all data is synchronized before the switch is made. This action minimizes data loss and ensures that the VMs on Site B are up-to-date.References:

• Veeam Backup & Replication User Guide: Failover and Failback
• Veeam Help Center: Planned Failover Procedure

To achieve the goal of recovering a single SQL Database in a consistent manner with minimal impact on the production environment during production hours, while allowing for granular restores through the Veeam console, the engineer should A: Schedule transaction log processing every 30 minutes. By enabling application-aware processing for the SQL VM and scheduling the main backup job to run every 24 hours, the base image of the SQL database is protected. However, to achieve a more granular Recovery Point Objective (RPO) and ensure the ability to restore to specific points in time, transaction log backups must be performed more frequently. Configuring the backup job to process transaction logs every 30 minutes captures the SQL database changes more frequently without the overhead of a full backup, allowing for point-in-time restores directly from the Veeam console without the need for SQL Management Studio (SSMS) or a Database Administrator (DBA). This setup aligns with the goals of maintaining operational efficiency and minimizing the impact on production while ensuring robust data protection capabilities.

For deploying the Veeam Agent on Amazon EC2 instances running Windows and Linux operating systems without direct network access from the Veeam Distribution Server, the appropriate type of Protection Group to use is D: Cloud machines. The "Cloud machines" protection group type in Veeam Backup & Replication is specifically designed for protecting cloud-based workloads, including instances in public cloud environments like Amazon EC2. This protection group type allows the Veeam Agent to be deployed and managed remotely, even when the Veeam Distribution Server cannot directly access the instances over the network. It facilitates centralized management of backup tasks for cloud instances, ensuring that the EC2 instances are adequately protected as per management's request, despite the network accessibility constraints.

The Veeam restore process that allows for custom scripting to be run before returning a server to production is Staged Restore. This feature enables administrators to perform necessary operations, like running a script to remove customer photos, during the restore process before the VM is brought back online.References: Veeam Backup & Replication User Guide, Veeam Staged Restore Guide