Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .NET)

where x is the drive letter of the old quorum disk.

12.Place the new disk resource in the Cluster Group.

13.Bring this disk resource online.

14.Right-click the cluster name and select Properties.

15.Select the Quorum tab and make the new drive the quorum resource.

16.Using the Computer Management Services tool, access the Cluster Service Properties dialog box and:

a.Stop the Cluster service.

b.Remove -fixquorumas a start parameter.

c.Start the Cluster service.

17.Start the Cluster service on the other node.

18.Delete the RemoveMe resource.

19.Bring the cluster group online.

20.Using the Computer Management Services tool, access the Cluster Service Properties dialog box and change the Cluster service startup type to Automatic on both nodes.

21.Reboot both nodes.

Recovering One Cluster Node

This section describes how to restore the Cluster Server and cluster database if one of the cluster nodes fails.

Unexpected software behavior, such as corruption of a cluster-critical file, may cause a partitioned cluster, in which one node of the cluster is unaware of the presence of the other operating node. In this situation, each node may attempt to take control of the shared quorum device, thus potentially rendering one node unable to function as a member of the cluster.

How to Recover One Cluster Node

The following procedure is based on an example scenario in which Node_B

has failed, and the quorum resource has successfully failed over to Node_A. 7 The operating system on each node is still intact, and therefore does not

require recovery. The status of MSCS on Node_B is unknown, so it must be reinstalled (if using Windows 2000) or cleaned up (if using Windows .NET).

Legato NetWorker, Release 7.0

129

Disaster Recovery Guide