Interoperability with other products and functions – HP StorageWorks XP Remote Web Console Software User Manual
Page 50
When M-VOLs and R-VOLs are exchanged by using the Basic HyperSwap function, TrueCopy for
Mainframe synchronous pairs are resynchronized using the path that is already established.
Therefore, when the path is not established, the exchange using the Basic HyperSwap function
cannot be done.
From the point of view of performance, the recommended number of pairs under the Basic
HyperSwap function is up to 1,000 per CHA to which the path for accessing the TrueCopy for
Mainframe volumes is connected.
If the Basic HyperSwap function operation is performed from TPC-R, the MIH value of the host I/O
and host operation is about a second. Therefore, the MIH may be reported for the host I/O and
host operation.
Figure 8 Exchange of TrueCopy for Mainframe Synchronous Pairs M-VOLs and R-VOLs using TPC-R
Interoperability with Other Products and Functions
Some types of volumes used by non-TrueCopy for Mainframe and non-TrueCopy for Mainframe
Asynchronous functions can also be used as M-VOL and R-VOL of TrueCopy for Mainframe and
TrueCopy for Mainframe Asynchronous.
“Whether Non-TrueCopy for Mainframe and Non-TrueCopy
explains whether non-TrueCopy for Mainframe
and non-TrueCopy for Mainframe Asynchronous volumes are also usable as TrueCopy for Mainframe
and TrueCopy for Mainframe Asynchronous volumes.
Table 19 Whether Non-TrueCopy for Mainframe and Non-TrueCopy for Mainframe Asynchronous
Volumes Can Be Used as TrueCopy for Mainframe and TrueCopy for Mainframe Asynchronous
Volumes
Can the Volumes be
Used as TrueCopy for
Mainframe
Asynchronous R-VOL?
Can the Volumes be
Used as TrueCopy for
Mainframe
Asynchronous M-VOL?
Can the Volumes be
Used as TrueCopy for
Mainframe R-VOL?
Can the Volumes be
Used as TrueCopy for
Mainframe M-VOL?
Functions and Volumes
ShadowImage for Mainframe
Yes
Yes
Yes
Yes
S-VOL in Split status
No
No
No
No
S-VOL in Resync-R
status
50
About TrueCopy for Mainframe Operations