Active/Active clustering

Hi all -
i am fairly new to clustering and here is what i am trying to accomplish:
- 2 DL380 g4 with 5 drives each.
- 2x Raid 1 for sys files
- 2x Raid 1
- 1x Raid 0
I dont have an external SAN device for shared external disk and my question
is A)do I need external SAN device to cluster two servers?
B) Can I use the last drive (Raid 0) for quorum drive?
C) when I run the "cluster wizard" on node 2 I can add the node to the
existing cluster but I am unable to add any disk resources?
thanks for the help!!
-Js
Hi
For clustering, you need shared storage. This is in the form of a SAN.
No SAN, no cluster.
Get familiar with the information on
http://www.microsoft.com/windowsserv...g/default.mspx
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JsX" <JsX@.discussions.microsoft.com> wrote in message
news:42B4652D-6AF1-4688-8493-B233306BFE57@.microsoft.com...
> Hi all -
> i am fairly new to clustering and here is what i am trying to accomplish:
> - 2 DL380 g4 with 5 drives each.
> - 2x Raid 1 for sys files
> - 2x Raid 1
> - 1x Raid 0
> I dont have an external SAN device for shared external disk and my
> question
> is A)do I need external SAN device to cluster two servers?
> B) Can I use the last drive (Raid 0) for quorum drive?
> C) when I run the "cluster wizard" on node 2 I can add the node to the
> existing cluster but I am unable to add any disk resources?
> thanks for the help!!
> -Js
|||Thanks for you response! So, I need an SAN attached storage device, so the 2
servers that i will be clustering can only have 2 drives each for sys files?
and everything else should be on the SAN? am I correct?
thx
-jim
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> For clustering, you need shared storage. This is in the form of a SAN.
> No SAN, no cluster.
> Get familiar with the information on
> http://www.microsoft.com/windowsserv...g/default.mspx
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "JsX" <JsX@.discussions.microsoft.com> wrote in message
> news:42B4652D-6AF1-4688-8493-B233306BFE57@.microsoft.com...
>
>
|||Hi
The OS and the SQL Server executables gets installed on the local drive.
Data and Quorum go on the SAN.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JsX" <JsX@.discussions.microsoft.com> wrote in message
news:5609833A-497E-4EA4-9FE3-872EFB3CB352@.microsoft.com...[vbcol=seagreen]
> Thanks for you response! So, I need an SAN attached storage device, so
> the 2
> servers that i will be clustering can only have 2 drives each for sys
> files?
> and everything else should be on the SAN? am I correct?
> thx
> -jim
> "Mike Epprecht (SQL MVP)" wrote:
|||thx a lot!
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> The OS and the SQL Server executables gets installed on the local drive.
> Data and Quorum go on the SAN.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "JsX" <JsX@.discussions.microsoft.com> wrote in message
> news:5609833A-497E-4EA4-9FE3-872EFB3CB352@.microsoft.com...
>
>
|||"JsX" wrote:
> Hi all -
> i am fairly new to clustering and here is what i am trying to
> accomplish:
> - 2 DL380 g4 with 5 drives each.
> - 2x Raid 1 for sys files
> - 2x Raid 1
> - 1x Raid 0
> I dont have an external SAN device for shared external disk
> and my question
> is A)do I need external SAN device to cluster two servers?
> B) Can I use the last drive (Raid 0) for quorum drive?
> C) when I run the "cluster wizard" on node 2 I can add the
> node to the
> existing cluster but I am unable to add any disk resources?
> thanks for the help!!
> -Js
Hi,
To get clustering to work correctly you need to have a disk set that
can be accessed from both nodes so a SAN or external disk array of
some form is needed. This is why you can add the second node but not
see any disk resources to add.
With regard using a RAID 0 for the quorum, I would say no as if the
quorum goes the cluster goes - again this needs to be on a disk set
that is accessible to both nodes.
Hope that helps,
Digger
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/Clustering-A...ict220965.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=760016

Activated Proc not firing.

Hi There

I just had the following scenario.

I checked sys.service_queues to confirm the my queue has an activated proc assigned to it and is activation_enabled.

I send messages to the service, however i see that the messages just sit in the queue. I run profiler with all SB and Error events there is nothing, i check the sql server log, there is also nothing.

So i have no idea why the activated proc is not firing, all i see in the profiler trace is that the messages are acknowledged but the activated proc does not execute.

For a while i was stumped. i then tried to execute the proc myself and i got a syntax error.

Basically what happened was that i altered a table that the proc used and now the proc cannot execute cos there are more columns that must be inserted so i altered the proc.

However the activated proc still did not fire.

I had to disable and re-enable activation for it to work.

