Win2k3 and the latest Microsoft iSCSI initiator handling the connection to a LUN sitting on a FAS960. A moderately active 5Gb MS-SQL database is mounted on the LUN. Transaction log on the local Win2k3 server. The LUN itself is only 10Gb, so it is only small.

We also have another system mapping a ~100Gb iSCSI LUN mounted on the same physical volume. This is used to hold a backup image catalog. Flat files, no SQL databases.

HP DL360 and 380 servers. No dedicated HBA's for iSCSI.

No clustering here.

The iSCSI path is shared with other traffic over gigabit fibre. i.e. No dedicated LAN.

We have not had any performance or contention issues of any kind related to iSCSI.

I evaluated the clustering as part of a solution and would strongly advise the use of a dedicated network path for the iSCSI connections to the cluster quorum and shared SQL database. In fact, I believe that it is required by Microsoft for the solution to be supported.

Aaron

-----Original Message----- From: Alan Biren [mailto:ABIREN@amccorp.com] Sent: Monday, 4 April 2005 10:26 PM To: Rob Winters; toasters@mathworks.com Subject: RE: experience with iSCSI from W2K3 servers?

When working with iSCSI on W2K3 server or any Microsoft OS, the key is the networking component. If it is at all possible, I enable Jumbo Frames and create a separate VLAN for the storage traffic, very similar to a FC SAN. You also want to make sure that you Bind the Volumes and make the target Persistent. I also use a VIF (multi or single) as well as etherchannels and NIC Teaming to try to aggregate bandwidth.

If you are able to use SnapDrive, it'll make connecting and managing the LUNs much easier, especially if you will need to increase their size.

I've only used HP Proliant servers. I've used the MS iSCSI Initiator (all versions) and the QLOGIC 4010.

If you are going to cluster and iSCSI environment, I recommend reading MS Article 883397. I would follow the steps even if it not a pure iSCSI environment.

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Rob Winters Sent: Wednesday, March 30, 2005 5:39 PM To: toasters@mathworks.com Subject: experience with iSCSI from W2K3 servers?

Does anyone have feedback or gotchas about W2K3 accessing large iSCSI space on NetApp filers? With what hardware? HBA and/or software initiator?

How about clustering W2K3 servers to a NetApp iSCSI target, or similar HA configurations?

Thanks!

/// Rob

P.S. Yes, *this* is how well the MacOS X research is going... :-|

-- Rob Winters SAIC, NASA Headquarters ISEM Contract rwinters@hq.nasa.gov **************************************************************************** ************************* If you have received this email in error please notify the the system manager or the sender immediately and do not disclosed the to anyone or make copies.

** eSafe scanned this email for viruses, vandals or malicious content ** ** To find out eSafe(TM) and other Aladdin Security Products, contact AMC Corporation at (212) 736-0111 **************************************************************************** *************************

************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************