Veeam VMCA2022 Dumps

The requirement C is vague and needs more clarification from the customer. It does not specify which public cloud provider, service, or storage tier should be used for the backup data. It also does not indicate how the backup data should be transferred, secured, or managed in the public cloud. The other requirements are more clear and specific, and can be met with the Veeam solution features and best practices. References: Veeam Certified Architect 2022 Exam Guide, page 9; Veeam Backup & Replication v11: Architecture and Design course, module 6.

The Veeam feature that can be used to help achieve compliance with privacy regulations is location tags on repositories. Location tags are labels that can be assigned to backup repositories to indicate their physical or logical location, such as country, region, or data center1. Location tags can help ensure that backup data is stored and processed in compliance with data residency and privacy laws, such as GDPR or CCPA, by allowing backup administrators to create backup policies based on the location of the source and target data2. The other options are not related to privacy compliance, as they are either used for network optimization (preferred networks), server identification (location tags on Veeam Backup & Replication servers), or backup scope (location tags on subnets). References: Location Tags, Using Location Tags.

Backup from storage snapshot is a feature of Veeam Backup & Replication that leverages the native snapshot capabilities of the storage system to create a consistent point-in-time copy of the VM data. Veeam Backup & Replication then reads data directly from the storage snapshot, bypassing the ESXi host and reducing the impact on the production environment1. Backup from storage snapshot is supported for VSAN datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems2.

Using backup from storage snapshot for the virtualized stock trading application servers can improve the backup performance and reduce the latency, as it minimizes the time that the VM is running on a snapshot and avoids the network overhead of other transport modes3.

The other options are not recommended because:

• B) Implementing Veeam Agent on the virtualized stock trading application servers is not necessary, as Veeam Backup & Replication can protect VMware VMs without agents. Veeam Agent is mainly used for physical servers, workstations, or cloud instances4.
• C) Using Veeam Replication to create replicas of the virtualized stock trading application servers at the remote site, then back up the replicas is not optimal, as it adds more complexity and cost to the backup process. Veeam Replication is mainly used for disaster recovery purposes, not for backup5.
• D) Turning off application-aware processing for the virtualized stock trading application servers is not advisable, as it may compromise the consistency and recoverability of the application data. Application-aware processing is a feature of Veeam Backup & Replication that ensures that the application data is in a consistent state before the backup or replication job starts.

You can find more information about backup from storage snapshot and other backup options for VSAN in the following resources:

• Backup from Storage Snapshots
• Storage Systems Supported for Backup from Storage Snapshots
• Optimizing Veeam Backup & Replication Configuration for VMware VSAN
• Veeam Agent Management
• Veeam Replication
• [Application-Aware Processing]

The best way to deploy the proxies for the remote office is to deploy eight virtual proxies with eight CPUs and 16 GB of RAM each. This option allows to leverage the Virtual appliance (Hot-Add) mode, which is the recommended transport mode for VSAN storage1. Virtual appliance mode enables LAN-free data transfer between the source datastore and the proxy, as well as load balancing and fault tolerance across multiple proxies2. The other options are either not optimal (option A and B, as physical proxies require LAN or SAN connection to access the source data, which may impact the networkperformance and backup SLAs3) or not supported (option C, as virtual proxies with more than eight CPUs are not compatible with Virtual appliance mode). References: Transport Modes, Virtual Appliance Mode, Direct Storage Access Mode, [Requirements and Limitations for VMware Backup Proxies].

The best option to still satisfy the requirement for offsite, immutable or air gapped backups if the cloud provider selected for archive storage does not support immutability is to set up Scale-out Backup Repository capacity tier to a different cloud provider than the archive tier. Scale-out Backup Repository is a logical entity that groups several backup repositories into a single pool of storage, and allows to move backup files between performance and capacity tiers1. The capacity tier can be configured to use Amazon S3 or Microsoft Azure Blob Storage, which support Object Lock feature for immutability2. By using a different cloud provider for the capacity tier than the archive tier, the backup data can be stored in two separate locations, with one copy being immutable or air gapped. The other options are either not feasible (option A, as the scenario does not mention another site), not secure (option C, as the backup data can still be accessed or modified when the repository is online), or not offsite (option D, as the scenario requires a copy of backup data in a public cloud). References: Scale-out Backup Repository, Object Storage Immutability.

