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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTE1IiwiaGFzaCI6IjI3MzVlODQ5LTY0MjYtNGQzNi05ZjVmLTFkZjI4Mzc5ZDUyOSJ9
1-800-691-1991 | 9am - 8pm ET
EN

SAN job failure

Challenge

The error message is as follows

“Backing up object  %objectname%
Unable to establish direct connection to the shared storage (SAN).
Please ensure that:
- HBA is properly installed in the Veeam Backup server computer, or software iSCSI initiator is configured correctly.
- SAN volume can be seen by operating system in the Windows Disk Management snap-in on the Veeam Backup server.
- Read access is allowed for the Veeam Backup server computer on the corresponding LUN (refer to your SAN documentation).”

 

Cause

This is an issue with backup console being unable to access LUNs storing the VMFS volume containing virtual machines. 

Solution

Disable automount (done automatically by v5 setup), install and configure SAN HBA card (or iSCSI Software Initiator), give Veeam Backup server access and read permission on VMFS LUNs (if applicable to your SAN), and ensure that you are seeing your VMFS volumes in the Windows Disk Management snap-in.

Finally it should look like in the figure below:

User-added image

To check what LUN is not presented, you may look through the job log:

 [30.06.2011 07:30:24] <12> Info    (Client) Service output: [2011-06-30 07:30:24.406 07552 verbose 'App'] Trying to open new LUN LVID:4a27de1f-3bdfa39c-f8fd-00237d22abc2/4a27de1e-32f259ff-c73e-00237d22abc2/1.\n

[30.06.2011 07:30:24] <18> Info    (Client) Service output: [2011-06-30 07:30:24.406 07552 trivia 'App'] Attempting to open LVID:4a27de1f-3bdfa39c-f8fd-00237d22abc2/4a27de1e-32f259ff-c73e-00237d22abc2/1.\n

[30.06.2011 07:30:24] <18> Info    (Client) Service output: [2011-06-30 07:30:24.406 07552 error 'App'] No path to device LVID:4a27de1f-3bdfa39c-f8fd-00237d22abc2/4a27de1e-32f259ff-c73e-00237d22abc2/1 found.\n

[30.06.2011 07:30:24] <18> Info    (Client) Service output: [2011-06-30 07:30:24.406 07552 error 'App'] Failed to open new LUN LVID:4a27de1f-3bdfa39c-f8fd-00237d22abc2/4a27de1e-32f259ff-c73e-00237d22abc2/1.\n

[30.06.2011 07:30:24] <18> Info    (Client) Service output: [2011-06-30 07:30:24.406 07552 verbose 'App'] Cannot access LUN LVID:4a27de1f-3bdfa39c-f8fd-00237d22abc2/4a27de1e-32f259ff-c73e-00237d22abc2/1

 You may install VCB framework on Veeam Backup server. It has special diagnostic tool included, called vcbSanDbg.exe. You may run this tool and investigate its output to see if this tool is able to see any LUNs containing VMFS signatures.

If vcbsandbg.exe cannot see VMFS signatures, we recommend opening a support case with SAN vendor on this, because some SAN storage devices have special security/access settings that must be set correctly before the data from mounted LUN can actually be accessed. As soon as vcbsandbg.exe can see signatures, Veeam will start working immediately as well.

More information


KB ID:
1115
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-07-29
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