HP 3PAR Operating System Software User Manual

Page 164

Advertising
background image

NOTE:

With the path_management policy enabled, host persona 11 configures the target

port groups of secondary volumes as STANDBY. With HP 3PAR OS 3.1.2 and earlier, this
can cause ESX host problems if the attached host can see only STANDBY target ports. As of
HP 3PAR OS 3.1.3, the path_management policy can be disabled, thereby allowing
non-uniform access to the secondary volumes that are in the ACTIVE read-only state.

Before you begin non-disruptive failover:

“Bidirectional 1-to-1 Remote-Copy Configuration—Example”
(page 165)

1.

Review the example remote-copy pair used to illustrate
1-to-1 non-disruptive failover.

“System Information during Normal Operation” (page 173)

2.

Review system information for 1-to-1 configurations.

To set the WWN of a volume, issue the setvv -wwn
<WWN> <vvname>

command.

3.

Ensure that all volumes to be exported on all primary
and secondary arrays share the same volume WWN.

To view the WWN of a volume, issue the showvv -d
<vvname>

command.

NOTE:

You cannot change the WWN of an exported

volume.

For more information about the setvv and showvv
commands, see the HP 3PAR Command Line Interface
Administrator's Manual
, HP 3PAR Command Line Interface
Reference
, and HP 3PAR CLI Help.

“System Information during Failover for 1-to-1
Configurations” (page 174)

4.

Understand what system information to look for during
a failover.

For additional information, see

“About the Remote-Copy Commands” (page 261)

.

The non-disruptive failover steps for 1-to-1 configurations refer to the example setup illustrated in

Figure 61 (page 165)

.

164 Using Peer Persistence for Non-disruptive Failover in 1-to-1 Remote Copy in Geocluster Environments

Advertising