Re: mount points help urgent

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Anthony Thomas" wrote:

Mounted volumes still have to be mounted to an assigned drive letter volume.
SQL Server still has to depend on this drive letter.


Quite true. In fact, a mounted volujme should depend on the root drive. But
the SQL Server 2005 resource doesn't have to depend the mounted volume
(although it probably should).

Linchi


--

"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D24BAF11-4962-4C2D-9DE9-84F0F9C7A984@xxxxxxxxxxxxxxxx
Does sql need to be dependant on any of the disks?

For some unknown reason, the SQL Server resource does not have to depend
on
a mounted volume when you place a database file on that mounted volume.
This
is different from the behavior with a drive letter. This also means that
you
can take that mounted volume offline, thus taking the database on it
offline,
without affecting the resource group. In most cases, this would not make
much
sense. After all you go through trouble to create a cluster for HA. So,
I'd
suggest that you still add the dependency so that the SQL Server resource
does depend on any used mounted volume.

Linchi

"mapleleaf" wrote:


I know how to create mount point in windows 20003 cluster, I am not sure
how
to set it up with SQL 2005 running on the cluster.
Does sql need to be dependant on any of the disks? I have tried
looking for
a guide, but cannot find.

current setup active active cluster running. I need to add san space
which
will hold the databases. The san will be carved up into drive letters.
each
drive letter will hold 3 mount points.
ie.
node 1
J:-2 mount point
k:2 mount point
l:2 mount point

node 2-
r:-2 mount point
s:2 mount point
t:2 mount point

each node would be able to own the disk if the other node failed over.

any help is appreciate. I have tried books online etc.. cannot find a
good
step by step.;


--
mapleleaf
------------------------------------------------------------------------
mapleleaf's Profile: http://www.dbtalk.net/m624
View this thread: http://www.dbtalk.net/t346064





.

Relevant Pages

  • Re: N+1 Configuration
    ... Server would try and start before the Tempdb mount point came fully online. ... different from using a drive letter, in which case the SQL Server resource ... The current cluster is Active/Passive. ...
    (microsoft.public.sqlserver.clustering)
  • Re: N+1 Configuration
    ... I'm all straight on using mount points and now only a single root LUN ... The current cluster is Active/Passive. ... I'm adding a new third server that has four LUNS presented to only it so far ... two instances of SQL can be using the same drive letter though (even if, ...
    (microsoft.public.sqlserver.clustering)
  • Re: N+1 Configuration
    ... Every clustered instance will require it's own drive letter but off that you ... can hang a bunch of mount points. ... How to configure volume mount points on a Microsoft Cluster Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: mount points help urgent
    ... DOES NOT depend on physical drive letter, ... I would still make SQL server depend on the mounted physical drive ... drive letter will hold 3 mount points. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Log Shipping share on cluster
    ... dependency of the SQL Server resource. ... SQL Server won't even see the drive letter. ... local disk should NEVER be used, because if you lose node in the cluster you ...
    (microsoft.public.sqlserver.replication)