Veeam University Retention Quiz

Veeam B&R 6.5 has support for multiple hypervisors, specifically VMWare Vsphere and Microsoft Hyper-V. These two hypervisors are compatible with Veeam Backup and Replication and can be used in conjunction with the software for data protection and disaster recovery purposes. Citrix Xen and Oracle VirtualBox, on the other hand, are not listed as supported hypervisors for Veeam B&R 6.5.

This methodology describes the Forward Incremental backup type. In this type, the first backup is a full backup that creates a .vbk file. On subsequent runs, only the changes or differences from the previous backup are saved in .vib files, which are not injected back into the .vbk file. This allows for faster backups and less storage space usage compared to other backup types.

The Enterprise Manager in Veeam Backup and Replication does indeed provide a single point of control and reporting for multiple Veeam servers. This means that administrators can manage and monitor multiple Veeam servers from a centralized interface, making it easier to oversee and control backup and replication processes across the organization.

Changed Block Tracking (CBT) is a technology used by VMWare and Veeam when backing up in Direct SAN mode. It allows for efficient and incremental backups by tracking and identifying the changed blocks within a virtual machine's disk. This means that only the blocks that have been modified since the last backup need to be transferred, reducing the amount of data that needs to be processed and improving backup performance.

The correct answer is Backup Repository because it is the default location selected during installation that stores backup files, copies of VM's, and metadata. The other options (Veeam Backup Service, SQL DB, and Catalog Service) are not primary architecture components of Veeam B&R 6.5.

Veeam's de-duplication works by analyzing file blocks and only backing up one copy of each block if multiple blocks are the same. It also ignores empty file blocks, which helps to reduce storage space requirements by eliminating redundant data. This process helps to optimize backup and recovery operations by reducing the amount of data that needs to be stored and transferred.

You are not limited to two backup proxies. You can deploy any # of them.

The U-AIR Wizards in Veeam Backup and Replication perform the function of restoring application items from any virtualized application. This means that it allows users to restore individual items, such as databases, mailboxes, or user accounts, from virtualized applications like SQL, Exchange, and Active Directory. It provides a convenient and efficient way to recover specific items without having to restore the entire application or virtual machine.

This methodology describes the Reverse Incremental backup type. In this type of backup, the first backup is a full backup, and all subsequent backups are incremental. The incremental backups create .vib files, which are then injected into the initial full backup (.vbk file) to create a synthetic backup. This ensures that the most recent backup is always a full backup.

VeeamZip is an ad-hoc backup tool used for easily backing-up and taking a backup file offsite like on a USB drive or CD. Good for archiving VM's to a full .vbk before decomissioning them...there is no need to power off the VM, there is no impact to the users of that VM, it compresses and deduplicates the file.

The correct answer is Direct WAN Mode. This is not a transport mode because it is not used to transfer data from the source (SAN) to the repository (Veeam server). The other three options (Network Mode, Direct SAN Mode, and Virtual Appliance Mode) are all valid transport modes that can be used for data transfer in this scenario.

Quiescing a virtual machine before backup ensures that the backup is application consistent. This means that all data and transactions in the applications running on the virtual machine are in a consistent state at the time of the backup. It ensures that no data is lost or corrupted during the backup process, allowing for a reliable restore of the virtual machine and its applications.

The preferred model for replication to an offsite location in Veeam Backup & Replication 6.5 is to have two backup proxies, one deployed in each location involved in the replica set. This allows for efficient and reliable replication of data between the two locations. Having a backup proxy in each location ensures that the replication process can utilize local resources and network connections, minimizing the impact on the production environment and optimizing the replication performance.

The correct answer is WRS-BUNRF2 :: Veeam B&R 6.5 :: E:\Veeam Backups. This is the correct combination because it matches the server name, Veeam version, and repository location where Veeam and its backup files are stored at WRS. The other options either have different server names, different Veeam versions, or different repository locations, making them incorrect choices.

After a SureBackup Job has completed and machines in an application group have been booted, there are several options for checking the verification of the backup. A ping test can be performed to verify if the machines are reachable and responding to network requests. A custom script can be executed to perform specific checks or tests on the machines, ensuring that they are functioning correctly. The VMware Tools Heartbeat can be monitored to confirm that the virtual machines are running and communicating properly with the host. These options collectively provide a comprehensive verification of the backup.

vPower runs directly from a compressed/de-duplicated backup file using resources on the backup server/storage. This means that instead of having to restore the VM to the production environment, vPower allows the VM to be run directly from the backup file. This saves time and resources as there is no need to fully restore the VM before it can be used. The compressed/de-duplicated backup file ensures efficient storage usage, while the resources on the backup server/storage provide the necessary computing power for the VM to run.

The reason why Veeam used Network Transport mode instead of Direct SAN transport mode for backing up the VM is that the backup server did not have the necessary rights to access the LUN where the VM is stored. As a result, Veeam was unable to utilize the Direct SAN transport mode and resorted to using the Network Transport mode instead.