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

Table 33 Analyzing the Consistency of XP Continuous Access Asynchronous S-VOLs
Description Usable for
Recovery? Consistency
Status Status of S-VOL
These states do not usually occur during XP Continuous Access
Asynchronous disaster recovery because the RCU suspends
all XP Continuous Access Asynchronous S-VOLs when
communication with the MCU is lost. XP Continuous Access
Asynchronous S-VOLs in these states should not be used for
disaster recovery.
NOTE: Simplex volumes cannot be distinguished from
S-VOLs that have already been released by the pairsplit-S
operation.
No
No
No
- - PAIR
COPY
SMPL
The update sequence consistency across these S-VOLs is
ensured. These S-VOLs can be used for disaster recovery at
the secondary system.
NOTE: The time of the latest update indicated on the
Detailed Information dialog box (MCU SVP time) will help to
determine the last time these S-VOLs were updated.
Yes Group PSUE
The contents of this S-VOL may be behind the other S-VOLs
in the consistency group. If this volume must be consistent
with the other volumes in the same group, this S-VOL should
not be used for disaster recovery.
The cause for this status is:
• The XP Continuous Access Asynchronous Error Level pair
option for this pair is LU (not Group), AND
•
This pair was suspended before the disaster/failure, at
the beginning of the rolling disaster, or during the initial
copy operation.
No LU
Transferring Operations Back to the Primary Site
Once the applications are running at the secondary (remote) site, the next activity is to restore the
primary (main) site and transfer operations back to the primary site. To transfer operations to the
primary site:
1. Bring up the host server(s) at the primary site, and make sure that all XP Continuous Access
components are fully operational.
2. At the primary site, release all XP Continuous Access pairs at the MCUs. The Delete Pair by
Force option must be used because the previous S-VOLs are in the SMPL state at the secondary
site.
3. At the main site, delete all XP Continuous Access Asynchronous consistency groups at the
MCUs.
4. At the main site, delete the RCUs. Remember to connect with each MCU and each CU to make
sure that all the RCUs have been deleted.
5. If you plan to use the same remote copy connections to copy back, change the existing initiator
ports to ordinary target ports.
6. If you plan to use the same switches, change the operating mode to the opposite direction
(see
“Remote Copy Connections” (page 54) ).
If you plan to use the same channel extenders, change the operating mode to the opposite
direction. The boxes/nodes connected to the MCUs must be set to channel-mode, and the
boxes/nodes connected to the RCUs must be set to device-mode.
7. At the remote site, configure the appropriate ports to enable XP Continuous Access operations
in the reverse direction (change target ports to initiator ports). This enables the original RCUs
Using XP Continuous Access for Disaster Recovery Operations 153