Host-Based Mirroring Failure Types And Responses - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

Secondary Cluster Fails but Secondary SAN Does Not
No additional response is necessary for this failure other than recovering the secondary cluster.
When you bring the secondary cluster back up, the LUNs are still in a secondary state to the primary
SAN.
Secondary Cluster and Secondary SAN Both Fail
Bring the secondary SAN back up and follow your SAN vendor's instructions to remirror. When you
bring the secondary cluster back up, the LUNs are still in a secondary state to the primary SAN.
Primary SAN Fails but Primary Cluster Does Not
When the primary SAN fails, the primary cluster also fails. Bring the primary SAN back up and
follow your SAN vendor's instructions to remirror and, if necessary, promote the former primary
SAN back to primary. You might need to demote the LUNs and resources to secondary on the
primary SAN before bringing them back up. You can use the
command to change resource states to offline and secondary. Bring up the former primary cluster
servers and fail back resources.
Secondary SAN Fails but Secondary Cluster Does Not
When the secondary SAN fails, the secondary cluster also fails. Bring the secondary SAN back up
and follow your SAN vendor's instructions to remirror. Then bring the secondary cluster back up.
When you bring the secondary SAN and cluster back up, resources are still in a secondary state.
Intersite SAN Connectivity Is Lost
Recover your SANs first, then remirror from the good side to the bad side.
Intersite LAN Connectivity Is Lost
Users might not be able to access servers in the primary cluster but can possibly access servers in the
secondary cluster. If both clusters are up, nothing additional is required. An error is displayed. Wait
for connectivity to resume.
If you have configured the automatic failover feature, see
on page 133.

7.6.2 Host-Based Mirroring Failure Types and Responses

"Primary Cluster Fails but Primary SAN Does Not" on page 90
"Primary Cluster and Primary SAN Both Fail" on page 90
"Secondary Cluster Fails but Secondary SAN Does Not" on page 90
"Secondary Cluster and Secondary SAN Both Fail" on page 90
"Primary SAN Fails but Primary Cluster Does Not" on page 90
"Secondary SAN Fails but Secondary Cluster Does Not" on page 90
"Intersite SAN Connectivity Is Lost" on page 90
"Intersite LAN Connectivity Is Lost" on page 91
cluster resetresources
Appendix C, "Setting Up Auto-Failover,"
Managing a Business Contiuity Cluster
console
89