Performance optimization of backup jobs in Multi-Tenant environments

KB ID: 4217
Product: Veeam Backup & Replication
Version: 11a
Published: 2021-10-04
Last Modified: 2021-12-28
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Purpose

This article documents how to alter the performance characteristics of backup jobs created in the Veeam self-service backup portal (for VMware Cloud Director and vSphere) and jobs pointed to the Veeam Cloud Connect repository.

Cause

In a multi-tenant environment, one of the most important goals a Service Provider has is to ensure the availability of the resources to all users serviced by the environment while working to mitigate the “noisy neighbor” or “one-tenant-takes-it-over” issues. Based on this principle, the backup jobs created in Veeam Self-Service Portal and Veeam Cloud Connect are by default given an equal opportunity to process data within set allocation windows. This technique helps Service Providers reduce and ultimately eliminate the impact of backup data processing on the underlying infrastructure and other Tenants. In some scenarios, the Service Provider may choose to temporarily remove this restriction to improve the processing speed of the backups.

Solution

To improve processing speed for the backup jobs created in Multi-Tenant environments, the Service Provider can switch to the “Hybrid” (recommended) or ”Dynamic” modes of quota allocation.

After altering quota allocation mode in an environment, closely monitor backup infrastructure resources consumption.

 

This registry value is created on each Veeam Backup & Replication server managed by the Enterprise Manager server (providing the Self-Service Portal) or Veeam Cloud Connect server itself.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: CloudConnectQuotaAllocationMode
Value Type: DWORD (32-Bit) Value
Value Data (Default): 0
Acceptable Values: 0 | 1 | 2

No service restart is needed. The registry value will affect all new tasks that are started after its creation.

0 – Default

Each IO stream for a backup file write operation is allowed to write at most 512MB of data every 15 seconds. This process gives each write operation equal access opportunity when using slower storage.

1 – Dynamic

The Target Data Mover responsible for the data processing requests the quota allocation based on the availability of the current resources combined with the resources needed to process the data sets more efficiently.

Note: High demand for the processing resources may result in a performance impact in slower infrastructure environments. Performance monitoring is advised.

2 - Hybrid (Recommended)

Defaults to the Dynamic quota allocation and resorts to the Default quota allocation as needed.

 

Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.