HP ProLiant Cluster HA/F500 for Enterprise Virtual Array Enhanced DT Supplement Guide

Disaster Recovery
3. Power on the Storage Management Appliance at the failed site.
4. From the management appliance, at the failed site, remove access to the cluster
for any disks that were failed over during the original site failover.
5. Be sure the cluster node at the failed site has been rebooted.
At this point the node at the failed site should show NO drives in Device
Manager because the failed over drives have been unpresented.
Determine which management appliance you will continue to use. The
management appliance at the failed site can be shutdown if you want to manage
your storage system from the alternate site.
6. Restore the ISL links by enabling the switch ports (EPort).
The EVA storage units will begin merging log data and negotiating state.
7. Re-present the failed over disks to the cluster nodes on the failed EVA.
The cluster is unaffected by the recovery process at this point.
NOTE: To minimize disruptions to the cluster, determine a good maintenance time to
move the failed disks back to their original storage subsystem.
ISL Failback Procedure
Problem
Both ISLs fail requiring a site failover:
•
•
•
•
•
All cluster resources continue unaffected on their respective storage arrays, but
cluster moves cannot be performed.
Manual failover to the alternate site is successful.
Cluster is successfully running on the alternate site.
Investigate the source of the ISL failures at the original site and correct.
During the repair of the ISLs, the cluster temporarily loses access to the disks
that had to be failed over.
3-6 HP ProLiant Cluster HA/F500 for Enterprise Virtual Array Enhanced DT Supplement Guide
HP CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Disaster Recovery.doc
Codename: 49er IV Part Number: 339223-002 Last Saved On: 9/30/03 10:48 AM