VMCE_V12 practice question 2 of 25

The engineer configured Veeam Backup & Replications 3 years ago with an all-in-one physical server with one job backing up all VMs. The environment grew considerably and RPOs are no longer met. The engineer checks the backup job and sees: Load: Source 0% > Proxy 68% > Network 0% > Target 0%. What should be done to decrease the backup processing time?

Full set: 109 questions

Domain Troubleshooting

Answer options
A: Edit the Backup Job settings and enable parallel processing from Advanced options
B: Split the VMs in several jobs with the same schedule to process the VMs in parade
C: From Backup Infrastructure add an extra Windows/Linux machine as Backup Proxy Correct answer
D: Install another Veeam Backup & Replication server and move half of the VMs to be processed in a separate job
Correct Answer:
C. From Backup Infrastructure add an extra Windows/Linux machine as Backup Proxy
Explanation

The job statistics Load: Source 0% > Proxy 68% > Network 0% > Target 0% clearly identify the backup proxy as the performance bottleneck. In an all-in-one deployment, the Veeam Backup Server itself performs the proxy role, and its resources (CPU/RAM) are overwhelmed by the data processing tasks for the grown environment. Adding a new, dedicated backup proxy server will offload this processing task. Veeam can then distribute the workload between the original proxy and the new one, allowing for more concurrent processing and significantly reducing the overall backup time to meet the RPOs.

Why Incorrect

A. Edit the Backup Job settings and enable parallel processing from Advanced options: Enabling more parallel tasks would increase the load on the already overwhelmed proxy, worsening the bottleneck rather than resolving it.
B. Split the VMs in several jobs with the same schedule to process the VMs in parallel: This would create more jobs competing for the same limited resources on the single, bottlenecked proxy, leading to resource contention and likely no improvement.
D. Install another Veeam Backup & Replication server and move half of the VMs to be processed in a separate job: This is an unnecessarily complex and costly solution that creates management overhead. The standard method to scale a Veeam deployment is by adding components like proxies, not entire VBR servers.

References

1. Veeam Backup & Replication V12 Help Center for VMware vSphere

Real-Time Statistics: This document explains how to interpret the bottleneck statistics. It states

"The bottleneck is the component with the highest load percentage... Proxy — the backup proxy is the bottleneck. The data processing on the proxy is slow." This confirms the analysis of the provided job statistics.

Source: https://helpcenter.veeam.com/docs/backup/vsphere/realtimestatistics.html?ver=120

Section: "Bottleneck Analysis".

2. Veeam Backup & Replication V12 Help Center for VMware vSphere

Backup Proxy: This guide details the role of the backup proxy and the benefits of deploying additional ones. It explicitly states

"To take the load off the backup server

you can deploy backup proxies... For better performance

it is recommended to deploy backup proxies on dedicated machines." This directly supports adding a new proxy to solve the performance issue.

Source: https://helpcenter.veeam.com/docs/backup/vsphere/backupproxy.html?ver=120

Section: "Backup Proxy".

3. Veeam Best Practices V12

VMware Proxies: This official best practices guide recommends scaling out by adding proxies for performance. It notes

"Deploying multiple proxies allows for proxy load balancing

which increases backup performance and reliability." This validates option C as the correct architectural approach to scaling.

Source: https://bp.veeam.com/vbr/2Design/DVeeamComponents/Dbackupproxies/vmwareproxies.html

Section: "Proxy Sizing".

Scroll to Top