Cluster
Cluster
63) What is the difference between SQL Server clustering methods: - Active/Active - Active/Passive
Active/Active means that both nodes are active and accessing the shared disk resources, but are running
independent instances. When a node fails, you need to be sure that the remaining node has the resources available
to handle the additional databases that fail over. You can think of it like this. Node A has 1 database on it, and Node
B has 1 database on it. Node A goes down, the resources fail over to Node B, and now Node B has 2 databases
running on it.
In an Active/Passive cluster, you would only have 1 database running on a single node at any given time. Node A is
active with 1 DB, Node B is passive with no DBs. Node A goes down, the resources fail over to Node B. Node B is now
active with 1 database running on it.
I'm sure more experienced cluster admins or SQL admins will savage me for my terminology, but that's it in a
nutshell.
LooksAlive check:
LooksAlive is a basic check in which the Cluster service queries the Windows Service Control Manager to check if the
SQL Server service is still running. By default this check happens every 5 seconds.
Cluster service calls looksAlive function every 5 seconds and LookAlive function Queries the service status by using
the Windows NT Service Control Manager. When the LooksAlive test fails ISAlive test is called immediately.
ISalive Check: A more rigorous IsAlive function is called every 60 second and monitors the health of the SQL Server
by opening up a connection to SQL Server and issuing “select @@servername” query over the connection. If the
checks fail the online Thread reports this failure to the Cluster Service.
During IsAlive check the Cluster Service connects to the SQL Server instance with the help of c:\windows\system32\
sqsrvres.dll and runs SELECT @@SERVERNAME against the instance.
By default, LooksAlive is fired every 5 seconds and IsAlive is fired every 60 seconds. The LooksAlive and IsAlive polling
intervals can be changed in Cluster Administrator or failover cluster manager from the advanced tab for the SQL
Server resource or using the cluster.execommand prompt utility.
65) What is meant by Active – Passive and Active – Active clustering setup?
An Active – Passive cluster is a failover cluster configured in a way that only one cluster node is active at any given
time. The other node, called as Passive node is always online but in an idle condition, waiting for a failure of the
Active Node, upon which the Passive Node takes over the SQL Server Services and this becomes the Active Node, the
previous Active Node now being a Passive Node.
An Active – Active cluster is a failover cluster configured in a way that both the cluster nodes are active at any given
point of time. That is, one Instance of SQL Server is running on each of the nodes always; when one of the nodes has
a failure, both the Instances run on the only one node until the failed node is brought up (after fixing the issue that
caused the node failure). The instance is then failed over back to its designated node.
66) List out some of the requirements to setup a SQL Server failover cluster.
Virtual network name for the SQL Server, Virtual IP address for SQL Server, IP addresses for the Public Network and
Private Network(also referred as Hearbeat) for each node in the failover cluster, shared drives for SQL Server Data
and Log files, Quorum Disk and MSDTC Disk.
67) On a Windows Server 2003 Active – Passive failover cluster, how do you find the node which is active?
Using Cluster Administrator, connect to the cluster and select the SQL Server cluster. Once you have selected the
SQL Server group, in the right hand side of the console, thecolumn “Owner” gives us the information of the node on
which the SQL Server group is currently active.
68) How do you open a Cluster Administrator?
From Start -> Run and type CluAdmin (case insensitive) and the Cluster Administrator console is displayed OR you
can also go to Start -> All programs -> Administrative Tools -> Cluster Administrator.
69) How will you restart your sqlserver on cluster without failing over ..?
Choose option ( Take offline and Bring online option by right clicking node)
70) What will you if want to add a disk to the SQL Group cluster ..?
Need to choose Add Dependancy option after doing that in Cluster administrator tool (or) in Failover Cluster admin
tool from 2008 version
71) As a DBA how will you design active/active cluster requirement . (i.e), how will you manage resource if failed
over ..?
Please read article from MSDN on this to have better understanding
73) Difference between SQLSERVER 2005 and SQLSERVER 2008 Cluster Installation ..?
In sql2005 we have the option of installing sql in remaining nodes from the primary node ., But in sql2008 we need
to go seperately(Login to the bith nodes) for installing sql cluster .
74) What is the status of services on passive node for failover cluster in SQL server?
SQL services will be in manual and stopped. Cluster service will be in automatic and started mode on both the nodes.
75) Can you move the resources after pausing the node?
Yes resources can be moved after pausing the node. But we can't move them back till the node is paused.
77) How does the failover happen? What checks are performed to ensure that another node is up?
LooksAlive - The node which host the SQL server resources is verifed whether this node (server) is up
IsAlive - The node which host the SQL server resources is verifed whether the SQL service is up or not. Basically
running SELECT @@SERVERNAME
78) What will happen if you try to start the fultext service on the passive node.
This can be started on both the nodes as this doesn't have any dependecy on SQL service or any resource which is
possessed by active node.
86) How is the quorum information located on the system disk of each node kept in synch?
The server cluster infrastructure ensures that all changes are replicated and updated on all members in a cluster.
89) What is the difference between a geographically dispersed cluster and an MNS cluster?
A geographic cluster refers to a cluster that has nodes in multiple locations, while an MNS-based cluster refers to the
type of quorum resources in use. A geographic cluster can use either a shared disk or MNS quorum resource, while
an MNS-based cluster can be located in a single site, or span multiple sites.
93) Does MNS get rid of the need for shared disks?
It depends on the application. For example, clustered SQL Server 2000 requires shared disk for data. Remember,
MNS only removes the need for a shared disk quorum.
95) What new functionality does failover clustering provide in Windows Server 2008 ?
New validation feature. With this feature, you can check that your system, storage, and network configuration is
suitable for a cluster.
Support for GUID partition table (GPT) disks in cluster storage. GPT disks can have partitions larger than two
terabytes and have built-in redundancy in the way partition information is stored, unlike master boot record (MBR)
disks.
96) What happens to a running Cluster if the quorum disk fails in Windows Server 2003 Cluster ?
In Windows Server 2003, the Quorum disk resource is required for the Clusterto function. In your example, if the
Quorum disk suddenly became unavailableto the cluster then both nodes would immediately fail and not be able
torestart the clussvc.
In that light, the Quorum disk was a single point of failure in a MicrosoftCluster implementation. However, it was
usually a fairly quick workaround toget the cluster back up and operational. There are generally two solutionsto that
type of problem.
1. Detemrine why the Quorum disk failed and repair.
2. Reprovision a new LUN, present it to the cluster, assign it a driveletter and format. Then start one node with the
/FQ switch and throughcluadmin designate the new disk resource as the Quorum. Then stop andrestart the clussvc
normally and then bring online the second node.
97) What happens to a running Cluster if the quorum disk fails in Windows Server 2008 Cluster ?
Cluster continue to work but failover will not happen in case of any other failure in the active node.
99) What is the standard setting of Lookslive, IsAlive and Pending Timeout?
LooksAlive - 5 sec IsAlive - 30 sec Pending Timeout - 180 sec
Note- Do not modify Pending Timeout. The value, represented in seconds, is the amount of time the resource in either
the Offline Pending or Online Pending states has to resolve its status before the Cluster Service puts the resource in
either Offline or Failed status.
To configure the failover policy, in the Threshold box, enter the number of times the group is allowed to fail over
within a set span of hours. In the Period box, enter the set span of hours. For example, if Threshold is set to 10 and
Period is set to 6, the Cluster Service fails the group over a maximum of 10 times in a 6-hour period. At the 11th
failover in that 6-hour period, the server cluster leaves the group offline. This affects only resources that were failed
over; therefore, if the SQL Server resource failed 11 times, it would be left offline, but the IP could be left online.
=========================================================
What is the difference between SQL Server clustering methods: - Active/Active - Active/Passive
Active/Active means that both nodes are active and accessing the shared disk resources, but are running
independent instances. When a node fails, you need to be sure that the remaining node has the resources available
to handle the additional databases that fail over. You can think of it like this. Node A has 1 database on it, and Node
B has 1 database on it. Node A goes down, the resources fail over to Node B, and now Node B has 2 databases
running on it.
In an Active/Passive cluster, you would only have 1 database running on a single node at any given time. Node A is
active with 1 DB, Node B is passive with no DBs. Node A goes down, the resources fail over to Node B. Node B is now
active with 1 database running on it.
I'm sure more experienced cluster admins or SQL admins will savage me for my terminology, but that's it in a
nutshell.
FAQ:
ISalive Check: A more rigorous IsAlive function is called every 60 second and monitors the health of the SQL Server
by opening up a connection to SQL Server and issuing “select @@servername” query over the connection. If the
checks fail the online Thread reports this failure to the Cluster Service.
During IsAlive check the Cluster Service connects to the SQL Server instance with the help of c:\windows\system32\
sqsrvres.dll and runs SELECT @@SERVERNAME against the instance.
By default, LooksAlive is fired every 5 seconds and IsAlive is fired every 60 seconds. The LooksAlive and IsAlive polling
intervals can be changed in Cluster Administrator or failover cluster manager from the advanced tab for the SQL
Server resource or using the cluster.execommand prompt utility.
Question: What is meant by Active – Passive and Active – Active clustering setup?
An Active – Passive cluster is a failover cluster configured in a way that only one cluster node is active at any given
time. The other node, called as Passive node is always online but in an idle condition, waiting for a failure of the
Active Node, upon which the Passive Node takes over the SQL Server Services and this becomes the Active Node, the
previous Active Node now being a Passive Node.
An Active – Active cluster is a failover cluster configured in a way that both the cluster nodes are active at any given
point of time. That is, one Instance of SQL Server is running on each of the nodes always; when one of the nodes has
a failure, both the Instances run on the only one node until the failed node is brought up (after fixing the issue that
caused the node failure). The instance is then failed over back to its designated node.
Question: List out some of the requirements to setup a SQL Server failover cluster.
Virtual network name for the SQL Server, Virtual IP address for SQL Server, IP addresses for the Public Network and
Private Network(also referred as Hearbeat) for each node in the failover cluster, shared drives for SQL Server Data
and Log files, Quorum Disk and MSDTC Disk.
Question: On a Windows Server 2003 Active – Passive failover cluster, how do you find the node which is active?
Using Cluster Administrator, connect to the cluster and select the SQL Server cluster. Once you have selected the
SQL Server group, in the right hand side of the console, thecolumn “Owner” gives us the information of the node on
which the SQL Server group is currently active.
Question: How do you open a Cluster Administrator?
From Start -> Run and type CluAdmin (case insensitive) and the Cluster Administrator console is displayed OR you
can also go to Start -> All programs -> Administrative Tools -> Cluster Administrator.
1. How will you restart your sqlserver on cluster without failing over ..?
Choose option ( Take offline and Bring online option by right clicking node)
2. What will you if want to add a disk to the SQL Group cluster ..?
Need to choose Add Dependancy option after doing that in Cluster administrator tool (or) in Failover Cluster admin
tool from 2008 version
3. As a DBA how will you design active/active cluster requirement . (i.e), how will you manage resource if failed
over ..?
Please read article from MSDN on this to have better understanding
5. Difference between SQLSERVER 2005 and SQLSERVER 2008 Cluster Installation ..?
In sql2005 we have the option of installing sql in remaining nodes from the primary node ., But in sql2008 we need
to go seperately(Login to the bith nodes) for installing sql cluster .
6. What is the status of services on passive node for failover cluster in SQL server?
SQL services will be in manual and stopped. Cluster service will be in automatic and started mode on both the nodes.
9. How does the failover happen? What checks are performed to ensure that another node is up?
LooksAlive - The node which host the SQL server resources is verifed whether this node (server) is up
IsAlive - The node which host the SQL server resources is verifed whether the SQL service is up or not. Basically
running SELECT @@SERVERNAME
10. What will happen if you try to start the fultext service on the passive node.
This can be started on both the nodes as this doesn't have any dependecy on SQL service or any resource which is
possessed by active node.
13. What is Quorum ? A shared storage need to provide for all servers which keeps information about clustered
application and session state and is useful in FAILOVER situation. This is very important if Quorum disk fails entire
cluster will fails.
18. How is the quorum information located on the system disk of each node kept in synch?
The server cluster infrastructure ensures that all changes are replicated and updated on all members in a cluster.
21. What is the difference between a geographically dispersed cluster and an MNS cluster?
A geographic cluster refers to a cluster that has nodes in multiple locations, while an MNS-based cluster refers to the
type of quorum resources in use. A geographic cluster can use either a shared disk or MNS quorum resource, while
an MNS-based cluster can be located in a single site, or span multiple sites.
25. Does MNS get rid of the need for shared disks?
It depends on the application. For example, clustered SQL Server 2000 requires shared disk for data. Remember,
MNS only removes the need for a shared disk quorum.
27. What new functionality does failover clustering provide in Windows Server 2008 ?
New validation feature. With this feature, you can check that your system, storage, and network configuration is
suitable for a cluster.
Support for GUID partition table (GPT) disks in cluster storage. GPT disks can have partitions larger than two
terabytes and have built-in redundancy in the way partition information is stored, unlike master boot record (MBR)
disks.
28. What happens to a running Cluster if the quorum disk fails in Windows Server 2003 Cluster ?
In Windows Server 2003, the Quorum disk resource is required for the Clusterto function. In your example, if the
Quorum disk suddenly became unavailableto the cluster then both nodes would immediately fail and not be able
torestart the clussvc.
In that light, the Quorum disk was a single point of failure in a MicrosoftCluster implementation. However, it was
usually a fairly quick workaround toget the cluster back up and operational. There are generally two solutionsto that
type of problem.
1. Detemrine why the Quorum disk failed and repair.
2. Reprovision a new LUN, present it to the cluster, assign it a driveletter and format. Then start one node with the
/FQ switch and throughcluadmin designate the new disk resource as the Quorum. Then stop andrestart the clussvc
normally and then bring online the second node.
29. What happens to a running Cluster if the quorum disk fails in Windows Server 2008 Cluster ?
Cluster continue to work but failover will not happen in case of any other failure in the active node.
31. What is the standard setting of Lookslive, IsAlive and Pending Timeout?
LooksAlive - 5 sec IsAlive - 30 sec Pending Timeout - 180 sec
Note- Do not modify Pending Timeout. The value, represented in seconds, is the amount of time the resource in either
the Offline Pending or Online Pending states has to resolve its status before the Cluster Service puts the resource in
either Offline or Failed status.
To configure the failover policy, in the Threshold box, enter the number of times the group is allowed to fail over
within a set span of hours. In the Period box, enter the set span of hours. For example, if Threshold is set to 10 and
Period is set to 6, the Cluster Service fails the group over a maximum of 10 times in a 6-hour period. At the 11th
failover in that 6-hour period, the server cluster leaves the group offline. This affects only resources that were failed
over; therefore, if the SQL Server resource failed 11 times, it would be left offline, but the IP could be left online.
33. What is the status of the Cluster Service and SQL service on both the nodes? Would they both were stop on
the passive node?
Cluster service is automatic and started mode on all the nodes. But SQL Service will run only on the active node.
34. Is it possible to put Cluster Group and SQL Group on different nodes?
Yes it is Possible. If you have one group on one node and another group on another node... that will run.
A:
Looks Alive check:Looks alive check is a basic resource health check to verify that the service(SQL service in our
context) is running properly.To perform this , cluster service queries the windows service control manager to check
the status of the service.By default looks alive check will happen in every five seconds.
Is Alive check: An exhaustive check to verify that a resource is running properly. If this check fails, the resource is
moved offline and the failover process is triggered. During the Is alive check the cluster service connects to the SQL
server instance and execute select @@SERVERNAME.It will check only the SQL server instance availability and does
not check the availability of user databases.
You can specify two polling intervals and a timeout value for resources. The polling intervals affect how often the
MSCS Resource Monitor checks that the resource is available and operating. There are two levels of polling; they are
known in Cluster Administrator as "Looks Alive" and "Is Alive." These values are named for the calls that the
Resource Monitor makes to the resource to perform the polling. In "Looks Alive" polling, MSCS performs a cursory
check to determine if the resource is available and running. In "Is Alive" polling, MSCS performs a more thorough
check to determine if the resource is fully operational. The timeout value specifies how many seconds MSCS waits
before it considers the resource failed.