Pass the Veeam Certified Architect VMCA2022 Questions and answers with ExamsMirror

If the repositories are able to accomplish much higher throughput, a new issue that might come up is that the bandwidth between sites might not be sufficient to support the backup copy jobs that need to run daily between Fresno and Carson City. This could cause the backup copy jobs to fail, take longer than expected, or consume too much network resources. Therefore, it is important to measure the available bandwidth between the sites and compare it with the backup copy data size and window. If the bandwidth is not sufficient, some possible solutions are to use compression, deduplication, or WAN acceleration to reduce the backup copy traffic.

Option A follows the 3-2-1 rule by having three copies of data (the original production data, the backup at the primary site, and the backup copy at the secondary site), two different media types (local disk and object storage), and one copy off-site (the backup copy at the secondary site). This option also reduces the amount of traffic sent over the network by using existing backups as seeds for backup copies, and reduces the storage costs by using cloud tier to move older backups to cheaper and unlimited cloud storage1

•Veeam CDP is a technology that helps you protect mission-critical VMware virtual machines when data loss for seconds or minutes is unacceptable12.

•Veeam CDP leverages vSphere APIs for I/O filtering (VAIO) to constantly replicate I/O operations performed on VMs without creating snapshots12.

•Veeam CDP allows you to configure the RPO per second and achieve near-zero RPO, which means almost no data loss12.

•Veeam CDP also provides minimum recovery time objective (RTO) in case of a disaster, as CDP replicas are in a ready-to-start state1.

Veeam image-based replication is not the best option, as it relies on snapshots and has a higher RPO than CDP3. Custom PowerShell scripting is not a reliable or scalable solution, as it requires manual coding and maintenance. Veeam Backup Copy with immediate mode is not suitable for replication, as it is designed for copying backup files, not VM replicas4.

References: 1: Continuous Data Protection (CDP) - User Guide for VMware vSphere 2: Veeam v11: Continuous Data Protection (CDP) configuration 3: Replication - User Guide for VMware vSphere 4: Backup Copy Modes - User Guide for VMware vSphere

According to the Veeam Backup & Replication Best Practice Guide1, some of the reasons why it is recommended to have a Veeam backup server at each of the three sites are:

•Each site has production data. This reason is based on the principle of locality, which states that backup data should be stored as close as possible to the source data, to reduce network traffic and latency, and to improve backup and restore speed and efficiency. Having a Veeam backup server at each site allows you to perform local backups of the production data at each site, without having tocross the WAN or VPN connections between sites.

•Use Hardened Repositories as the primary target, which are Linux-based repositories that support immutability and prevent ransomware from accessing or deleting backup files12.

•Use backup copy jobs to create a second copy of the backups to a different site, which will provide additional protection and redundancy in case of a disaster or data loss34.

•Use Veeam Backup & Replication servers at one location, which will simplify the management and monitoring of the backup infrastructure and reduce the operational costs.

The other configurations are not as effective or secure, as they either do not use immutability, do not create a second copy of the backups, or do not leverage the benefits of Veeam Backup & Replication servers.

References: 1: Protect against Ransomware with Immutable Backups - Veeam 2: Hardened Repository - User Guide for VMware vSphere 3: Backup Copy Modes - User Guide for VMware vSphere 4: Backup copy jobs - Veeam Backup & Replication Best Practice Guide : Veeam Backup & Replication Architecture Overview

According to the Veeam Backup & Replication Best Practice Guide1, the proxy and repository servers are the components that should be sized correctly to ensure that synthetic operations and backup copy jobs can be completed in the desired window. This is because:

•The proxy server is responsible for retrieving data from the source and sending it to the target. The proxy server performance depends on the CPU, memory, network, and storage resources available. The proxy server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to transfer data efficiently.

•The repository server is responsible for storing backup files on the target storage. The repository server performance depends on the CPU, memory, network, and storage resources available. The repository server should have enough CPU cores and memory to handle concurrent tasks, as well as sufficient network bandwidth and storage throughput to write data efficiently. The repository server should also support the backup format and retention policy chosen for the backup copy job.

References: 1: Backup copy jobs - Veeam Backup & Replication Best Practice Guide

To design a solution that meets the immutability requirement for Veeam University Hospital, you need to consider how this constraint affects the other requirements and expectations of the customer. This will help you to avoid any conflicts or inconsistencies that may arise from applying immutability settings to the backup data.

