1-800-691-1991 | 9am - 8pm ET
EN

Building SAN path is taking a long time

KB ID: 1630
Product: Veeam Backup & Replication
Version: 5.X, 6.X
Published: 2012-05-23
Last Modified: 2020-08-13
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

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.

Challenge

The path discovery and mount process can take a while to populate the correct path to the VMDKs.

16.05.2012 18:28:09] <26> Info           [AP] (Client) output: VixDiskLib: Trying to open disk [Datastore] VMName/VMName.vmdk using mode san.\n
[16.05.2012 18:34:41] <26> Info           [AP] (Client) output: DISKLIB-LINK  : Opened 'san://snapshot-16089[Datastore] VMName/VMName.vmdk@XXX?veeam02/XXX' (0x1e): plugin, 62914560 sectors / 30 GB.\n
[16.05.2012 18:37:01] <17> Info           [AP] (Client) output: VixDiskLib: Trying to open disk [Datastore] VMName2/VMName2.vmdk using mode san.\n
[16.05.2012 18:43:27] <17> Info           [AP] (Client) output: DISKLIB-LINK  : Opened 'san://snapshot-16091[Datastore] VMName2/VMName2.vmdk@XXX?veeam02/XXX' (0x1e): plugin, 62914560 sectors / 30 GB.\n

Cause

There's several possible causes to this behavior. Some Multipathing software can cause delays in choosing the correct path and cause it to recalculate this path. Another possible cause is latancy on the C:\ (System Partition) as it's also included in the storage discovery process. If the C:\ drive is on stored on a raid controller, having it failover to write-through instead of write-back mode can cause enough disk latency to cause the same issue.  This can occur in some instances such as raid controller battery failure or if the write-through mode is already set.

Solution

As this is an environmental issue, the first thing to do is try to isolate possible causes. Verify MTU sizes match, remove/disable Multipathing temporarily, check for latency on locals drive on the Veeam server or with SAN itself. 
Click here to send feedback regarding this KB, or suggest content for a new KB.
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 Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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.