Database Reference
In-Depth Information
2.
Execute the following TSQL by opening a New Query window within SSMS:
declare @loop1 int
declare @loop2 int,@j int
print 'enter number'+ Cast(@loop2 as varchar)
set @loop1=1
while (@loop1<=100)
begin
print @loop1
set @j=@loop1*@loop2
print @loop2
set @loop1=@loop1+1
end
go
The common cause for a failover cluster may be due to hardware failure or an operating
system failure. To perform the recovery steps, let us assume the following two scenarios
as an example:
F
Scenario one is a failure caused by corruption of the Windows operating system. This
is a serious problem to resolve.
F
Scenario two is a failure of the disk controller due to a mismatch of firmware drivers.
This is a less serious problem where the node is offline but not irretrievably broken.
How to do it...
In the event of a failover cluster failure, it is essential to recover from the failure as quickly as
possible. Let us have a look at the required steps in recovering and troubleshooting a failover
cluster failure.
1. The most efficient way to monitor the failover cluster nodes is to monitor the log files.
Open the utility named Failover Cluster Management (FCM) snap-in from Start |
Programs | Administrative tools.
2.
In case the operating system is Windows Server 2003, then use Cluster
Administrator (or
cluadmin.exe
) MMC (Microsoft Management Console)
snap-in by navigating to Start | Programs | Administrative tools. Using the
Cluster Administrator snap-in displays the properties of each new node by
right-clicking on a resource.
3.
The FCM displays the status of the Windows failover cluster in the middle pane.
This console can also be used to configure nodes and services in addition to the
information status displayed.
Search WWH ::
Custom Search