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

delta resync operation will not be performed because the necessary journal data does not exist
when:
•
After splitting the XP Continuous Access Journal pair, the secondary data volume of the XP
Continuous Access Journal pair associated with the secondary data volume of the XP Continuous
Access Journal pair for delta resync operation is updated
•
After splitting a XP Continuous Access Journal pair and as a result of the update of the primary
data volume, the capacity of the journal data exceeds 70% of the journal volume in the XP
Continuous Access Journal secondary site associated with the primary data volume of the XP
Continuous Access Journal pair for delta resync operation.
•
The primary data volume in the XP Continuous Access Journal pair for delta resync operation
is updated and then the capacity of the journal data exceeds 70% of the journal volume in
the primary site of a XP Continuous Access Journal pair for delta resync operation.
•
After creating the XP Continuous Access Journal pair for delta resync operation, no volumes
(including volumes after failover or failback) in the primary site are updated.
If the delta resync operation to support remote command devices is performed, you can execute
the delta resync operation from directly after the primary site is updated.
Consider the following when creating the XP Continuous Access Journal pair for delta resync
operation:
◦ When the XP Continuous Access Journal pair status changes to HOLD after the delta
resync operation.
◦ When you re-create the XP Continuous Access Journal pair for delta resync operation
when recovering the primary site.
In the delta resync operation performed in the cascading configuration combining three XP
Continuous Access Journal sites, by specifying an option, you can copy all the data in the primary
data volume to the secondary data volume and avoid the error when only a part of the differential
data between primary and secondary data volume is stored in the journal volume. For detailed
information about the option, see
“Changing Options for a Journal Group” (page 167) .
If the status of of the S-VOL the XP Continuous Access Journal pair for delta resync operation does
not change after you performed delta resync operation, some requirements listed in this section
may not set properly. Check the status of the XP Continuous Access Journal pair and XP Continuous
Access Journal pair for delta resync operation, and make sure that all pairs are in the required
status.
If the status of the XP Continuous Access Journal pair for delta resync operation becomes HLDE,
you cannot restore the pair status to HOLD by resynchronizing the pair. Delete the XP Continuous
Access Journal pair for delta resync operation and create the XP Continuous Access Journal pair
again.
Transferring Business Tasks from the XP Continuous Access Journal Intermediate Site
to the Primary Site
If you remove failures from the primary site, you can transfer your business tasks back to the primary
site using RAID Manager and the following procedure:
1.
If the status of the XP Continuous Access Journal pair between the primary site and the
intermediate site is suspended, use RAID Manager to resynchronize the pair to reverse the
primary and secondary volumes.
2. Stop business tasks at the intermediate site.
3. Use RAID Manager to execute the horctakeover command on the XP Continuous Access
Journal pair between the primary site and the intermediate site. The XP Continuous Access
Journal pair between the intermediate site and the secondary site is automatically suspended.
4. Use the primary volume in the primary site to resume business tasks.
3DC Cascading Configuration of Three XP Continuous Access Journal Sites 69