Having fun with moint points

To keep the number of driveletters to a minimum, have
the same directory structure on the instances and do
something with disks and performance I tried this:
MSSQL$I1\Data
\Data1 <- mount point
\Tlog
\Backup
\Backup1 <- mount point
MSSQL$I2\Data
\Data1 <- mount point
\Tlog
\Backup
\Backup1
MSSQL$I3\Data
\Data1
\Tlog
\Backup
\Backup1
And ran into the SQL Setup does not support mount points
bug or feature. So I added driveletter to the mounted disk.
I am still thinking off using the mount points next to the drive
letters. Are the any other issues or disadvantages I should be
aware off?
Hans
Hi
Have you looked at http://support.microsoft.com/kb/819546/en-us "SQL Server
2000 support for mounted volumes"?
On non-clustered systems, the base drive needs a drive letter.
Regards
Mike
"Hans de Bruin" wrote:

> To keep the number of driveletters to a minimum, have
> the same directory structure on the instances and do
> something with disks and performance I tried this:
> MSSQL$I1\Data
> \Data1 <- mount point
> \Tlog
> \Backup
> \Backup1 <- mount point
> MSSQL$I2\Data
> \Data1 <- mount point
> \Tlog
> \Backup
> \Backup1
> MSSQL$I3\Data
> \Data1
> \Tlog
> \Backup
> \Backup1
> And ran into the SQL Setup does not support mount points
> bug or feature. So I added driveletter to the mounted disk.
> I am still thinking off using the mount points next to the drive
> letters. Are the any other issues or disadvantages I should be
> aware off?
> --
> Hans
>

Has anyone resolved [sqsrvres] StartResourceService: StartService?

Hello all,
I am working with a 2 node SQL Server 2000 cluster on Windows Server 2003.
Each node is a primary node for one of two SQL instances (Active/Active).
Everything worked fine until I applied the latest SQL Server service pack
(MS03-031). When I try to move a group (disks and SQL resources) from a
primary node to the secondary node the disks transfer fine but the SQL Server
service fails to start and the group goes back to its original owner after 3
tries. The following errors are in the event log. Any ideas? -Phil
[sqsrvres] StartResourceService: StartService (MSSQL$Inst1) failed. Error:
41d
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 41d)
[sqsrvres] OnlineThread: Error 41d bringing resource online.
Error 41d corresponds to message:
The service did not respond to the start or control request in a timely
fashion.
So the problem seems the sql service itself is unable to start on the other
node. To troubleshoot further you will need to
1- check app + sys logs for any other clues, what errors do you see when
attempting to start the MSSQL$Inst1
do you see that the MSSQL$Inst1 started but then shut down? Are there any
errors stating some dll could not be loaded? Or do you only see the errors
you reported?
2. check the sql error logs(c:\program files\microsoft sql
server\mssql$INST1\LOG\errorlog), if SQL Server started a new errorlog file
should have created during this time. Was one created, if so check for any
errors
3. Check for: "The application failed to initialize properly" error when
starting SQL - ID: 326571.KB.EN-US
4. can you start sql on from a command prompt on the second node? To do
this you will need to fail over to node2, bring online the network name and
sql disks, now run (sql resource would still be offline/failed state)
c:\program files\microsoft sql server\mssql$INST\binn\sqlservr -iINST -c
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
sql

Has anyone resolved [sqsrvres] StartResourceService: StartService?

Hello all,
I am working with a 2 node SQL Server 2000 cluster on Windows Server 2003.
Each node is a primary node for one of two SQL instances (Active/Active).
Everything worked fine until I applied the latest SQL Server service pack
(MS03-031). When I try to move a group (disks and SQL resources) from a
primary node to the secondary node the disks transfer fine but the SQL Server
service fails to start and the group goes back to its original owner after 3
tries. The following errors are in the event log. Any ideas? -Phil
[sqsrvres] StartResourceService: StartService (MSSQL$Inst1) failed. Error:
41d
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status 41d)
[sqsrvres] OnlineThread: Error 41d bringing resource online.Error 41d corresponds to message:
The service did not respond to the start or control request in a timely
fashion.
So the problem seems the sql service itself is unable to start on the other
node. To troubleshoot further you will need to
1- check app + sys logs for any other clues, what errors do you see when
attempting to start the MSSQL$Inst1
do you see that the MSSQL$Inst1 started but then shut down? Are there any
errors stating some dll could not be loaded? Or do you only see the errors
you reported?
2. check the sql error logs(c:\program files\microsoft sql
server\mssql$INST1\LOG\errorlog), if SQL Server started a new errorlog file
should have created during this time. Was one created, if so check for any
errors
3. Check for: "The application failed to initialize properly" error when
starting SQL - ID: 326571.KB.EN-US
4. can you start sql on from a command prompt on the second node? To do
this you will need to fail over to node2, bring online the network name and
sql disks, now run (sql resource would still be offline/failed state)
c:\program files\microsoft sql server\mssql$INST\binn\sqlservr -iINST -c
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Hardware - Multiple Instances of SQL in a cluster

