Installing SQL205 in a cluster with mount points

I am struggling with an installation of SQL2005 on Windows Server 2003 SP1. I
am trying to set up a 2 node cluster with a single instance of sql2005. I
need to use mount points so I create a shared disk for the mount points and 2
disks which are mounted in there. The shared disk is called M: and the other
disks have names (DB and Logs). There will be more in due course but I
thought I would start with 2.
The install proceeds okay until it gets to the point where I have to choose
a cluster group to put it in. I have created one with M: in it plus the two
mounted disks. However, when I select that one it insists in making M: the
destination for the data files and, of course there is not enough space there
for them. It seems to be completed incapable of using the mount points. In
fact ir doesn't see them at all.
Does anyone know how to fix this or is it just not possible to use mount
points with SQL2005 in a cluster despite what the documentation says
Hi Colin,
This link has information about special mount point considerations
http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribi en el mensaje
news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>I am struggling with an installation of SQL2005 on Windows Server 2003 SP1.
>I
> am trying to set up a 2 node cluster with a single instance of sql2005. I
> need to use mount points so I create a shared disk for the mount points
> and 2
> disks which are mounted in there. The shared disk is called M: and the
> other
> disks have names (DB and Logs). There will be more in due course but I
> thought I would start with 2.
> The install proceeds okay until it gets to the point where I have to
> choose
> a cluster group to put it in. I have created one with M: in it plus the
> two
> mounted disks. However, when I select that one it insists in making M: the
> destination for the data files and, of course there is not enough space
> there
> for them. It seems to be completed incapable of using the mount points. In
> fact ir doesn't see them at all.
> Does anyone know how to fix this or is it just not possible to use mount
> points with SQL2005 in a cluster despite what the documentation says
|||Dear Antonio,
Thanks for the info. The bit that is mssing from that document - at least I
cannot find it is how big the base drive has to be. As far as I can see what
is not mentioned is that the SQL 2005 installation will put some files in the
base drive. Most of the installation goes somewhere such as C:\Program
Files\... but some files are put in the shared drive which is acting as the
base drive. I have tried creating the base drive with about 50 GB and SQL
2005 then installs. I don't know how much will go in there for different
installation choices but I am now trying a 30GB base drive to see if that is
big enough.
Anyway, to summarise, the base drive isn't just for mount points as the
document suggests but also holds quite a few installation files which I guess
need to be shared between the cluster nodes.
Best wishes...
Colin
"Antonio Soto" wrote:

> Hi Colin,
> This link has information about special mount point considerations
> http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of the
> sender. This message does not imply endorsement from Solid Quality Learning,
> and it does not represent the point of view of Solid Quality Learning or any
> other person, company or institution mentioned in this message
>
> "Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribió en el mensaje
> news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>
>