HP XP7 Continuous Access Synchronous User Guide (TK911-96004)

The following table shows S-VOL consistency information, based on Remote Web Console pair
status and the P-VOL fence level setting.
Consistency of S-VOLFence levelTypeS-VOL status
Not consistent. The S-VOL does not belong to a pair. Even if you have
created a pair using this volume, if the pair status is still unpaired, you
must regard its data as not consistent with the P-VOL.
Data Status
Never
--Unpaired
Not consistent. The S-VOL is not synchronized because not all tracks
have been copied from the P-VOL yet. This S-VOL must be initialized
(or copied from the P-VOL at a later time).
Data Status
Never
--COPY
Consistent. The S-VOL is synchronized with its P-VOL.Data Status--PAIR
Needs to be analyzed*. The S-VOL requires further analysis to
determine its level of consistency.
Never
Not consistent. The S-VOL is not synchronized because not all tracks
have been copied from the P-VOL yet. The S-VOL must be initialized
(or copied from the P-VOL at a later time).
Data Status
Never
Initial copy
failed
PSUE
Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os
were issued to the P-VOL after the pair was split. The pair should be
Data Status
Never
S-VOL by
operator
PSUS
released and restarted using Entire for the Initial Copy Type option. If
you are sure that no data on the P-VOL changed, you can use No
Copy for Initial Copy Type.
Consistent. The S-VOL is synchronized with its P-VOL.DataAll other typesPSUS or PSUE
Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os
were issued to the P-VOL after the pair was split. Restore the consistency
Status Never
of the S-VOL and update it, if required. The time of suspension indicated
on the Last Update Time field of the Detailed Information dialog box
(MCU SVP time) will help to determine the last time the S-VOL was
updated.
For pairs with a P-VOL fence level setting of No Copy, further analysis is required to determine the S-VOL consistency. This can
be determined by using sense information transferred via host failover, or by comparing the contents of the S-VOL with other files
that are confirmed to be consistent (for example, database log files). The S-VOLs should be recovered using the files that are
confirmed to be consistent.
Actual data recovery must be done using recovery point data in the database operation log.
Transferring operations back to the local site
When host operations are running at the remote site, the local site should be restored and operations
transferred back.
In the following procedure, you will establish Cnt Ac-S pairs at the remote site, with data flow
moving from the remote site to the local. After the pairs are synchronized and in PAIR status, they
will be released, then new pairs will be created at the local site with data flow moving from local
to remote, as originally set up.
Select the appropriate procedure below based on whether you deleted pairs to switch operations
to the remote site, or ran the RAID Manager Run horctakeover or pairsplit-RS to the S-VOL command.
Procedure 30 To transfer operations to the local site—if pairs were deleted when operations were
switched to the remote site
1. At the local site, bring up the host. Make sure that Cnt Ac-S components are operational.
2. At the local site, release all pairs on the primary system.
The Delete Pair by Force option must be used because the paired S-VOLs are in the SMPL state
at the remote site.
Transferring operations back to the local site 77