Recovering One Cluster Node
To recover Node_B in this example scenario:
1.Using the Cluster Administrator on Node_A, evict Node_B from the cluster.
2.On Node_B, reinstall or clean up MSCS as follows: Windows 2000:
a.Using the Control Panel Add/Remove Programs tool, uninstall the Windows component Cluster Service.
b.Reboot Node_B.
c.Log on to Node_B as Administrator for the domain in which the cluster nodes reside.
d.Using the Control Panel Add/Remove Programs tool, add the Windows component Cluster Service.
Windows .NET:
At the command prompt, run the following command to clean up MSCS:
cluster node Node_B /forcecleanup
Important: After reinstalling the Cluster Service (Windows 2000) or cleaning up the Cluster Server (Windows .NET), you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform disaster recovery procedures for each application that was previously installed on the node.
3. | Using the Cluster Administrator, select Join An Existing Cluster and enter | ||
|
|
| the cluster name. |
4. | Using the Cluster Administrator on Node_A, ensure that Node_B appears | ||
|
|
| available for failover operations. |
5. | Only Node_A, the node that owns the shared resources, can be running | ||
|
|
| while the cluster database is being recovered. Stop the Cluster service on |
|
|
| Node_B using one of the following methods: |
|
|
| |
7 |
|
| • Using the Control Panel Services tool, stop the Cluster service. |
|
| • At the command prompt, run: | |
|
|
| |
|
|
| net stop clussvc |
| 6. | On Node_A, start the NetWorker User program and click Recover. | |
7. | In the Source Client dialog box, select Node_A. | ||
|
|
|
|
130 | Legato NetWorker, Release 7.0 | ||
Disaster Recovery Guide | |||