The tiers of Veeam Financial Services’ backups that will require SureBackup jobs are the silver and gold tiers. SureBackup jobs are used to verify the recoverability of backup files by running virtual machines from backups in an isolated environment and performing tests against live applications1. This feature is suitable for the silver and gold tiers, which have recovery time objectives of six hours and 30 minutes, respectively, and require backups to be verified. The bronze tier, which consists of development machines and field portables, has a recovery point target of seven days, with no recovery time target set, and does not require backup verification. Therefore, SureBackup jobs are not necessary for the bronze tier. Laptop backups are performed by Veeam Agent for Microsoft Windows, which does not support SureBackup jobs2. References: SureBackup, Veeam Agent for Microsoft Windows.

The information related to the virtual infrastructure that is missing and must be collected during the discovery are the total number of virtual machines and the size of the source data set. These are essential metrics for sizing the backup components, such as proxies, repositories, and transporters, as well as estimating the backup storage requirements and bandwidth consumption. The other options are either already provided in the scenario (recovery time objective, backup window) or not relevant for the Veeam solution (speed of Fibre Channel fabric). References: Veeam Certified Architect 2022 Exam Guide, page 10; Veeam Backup & Replication v11: Architecture and Design course, module 3.

Reducing the recovery point objective (RPO) for silver tier workloads means that the backup frequency will increase, resulting in more backup data being generated and transferred. This will affect the sizing requirements of the Veeam components that are responsible for storing and processing the backup data, namely the Veeam repository and proxy roles1.

The Veeam repository is a storage location where the backup files are stored. The repository size depends on the amount of data to be backed up, the backup method, the retention policy, and the compression and deduplication settings2. Reducing the RPO will increase the amount of data to be backed up, and may require more frequent synthetic full backups or active full backups to maintain the retention policy. This will increase the repository size and the disk space consumption.

The Veeam proxy is a data mover that performs backup, replication, and restore tasks. The proxy size depends on the number of concurrent tasks, the transport mode, the backup method, and the compression and deduplication settings3. Reducing the RPO will increase the number of concurrent tasks and the amount of data to be processed by the proxy. This will increase the proxy size and the CPU and memory consumption.

You can find more information about the sizing requirements and best practices for the Veeam repository and proxy roles in the following resources:

• Veeam Backup & Replication Best Practices
• Veeam Backup Repository Sizing Calculator
• Veeam Proxy Sizing Calculator

If you separated the large VMDKs into their own backup jobs, you would be creating more manual work for the backup administrator, who would have to configure and maintain multiple jobs for the same group of VMs. This would go against the requirement of reducing administrative overhead by using dynamic scoping.

Dynamic scoping is a feature of Veeam Backup & Replication that allows you to automatically include or exclude VMs from backup jobs based on tags, attributes, or policies1. For example, you can use VMware tags to assign a backup policy to a VM, and then use the tag as a filter in the backup job. This way, any VM with that tag will be automatically added to the backup job, and any VM without that tag will be automatically excluded. This simplifies the backup management and ensures that all VMs are protected according to their assigned policy.

For large VMDKs with high I/O, you can use alternative backup methods to avoid performance impact and stuns, such as storage snapshots, direct SAN access, or hot-add2. You can also use different storage optimization options to balance the deduplication ratio and the backup file size3. These options can be configured within the same backup job, without the need to separate the large VMDKs.

You can find more information about dynamic scoping and backup methods for large VMDKs in the following resources:

• How to Use Dynamic Scoping in Veeam Backup & Replication
• Backing up large vmdks (~12 TB)
• Backup strategies for a large VM

The component sizing that should be adjusted is the physical storage in the repositories. The repositories are the backup storage locations where Veeam Backup & Replication stores backup files, VM copies and metadata for replicated VMs1. Increasing the retention period from four to five years means that more backup files will be kept on the repositories, and thus more storage space will be required. The other options are not affected by the retention period change, as they are either related to off-site backups (option A), Veeam Backup & Replication server performance (option C), or backup proxy performance (option D). References: Backup Repositories.

