HP 3PAR Geocluster Software - Manual (Page 14)

3PAR GeoCluster 1.0.0.14 for Windows User’s Guide
320-200263 Page 14
secondary InServ will become Primary-rev (Primary in a reversed replication situation). The
VVs included in the Remote Copy groups will change from read-only to read-write status.
The Secondary-rev status can be set manually in certain scenarios. This implies that the
primary InServ has been set to be the replication destination while the secondary InServ
has become the primary-rev due to a failure.
2.2.3 Failover Outcome
Depending upon the site on which that owner node ends up being located, the failover will
do one of the followings:

The owner node stays on the local site – There is no consequence for the status of
the InServ storage arrays hosting the Remote Copy groups.

The owner node ends up being located on the remote site, with no disruption to the
replication - The primary and secondary InServs see their roles reversed with no
further notable effect. This scenario is typical of a manually initiated failover or a disk
or application resource failure.

The owner node ends up being located on the remote site, with the secondary InServ
becoming primary-rev because of a replication failure - While the disruption to
continuity of service will be limited, the restoration of the cluster to its original
situation will require additional manual operations, which are described in section
4.1.
CAUTION: In the latter scenario, the primary InServ will not automatically
switch to the secondary-rev role and will continue to identify itself as the
primary server. This scenario requires careful administrator consideration,
as it can result in data loss. For more information, see section 4.1.