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

11 Usage Scenarios
This chapter describes how to use Universal Replicator for Mainframe to enables to make
Point-in-Time (PiT) duplicates of groups of volumes:
•
“Creating a Point-in-Time Copy of Data Volumes” (page 219)
•
“Performing Disaster Recovery Operations” (page 219)
•
“Recovering from Failures in the Primary Site (When the Delta Resync Operation is Performed)”
(page 225)
Creating a Point-in-Time Copy of Data Volumes
Universal Replicator for Mainframe enables you to make Point-in-Time (PiT) duplicates of groups
of volumes. The term Point-in-Time (PiT) refers to an act of obtaining a copy of data immediately
when you want to obtain it. The Universal Replicator for Mainframe can be used to create a PiT
copy of data volumes belonging to a journal group.
To produce a PiT duplicate of data volumes belonging to a journal group:
1. Stop all write I/Os from hosts to primary data volumes in the journal group. Stop all host
updates to all Universal Replicator for Mainframe primary data volumes in the group.
2. After all write I/Os to primary data volume have stopped, split the mirror (that is, a pair of
the master and restore journal group. When splitting it, use the Suspend Pair window and
then specify Group for Range and specify Flush for Suspend Mode.
3. When the status of all data volume pairs in the journal group has changed to Suspend, the
duplicate set of volumes is complete. If desired, you can restart your business application at
the primary site to resume business activities.
Performing Disaster Recovery Operations
Preparing for Disaster Recovery Operations
The type of disaster and the status of the Universal Replicator for Mainframe volume pairs will
determine the best approach for disaster recovery. 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.
The major steps in preparing for disaster recovery are:
1. Identify the journal groups and data volumes that contain important files and data (for example,
DB2 log files, master catalogs, key user catalogs, and system control datasets) for disaster
recovery.
2. Install the Remote Web Console computer and Universal Replicator for Mainframe hardware
and software, and establish XP Continuous Access operations for the journal groups and data
volumes identified in step (1).
3. Establish file and database recovery procedures. These procedures should already be
established for recovering data volumes that become inaccessible due to some failure.
4. Install and configure error reporting communications (ERC) between the primary and secondary
sites.
File and Database Recovery Procedures
When the primary storage system (or secondary storage system for Universal Replicator for
Mainframe) suspends a Universal Replicator for Mainframe pair due to an error condition, the
primary storage system or secondary storage system sends sense information with the unit check
status to the appropriate host(s). This sense information is used during disaster recovery. You must
transfer the sense information to the secondary site via the error reporting communications (ERC).
Creating a Point-in-Time Copy of Data Volumes 219