- Posts: 1
- Liked: never
- Joined: Jun 28, 2010 11:14 pm
We recently pruchased a VNX 5100 SAN. I have added a Fibre HBA into the Veeam server and my ESXi 5.1 servers. Everything is working from a VMware perspective. Now I am trying to get direct SAN access to Veeam for quick backups.
When configuring the LUNs for ESX, I was told by EMC that I should create 1TB luns and the stick them together to make a bigger disk using VMFS extents. That is what I have done and have a VMFS datastore that is 3TB in size; 3 x 1 tb luns jouned together with the extents expansion feature.
On the veeam server I am able to see that the HBA is installed correctly in device manager. EMC told me to install 'Powerpath for winddows" on the veeam server. Disk manager shows me each 1 tb disk (not the 3tb disk that was glued together via extents), all the disks appear offline with a red down arrow, if I right click I can make them online.
In veeam I have modified my backup proxy, selected direct san access transport mode and unticked failover to network. I have manual specified the 3tb VMFS datastore. In my backup job > storage I have selected the correct backup proxy.
I am unable to get the backup job to use the fibre network. It seems to somehow find my old iSCSI direct SAN access network and backup through it instead of the new fibre. What worries me is that in Windows the disks are sperated into 1tb luns rather than appearing as a 3tb datastore; not sure if this is expected. Maybe EMC's advice to use extents is not going to work out....
Any ideas what I might be doing wrong here?
- Product Manager
- Posts: 16901
- Liked: 1439 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
Can you also confirm that you’ve followed the described procedure correctly?
Hope this helps.
- Product Manager
- Posts: 23001
- Liked: 1557 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Users browsing this forum: Bing [Bot] and 6 guests