Re: SQL 2005 clustered virtual server

OK, thanks for the advice. Here is the background:

We are implementing a 2 node SQL 2005 cluster with SAN array. The array has
14x 146GB drives. I am now reconfiguring these to 1x mirror for the quorum
resource, 1 mirror for the logs and 5x mirrors for data in which I am
creating 2x partitions on each mirror of 72GB creating 10 logical drives.
This therefore allows me to have 10 instances of SQL?

Can the mirror containing the quorum be partitioned to contain 2 drives of
72GB also to contain both Logs and quorum? This would allow me to create a
further 2x 72GB drives.

Hope this makes sense!

Thanks,
Neil Paddock.

"Edwin vMierlo [MVP]" wrote:


"Neil Paddock" <NeilPaddock@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4DF25485-F208-464B-83B9-92D941CD2286@xxxxxxxxxxxxxxxx
I am looking at mount points to store my individual SQL instances - I have
created a number of mount points on a new volume in the array. When I go
to
add them in to a cluster group, do I select a physical drive? When I do
this, it will only allow me to select the host (G:) which contains the
various mount points!

Can anyone help me with this?


mountpoints in a cluster
http://support.microsoft.com/kb/280297

mountpoints for SQL
http://support.microsoft.com/kb/819546/

Really, what you want is NOT possible.
Stick to how this is documented and supported.

Group1
---rootdisk1 (a drive letter, physical disk resource)
-----mountpointA (physical disk resource)
-----mountpointB (physical disk resource)
--------- SQL instance1

Group2
---rootdisk2 (another drive letter, physical disk resource)
------mountpointC (physical disk resource)
------mountpointD (physical disk resource)
----------SQL instance2

ALL disks an Instance uses MUST be in the Group of the instance. and you can
only have one instance per group
I would only do mount points if you have to (e.g. you run out of drive
letters)

So, why don't your configure multiple groups, with multiple disks inside
each group (as many as your instance need), and configure your instances.
(and only use mount points if you have to !)

If this is not a solution, then you need to have fewer (or one) instance,
and have more databases per instance. That way you can have multiple
databases on disks in one group (performance impact, but that you need to
determine)

Eitherway, what you are trying to do is impossible, stick to
documented/supported setup.

HTH & Rgds,
Edwin



.

Relevant Pages

  • Re: RAID options
    ... scenario you can yank the two partners and use them as fallback should ... This would also be my motivation for the additional drives, ... have OS and programs on the mirror and DATA on the RAID5, ... >> Though SBS is IO intensive performance of the array should not be your ...
    (microsoft.public.windows.server.sbs)
  • Re: Hardware triple mirror RAID 1?
    ... We recently experienced a failure of our 4-disk RAID ... rebuilding, another drive in the array failed, thus trashing the ... three drives would have to fail before the spare drive was rebuilt. ... our concrete and steel industrial building that would mirror the data ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Replacing hard disks in an RAID array
    ... four SATA drives, and move some data off one RAID1 to a second RAID1? ... Computer will declare array "degraded". ... because it is a mirror after all. ... Bring up the Intel Management software for handling RAID arrays. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: Quick question regarding RAID1
    ... If you have just created this array both members will be empty. ... It took roughly 5 minutes on my mirrored 36GB drives. ... If you mean you started out with a single drive and later added a mirror to ... It's a lot more likely that mdadm will just do a dumb copy. ...
    (comp.os.linux.misc)
  • [Summary] saving disksuite info while rebuilding server
    ... "Caution - If a full install of Solaris is performed, ... make sure you have tape backups of everything. ... I had an old workgroup storage array with six 18G drives formatted RAID5 ...
    (SunManagers)