According to the Veeam Backup & Replication Best Practice Guide, immutability is a feature that prevents backup files from being deleted or modified by anyone until the specified retention periodexpires. Immutability can be achieved by using S3 Object Lock or Hardened Repository, which are two different solutions that Veeam Backup & Replication supports.

Based on this definition, the requirement that is impacted by the immutability constraint is D. Backup must take advantage of public cloud storage for long-term retention.

This requirement is impacted by the immutability constraint because:

•Public cloud storage is a type of storage that is provided by a third-party service provider over the internet, such as Amazon S3, Microsoft Azure, Google Cloud, etc.

•Public cloud storage can be used for long-term retention, which is a policy that defines how long backup data should be kept for compliance or historical purposes, such as months, years, or decades.

•Public cloud storage can also support immutability, which is a feature that prevents backup data from being deleted or modified by anyone until the specified retention period expires, such as days, weeks, or months.

•However, not all public cloud storage providers or services support immutability, or support it in the same way. For example, Amazon S3 supports S3 Object Lock, which allows you to apply a legal hold or a retention period to individual objects or object versions. Microsoft Azure supports Immutable Blob Storage, which allows you to create time-based policies or legal holds for blob containers. Google Cloud supports Bucket Lock, which allows you to lock a bucket and prevent objects from being overwritten or deleted.

•Therefore, the choice of the public cloud storage provider or service may affect the immutability setting and requirement for the backup data. You need to verify and compare the compatibility and supportability of the public cloud storage providers or services with Veeam Backup & Replication and with the customer expectation.

•Virtual machine backup jobs with log shipping enabled allow you to create image-level backups of SQL Server databases and also back up the transaction logs periodically12.

•Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, allowing for better backup performance, scalability, and management3.

•Scale-out Backup Repository capacity tier is a feature that allows you to offload older backup files to a public cloud object storage, such as Amazon S3 or Azure Blob Storage .

The other options are not as effective or efficient, as they either do not use Veeam features, do not offload to object storage, or do not create image-level backups.

References: 1: Transaction Log Shipping - User Guide for VMware vSphere 2: How to Back Up SQL Server Transaction Logs - Veeam 3: Scale-Out Backup Repository - Veeam Backup & Replication Best Practice Guide : Capacity Tier - User Guide for VMware vSphere : How to Use Capacity Tier in Veeam - Veeam

•MFA is a security method that requires users to provide two or more pieces of evidence to verify their identity, such as a password, a code, a token, or a biometric factor3.

•MFA adds an extra layer of protection against ransomware attacks, as it prevents attackers from accessing the Veeam components even if they manage to steal or guess the passwords of the administrative accounts12.

•MFA also helps to prevent unauthorized changes or deletions of backup data, as well as unauthorized restores or failovers of VMs or applications12.

The other options are not as effective or feasible, as they either do not provide enough security, limit the functionality, or disrupt the integration of the Veeam infrastructure.

References: 1: 6 Best Practices For Ransomware Protection | Veeam 2: Ransomware Prevention Best Practices - Veeam 3: Multi-factor authentication - Wikipedia

To design a solution that meets the replication requirement for Veeam University Hospital, you need to consider some of the mitigating techniques that might be required for the virtual machines that have several separate large VMDKs with a high change rate per virtual machine on the same datastore. This will help you to overcome some of the challenges and limitations that may affect the replication performance and efficiency, as well as the recovery point objective (RPO) of the organization.

According to the Veeam Backup & Replication Best Practice Guide, some of the mitigating techniques that might be required are:

•Implement WAN accelerator. This technique can help you to reduce the amount of data that needs to be transferred and processed between the source and target sites, by using caching, deduplication, compression, and encryption. You need to deploy a pair of WAN accelerators, one at the source site and one at the target site, and configure them in the replication job settings. This technique can improve the replication speed and efficiency, as well as save network bandwidth and storage space.

•Recommend migrating some of the VMDKs to alternative datastores. This technique can help you to avoid performance degradation and resource contention on the source datastore, by distributing the load and I/O across multiple datastores. You need to use VMware tools or commands, such as Storage vMotion or svmotion, to migrate some of the VMDKs to other datastores that have enough capacity and performance. This technique can improve the replication stability and reliability, as well as reduce the impact on the production environment.

Therefore, based on these techniques, the answer that describes which mitigating techniques might be required is A and C.