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

3. At the primary site, locate the primary data volumes whose pair status is not Simplex, and
then locate the corresponding secondary data volumes whose pair status is Simplex. If such
volume pairs are found, issue a request for releasing the pairs to the primary data volumes.
4. At the primary site, locate the data volume pairs whose pair status is Simplex, and then use
Business Continuity Manager to execute YKRECVER on the secondary data volume (YKRECVER
is a command for releasing a pair).
5. Execute the YKRESYNC REVERSE option on the secondary data volumes whose pair status is
Suspend, which is equivalent to SWAPPING in Business Continuity Manager terminology
(YKRESYNC is the Business Continuity Manager command for resynchronizing pair). This
reverses the primary data volumes and secondary data volumes to resynchronize the pairs.
6. Create pairs, specifying the secondary data volumes whose pair status is Simplex as the
primary data volumes. This creates pairs in which the primary data volumes and secondary
data volumes are reversed.
7. Verify that the pair status of all secondary data volumes (which were originally primary data
volumes) changes from Pending Duplex to Duplex. If the pair status is changed to Duplex,
initial copy operations are finished and consistency is maintained.
The above procedure enables copying of data from the secondary site to the primary site. Data
in the secondary site will be reflected on the primary site.
For detailed information about how to use Business Continuity Manager, see the HP StorageWorks
XP for Business Continuity Manager Software User's Guide.
For detailed information about status of data volumes, see “Pair Status” (page 37) .
Resuming Normal Operations at the Primary Site
Once the Universal Replicator for Mainframe volume pairs have been established in the reverse
direction, you are ready to resume normal operations at the primary site. The following procedure
explains how to resume normal operations at the primary site by using Business Continuity Manager.
Remember that the Universal Replicator for Mainframe terminology is now reversed: the original
primary data volumes are now secondary data volumes, and the original secondary data volumes
are now primary data volumes.
1. At the primary and secondary sites, make sure that all Universal Replicator for Mainframe
components are fully operational and are free from failures.
2. Make sure that the pair status of the primary and secondary data volumes in all Universal
Replicator for Mainframe pairs is Duplex. This indicates that the Universal Replicator for
Mainframe initial copy operations are complete and consistency is maintained.
3. Stop the applications at the secondary site.
4. Issue a request for splitting pairs to master journal groups (which were originally restore journal
groups); use Business Continuity Manager to execute the YKSUSPND FLUSH SVOL PERMIT
option on the master journal group (which was originally the restore journal group); YKSUSPND
is a command for splitting pairs. If an error occurs when splitting pairs, remove the error cause
and go back to step 1 after resuming your business task at the secondary site.
5. If no error occurs in step 4, wait until the suspension finishes. After the suspension finishes,
check whether there is a secondary data volume (which was originally a primary data volume)
whose pair status is other than Suspend (equivalent to SUSPOP with Business Continuity
Manager). If such a pair exists, remove the error cause and go back to step 1 after resuming
your business task at the secondary site.
6. If there is no secondary data volume (which was originally a primary data volume) whose
pair status is other than Suspend (equivalent to SUSPOP with Business Continuity Manager),
data in the primary data volumes are the same as data in the secondary data volumes, and
the secondary data volume (which were originally the primary data volumes) are usable.
Resume applications at the primary site.
228 Usage Scenarios