Analyze R-Vol Currency; Transfer Operations Back To The Main Site - HP StorageWorks P9000 User Manual

1. Clear the remote copy SIMs from the RCUs before OS IPL. Connect to each RCU, open
the Continuous Access Synchronous Z System Option window, and click Clear SIM.
2. Perform an IPL of the remote host system.
3. Wait until the IPL is complete, and then vary the R-VOLs online (if they did not come online
automatically).
10. At the remote site, start critical host operations, with the previous R-VOLs now the main volumes.

Analyze R-VOL currency

Use the following table to determine an R-VOL's currency based on pair status and M-VOL fence
level setting.
Table 30 Analyzing R-VOL currency
R-VOL status
Simplex
Pending Duplex
Duplex
Suspended
Suspended
Suspended
For pairs with a M-VOL fence level setting of Never, further analysis is required to determine the R-VOL currency. This
can be determined by using sense information transferred via host failover, or by comparing the contents of the R-VOL
with other files that are confirmed to be current (for example, database log files). The R-VOLs should be recovered
using the files that are confirmed to be current.
Actual data recovery must be done using recovery point data in the database redo log.

Transfer operations back to the main site

When host operations are running at the remote site, the main site should be restored and operations
transferred back.
In the following procedure, you will establish Continuous Access Synchronous Z pairs at the remote
site, with data flow moving from the remote site to the local. After the pairs are synchronized and
in Duplex 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.
Type Fence level
-- Data Status
Never
-- Data Status
Never
-- Data Status
Never
Initial copy Data Status
failed Never
R-VOL by Data Status
operator Never
All other types Data
Status Never
Currency of R-VOL
Inconsistent. This R-VOL does not belong to a Continuous Access
Synchronous Z pair. Even if you established a Continuous Access
Synchronous Z pair for this volume, you must regard this volume
as inconsistent.
Inconsistent. This R-VOL is not synchronized because not all tracks
have been copied from the M-VOL yet. This R-VOL must be
initialized (or copied from the M-VOL at a later time).
Current. This R-VOL is synchronized with its M-VOL.
* Needs to be analyzed. This R-VOL requires further analysis to
determine its level of currency.
Inconsistent. This R-VOL is not synchronized because not all tracks
have been copied from the M-VOL yet. This R-VOL must be
initialized (or copied from the M-VOL at a later time).
Suspect. This R-VOL is not synchronized with its M-VOL if any
write I/Os were issued to the M-VOL after the pair was
suspended. This pair should be released and restarted using
Entire Volume for Initial Copy option. If you are sure that no data
on the M-VOL changed, you can use the None option.
Current. This R-VOL is synchronized with its M-VOL.
Suspect. This R-VOL is not synchronized with its M-VOL if any
write I/Os were issued to the M-VOL after the pair was
suspended. Restore the consistency of this R-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 this R-VOL was updated.
Transfer operations back to the main site 77