VEEAM Exam VMCA2022 Topic 5 Question 1 Discussion

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