https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDUyIiwiaGFzaCI6ImE4N2UxMTFjLTljYTEtNDY1OC04ZmQ2LWQwNDFjMmY5YjFlYiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Slow restore performance in SAN mode

Challenge

In some cases, depending on infrastructure setup you can observe poor processing rate when performing full VM restore in SAN mode. You can notice as well that Network mode is faster.

Cause

If you restore Thick Lazy Zero disk using SAN mode, overall restore performance can be affected because of round trips through the disk manager APIs, AllocateBlock and ClearLazyZero requests. The reason that NBD mode can work faster in comparison to SAN mode (when not using block-sized writes) is because the write is performed by the host which has inside knowledge about layout of the vmdk. This inside knowledge must be requested from the host when VDDK is doing direct writes to the LUN.

Solution

Use alternative transport mode: network, virtual appliance
You can also try to restore in SAN mode via standalone ESXi. In some cases you may see a higher processing rate

More information at kb.vmware.com/kb/1035096
 
KB ID:
2052
Product:
Veeam Backup & Replication
Version:
8.x
Published:
2015-07-08
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later