Situation: The client configured 3 NICs to access EqualLogic
However, the Networking under Windows Task Manager
shows only one NIC has traffics. If you open iSCSI Initiator, you should see
all connections under Dell EquallLogic MPIO. If not, we may have SAN
Case 1: Need to install EqulLogic Integration (MPIO) Tools.
Case 2: If you don't install MPIO Tool, you may configure MPIO
Manually. To configure MPIO manually, open iSCSI and select Discovery tab.
Click Discovery Portal and enter group IP address. Select Advanced. In the
General tab, select Microsoft iSCSI Initiator under Local adapter. In
Initiator IP, select the SAN IP in the server. Click OK when finishing
Case 3: One of SAN NIC has a connectivity issue.
Case 4: The Cisco switch port didn't configure right. Missing VLAN
Case 5: .The client uses VLAN 800 for SAN. He needs to add 800 to the
Properties of the NIC configuration.
Case 6: Configure the NIC TCP/IP settings.. EqualLogic recommends to disable
all services except IPv4 as shown below.
Case 7: Re-configure NIC, for example, enable Flow Control; disable both
IPv4 and 6 Large send offload; disable both IPv4 and 6 TCP Connection
Q: We have 3 SQL servers running on windows 2003 and windows 2008. We are
planning to use SQL backup to back up all SQL servers' data to a volume in EqualLogic
SAN. Then use Backup Exec to back up all files in the SAN.
The problem is the Backup server can't see the files in the SQL servers
created. For example, REPEWIN server backs up the SQL data to a folder
called REPEWIN under the SAN volume called SQLinSAN
The PEONLINE server backs up it SQL data to a folder called PEONLINE under
the same SAN volume.
The Backup server doesn't see these two folders: REPEWIN and PEONLINE.
The two SQL servers don't see each other's folder. Why?
What you see is expected. In order to present a
LUN to more than one server you will need to use something like Windows
Cluster Server. Consider this, if you could concurrently access the same
single LUN, how do you protect the data consistency? Two servers could be
writing to the same file at the same time which would cause the data
corruption. In order to share a LUN you need some lock management here to
ensure the data is locked when being concurrently accessed and written to.
What you need to do is to backup the SQL data to
the LUN, un-present the LUN from the SQL server, present it to the
BackupExec server, backup the data and then un-present and present back. You
need to do it in the SAN configuration tool. You could contact your storage
vendor and they will share you with the information you