Having problems service packing (sp2) on 4 node cluster

underprocessablep.s. I should have added that this is all x64 windows and sql.
"Mark Broadbent" <nospam@.nospam.com> wrote in message
news:%232X3csx3HHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hope somebody has had this problem too..
> Keep trying to install SP2 (on active node as per instructions) and have
> had several problems.
> When I had all four instances failed onto the node and I was trying to SP
> all of them the installer would simply disappear (and close) - no process
> remained.
> Then I attempted to do the install only to first instance (failing other 3
> over to other nodes). Installer was slightly more successful, upgrading
> all shared components but failed on the instance based ones e.g. the SQL
> Service and Analysis service.
> After reboots and several attempts to upgrade these two components of the
> first instance (which causes the installer to disappear). I have decided
> to upgrade the instance components of another instance via another
> physical host. Now the installer seems to just be hanging doing nothing
> (around 2 hours now). See screen shot. Any one got any advice?
> Thanks in advance,
> Mark.
>
>

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 upgrade of active/active cluster

I'm planning a hardware upgrade of our active/active dual node Windows
2000 sql cluster. Hostnames and IP addresses will remain unchanged.
Here's a high level overview of my plan..
1. move all cluster groups/resources to node 2
2. shutdown sql services on node 1
3. uninstall MSCS on node 1
4. evict node 1 from cluster using cluster administrator on node 2
5. power down node 1
6. reset node 1 account in domain
7. add new node 1 to domain
8. install MSCS on new node 1
9. install sql server on new node 1
10. install sql sp2 on new node 1
11. add new node 1 to existing cluster
12. verify that all resources can move to new node 1 correctly
** repeat for node 2
I know this has been discussed several times before in this newsgroup,
but there's a few extra steps in there that I believe have not been
addressed in the past. Does the above look accurate and also is it
feasible to roll back to a ghost image and backup of the quarum in the
event of a problem with either server?
Thanks in advance,
David
Step 1.5 Uninstall SQL from Node 1. If you do not do this step, you cannot
do step 9. Uninstalling SQL also tells the existing cluster not to look for
that node any longer as a valid SQL host node. You can do it as step 8.5,
but you will have to wait on some timeouts since the node is no onger there.
I haven't tried a ghost of the quorum as a restore technique, but I suspect
that given the SQL configuration changes, it wouldn't work.
Since you are reusing node names, make sure you have removed all traces of
the nodes from Active Directory and allowed it to globally synch before
trying to add the machines back in.
IMHO, I would take the opportunity to upgrade to Windows 2003 as a host OS
during the upgrade. In that case, you would need to be on at least SP3a
before starting the cluster upgrade.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<davidawest@.gmail.com> wrote in message
news:1132725533.573424.291710@.z14g2000cwz.googlegr oups.com...
> I'm planning a hardware upgrade of our active/active dual node Windows
> 2000 sql cluster. Hostnames and IP addresses will remain unchanged.
> Here's a high level overview of my plan..
> 1. move all cluster groups/resources to node 2
> 2. shutdown sql services on node 1
> 3. uninstall MSCS on node 1
> 4. evict node 1 from cluster using cluster administrator on node 2
> 5. power down node 1
> 6. reset node 1 account in domain
> 7. add new node 1 to domain
> 8. install MSCS on new node 1
> 9. install sql server on new node 1
> 10. install sql sp2 on new node 1
> 11. add new node 1 to existing cluster
> 12. verify that all resources can move to new node 1 correctly
> ** repeat for node 2
> I know this has been discussed several times before in this newsgroup,
> but there's a few extra steps in there that I believe have not been
> addressed in the past. Does the above look accurate and also is it
> feasible to roll back to a ghost image and backup of the quarum in the
> event of a problem with either server?
> Thanks in advance,
> David
>

Hardware Requirements for SQL server DB Clustering

Hi,
I want to cluster my SQL server DB and just wondering what hardware (how
many systems, adapters, what will be installed on what etc) will be required
to do the same. We are planning to use Win2k3 "Server Cluster" service for
the same.
Where will SQL Server DB reside? What will be installed on Nodes?
Thanks in advance
Pankaj A. Chitriv
Its a pretty vague question with a lot of decisions to be made. You need at
least two servers with the same hardware. Each server should have at least 2
nic cards. You need to decide what type of shared storage you want. It can
range from a scsi drive array to a fiber channel SAN.
The database needs to reside on the shared storage. If you have only one
database you will be using and active/passive clustering model.
You can Google or search MS for SQL and clustering and come up with a slew
of reading. Check with your hardware vendor to work out the hardware details
and come up with something you want and can afford. We'll be here to help
along the way.
Hope it helps.........
dw
Don Wilwol
http://spaces.msn.com/members/wilwol/
"Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
news:36FB2975-3CCB-4160-8503-DAD488F140E0@.microsoft.com...
> Hi,
> I want to cluster my SQL server DB and just wondering what hardware (how
> many systems, adapters, what will be installed on what etc) will be
> required
> to do the same. We are planning to use Win2k3 "Server Cluster" service for
> the same.
> Where will SQL Server DB reside? What will be installed on Nodes?
> Thanks in advance
> Pankaj A. Chitriv
>
|||Pankaj,
I've got more information for you. I'm most familiar with
COMPAQ/HP cluster implementations, so I'll suggest
something from their product line that will give you an
idea as to what hardware is needed. There is something
called a "packaged cluster", which contains what you need
(a baseline config only. There are many options to consider)
Just google for "DL380 packaged cluster" and hit the first link
that comes up. (today, anyway) It should
Now, for more in-depth "how-to-do-it" information, I will
suggest that you get a book called
"Sql server 2000 Black Book" by Coriolis.
This book explains in great detail what needs to be done to
get clustered SQL working. Only about 40 pages of it is
for clustering, but I still think that it is the best
printed resource.
Costs about 60 bucks but worth it, since you are about to spend 40K or more...
Good Luck!
jg

