Direct SAN Access doesnt work - support case ID 01806799

[Goran]

Hi to all,

I have tried all suggestions which I could find on this forum with no luck.
Veeam support is trying to solve this too, but since this take some time I decided to try this forum too..
Veeam case nr is 01806799.

We cannot get Direct SAN Access to work.
We have small VMware environment (vCenter and 3 hosts on version 5.1).
Veeam is installed on physical server (all roles), v9.
VMware datastores which are on two IBM storages (IBM DS3524 and IBM DS3400) are presented to Veeam server. They are visible in disk management.
We cannot get Direct SAN access to work, it always fails to network mode.

So far we tried to do following:

-connect Veeam to host instead vCenter, same error
-check all permissions, looks OK (user which Veeam uses to connect vCenter is administrator in vSphere)
-UAC disabled on Veeam server
-antivirus solution disabled on Veeam and vCenter
-datastores manually specified in backup proxy settings

Somehow is suspect that disk are not presented right to Veeam server. Storage team say there is everything OK and there is no special permissions to give.
Microsoft MPIO is installed on Veeam server (before that all LUNs was presented twice).

Disk are in offline status on Veeam server. I se them and can match LUN IDs between disks in windows on Veeam server and vSphere. As I could find on Veeam KB they should be visible as offline?
Can someone verify is that OK? (this link shows online disk https://www.veeam.com/kb1115 , but this is v5?).

Is there way to verify does Veeam sees LUNs as it should?
Do you have any other suggestions?

Thank you in advance.

Goran

[widmerkarl]

Hi Goran,

Just one question: do you use some kind of link aggregation between veeam backup server NICs and SAN switches? For example LACP trunks or so?

[foggy]

Hi Goran, basically, if you see the LUNs in Disk Management snap-in on the proxy, it is enough for direct SAN to be used. There's no particular reason to make disks online as Veeam B&R requires read-only access to the LUN, which is provided when it is in offline mode. There're some limitations of using direct SAN that are outlined in the corresponding user guide section, however, I believe the particular failure reason should be outlined in the job debug log. Do you have the ability to check whether direct SAN works with some other proxy?

[Goran]

Hi to all,

thank you for help.

@kawiMTF
Veeam is installed on physical server (backup, proxy and repository).
This server has two NICs and only one is connected and in use.
FC HBA has two ports and both ports are zoned with storages. MS MPIO is installed.

@foggy
I dont have other server to try other proxy.
I believe that we are compliant with all constraints, I have checked limitations.

We found this error in log:

Code: Select all

WARN|VDDK logon has failed. Logon specification: [VC/ESX: [ip_add_vCenter];Port: 443;Login: [customer_domain\veeamadm];VMX Spec: [moref=vm-5018];Snapshot mor: [snapshot-5025];Transports: [san];Read Only: [true]]. VMDK path: [[VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk]. Read only mode: [true].
[10.07.2016 13:47:45] <  4168> dsk| >>  |VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
[10.07.2016 13:47:45] <  4168> dsk| >>  |Failed to open virtual disk [VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk (flags: 4)
[10.07.2016 13:47:45] <  4168> dsk|       Opening VDDK disk. Logon information: [viConnRef: ip_add_vCenter;host: ip_add_vCenter;login: customer_domain\veeamadm;SOAP port: 443;Authd port: 443;VIC port: 443;Datacenter: customer_domain_Datacenter;Datacenter (mor): datacenter-21;Snapshot: snapshot-5025;VMX: [VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmx;VMDK: [VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk;Transports: san]. Failed.
[10.07.2016 13:47:45] <  4168> dt |     Opening disk. Disk path: [vddk://<vddkConnSpec><viConn name="ip_add_vCenter" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-5018" datacenterRef="datacenter-21" datacenterInventoryPath="customer_domain_Datacenter" snapshotRef="snapshot-5025" datastoreName="VL_ESX_LUN_REPLICA" path="Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmx" /><vmdkPath datastoreName="VL_ESX_LUN_REPLICA" path="Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk" /><transports seq="san" hotAddRedirection="1" /><readBuffer size="4194304" /></vddkConnSpec>]. Is read-only: [true]. Failed.
[10.07.2016 13:47:45] <  4168> dt |   Opening live disk source. Disk path: 'vddk://<vddkConnSpec><viConn name="ip_add_vCenter" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-5018" datacenterRef="datacenter-21" datacenterInventoryPath="customer_domain_Datacenter" snapshotRef="snapshot-5025" datastoreName="VL_ESX_LUN_REPLICA" path="Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmx" /><vmdkPath datastoreName="VL_ESX_LUN_REPLICA" path="Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk" /><transports seq="san" hotAddRedirection="1" /><readBuffer size="4194304" /></vddkConnSpec>'. Failed.
[10.07.2016 13:47:45] <  4168> dt | Performing disk upload (vddkConnSpec>). Failed.
[10.07.2016 13:47:45] <  4168> cli| ERR |Failed to process method {DataTransfer.SyncDisk}
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open VDDK disk [[VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk] ( is read-only mode - [true] )
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:{
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open virtual disk [VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk (flags: 4)
[10.07.2016 13:47:45] <  4168> cli| >>  |Logon attempt with parameters [VC/ESX: [ip_add_vCenter];Port: 443;Login: [customer_domain\veeamadm];VMX Spec: [moref=vm-5018];Snapshot mor: [snapshot-5025];Transports: [san];Read Only: [true]] failed because of the following errors:
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:}
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open disk for read.
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:Failed to open live disk source.
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to upload disk.
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:Disk upload failed.
[10.07.2016 13:47:45] <  4168> cli| >>  |An exception was thrown from thread [4168].
[10.07.2016 13:47:45] <  4168> cli| Trying to poll message from the notification channel (from server side).
[10.07.2016 13:47:45] <  4168> net| Triggering AUX channel synchronization. Request id: {11e8f024-cbbc-4fde-ab5e-37cdf62acbb0}
[10.07.2016 13:47:45] <  3396> net| Received synchronization response {11e8f024-cbbc-4fde-ab5e-37cdf62acbb0}
[10.07.2016 13:47:45] <  4168> cli| No server exception available.
[10.07.2016 13:47:45] <  4168> cli| ERR |Failed to process {Invoke} command
[10.07.2016 13:47:45] <  4168> cli| >>  |Details:
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open VDDK disk [[VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk] ( is read-only mode - [true] )
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:{
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:VDDK error: 13 (You do not have access rights to this file). Value: 0x000000000000000d
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open virtual disk [VL_ESX_LUN_REPLICA] Veeam Test 2 - Thin OS/Veeam Test 2 - Thin OS.vmdk (flags: 4)
[10.07.2016 13:47:45] <  4168> cli| >>  |Logon attempt with parameters [VC/ESX: [ip_add_vCenter];Port: 443;Login: [customer_domain\veeamadm];VMX Spec: [moref=vm-5018];Snapshot mor: [snapshot-5025];Transports: [san];Read Only: [true]] failed because of the following errors:
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:}
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to open disk for read.
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:Failed to open live disk source.
[10.07.2016 13:47:45] <  4168> cli| >>  |Failed to upload disk.
[10.07.2016 13:47:45] <  4168> cli| >>  |--tr:Disk upload failed.
[10.07.2016 13:47:45] <  4168> cli| >>  |Agent failed to process method {DataTransfer.SyncDisk}.

Best regards
Goran

[foggy]

Please show this excerpt to your support engineer.

[Goran]

Hi to all,
just to let you know: installing IBM multipathing software solved issue.

Thanks all for help
Goran