Changing the backup window from 12 hours to 14 hours means that the backup jobs will have more time to complete, and therefore less concurrency will be required. This will reduce the load on the proxies, which are the data movers that perform backup, replication, and restore tasks1. The proxies will need fewer resources, such as CPU and memory, to handle the same amount of data.

The other options are incorrect because:

• A) Proxies will not require more resources, as explained above.
• B) Mount servers will not require fewer resources, as they are not affected by the backup window. Mount servers are used to mount backup files and restore data from them2. Their resource consumption depends on the restore frequency and performance, not the backup window.
• D) Repositories will not require more storage space, as the backup window does not affect the backup size. Repositories are storage locations where the backup files are stored3. Their storage space consumption depends on the amount of data to be backed up, the backup method, the retention policy, and the compression and deduplication settings, not the backup window.

You can find more information about the backup window and the Veeam components in the following resources:

• Backup Window
• Mount Server
• Backup Repository

To design a solution that meets the needs and requirements of Veeam University Hospital, you need to gather some information during the discovery phase. This information will help you to understand the current state of the environment, the goals and expectations of the stakeholders, and the constraints and challenges of the project.

According to the Veeam Backup & Replication Best Practice Guide1, some of the information that is necessary for designing a solution and must be gathered during discovery are:

•Operating systems used to run the workloads. This information will help you to determine the compatibility and supportability of the workloads with Veeam products and features, as well as the licensing and configuration requirements.

•Allowed backup windows. This information will help you to plan and schedule the backup jobs according to the availability and performance of the workloads, as well as the service level agreements (SLAs) and recovery point objectives (RPOs) of the organization.

•Amount of used disk space. This information will help you to estimate the backup storage requirements, as well as the backup compression and deduplication ratios, based on the type and size of the data.

To design a solution that meets the needs and requirements of Veeam University Hospital, you need to conduct a thorough analysis on the areas mentioned in the case study. This will help you to understand the current state of the environment, the goals and expectations of the stakeholders, and the constraints and challenges of the project.

According to the case study, some of the areas that would benefit from additional analysis are:

•NAS. This area would benefit from additional analysis because NAS systems are used to store confidential patient data as unstructured data, which need to be backed up consistently and securely. You need to collect more information about the characteristics and performance of the NAS systems, such as the size and type of data, the number and distribution of files, the largest file size, the version of SMB protocol, the deduplication and compression ratios, etc. This will help you to design a solution that can meet the backup and recovery objectives, as well as the regulatory and security requirements, for the NAS data.

•PostgreSQL. This area would benefit from additional analysis because PostgreSQL databases are used by some of the departments, with a mix of virtual and physical deployments. You need to collect more information about the configuration and performance of the PostgreSQL databases, such as the version and edition, the operating system and platform, the backup and restore methods and tools, the consistency and integrity requirements, etc. This will help you to design a solution that can support and integrate with PostgreSQL databases, as well as provide consistent and reliable backups and restores.

•OneDrive. This area would benefit from additional analysis because OneDrive is used by all doctor and lab staff to store their user data on their laptops, which also need to be backed up. You need to collect more information about the usage and performance of OneDrive, such as the number and size of files, the synchronization frequency and settings, the authentication and authorization methods, etc. This will help you to design a solution that can protect and recover OneDrive data, as well as exclude any operating system or personal files from backup.

To design a disaster recovery solution that meets the needs and requirements of Veeam University Hospital, you need to identify some information during the discovery phase. This information will help you to understand the scope and scale of the replication and failover processes, the network andstorage resources and limitations, and the recovery time objectives and recovery point objectives.

According to the Veeam Backup & Replication Best Practice Guide, some of the information that is necessary to design the disaster recovery solution and must be identified during discovery are:

•The number of virtual machines to be replicated. This information will help you to determine the number and size of the replication jobs, as well as the replication performance and scalability, based on the number and type of virtual machines.

•The available bandwidth between locations. This information will help you to estimate the network bandwidth and throughput that are available for replication traffic, as well as the impact of replication activities on the network performance and latency.

•Which sites will be the source of replication and which sites will be the targets for recovery. This information will help you to plan and configure the replication infrastructure, such as the proxy servers, repository servers, WAN accelerators, and failover plans, based on the source and target locations.

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.

