Disaster Scenarios and Their Handling
The following table lists all the disaster scenarios that are handled by the Extended Distance Cluster software. All the scenarios assume that the setup is the same as the one described in “Extended Distance
Clusters” on page 18 of this document.
Table | Disaster Scenarios and Their Handling | |||
|
|
|
| |
Disaster Scenario | What Happens When | Recovery Process | ||
This Disaster Occurs | ||||
|
|
| ||
|
|
| ||
A package (P1) is running on a | The package (P1) fails over | As the network and both the | ||
node (Node 1). Node 1 | to another node (Node 2). | mirrored disk sets are accessible | ||
experiences a failure. |
| This node (Node 2) is | on Node 2, and were also | |
|
| accessible when Node 1 failed, you | ||
|
| configured to take over the | ||
|
| only need to restore Node 1. Then | ||
|
| package when it fails on | ||
|
| you must enable the package to | ||
|
| Node 1. | ||
|
| run on Node 1 after it is repaired | ||
|
|
| ||
|
|
| by running the following | |
|
|
| command: | |
|
|
| # cmmodpkg | |
|
|
|
| |
86 | Chapter 4 |
