Veeam Support Knowledge Base
Slow replication when target proxy uses Virtual Appliance (HotAdd) mode

Slow replication when target proxy uses Virtual Appliance (HotAdd) mode

KB ID:	1947
Product:	Veeam Backup & Replication
Version:	6.x, 7.x
Published:	2014-11-11
Last Modified:	2020-08-13
Languages:	FR

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

Oops! Something went wrong.

Please try again later.

Challenge

Incremental replication throughput is slow when target proxy uses Virtual Appliance transport mode (HotAdd).

Cause

This issue is caused by VMware's limitation. Writing to VM snapshot in hotadd mode may cause high I/O load on the target datastore and result in latency spikes and slow throughput. Network transport mode is usually much faster in that case.

Solution

Re-configure the target proxy to use Network (NBD) transport mode.

More Information

Veeam v8 is not affected by this VMware bug, v8 no longer uses VMware VDDK API function VixDiskLib_Write() for hotadd mode.

Veeam is currently addressing this problem with VMWare.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

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

Product

Topic

Description

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:

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!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.