There on and accessable through Explorer and Disk Management. However when I
try to install SQL as a new virtual instance I only have access to my Quorum
Resources.

Installing Sql2000 on 2003 server Active /Passive.

One instance is already installed and running. Has been for several months.

If I remember right for each SQL Instance you would need new spindles as
they cannot be shared between SQL Instances on a MSCS.

"dibblm" <dibblm (AT) hotmail (DOT) com> wrote

Correct.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog

"wasonce" <mike (AT) ntadmins (DOT) org> wrote

I dont understand what you mean as far as new spindles.

I have 3 columes in a 6TB SAN. I have SQL installed to one. With the datbase
on another and the log files on another. Thus utilizing 3 seperate volumes
for disaster management and recovery. What do you mean as far as needing a
new spindle?


"Rodney R. Fournier [MVP]" <rod (AT) die (DOT) spam.die.nw-america.com> wrote in
message news:ekNy3YQIFHA.3364 (AT) TK2MSFTNGP10 (DOT) phx.gbl...

This article
http://www.sqlservercentral.com/colu...youbuyasan.asp
gives you great examples. More disks, more spindles.

Here is a pretty explanation of what a spindle is
http://www.webopedia.com/TERM/s/spindle.html.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"dibblm" <dibblm (AT) hotmail (DOT) com> wrote

I personally think this isn't my issues. I have 42 Drives (Or spindles) I
have plenty of room. The problem is with Sql itself on the install.
Something is hosed in the os where the SQL install doesnt even see the
resources.

Let me get you a little closer to the problem.

You state the sql setup.

You can shoose either local, remote or virtual. ( I choose virtual)
then you have to assign ip's and so on

once you get to the area where you pick where you want to install the
instance to............. My only resource is the Quorum resource itself. I
do not even see my other resources that contain other volumes.

My initial install showed as follows

<Quorum>
<<<<<Q:
<<<<<F: ( left over storage that wasnt needed)
<MSDTC>
<<<<<G: ( About 2 TB of storage)
<<<<<H: (About 2 TB of storage)
<<<<<I: (About 2 TB of storage)
<WEB IP's>
<<<<<Resource of a list of clustered IP;s I use for internal web
addreses

Now when I re-intall or try to install a new instance....

I only see my Quorum resource. My other 2 resources arent even showing.. Yes
they are running , Yes they are on the same node in which I am installing
from. No I cannot see them from the other node when I move them and try to
install from the 2nd node ( as a test)

Everything works normal, I have a 1.5 TB Database that is growing daily that
works great, Clustered resources work and failover as planned.

Now after further explination. Do you still think that this is a spindle
issue when I have plenty of room to work with still?
"Rodney R. Fournier [MVP]" <rod (AT) die (DOT) spam.die.nw-america.com> wrote in
message news:OVLes8zIFHA.1280 (AT) TK2MSFTNGP09 (DOT) phx.gbl...

It sounds like you have configured the SAN as one drive to the OS, but with
multiple partitions. Clustering can only talk to drives, all parturitions
are treated as the same thing. Is this the case?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog

"dibblm" <dibblm (AT) hotmail (DOT) com> wrote

Not at all.
I have 6 mounted volumes.

C: (2 - 36 gig drives in a mirror 0+1 (Operating System))
D: CD Rom
F: (See quorum)
G: (14 - 146 Gig DRives. raid 5 with 1 HOT online spare( 2 TB))
H: (14 - 146 Gig DRives raid 5 with 1 HOT online spare( 2 TB))
I : (14 - 146 Gig DRives raid 5 with 1 HOT online spare( 2 TB))
QQuorum Drive - 2 36 Gig Drives 0+1 Mirror. 2 partitions. Q for Quorum 10
Gig - F for left over.)

SQL Was originally Installed to G Holding the data with H holding the log
files and I holding the backups.

Again,, When I install now to create a new virtual instance, I dont even see
the G, H, and I drives that are in the MSDTC Resource. I dont even see the
Resource. I will do another install today and priovide a screen capture of
my scenario. I will also Provide a screen capture of the mounted Volu mes.


"Rodney R. Fournier [MVP]" <rod (AT) die (DOT) spam.die.nw-america.com> wrote in
message news:O6qswCAJFHA.3788 (AT) tk2msftngp13 (DOT) phx.gbl...

Ok, cause its just not adding up yet.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog

"dibblm" <dibblm (AT) hotmail (DOT) com> wrote

Just to clarify you have what appears to your cluster as six physical disks

C: (2 - 36 gig drives in a mirror 0+1 (Operating System))
D: CD Rom
F: (See quorum)
G: (14 - 146 Gig DRives. raid 5 with 1 HOT online spare( 2 TB))
H: (14 - 146 Gig DRives raid 5 with 1 HOT online spare( 2 TB))
I : (14 - 146 Gig DRives raid 5 with 1 HOT online spare( 2 TB))
QQuorum Drive - 2 36 Gig Drives 0+1 Mirror. 2 partitions. Q for Quorum 10
Gig - F for left over.)

Based on this that would allow you to use disks G:, H: and I: as possible
SQL Server disks

you stated that "SQL Was originally Installed to G Holding the data with H
holding the log
files and I holding the backups."

That would leave you with only the Quorum drives Q:, F: as possible disks

Once you added the H: and I: drives to the existing SQL Server they are no
longer available for use with another instance of SQL Server.

Each SQL Server instance will require its own group, name, IP address and
phyiscal disk

Simple way to look at this is any disk in the group with an existing
instance of SQL Server will not be available and sharing of resources in a
group between multiple groups is not possible.

Dave Whitney
SQL Support