HP ProLiant Cluster HA/F500 for MA8000 Enhanced DT Supplement Guide

Disaster Recovery
Use the standard failback mechanisms provided by MSCS after the failed server has
been repaired or replaced. The server node automatically joins the cluster when the
repaired server comes back online. The failback of each cluster group is determined
by the failback policy that has been defined in MSCS for that group. Remove the
failed server from the cluster before reinstalling the operating system if the server
must be replaced. Then install MSCS and join it to the existing cluster. Fail back to
the other server to perform a failback after a resource failure. There is no storage
failback because there was no storage failover.
Figure 3-2: Local server failure
Initiator Site Failover
A small amount of downtime occurs during a site failover. The cluster does not have
access to any data or applications if the initiator storage system fails or is no longer
available. The cluster is not available during this time.
Refer to the DRM guide to determine the scenarios that warrant a failover.
There are two types of failover procedures to recover the remote copy sets: planned
and unplanned. Use the planned failover procedure when failover is a scheduled
event. Otherwise, use an unplanned failover procedure.
HP ProLiant Cluster HA/F500 for MA8000 DT Enhanced Supplement Guide 3-3
HP CONFIDENTIAL
Writer: Bill Akers File Name: d-ch3 Disaster Recovery
Codename: Chargers II Part Number: 324547-001 Last Saved On: 4/7/03 10:43 AM