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

7 TrueCopy for Mainframe Usage Scenarios
This chapter describes several usage scenarios for TrueCopy for Mainframe.
•
“Using TrueCopy for Mainframe for Disaster Recovery” (page 167)
•
“Using TrueCopy for Mainframe for Data Migration” (page 174)
•
“Using TrueCopy for Mainframe for Duplication” (page 175)
Using TrueCopy for Mainframe for Disaster Recovery
Preparing for Disaster Recovery
The type of disaster and the status of the TrueCopy for Mainframe pairs will determine the best
approach for disaster recovery. For example, if all TrueCopy for Mainframe pairs are in the duplex
state when a total system failure occurs at a single point in time, the R-VOLs are current and recovery
is straightforward. Unfortunately, some disasters are not so orderly and involve intermittent or
gradual failures occurring over a longer period of time. The user should anticipate and plan for
all types of failures and disasters. For additional information on planning for disaster recovery,
see Planning for IBM Remote Copy, IBM document SG24-2595.
The major steps in preparing for disaster recovery are:
1. Identify the volumes and volume groups which contain important files and data for disaster
recovery, for example, DB2 log files, master catalog, key user catalogs, and system control
data sets. In addition to supporting TrueCopy for Mainframe remote copy operations as well
as PPRC commands, the HP disk array provides battery-backed nonvolatile duplexed cache,
full hardware redundancy, dynamic sparing, and an advanced RAID-5 implementation to
ensure full data integrity in the event of a sudden power outage or other failure.
2. Install the TrueCopy for Mainframe hardware and software, and establish TrueCopy for
Mainframe operations for the volumes and groups identified in step (1). Make sure to select
the proper CUs to access the desired volumes. Use the appropriate combination of TrueCopy
for Mainframe options for disaster recovery:
•
RCU options: Incident of RCU, FREEZE Option, Service SIM of Remote Copy, and PPRC
Support by host.
•
TrueCopy for Mainframe Asynchronous Offloading Timer async option, TrueCopy for
Mainframe Asynchronous Time Out (copy pending) group option. The Time Out (copy
pending) group option can be used to limit the time duration during which updates may
be lost.
•
TrueCopy for Mainframe Asynchronous Error Level pair option, and M-VOL Fence Level
pair option for TrueCopy for Mainframe Synchronous pairs.
3. Establish file and database recovery procedures. These procedures should already be
established for recovering volumes which become inaccessible due to control unit failure.
4. Install and configure error reporting communications (ERC) between the main and remote
sites. ERC is essential if you use the M-VOL fence level setting of Status or Never for any
TrueCopy for Mainframe pairs.
5. Configure the primary host system to use the IEA494I message as a trigger for automation
rather than the IEA491E message. The IEA491E message is reported to only one host, whereas
the IEA494I message is reported to all attached MVS hosts each time the M-VOL pair status
changes.
Considering the M-VOL Fence Level Setting
The M-VOL fence level setting for each TrueCopy for Mainframe Sync pair determines whether the
M-VOL will be fenced when TrueCopy for Mainframe remote copy operations fail.
“Effect of the
Using TrueCopy for Mainframe for Disaster Recovery 167