What i am wondering is why was there no indication in profiler or the sql og as the the fact that something was wrong with the activated proc ? Surely the activated proc should have fired and given the same error i got either to the sql log or profiler ?

And why did i have to re-enable activation ? Does sql cache the proc when you activate it and not know that the proc has changed when you alter it ?

Thanx

I had a similar issue...and I am trying to get a resolution on this. In my scenario, it was a new service broker startup (complete rebuild of queues from build scripts that were working in our development database environment)...We have about 30 queues in which all but 1 worked fine. When I went to look to see what happened, the queue was up and activation was on and the messages were sitting in the target queue. When I manually executed the activation stored procedure everything was successful and processed fine (no errors). This is not the first time this has happened, and after it is manually executed the activation seems to occur without issue from that point forward. I am just kind of concerned that when this system is in production and they have to take it down to perform maintenance, this will happen again and since nothing is really "wrong" with the queue, monitoring this is fairly difficult.

Any ideas or suggestions?

|||

When you run into this problem, look at sys.dm_broker_queue_monitors, sys.dm_broker_activated_tasks and sys.service_queues views. We need the content of these views to diagnose the issue.

HTH,
~ Remus

|||

Hi Remus

Ok next time i will get that information.

Thanx

Activated Proc not firing.

Hi There

I just had the following scenario.

I checked sys.service_queues to confirm the my queue has an activated proc assigned to it and is activation_enabled.

I send messages to the service, however i see that the messages just sit in the queue. I run profiler with all SB and Error events there is nothing, i check the sql server log, there is also nothing.

So i have no idea why the activated proc is not firing, all i see in the profiler trace is that the messages are acknowledged but the activated proc does not execute.

For a while i was stumped. i then tried to execute the proc myself and i got a syntax error.

Basically what happened was that i altered a table that the proc used and now the proc cannot execute cos there are more columns that must be inserted so i altered the proc.

However the activated proc still did not fire.

I had to disable and re-enable activation for it to work.

What i am wondering is why was there no indication in profiler or the sql og as the the fact that something was wrong with the activated proc ? Surely the activated proc should have fired and given the same error i got either to the sql log or profiler ?

And why did i have to re-enable activation ? Does sql cache the proc when you activate it and not know that the proc has changed when you alter it ?

Thanx

I had a similar issue...and I am trying to get a resolution on this. In my scenario, it was a new service broker startup (complete rebuild of queues from build scripts that were working in our development database environment)...We have about 30 queues in which all but 1 worked fine. When I went to look to see what happened, the queue was up and activation was on and the messages were sitting in the target queue. When I manually executed the activation stored procedure everything was successful and processed fine (no errors). This is not the first time this has happened, and after it is manually executed the activation seems to occur without issue from that point forward. I am just kind of concerned that when this system is in production and they have to take it down to perform maintenance, this will happen again and since nothing is really "wrong" with the queue, monitoring this is fairly difficult.

Any ideas or suggestions?

|||

When you run into this problem, look at sys.dm_broker_queue_monitors, sys.dm_broker_activated_tasks and sys.service_queues views. We need the content of these views to diagnose the issue.

HTH,
~ Remus

|||

Hi Remus

Ok next time i will get that information.

Thanx

Accessing sys.syslockinfo from an application role

In SQL Server 2005, you must have the VIEW SERVER STATE permission in order to access sys.syslockinfo (http://msdn2.microsoft.com/en-us/library/ms189497).

It seems that the VIEW SERVER STATE permission can only be granted to users.

Once you execute sp_setapprole, the connection loses the permissions of the user and assumes the permissions of the application role (http://msdn2.microsoft.com/en-us/library/ms190998).
So, how can I access the sys.syslockinfo view while using an application role?
Note: I have to maintain compatibility with SQL Server 2000

Here are two ways to allow an application role access to syslockinfo:

a) Create a signed stored procedure that exposes syslockinfo and grant execute on it to the application role. An example of procedure signing has been presented in the following post:

controlling security through stored procedures -- 2005 behaviour

b) Grant VIEW SERVER STATE to public.

Thanks
Laurentiu|||

Thanks for your help. I see that they just added this knowledge base article: http://support.microsoft.com/kb/906549, which has another example. Did you write the kb article?

|||Thanks for posting the KB link, this is recent indeed. No, I didn't write that article but I see it's a complete description of the solution I mentioned as (a). Let us know if you have any trouble with that solution.

Thanks
Laurentiu|||Their example works great for syslogins and sysprocesses. However, it doesn't work for syslockinfo.

This is the error message:
The user does not have permission to perform this action.|||Nevermind, I think there was just something wrong with my install. I reinstalled, and now it is working. Thanks again for your help.