Can anyone advise as to the best practices for installing mulitple instances
of SQL into a cluster? Specifically as to the harddrive quantity and
configuration.
I already have 1 instance in a cluster and need to add more to it. So, my
cluster already has a drive for OS (Mirrored), a drive for MSDTC (Mirrored),
a drive for the quorum (Mirrored) and a drive for the database and
transaction logs (Raid5) (these are not high usage, so 1 drive for db and
logs should be more than sufficient).
I obviously need to add more hard drives to the cluster, but how many per
instance? I assume that I don't need more drives for MSDTC? Howabout the
quorum - is that one per instance? or is it just the databses ?
Thanks
Setesh
You should think of each virtual server as a separate real server. Decide
the disk layout as you would any stand-alone server. It takes at least one
physical disk to 'anchor' the virtual server.
You only need one Quorum disk and one MSDTC instance per cluster.
Geoff N. Hiten
Microsoft SQL Server MVP
"Setesh" <setesh@.nospam.NO> wrote in message
news:e177C7fZFHA.2076@.TK2MSFTNGP15.phx.gbl...
> Can anyone advise as to the best practices for installing mulitple
> instances of SQL into a cluster? Specifically as to the harddrive
> quantity and configuration.
> I already have 1 instance in a cluster and need to add more to it. So, my
> cluster already has a drive for OS (Mirrored), a drive for MSDTC
> (Mirrored), a drive for the quorum (Mirrored) and a drive for the database
> and transaction logs (Raid5) (these are not high usage, so 1 drive for db
> and logs should be more than sufficient).
> I obviously need to add more hard drives to the cluster, but how many per
> instance? I assume that I don't need more drives for MSDTC? Howabout the
> quorum - is that one per instance? or is it just the databses ?
> Thanks
> Setesh
>
|||Setesh
Here is some good information on SQL Clustering and Instances. In short you
will need additional disks only for SQL. The cluster quorum is a single
resource that is created when you install the cluster. You also have to plan
for each node to be able to scale to acceptable performance if a node has to
run more than one instance if their is a failure.
http://msdn.microsoft.com/library/de...ar_cs_9i5u.asp
Also if your installing a Named instance of SQL 2000 on a Windows 2003
cluster you will need to follow this article, setup will fail everytime until
you do. I had to learn this the hard way , my loss is your gain...good
luck!
http://support.microsoft.com/?kbid=815431
Regards
CT
"Setesh" wrote:

> Can anyone advise as to the best practices for installing mulitple instances
> of SQL into a cluster? Specifically as to the harddrive quantity and
> configuration.
> I already have 1 instance in a cluster and need to add more to it. So, my
> cluster already has a drive for OS (Mirrored), a drive for MSDTC (Mirrored),
> a drive for the quorum (Mirrored) and a drive for the database and
> transaction logs (Raid5) (these are not high usage, so 1 drive for db and
> logs should be more than sufficient).
> I obviously need to add more hard drives to the cluster, but how many per
> instance? I assume that I don't need more drives for MSDTC? Howabout the
> quorum - is that one per instance? or is it just the databses ?
> Thanks
> Setesh
>
>
|||Thanks for the info guys, especially the info on installing a named instance
on a 2003 cluster - thats probably saved me hours of work
Cheers
S.
"Charles Tolento" <CharlesTolento@.discussions.microsoft.com> wrote in
message news:F696B9E9-FCB9-481A-8541-5CD4FFE666B7@.microsoft.com...[vbcol=seagreen]
> Setesh
> Here is some good information on SQL Clustering and Instances. In short
> you
> will need additional disks only for SQL. The cluster quorum is a single
> resource that is created when you install the cluster. You also have to
> plan
> for each node to be able to scale to acceptable performance if a node has
> to
> run more than one instance if their is a failure.
> http://msdn.microsoft.com/library/de...ar_cs_9i5u.asp
> Also if your installing a Named instance of SQL 2000 on a Windows 2003
> cluster you will need to follow this article, setup will fail everytime
> until
> you do. I had to learn this the hard way , my loss is your gain...good
> luck!
> http://support.microsoft.com/?kbid=815431
> Regards
> CT
> "Setesh" wrote: