- Posts: 2
- Liked: never
- Joined: Jan 25, 2011 11:15 am
- Full Name: Bruce English
Today I updated a customer's live environment to v6. They are running ESX 4.1U2 and using VEEAM for backup and replication. The source cluster has an iSCSI attached HP P2000 and the target site had an IBM DS4000 FC attached SAN. The VEEAM server is a virtual server in the source cluster.
After the upgrade I configured a proxy on the target site using an FC attached Windows 2003 server from which I can see the LUNS in use by the cluster and on the source site I have given iSCSI access to the VEEAM server and it can see the LUNS on the souce cluster.
If I configure the proxies to only use direct SAN access my jobs fail stating that they cant access the storage and if I enable failover to LAN the jobs work over the LAN but very slowly.
Have I missed anything or is there any advice on where I should be looking to undertsand why Direct SAN access mode is failing.
Any help or advice appreciated.
- Veeam Software
- Posts: 6041
- Liked: 1847 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2021
Veeam VMCE #1
- VP, Product Management
- Posts: 5638
- Liked: 1163 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
Normal state: "online, healthy, Unknown partiotion"
Do you use a Multipath Driver? (Think it works with and without)
I know only the IBM DS4000 System.
So for that system please check the following:
Do you use the same host type on your storage system for the veeam proxy server like it is configured for the ESX hosts?
What host type setting do you use?