The gateway is a component that acts as a data mover between the backup proxy and the backup repository. If the gateway does not have enough CPU, RAM and task slots assigned, it may not be able to handle the incoming data from the backup proxy efficiently, and cause a bottleneck at the target. By increasing the resources and task slots for the gateway, you can improve its performance and throughput, and reduce the load on the target2

•Use Linux repositories as the performance tier, which are more secure and resilient than Windows repositories, as they support immutable backups and prevent ransomware from accessing or deleting backup files1.

•Use immutable cloud storage as the capacity tier, which will offload older backup files to a public cloud object storage that supports immutability, such as Amazon S3 Object Lock or Azure Blob Storage with immutable policies2. This will ensure that the backup files cannot be modified or deleted by ransomware or malicious users for a specified period of time.

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

References: 1: Protect against Ransomware with Immutable Backups - Veeam 2: Ransomware Protection: Learn How Veeam Can Protect Your Data 3: Scale-Out Backup Repository - Veeam Backup & Replication Best Practice Guide

•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

If using Veeam’s native encryption, the repository type that will be impacted the most is the deduplicating storage appliance. This is because Veeam Backup & Replication uses different encryption keys for every job session, which makes the encrypted data blocks appear as different even if they contain duplicate data. This reduces the deduplication ratio and increases the storage consumption on the deduplicating appliance. If you want to achieve a higher deduplication ratio, youcan disable data encryption or use the encryption feature on the deduplicating appliance itself1

According to the Veeam Backup & Replication Best Practice Guide1, one of the possible ramifications of shortening the backup window to eight hours is that the CPU and memory requirements of the proxies will be increased. This is because:

•The proxies are responsible for retrieving data from the source and sending it to the target. They perform data compression, deduplication, encryption, and other tasks that consume CPU and memory resources.

•To shorten the backup window, the proxies need to process more data in less time, which means they need more CPU cores and memory to handle concurrent tasks and avoid bottlenecks.

•The backup window can also be affected by other factors, such as the network bandwidth, the storage throughput, the backup methods, and the backup settings. Therefore, it is important to consider all these aspects when designing a backup solution.

References: 1: Proxy - Veeam Backup & Replication Best Practice Guide

Veeam University Hospital is considering using Veeam ONE to collect alarms from the virtual and backup infrastructure. Veeam ONE is a powerful monitoring and reporting tool that provides visibility and insight into the performance, configuration, and utilization of your backup and virtual infrastructure. Veeam ONE can also alert you about any issues or problems that may affect the availability or reliability of your data protection and recovery processes.

One of the options that is available for integrating Veeam ONE with ticketing systems is A. Configure Veeam ONE to send SNMP traps to the ticketing system.

This option means that:

•SNMP (Simple Network Management Protocol) is a protocol that allows network devices to communicate and exchange information with each other.

•SNMP traps are messages that are sent by network devices to notify a management system about events or conditions that require attention or action.

•Veeam ONE can be configured to send SNMP traps to a ticketing system when an alarm is triggered or resolved. This allows you to automate the creation and update of tickets based on the alarm data, such as the alarm name, severity, status, description, etc.

•To configure Veeam ONE to send SNMP traps to a ticketing system, you need to enable SNMP notifications in the Veeam ONE settings, as well as specify the SNMP server address, port, community string, and trap format. You also need to configure the ticketing system to receive and process the SNMP traps from Veeam ONE.

This option is a good choice for integrating Veeam ONE with ticketing systems, as it allows you to leverage the benefits and features of both solutions, such as:

•You can use Veeam ONE to monitor and analyze your backup and virtual infrastructure, as well as to detect and alert you about any issues or problems that may affect your data protection and recovery processes.

•You can use the ticketing system to manage and track the resolution of the issues or problems that are reported by Veeam ONE, as well as to assign and prioritize tickets to the appropriate staff or team members.

•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

The transport modes that could be used during the redesign for gold tier virtual machines with a one-hour RPO are Virtual Appliance (HotAdd) and Backup from Storage Snapshots. A transport mode is a method of retrieving VM data from the source storage during backup or replication. Virtual Appliance (HotAdd) is a transport mode that allows a proxy server running on a VM to attach disks of another VM to itself via hot-add SCSI commands and read data directly from these disks. Backup from Storage Snapshots is a transport mode that allows a proxy server to retrieve data from storage snapshots created by supported storage systems without affecting the production VMs or hosts. Both transport modes can improve backup performance, reduce backup window, and minimize impact on the production environment.

