HP StorageWorks XP24000/XP20000 for FlashCopy Mirroring Software User Guide (T5240-96012, May 2011)

T-VOL is blocked because of the blockade watch, and the host I/O to the S-VOL can be
maintained.
• If the host I/O to the T-VOL and the T-VOL data is more important than the host I/O to the
S-VOL, use the default setting for the path blockade watch for the external volume that is to
be specified as the T-VOL.
“Whether Reverse Restore and Fast Reverse Restore Can be Used When a Version 2 Volume is
Used as a Volume of Other Solutions” (page 54) describes whether you can perform Reverse
Restore and Fast Reverse Restore on the S-VOL or the T-VOL of a Version 2 pair for which attributes
are set by other solutions.
Table 27 Whether Reverse Restore and Fast Reverse Restore Can be Used When a Version 2 Volume
is Used as a Volume of Other Solutions
Version 2AttributeSolutions
T-VOLS-VOL
This attribute cannot be set.This attribute cannot be set.ProtectVolume Retention Manager
YesYesRead only
YesYesRead/Write
This setting can be made.This setting cannot be made.Security setting that disables
the volume for use as S-VOL
Volume Security
NoNoExternal VolumeXP External Storage
The following volumes cannot be used as the S VOL or T VOL of the Version 2 pair.
• Command devices used by Business Continuity Manager
• Journal volumes of Universal Replicator for Mainframe
• Reserve volumes used by ShadowImage for MainframE
• Alias volumes used by the Compatible PAV feature
• System disks
Using Version 2 with ShadowImage for Mainframe
“Pair Configuration Where an S-VOL of Version 2 and ShadowImage for Mainframe is Shared”
(page 54) shows an example of combining Version 2 with ShadowImage for Mainframe.
Figure 29 Pair Configuration Where an S-VOL of Version 2 and ShadowImage for Mainframe is
Shared
Usually, you need to specify a volume in Simplex status as a copy source (S-VOL) or a copy target
(T-VOL). When you specify a ShadowImage for Mainframe S-VOL as a copy source, you can
establish or release a Version 2 relationship only if the ShadowImage for Mainframe pair is not
in Resync-R status.
54 About Version 2 Operations