Clustering using iSCSI+LUN using NetAPP

[Ste]

Hi All,

i'm trying to create a cluster for SQLServer using two Win2k3 Enterprise
and one Netapp FAS250 appliance. I've netapp license for iscsi, so I've
created a Lun, and mapped using microsoft iSCSI tools on first host,
created a simple disk. Now if I go on second host I see a raw disk, and
windows wanna to repartiton and format again.
But should i see the same partition with the same data on both devices,
isn't it?

Thanks
Ste

[Ryan Sokolowski [MVP]]

Windows uses a shared-nothing model, meaning that only one node can have
access to the volume at a time.

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

This posting is provided "AS IS" with no warranties, and confers no rights.
"Ste" <s...@i.net.it> wrote in message
news:5o3v69F...@mid.individual.net...

[John Toner [MVP]]

I agree. You should not attempt to have both nodes accessing the disk
simultaneously until cluster is installed. If you want to verify that the
2nd node can see the partition, you should reboot the box and then mount the
partition in disk manager. By default in 2003 Enterprise edition, Windows
has the "automount" feature disabled...this is why you would need to add a
mount point to this disk in order to see it properly. See the following KB
for more details.

http://support.microsoft.com/kb/822653

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"Ryan Sokolowski [MVP]" <ry...@clustering101.com> wrote in message
news:%23$XjerOFI...@TK2MSFTNGP04.phx.gbl...

[John Fullbright]

It sounds very much like you're creating the LUN on the FAS250, then
directly connecting via the MS iSCSI initator. Why don't you use SnapDrive
(the Netapp host provisioning component)?

With or without SnapDrive, you need to have clustering installed so that the
Clusdisk driver controls access to the chared disk resource. I guess
without Snapdrive the process would be:

1. Create LUNs for the quorum, Dtc, and application of the FAS.
2. On NodeA, connect to the LUNs
3. On NodeA, configure MSCS
4. On NodeA, create the disk resources and bring them online
5. On NodeB, connect to the LUNs (confire the iSCSI initator)
6. On NodeB, configure MSCS

If you have SnapDrive installed on each host, the process is much simpler.
You'll find the process detailed in the SnapDrive Installation and
Administration Guide. If you plan on leveraging the Netapp hardware VSS
provider to backup SQL, then you'll want both SnapDrive and SnapManager for
SQL installed. The VSS writer for SQL is built into the application.
Netapp has a hardware VSS provider built into the firmware of each FAS
device. The VSS requestor, the VSS component that cordinates the backup is
implemented in SMSQL. Snapdrive provides provisioning and path manaagement
as well as the "glue" or ZAPI interface that connects all the pieces.

John

"Ste" <s...@i.net.it> wrote in message
news:5o3v69F...@mid.individual.net...