The component that can help meet the requirement of alternative decryption capabilities on encrypted backups in the event of lost passwords is Veeam Backup Enterprise Manager. Veeam Backup Enterprise Manager is a web-based interface that allows centralized management of multiple Veeam backup servers. It also provides a password loss protection feature that enables authorized users to restore encrypted backups without entering passwords if they forget or lose them. This feature requires enabling password loss protection in Veeam Backup Enterprise Manager settings and assigning a security officer role to a user who can approve password recovery requests.

References: [Veeam Backup Enterprise Manager], [Password Loss Protection]

The recommended method to replicate VMware virtual machines with a less than five-minute RPO is Veeam Continuous Data Protection (CDP). CDP is a feature that allows near-continuous replication of VMware virtual machines to a secondary site or cluster with minimal data loss and downtime. CDP uses VMware vSphere APIs for I/O Filtering (VAIO) to capture every write operation from the source VMs and send them to the target VMs in near real-time. CDP can achieve RPOs as low as seconds and enable fast failover and failback in case of a disaster.

A possible cause of failures to meet the requirement to test gold tier backups is that you cannot firewall traffic between vLANs in the SureBackup job configuration. This could prevent the gold tier virtual machines from communicating with each other or with other required services in the isolated virtual lab. For example, if a gold tier virtual machine needs to access a database server or a domain controller in another vLAN, it might fail to start or function properly in the SureBackup job. Therefore, it is important to ensure that all necessary vLANs and network settings are configured correctly in the SureBackup job.

The component that will help the customer meet their stated objectives of role-based access control (RBAC) and alternative decryption capabilities is Veeam Backup Enterprise Manager. Veeam Backup Enterprise Manager is a web-based interface that allows centralized management of multiple Veeam backup servers. It also provides RBAC policies that enable granular control over user permissions and access to backup data. For example, you can assign different roles to different users or groups based on their responsibilities and needs, such as backup administrator, restore operator, securityofficer, etc. Veeam Backup Enterprise Manager also provides password loss protection feature that enables authorized users to restore encrypted backups without entering passwords if they forget or lose them.

The action that Veeam Life and Indemnity should take to improve the likelihood that a ransomware attack on the Veeam infrastructure will not be successful is to protect the Veeam components on the production Active Directory Forest with multi-factor authentication. Multi-factor authentication (MFA) is a security mechanism that requires users to provide two or more pieces of evidence to prove their identity before accessing a system or resource. MFA can prevent unauthorized access to the Veeam components even if the user credentials are compromised by ransomware or other means.

The assumption that can be made for the conceptual design is that Veeam Agent backups of sale staff laptops should be managed by the backup server. This assumption is based on the best practice and recommendation for using Veeam Backup & Replication. Veeam Agent backups of sale staff laptops should be managed by the backup server to enable centralized management, monitoring, and reporting of all agent-based backups. This can also simplify the backup configuration, scheduling, and retention for the laptop agents.

The best option for the primary backup repository design that fits the requirements in the case study is a Linux Repository using XFS integration, single-use credentials, and immutability. A Linux Repository is a type of backup repository that uses a Linux server as a backup target. A LinuxRepository can leverage XFS integration to enable fast creation and transformation of synthetic full backups by using XFS file system features such as reflink and copy-on-write. A Linux Repository can also use single-use credentials to enhance security by generating unique credentials for each backup job session. A Linux Repository can also provide immutability and ransomware protection for backup files by using Linux access control mechanisms such as immutable flag or chattr command.

The gold tier backup jobs have the most stringent recovery point objective (RPO) of one hour for image backup and 15 minutes for transaction log backup. This means that they need to run more frequently than the other backup jobs and create more restore points per day. Therefore, to properly plan the backup copy job settings, you will need more information on the gold tier backup jobs, such as the number of VMs, the size of backups, the change rate, the retention policy, and the bandwidth available for copying backups to the offsite location.

References: [Backup Copy], [Backup Methods], [Continuous Data Protection]