Seguimiento a las producciones escritas por los estudiantes. Etapa previa

The following procedure describes how to recover a single node in a two-node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available.

IMPORTANT

!

While performing cluster disaster recovery, evict a node from cluster only if the node is corrupt or down. However before recovery, ensure to rejoin the node with the cluster once the node is up and running.

To perform a disaster recovery of a cluster client, follow these tasks:

1. “Evict Node_B from the cluster” on page 134

2. “Select the required items to be recovered for Node_B” on page 135 3. “Start the Cluster service on Node_A” on page 136

Evict Node_B from the cluster

Follow these steps:

1. Use the Cluster Administrator tool on Node_A to evict Node_B from the cluster.

The Microsoft website or documentation for the Cluster Administrator tool provides information about evicting a cluster.

2. At the command prompt, type the following to clean up MSCS:

cluster node Node_B /forcecleanup

CAUTION

!

After cleaning the cluster server, you must reproduce the preexisting application environment on Node_B so that MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to either perform a restore or reinstall each application that was previously installed on the node.

3. Use the Cluster Administrator tool to select Join an existing Cluster and type the cluster name.

4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations.

5. Stop the cluster service in Node_A by using one of the following methods:

• With the control panel service tool, stop the Cluster service.

• At the command prompt, type the following:

Performing Windows Server 2003 and Windows Server 2003 R2 clustered client disaster recovery ¹³⁵ Microsoft Windows Cluster Backup and Recovery

Select the required items to be recovered for Node_B

The procedure differs depending on whether or not the cluster service resides on a domain controller. The following sections provide more information:

◆ “If the cluster service resides on a member server and is not a domain controller”

on page 135

◆ “If the cluster service resides on a domain controller” on page 135 If the cluster service resides on a member server and is not a domain controller

If the cluster service resides on a member server and is not a domain controller:

1. Open the NMM client software on Node_B.

2. From the left pane, select Recover > System Recover Session.

3. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder.

4. Select theSYSTEM COMPONENTSfolder.

Note: If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK.

5. From the System Recover Session toolbar:

a. Click Recover.

b. Click Restore.

If the cluster service resides on a domain controller If the cluster service resides on a domain controller:

1. Boot the NMM client in directory service restore mode.

“Booting the NMM host in Directory Service Restore mode” on page 117 provides more information about these recovery options.

2. Open the NMM client software.

3. From the Options menu, select System Recover Session Options and click NetWorker.

4. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.

IMPORTANT

!

Do not clear the “Use Microsoft best practices for selecting the system state”

box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute.

Microsoft does not support recovery of portions of the operating system.

Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected.

5. Click OK to close the dialog box.

6. From the left pane, select Recover > System Recover Session.

Microsoft Windows Cluster Backup and Recovery

7. Stop the cluster service in Node_B by using one of the following methods:

• With the control panel service tool, stop the Cluster service.

• At the command prompt, type the following:

net stop clussvc

8. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder.

9. In the navigation tree:

a. Select BootableSystemState.

b. Select Cluster Writer.

10. Select theSYSTEM COMPONENTS:\folder.

If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS:\, clear ASR DISK.

11. From the System Recover Session toolbar:

a. Click Recover.

b. Click Restore.

12. When prompted, restart Node_B.

Start the Cluster service on Node_A

Follow these steps:

1. Start the Cluster service on Node_A by using one of the following methods:

• With the control panel service tool, start the Cluster service.

• At the command prompt, type the following:

net start clussvc

2. Use the Cluster Administrator on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred.

Note: If you are performing regular scheduled backups, this will recover the cluster database to a point shortly before the loss of Node_B.

3. Use the Cluster Administrator on Node_A to monitor the cluster “joining” status of node_B.

4. Use the Cluster Administrator on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group.

Performing Windows Server 2003 and Windows Server 2003 R2 clustered client disaster recovery ¹³⁷ Microsoft Windows Cluster Backup and Recovery