HP 3PAR Operating System Software - Manual (Page 136)

Figure 44 Manual Peer Persistence Switchover
Performing a switchover moves an entire VMware data store from one array to another. Executing
a switchover in response to a VM migrating from one site to the other makes sense only if every
VM has its own data store—that is, its own logical unit number (LUN). This is generally not the
case.
For HP 3PAR Peer Persistence to be enabled on volume groups under synchronous remote copy,
the volumes must be created on the source and target arrays using the same WWN addresses.
The volumes should also be exported to the same host from both arrays.
Using ALUA, the paths to the source volumes are presented as active, while the paths to the target
volumes are presented as standby. During a peer-persistence operation, this replication pattern is
reversed: the source volume becomes the target, and the target volume becomes the source, and
the paths between them are reversed from the original configuration, as demonstrated by
Figure 45
(page 137) .
136 HP 3PAR Peer Persistence with Transparent Failover