Quote:

Originally posted by Pankaj
Hi,
I want to cluster my SQL server DB and just wondering what hardware (how
many systems, adapters, what will be installed on what etc) will be required
to do the same. We are planning to use Win2k3 "Server Cluster" service for
the same.
Where will SQL Server DB reside? What will be installed on Nodes?
Thanks in advance
Pankaj A. Chitriv

|||Thanks a lot Don.
"Don Wilwol" wrote:

> Its a pretty vague question with a lot of decisions to be made. You need at
> least two servers with the same hardware. Each server should have at least 2
> nic cards. You need to decide what type of shared storage you want. It can
> range from a scsi drive array to a fiber channel SAN.
> The database needs to reside on the shared storage. If you have only one
> database you will be using and active/passive clustering model.
> You can Google or search MS for SQL and clustering and come up with a slew
> of reading. Check with your hardware vendor to work out the hardware details
> and come up with something you want and can afford. We'll be here to help
> along the way.
> --
> Hope it helps.........
> dw
> Don Wilwol
> http://spaces.msn.com/members/wilwol/
>
> "Pankaj" <pankajchitriv@.rediffmail.com(donotspam)> wrote in message
> news:36FB2975-3CCB-4160-8503-DAD488F140E0@.microsoft.com...
>
>

Hardware general question about sql

Dear folks,
Nowadays, we have got an Active-Active cluster for to attend our business as
usual. Each node own the following main features:
-8 processors xeon 700 Mhz
-8 Gb RAM
-RAID 5 (up to 400 gb ) 12 disks approx.
-OS 32 bit (Advanced Server)
-Sql2000k with sp3
-Quorum disk have 36,6 GB
-Our growing per w is almost 50 gb.
-Databases are forty.
The above configuration was bough five years ago, so that, which could be a
good migration of this hardware?
We are thinking over to buy Itanium but we don't know if TCO is good with
such growing of data.
Maybe a good solution will be buy 64-bit hardware and by the moment to
install our sql2000k and within six months or so (when SP1 for sql server
2005 is released) move the data to that version.
Any input will be greatly.
Regards,Enric wrote:
> Dear folks,
> Nowadays, we have got an Active-Active cluster for to attend our
> business as usual. Each node own the following main features:
> -8 processors xeon 700 Mhz
> -8 Gb RAM
> -RAID 5 (up to 400 gb ) 12 disks approx.
> -OS 32 bit (Advanced Server)
> -Sql2000k with sp3
> -Quorum disk have 36,6 GB
> -Our growing per w is almost 50 gb.
> -Databases are forty.
> The above configuration was bough five years ago, so that, which
> could be a good migration of this hardware?
> We are thinking over to buy Itanium but we don't know if TCO is good
> with such growing of data.
> Maybe a good solution will be buy 64-bit hardware and by the moment to
> install our sql2000k and within six months or so (when SP1 for sql
> server 2005 is released) move the data to that version.
> Any input will be greatly.
> Regards,
What hardware issues, if any, are you currently having? Assuming your
queries are performance tuned (which should always be the first order of
business when it comes to performance), you need to determine where the
hardware is failing you. Are you CPU bound? Disk bound? Memory bound?
50GB of growth per w is significant. Could you have meant 50MB /
w? Given that you only have 400GB of disk, 50GB / w doesn't leave
you much time.
You have a powerful, but older server. You could probably get better
performance out of a modern 4-way Xeon server. Since SQL 2005 will run
on 64-bit AMD and x86 boxes, I might consider waiting for that version
and skip Itanium.
If you determine that you are disk bound, you may want to consider using
a SAN or a different RAID implementation. It sounds like you have RAID 5
for everything (data, logs, temdb). You will normally get much better
performance using a RAID 1+0 array for data, and RAID 1+0 or RAID 1
arrays for log files and tempdb. Unless activity is low during log
backups and full backups, you may want to consider backing up to an
array that's different than the data array.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If you're not experiencing any problems with your current set-up, and the SW
side is fully optimized, then IMHO you don't really have to change anything.
ML

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:

Hangs on Applying Computer Settings

I have 2 nodes Cluster Active/Passive on Windows 2003. When I reboot either
one, it comes fast no problem but when I logon to the node it takes 15
minutes waiting on "Applying Computer Settings" message then it will show
the desktop.
I didn't install SQL 2000 yet, I need to solve this issue before I install
it.
Does any one have this issue that it takes so long to logon?
Thanks
Ayad
Sounds like a service start issue. Check your system event log to see if
any services are hanging on startup. BITS is one I typically have problems
with. Setting it to manual startup seems help.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Ayad" <ashammout1@.hotmail.com> wrote in message
news:eU0BdXBzEHA.352@.TK2MSFTNGP14.phx.gbl...
> I have 2 nodes Cluster Active/Passive on Windows 2003. When I reboot
either
> one, it comes fast no problem but when I logon to the node it takes 15
> minutes waiting on "Applying Computer Settings" message then it will show
> the desktop.
> I didn't install SQL 2000 yet, I need to solve this issue before I install
> it.
> Does any one have this issue that it takes so long to logon?
> Thanks
> Ayad
>