Resuming normal operations at the primary site – HP StorageWorks XP Remote Web Console Software User Manual
Page 136
136 Continuous Access XP Journal
4.
At the primary site, locate data volume pairs whose pair status is SMPL, and issue a request for
deleting 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 pair and -swaps is a swap option).
This reverses primary and secondary data volumes to resynchronize pairs.
CAUTION:
When executing the pairresync -swaps command, 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 more information about journal
group status, see ”
Displaying detailed information about journal groups
6.
Create pairs, specifying secondary data volumes whose pair status is SMPL as primary data volumes.
This creates pairs in which primary and secondary data volumes are reversed.
7.
Verify that 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.
This 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 more information about status of data volumes, see ”
Continuous Access XP Journal data volume pair
Resuming normal operations at the primary site
After the Continuous Access XP Journal 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 use
RAID Manager to resume normal operations at the primary site. Remember that the Continuous Access XP
Journal 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, ensure that all Continuous Access XP Journal components are fully
operational and are free from failures.
2.
Ensure that pair status of primary and secondary data volumes in all Continuous Access XP Journal
pairs is PAIR. This indicates that the Continuous Access XP Journal 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 the Flush option when splitting pairs. If an error occurs when splitting pairs, remove the
error cause and go back to
after resuming your business task at the secondary site.
5.
If no error occurs in
, wait until suspension finishes. After suspension finishes, check whether there
is a secondary data volume (which was originally a primary data volume) whose pair status is other
than PSUS. If such a pair exists, remove the error cause and go back to
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 PSUS, data in primary data volumes is the same as data in secondary data volumes, and
the secondary data volume (which was originally primary data volume) is usable. Resume applications
at the primary site.
7.
Execute the pairresync -swaps command (pairresync is the RAID Manager command for
resynchronizing pair and -swaps is a swap option). This reverses primary and secondary data volumes
to resynchronize pairs.
CAUTION:
When executing the pairresync -swaps command, 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 more information about journal
group status, see ”