Resuming normal operations at the primary site – HP StorageWorks XP Remote Web Console Software User Manual
Page 186
3.
At the primary site, locate primary data volumes whose pair status is not Simplex, and then
locate 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 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 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 primary data volumes and secondary data volumes to resynchronize pairs.
6.
Create pairs, specifying secondary data volumes whose pair status is Simplex as primary
data volumes. This creates pairs in which primary data volumes and secondary data volumes
are reversed.
7.
Verify that 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 Business Continuity
Manager user's guide.
For detailed information about status of data volumes, see
.
Resuming Normal Operations at the Primary Site
Once the URz 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 URz
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 URz components are fully operational
and are free from failures.
2.
Make sure that pair status of primary and secondary data volumes in all URz pairs is "Duplex."
This indicates that the URz 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 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 suspension finishes. After suspension finishes, check
whether there is a secondary data volume (which is 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 is originally a primary data volume) whose pair
status is other than Suspend (equivalent to SUSPOP with Business Continuity Manager), data
in primary data volumes are the same as data in secondary data volumes, and the secondary
data volume (which are originally primary data volumes) are usable. Please resume applications
at the primary site.
186 Disaster Recovery Operations