Transferring operations back to the primary site – HP StorageWorks XP Remote Web Console Software User Manual

Page 204

Advertising
background image

XP Continuous Access Journal pairs enables your business tasks to be taken over to the secondary
site, using secondary data volumes in the secondary site.

The horctakeover command checks the pair status of secondary data volumes and splits
journal groups that will become an XP Continuous Access Journal pair. This ensures consistency
of secondary data volumes and makes the secondary data volumes usable.

If possible, the horctakeover command attempts to restore pairs to reverse primary data
volumes and secondary data volumes.

If the horctakeover command executes successfully, your business tasks are taken over to
(or your business application is started at) the secondary site, using secondary data volumes.
For detailed information about how to use RAID Manager, see the HP StorageWorks RAID
Manager User Guide
.

Transferring Operations Back to the Primary Site

Once the disaster recovery procedure is finished and your business applications are running at
the secondary site, the next activity is to restore the primary site and make arrangements for copying
data from the secondary site back to the primary site. The following procedure explains how to
use RAID Manager to copy data from the secondary site to the primary site:

1.

Restore the primary storage system and remote copy connections, bring up the host server(s)
at the primary site, and make sure that all XP Continuous Access Journal components are fully
operational.

2.

At the primary site, locate the primary data volumes whose pair status is COPY or PAIR, and
then locate the corresponding secondary data volumes whose pair status is SSWS. If such
volume pairs are found, issue a request for splitting the pairs to the primary data volumes.

3.

At the primary site, locate the primary data volumes whose pair status is not SMPL, and then
locate the corresponding secondary data volumes whose pair status is SMPL. 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 SMPL, and then issue a
request for releasing the pairs to the secondary data volumes.

5.

Execute the pairresync -swaps command on secondary data volumes whose pair status is
SSWS (pairresync is the RAID Manager command for resynchronizing pairs and -swaps is a
swap option). This reverses primary data volumes and secondary data volumes to resynchronize
the pairs.

Caution: When you execute the pairresync -swaps command, you can use the -d option to
specify a data volume. However, if the restore journal group where the data volume belongs
is in Active, Halting, or Stopping status, the pairresync -swaps command is rejected. For
detailed information about journal group status, see

“Displaying Detailed Information about

a Journal Group” (page 164)

.

6.

Create pairs, specifying secondary data volumes whose pair status is SMPL as primary data
volumes. This creates pairs in which 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 COPY to PAIR. If the pair status is changed to PAIR, 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 is reflected on the primary site.

For detailed information about how to use RAID Manager, see the HP StorageWorks RAID Manager
User Guide
.

For detailed information about the status of data volumes, see

“Pair Status” (page 32)

.

204 Performing Disaster Recovery Operations

Advertising