HP StorageWorks XP Remote Web Console Software - Manual (Page 170)

IEA494I System Console Message
The IEA494I message is recommended as a trigger for automation over the IEA491E message,
because the IEA494I message is reported to all attached MVS hosts each time the M-VOL pair
status changes, whereas the IEA491E message is reported to only one host system.
Switching Operations to the Remote Site
If a disaster or failure occurs at the main site, the first disaster recovery activity is to switch your
operations to the remote backup site. The TrueCopy for Mainframe Synchronous R-VOLs are
recovered individually based on the pair status and M-VOL fence level information for each pair.
The TrueCopy for Mainframe Asynchronous R-VOLs are recovered based on pair status, consistency
status, and consistency time.
The basic procedures for switching operations to the remote backup site are:
1. Analyze the currency of the TrueCopy for Mainframe Synchronous R-VOLs and the consistency
of the TrueCopy for Mainframe Asynchronous R-VOLs.
2. Record the consistency time (C/T) of each group. The suspended TrueCopy for Mainframe
Asynchronous R-VOLs with consistency status of group will indicate the same C/T.
3. Perform file recovery as needed. The C/T of each TrueCopy for Mainframe Asynchronous
group can be used to retrieve lost updates.
4. At the remote site, suspend all pairs by issuing the CSUSPEND TSO command to the R-VOLs.
Use the TrueCopy for Mainframe Asynchronous group and drain suspend options to de-stage
pending updates in cache to the R-VOLs. And then, change the state of R-VOLs to simplex by
issuing the CRECOVER TSO command.
If PPRC is not installed, connect to each RCU, and release all TrueCopy for Mainframe pairs.
For TrueCopy for Mainframe Asynchronous pairs, select C/T for the Delete Range option on
the Delete Pair dialog box to release all consistent pairs in the group at the same time. This
option prevents you from accidentally using inconsistent pairs for disaster recovery. Release
all TrueCopy for Mainframe sync pairs in the MCU using the Deleting Mode-All option.
CAUTION: If necessary, use ICKDSF REFORMAT to change the labels (VOLSERs) of the
R-VOLs.
5. Make sure that all required file recovery procedures have been completed before varying the
R-VOLs online. If an IPL of the remote host system is not required, bring the R-VOLs online. If
an IPL is required:
a.
Clear the remote copy SIMs from the RCUs before OS IPL. Connect to each RCU, open
the TrueCopy for Mainframe System Option window, and click Clear SIM.
b. Perform IPL of the remote host system.
c. Wait until the IPL is complete, and then vary the R-VOLs online (if they did not come online
automatically).
6. At this point, you may start critical applications at the remote site with the previous R-VOLs
taking the place of their M-VOLs.
Analyzing the Currency of TrueCopy for Mainframe Sync R-VOLs
“Analyzing the Currency of TrueCopy for Mainframe Sync R-VOLs” (page 171) shows how to
determine the currency of a TrueCopy for Mainframe Synchronous R-VOL based on its pair status
and M-VOL fence level setting. For TrueCopy for Mainframe Synchronous pairs with an M-VOL
fence level setting of Never, further analysis will be required to determine the currency of these
R-VOLs. The currency of these R-VOLs can be determined by using the sense information transferred
via the ERC or by comparing the contents of the R-VOL with other files which are confirmed to be
current (for example, DB2 log files). These R-VOLs should be recovered using the files which are
confirmed to be current.
170 TrueCopy for Mainframe Usage Scenarios