Pass the Veeam Certified Architect VMCA2022 Questions and answers with ValidTests

The additional information that is needed to define the implementation process later is how much backup data is stored on the old hardware. This information is important for designing and sizing the migration strategy and timeline for moving the backups from the old hardware to the new hardware. For example, you can use the amount of backup data to estimate how long it will take to copy or move the backups to the new storage devices. You can also use the amount of backup data to determine whether you need to use compression, deduplication, or WAN acceleration to optimize the migration traffic.

References: [Migrating Backup Files], [WAN Acceleration]

The configuration that would verify the SLA compliance during audits and protection against exposure to personally identifiable information in the event of exposure is to create a virtual lab environment and periodically perform staged restores with custom scripts. A virtual lab is an isolated environment where you can run your backups or replicas without affecting the production environment. A staged restore is a process that allows you to run custom scripts on the restored data before publishing it to the production environment. By using these features, you can demonstrate that your backups are recoverable and compliant with legal regulations, as well as remove or mask any sensitive data before restoring it.

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 requirement C will act as a constraint on the decision of whether to use a local repository or not for the remote sites. Data locality and privacy laws may vary by country or region, and may impose restrictions on where the backup data can be stored or transferred. For example, some countries may prohibit the export of personal data outside their borders, or require encryption or anonymization of sensitive data. Therefore, the Veeam solution must comply with these laws and regulations, and may need to use a local repository for each remote site, or use a cloud provider that has a local presence in each region. The other requirements are not constraints, as they can be met with either a local or a central repository, using the features and options of the Veeam solution. References: Veeam Certified Architect 2022 Exam Guide, page 11; Veeam Backup & Replication v11: Architecture and Design course, module 5.

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.

Backup from Storage Snapshots and Direct NFS are the preferred processing modes for NFS datastores, as they offer the best performance and reliability for backup and restore operations12.

Backup from Storage Snapshots 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 environment3. Backup from Storage Snapshots is supported for NFS datastores on NetApp, Nimble, Dell EMC, HPE, and Pure Storage systems4.

Direct NFS is a proprietary transport mode of Veeam Backup & Replication that uses a native NFS client deployed on the backup proxy to read and write data directly from and to the NFS datastore. Veeam Backup & Replication also bypasses the ESXi host and reduces the load on the production environment. Direct NFS is supported for NFS datastores on any storage system that supports NFS version 3 or 4.1.

The other options are not preferred because:

B) Network (NBD) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network. This mode produces additional load on the ESXi host and the network, and may result in slower backup and restore performance.

C) Virtual Appliance (HotAdd) mode is a transport mode that uses the VMware VDDK to attach the disks of the processed VM to the backup proxy VM. This mode also produces additional load on the ESXi host and the network, and may cause issues with disk alignment or SCSI controller limitations.

D) Network mode with Encryption (NBDSSL) mode is a transport mode that uses the VMware VDDK to communicate with the ESXi host over the network with SSL encryption. This mode provides an extra layer of security, but also adds more overhead and reduces the backup and restore performance.

You can find more information about the processing modes and how to choose the best one for your environment in the following resources:

Transport Modes

Selecting a Transport Mode

Backup from Storage Snapshots

Storage Systems Supported for Backup from Storage Snapshots

[Direct NFS Access]

[Network Mode]

[Virtual Appliance Mode]

[Network Mode with Encryption]

The Veeam component that will be required at each site for disaster recovery with a one minute recovery point objective is the Veeam CDP proxy. Veeam CDP proxy is a data mover that transfers data between the source and target hosts, using VMware vSphere APIs for I/O Filtering (VAIO) to capture the changes in real time1. Veeam CDP proxy can achieve near-zero recovery point objectives for business critical virtual machines, as well as provide short-term restore points and data encryption2. The other components are not required for this scenario, as they are used for different purposes, such as guest processing, backup storage, or backup jobs3. References: VMware CDP Proxies, Continuous Data Protection, Backup Proxies.

Immutable repositories are backup storage locations that prevent unauthorized modifications or deletions of backup data, ensuring its integrity and recoverability. Immutable repositories are essential for protecting backups against ransomware attacks, accidental deletions, or malicious insiders1.

Veeam Backup & Replication supports several types of immutable repositories, such as hardened repositories, immutable object storage repositories, and immutable deduplicating storage appliances2. Among these options, the best configuration for ensuring SLA compliance and providing protection against ransomware is to leverage hardened repositories at both primary and secondary sites, and offload to object storage in a public cloud with immutability enabled.

Hardened repositories are Linux-based repositories that use XFS file system with immutability flag to protect backup files from changes or removals. Hardened repositories can be used as primary or secondary backup targets, and can be combined with Veeam Scale-out Backup Repository to simplify backup management and optimize storage utilization3.

Object storage repositories are cloud-based repositories that use object storage services, such as Amazon S3, Microsoft Azure Blob Storage, or Google Cloud Storage, to store backup data. Object storage repositories can be used as secondary backup targets, and can leverage the immutability feature of the cloud provider to prevent backup data from being overwritten or deleted.

By using hardened repositories at both primary and secondary sites, you can achieve high availability and redundancy for your backup data, as well as fast and reliable restores. By offloading to object storage in a public cloud with immutability enabled, you can achieve long-term retention and compliance, aswell as cost savings and scalability. This configuration also follows the 3-2-1-1 backup rule, which recommends having three copies of data, on two different types of media, with one copy off-site and one copy immutable.

You can find more information about immutable repositories and how to configure them in the following resources:

Immutable Backup Solutions: Linux Hardened Repository

Unstructured Data Backups in Immutable Repositories

Hardened Repository

[Immutability for Object Storage Repositories]

[3-2-1-1 Backup Rule]

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

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]