Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION, Руководство администратора

Страница: 90 / 142

90 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
no
vd
ocx
(e
n)
13
Ma
y 20
09
Primary Cluster Fails but Primary SAN Does Not
Response for this failure is the same as for SAN-based mirroring described in Primary Cluster Fails
but Primary SAN Does Not in Section 7.6.1, “SAN-Based Mirroring Failure Types and Responses,”
on page 88 . Do not disable MSAP (Multiple Server Activation Prevention), which is enabled by
default.
Primary Cluster and Primary SAN Both Fail
Bring up your primary SAN or iSCSI target before bringing up your cluster servers. Then run the
Cluster Scan For New Devices
command from a secondary cluster server. Ensure that
remirroring completes before bringing downed cluster servers back up.
If necessary, promote the former primary SAN back to primary. Then bring up the former primary
cluster servers and fail back the cluster resources.
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 up your secondary SAN or iSCSI target before bringing up your cluster servers. Then run the
Cluster Scan For New Devices
command on a primary cluster server to ensure that remirroring
takes place. 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
If your primary SAN fails, all nodes in your primary cluster also fail. Bring up your primary SAN or
iSCSI target and then bring up your cluster servers. Then run the
Cluster Scan For New
Devices
command from a secondary cluster server. Ensure that remirroring completes before
bringing downed cluster servers back up.
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
cluster resetresources
console 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
Bring up your secondary SAN or iSCSI target before bringing up your cluster servers. Then run the
Cluster Scan For New Devices
command on a primary cluster server to ensure remirroring
takes place. 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
You must run the
Cluster Scan For New Devices
command on both clusters to ensure that
remirroring takes place. Recover your SANs first, then remirror from the good side to the bad side.