VMCE_v12 Veeam Certified Engineer v12 Questions and Answers

To change a backup copy job from periodic mode to immediate mode, an administrator can edit the original backup copy job and select the immediate copy mode from within the job settings. This change ensures that backup copy jobs are started immediately after the source backup job completes, rather than waiting for a defined copy interval. References:

Veeam Backup & Replication User Guide: Backup Copy Job

Veeam Help Center: Backup Copy Job Modes

To ensure VMs running interdependent applications fail over one by one, as a group, the method to use is D: Failover plan . In Veeam Backup & Replication, a failover plan allows for the orchestration of a group of replicas to fail over in a predefined sequence. This includes the capability to set up delays between starting each VM, which is crucial for interdependent applications that must be started in a specific order to function correctly. The failover plan ensures that dependencies among the group are respected and that the startup sequence follows the correct order, enabling a smooth and organized transition to the failover state.

Given the provided transport modes and the fact that no modifications are allowed to these settings, a possible cause for the restore of a VMware virtual disk to fail using this proxy server is C: The virtual disk is thin-provisioned . In the transport modes shown, the Direct storage access and Virtual appliance options would require the VM disk files to be accessible in a certain way that might not be compatible with thin-provisioned disks depending on the storage configuration and the current state of the VM. If the storage integration specifics or the snapshot handling do not support the thin-provisioned format, the restore operation could fail. It ' s important to ensure that the transport mode selected is compatible with the type of virtual disk being restored to prevent such issues.

After using Instant VM Recovery to bring a critical crashed server back online quickly, the final step required to complete the recovery process is A: Migrate to production . Instant VM Recovery allows a VM to run directly from the backup file in a temporary location, enabling rapid recovery and minimal downtime. However, because the VM is running in this provisional state, it ' s essential to migrate it back to the production environment to ensure long-term stability and performance. The " Migrate to production " operation involves moving the running VM from the backup storage to the production storage, typically involving a storage vMotion in VMware environments or a similar process in other hypervisors. This step ensures that the VM is fully restored to its original or a new production environment, solidifying the recovery and allowing the VM to operate as part of the normal infrastructure once again.

Based on the configuration shown in the image, backups older than 21 days are moved to the capacity tier. Since the VMware backup job retention is set for 31 days and keeps weekly GFS full backups for 14 weeks, the backup from the week of January 1st is older than 21 days but within the 14-week GFS retention policy. Therefore, as of March 20, the backup data you need to recover would be in the capacity tier, not on the local performance tier, because it has been offloaded to the object storage configured as the capacity tier to reduce long-term retention costs.

References: Veeam Backup & Replication Documentation, Scale-Out Backup Repository Configuration Guide

Virtual Labs is the ideal feature for testing the impact of operating system updates in an isolated environment. Virtual Labs allow you to create a secure, isolated copy of your production environment where you can test updates, patches, and other changes without affecting the live environment. References: Veeam Backup & Replication Documentation, Veeam Virtual Lab Guide

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 flexi bility 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.

A SureBackup Job in Veeam Backup and Replication can be utilized to create a secure, isolated environment to test new applications. This feature allows companies to validate backups and run their VMs in an isolated environment, providing an opportunity to test applications, patches, or updates without impacting the production environment. References: Veeam Backup & Replication Documentation, Veeam SureBackup 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. References: Veeam Data Platform Documentation, Veeam Solaris Backup Guide

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.

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 ensure that a group of VMs starts in a specific order with time delays during a disaster scenario, the solution is B: Create a failover plan . A failover plan in Veeam Backup & Replication is a feature designed to manage the startup sequence of VMs within a DR site. The failover plan can be customized to specify the order in which VMs should start and to include necessary delays between the startups of each VM. This is especially useful for multi-tier applications where the order of startup is essential for the application stack to become fully operational. By using a failover plan, companies can control the recovery process, ensuring that VMs are brought online in an orderly and coordinated fashion that respects their interdependencies.

The feature that is unique to Veeam Agent for Linux and not available in other Veeam Agent configurations is C: Backup from native snapshots . Veeam Agent for Linux includes the ability to leverage native snapshot capabilities of the Linux kernel, such as LVM (Logical Volume Manager) snapshots or Btrfs subvolume snapshots, to create consistent point-in-time copies of data. This capability allows for application-consistent backups even in complex Linux environments, ensuring that data is captured in a consistent state without the need for custom scripting or downtime. Native snapshot support in Veeam Agent for Linux enhances the flexibility and reliability of backups, particularly in environments where Linux-based applications and databases are critical to business operations.

The REST API through Veeam Backup and Replication Server is the available API for automating Veeam Backup and Replication operations. This API enables programmatic control over Veeam Backup & Replication and allows for integration with external systems and custom automation scripts. References: Veeam Backup & Replication RESTful API Reference, Veeam Automation and Scripting Guide

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

The primary benefit of configuring replica mapping in Veeam Backup & Replication is C: Reduced WAN traffic. Replica mapping is a feature that allows an administrator to map an existing VM in the disaster recovery site to a replica job. This is particularly useful when the initial replication of a large VM has been performed by other means (such as shipping a hard drive with the VM data to the DR site) or if a replica VM already exists and needs to be re- synced with the source VM. By using replica mapping, Veeam can avoid transferring the entire VM over the WAN again and instead only synchronize the differences between the source VM and the existing replica. This significantly reduces the amount of data that needs to be transferred over the WAN, conserving bandwidth and speeding up the replication process. It ' s an efficient way to manage replicas, especially for large VMs or in environments with limited bandwidth.

Instant file share recovery is the most effective method to minimize service impact in this scenario. This feature allows users to instantly access the NAS data directly from the backup files without having to wait for the entire file share to be restored. This approach is beneficial when quick access to data is crucial. References: Veeam Backup & Replication Documentation, Veeam NAS Backup Guide

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

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.

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.

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

If VMware Tools (VIX) cannot be used due to security regulations, the backup administrator can use the proxy server as a guest interaction proxy to enable guest file system indexing for a backup job. The guest interaction proxy is responsible for the deployment and coordination of guest processing tasks, such as guest file system indexing, which does not require VIX. References:

Veeam Backup & Replication User Guide: Guest Interaction Proxy

Veeam Knowledge Base: Configuring Guest Interaction Proxies

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.

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

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

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.

References:

Veeam Backup & Replication User Guide: Backup Proxy

Veeam Help Center: Managing Backup Proxies

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

To alleviate the workload on the backup team while still accommodating the frequent restore requests from developers, the most effective strategy is to empower the developers themselves with the ability to perform file restores. This can be achieved by granting them access to the Enterprise Manager Self-Service File Restore Portal. Veeam Enterprise Manager offers a Self-Service File Restore Portal, which allows users to independently restore files from backups of their VMs without the need for direct intervention by the backup team. This portal is designed with security and ease of use in mind, ensuring that developers can perform restores as needed while adhering to the principle of least privilege, thus reducing the strain on the backup team. This approach aligns with Veeam ' s emphasis on enhancing operational efficiency and self-service capabilities in data management practices.