HP P6000 Continuous Access Implementation Guide (T3680-96431, August 2012)

Table 5 When to fail over a DR group, managed set, or array
Recommended HP P6000 Continuous Access actionFailure situation
DR group in failsafe modeDR group in normal mode
Perform a planned failover on the destination array. See “Planned failover” (page 105).Maintenance preventing access to
source array
Manually intervene to fail over data on destination array, and then restart processing
at the destination array. Perform an unplanned failover. See “Unplanned failover”
(page 108).
Total loss of source array
Loss of both source controllers
NoneLoss of single source controller
Manually intervene to continue processing
at the source array. See “Recover from
NoneTotal destination array loss
Loss of both destination controllers
failsafe-locked after destination loss”
(page 108).
Loss of all ISLs
Investigate to determine the reason for the outage and if appropriate manually intervene
to fail over data on the destination array, and then restart processing at the destination
array. Perform an unplanned failover. See “Unplanned failover” (page 108).
Loss of SAN connectivity from the server
to the source array
NoneLoss of single source intersite switch
Manually intervene to fail over data to the destination array, and then restart processing
at the destination array. Perform an unplanned failover. See “Unplanned failover”
(page 108).
Extended power outage at primary site
Failover not necessary. Browse to standby managing server.Loss of managing server
NoneLoss of a single disk in redundant
storage
NoneLoss of single host of cluster
Failover may not be necessary. Any data generated is being replicated to the destination
array. If the virtual disk fails completely then fail over to the destination. See “Disk group
hardware failure on the source array ” (page 114).
Disk group hardware failure (loss of
redundancy) on the source array
Failover not necessary. See “Disk group hardware failure on the destination array”
(page 115).
Disk group hardware failure (loss of
redundancy) on the destination array
Planned failover
Scenario: Due to scheduled maintenance at the local site, you need to move operations from the
local array to the remote array.
Action summary: Stop processing in the local data center and allow any data in the write history
log to drain, and then begin the failover. When the failover is complete, you can continue to
operate from the new source and enable failsafe mode if desired. When the planned maintenance
is complete, you can fail back to the original source (this is another planned failover event).
Figure 54 (page 106) shows a planned transfer of operations to a remote site.
Failover and recovery procedures 105