HP StorageWorks XP24000 Continuous Access Journal Software User and Reference Guide, v01 (T5278-96001, June 2007)

(or your business application will be started at) the secondar y site, using secondary data volumes. For
detailed information about how to use RAID Manager, see HP StorageWorks XP RAID Manager User’s
Guide.
Transferring
Operations Back to the Primary Site
Once the disas
ter recovery procedure is finished and your business applications are running at the
secondary sit
e , the next activity is to restore the primary site and make arrangements for copying data
from the seco
ndary site back to the primary site. The following procedure explains how to use RAID
Manager to co
py data from the secondar y site to the primary site:
1. Restore the primary storage system and remote copy connections, b ring up the host ser ver(s)
at the
primary site, and make sure that all Continuous Access Journal components are fully
operational.
2. At the prim
ary site, locate the primary data volumes whose pair status is COPY or PA IR, 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 th
e
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 p rimary site, locate the data volume pairs whose pair status is SM PL, and then issue a
request for releasing the pairs to the secondary da ta volumes.
5. Execute
the
pairresync -swaps command on secondary data volumes whose p a ir status is
SSWS (pairresync is the R AID Manager comma nd for resynchroniz ing pa ir and -swaps is a
swap option). This reverses primary data volumes and secondary data volumes to resynchronize
the
pair
s.
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 vo
lume belongs
is in Ac tive, Halting or Stopping status, the pairresync -swaps
comman
d
will be rejected. For detaile d information about journal group status, see
“Disp
laying Detailed Information about a Journal Group” on page 115.
6. Creat
e
pairs, specifying secondar y 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. Veri
fy that the pair status of all secondar y data volumes (which were originally primary data
volu
mes) changes from COPY to PAIR. If the pair status is changed to PAI R, initial copy
oper
ations are fi nished and c onsistency is maintained.
The above procedure enables copying of data from the secondar y site to the p rimary site. Data in the
secondary site will be reflected on the primar y site.
For detailed information about how to use R A I D Manager, see H P StorageWorks XP RAID Manager
Use
r’s Guide.
For detailed information about the status of data volumes, see “Pair Status”onpage32.
Resuming Normal Operations at the Primary Site
Once the Continuous Access Journal volume pairs have been established i n 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 RAID Manager. Remember that the Continuous
Access Journal terminology is now reversed: the original primary data volumes are now secondary data
volumes, and the original secondary d ata volumes are now primary data volumes.
1. At the primary and secondary sites, make s ure that all Continuous Access Journal components
arefully operationaland arefreefromfailures.
2. Make sure that the pair status of primary and secondary data volumes in all Continuous Access
Journal pairs is PAIR. This i ndicates that the Continuous Access Journal initial copy operations
are c omplete and consistency is ma intaine d.
3. Stop the applications at the secondary s ite.
146
Performing Disaster Recovery Operations