B&R 6.5 - Direct San Access not working on an IBM DS3300

[WinstonWolf]

Hello ,

I try since 4 days to become Veeam Backup & Replication to work with direct SAN Access .
I use Veeam Backup & Replication 6.5 on an Windows 2008 R2 Server, who is connected with two Network Cards with both of the Controllers of an DS3300 Storage from IBM, for working with direct SAN Access.

What i do is :

- I disabled Multipath in Windows Server Features
- I connect the DS 3300 via ISCSI Initiator


- I can see the Disks in Windows Disk Manager


- I choose Direct San Access as Transport Mode at the Backup Proxy


- I choose manual Selection for the connected Datastores and i add the Datastores


- I do an rescan on the Managed Servers

But allways the same

Is there something i forgot ? Please help .

[claudiofolu]

Hello Winston,
Are those disks mapped to the Windows Server VMFS datastores?

[WinstonWolf]

I dont understand you question .

Windows Server VMFS Datastore ? I see this Disks as unmount an uninitialised in Windows Disk Manager . Do you mean this ?

[claudiofolu]

I mean the content of the disks, are VMFS filesystem?
Are those disk also presented to a ESX or your are working with HyperV?

[dellock6]

Well, looking at the names of the datastores they are VMFS.
Seems to me everything is configured correctly, just to be sure, ACL on the DS3300 are enabled to let Veeam physical server read datastores?

Luca.

[WinstonWolf]

Hello ,

I cant find any ACL in the DS3300 . The only thing i find is the Host to Logical Drive Mapping .

Hmm ?!?!?

[Vitaliy S.]

Do you have any kind of access control on that SAN device management UI (sorry I'm not familiar with this make and model)?

[mykl_74]

Hi Winston, I also have a DS3300 and am trying to set up Direct SAN. I have an open case with support. When I make some progress I'll let you know what I had to do to make it work.

But my issue sounds similar to yours. I can see the uninitialized volumes in Windows disk mgr, but directsan backup fails.

[mykl_74]

Good morning Winston, I have made some good progress getting veeam running with my DS3300. One question- do you have a single or dual controller model? I have dual. Here's what I've had to do on my Veeam server, which is a physical server. I have a NIC dedicated iSCSI, and connected directly to the same switch that runs all iSCSI traffic.

1) Windows iSCSI initiator Setup.
Make sure your targets are set up to automatically log on, and you have entered the CHAP password if you use one. (I do)
If you have dual controllers, make sure the IP address for each controller is configured on the Discovery tab.
On the Volumes & devices tab, use the autoconfigure button to fill in the scsi device paths. You should have one path for each LUN. Example:
\\?\scsi\#disk&ven_ibm&prod_1726-3xx__fastt#1&1c121344&0&00.........

2) Windows volumes.
Make sure you can see each LUN in Windows Disk Management. When I started, I saw all LUNs, but some showed 'Offline - Healthy' and some were 'Offline - Unallocated'. The unallocated ones were not able to back up.

3) IBM Controller setup.
Open IBM DS Storage Manager 10, and connect to your DS3300 device. On modify tab, click on Change logical drive ownership/Preferred path. As I mentioned in #2, half my LUNs were failing. It was due to some luns preferring Controller A vs. B. All my A LUNs worked, B LUNs failed. I moved all my LUNs to controller A, and all my VMs are now ableto back up with direct SAN.

Hope this helps!