The information related to sizing the NAS infrastructure that is missing and must be collected during the discovery are the size of the source data set and the recovery point objective (RPO). These information are important for designing and sizing the NAS backup jobs and repositories. For example, you can use the size of the source data set to estimate how much storage space and network bandwidth are required for backing up NAS devices. You can also use the RPO to determine how frequently you need to run NAS backup jobs and how many restore points you need to keep on the backup repositories.

The retention requirement for this project is 12 weekly backups, six monthly backups and seven yearly backups.  This is stated in the business requirements section of the scenario, where it says “To meet regulatory requirements, backups must be retained for four years.” This implies that the backup data must be archived for long-term retention, and the Veeam solution supports the 3-2-1 rule, which means having three copies of data, on two different types of media, with one copy off-site 1 . The other options are not retention requirements, but rather technical requirements or design choices, such as having on-premises backups on hardened repositories, having at least one copy of data on-premises, or having 14 daily backups on-site.  References:   Veeam Certified Architect 2022 Exam Guide , page 9;  Veeam Backup & Replication v11: Architecture and Design course , module 4.

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 storage 1 .  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 proxies 2 .  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 network performance and backup SLAs 3 ) 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 Veeam backup method that should be used for the virtualized stock trading application is to separate the virtual machine into its own job and enable application aware processing.  This method allows Veeam Backup & Replication to create transactionally consistent backups of the application, by quiescing the application and creating a snapshot of its data 1 . This ensures that the application can be restored to a working state, without data loss or corruption.  The other options are either not suitable for the application (option A, as Veeam agent is designed for physical machines or cloud instances 2 ), not sufficient for the application (option C, as pre-freeze and post-thaw scripts do not guarantee transactional consistency 3 ), or not related to the backup method (option D, as replication is a different process from backup).  References:   Application-Aware Processing ,  Veeam Agent Management ,  Pre-Freeze and Post-Thaw Scripts , [Replication].

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

Veeam Backup & Replication supports several types of immutable repositories, such as hardened repositories, immutable object storage repositories, and immutable deduplicating storage appliances 2 . 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 utilization 3 .

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, as well 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]

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 center 1 .  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 data 2 . 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 .

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

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 settings 2 . 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 settings 3 . 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 Snapshots and Direct NFS are the preferred processing modes for NFS datastores, as they offer the best performance and reliability for backup and restore operations 1 2 .

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

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 time 1 .  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 encryption 2 .  The other components are not required for this scenario, as they are used for different purposes, such as guest processing, backup storage, or backup jobs 3 .  References:   VMware CDP Proxies ,  Continuous Data Protection ,  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 tiers 1 .  The capacity tier can be configured to use Amazon S3 or Microsoft Azure Blob Storage, which support Object Lock feature for immutability 2 . 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 .