Interoperability with other products and functions – HP StorageWorks XP Remote Web Console Software User Manual
Page 8

1.
Establish a Version 1 relationship by using simplex volumes. When the relationship is
established, the volume status changes to F-Copy.
2.
After the relationship is established, the on-demand copy operation starts when the S-VOL is
updated.
The background copy operation will not be performed when the NOCOPY option is specified.
For details on the NOCOPY option, see
“Parameters for the FCESTABL Command (Version
.
3.
The relationship will be automatically withdrawn when the background copy operation is
completed. However, if the relationship is established with the NOCOPY option, the relationship
is not automatically withdrawn when the on-demand copy operation is completed.
When the background or on-demand copying of extent data fails, the Version 1 relationship will
be released automatically, the T-VOL will become blocked, and the status of the relationship will
become simplex.
“Version 1 Relationship Status Condition” (page 8)
describes the Version 1 relationship status
condition.
Table 1 Version 1 Relationship Status Condition
T-VOL Access
S-VOL Access
Description
Status
Read/write.
Read/write.
Version 1 is requested with
host commands. The S-VOL
differential data is copied to
the T-VOL in the
background. When the
NOCOPY option is
specified, no background
copy is performed.
F-COPY
Interoperability with Other Products and Functions
This section describes the conditions and requirements when you use Version 1 and other storage
system program products.
“Version 1 and Other Copy Solutions Shared Volumes” (page 8)
describes whether or not you
can share Version 1 volumes with the volumes of other copy solutions.
Table 2 Version 1 and Other Copy Solutions Shared Volumes
Conjunction
Copy Solution
N/A
Version 2
Supported
ShadowImage for Mainframe
Hitachi TrueCopy™ for Mainframe
Hitachi Universal Replicator™ for Mainframe
Concurrent Copy (CC)
N/A
HP StorageWorks XP Auto LUN Software
“Compatibility of Volumes Shared by Version 1 and Security Solutions” (page 9)
describes whether
or not you can set attributes for the S-VOL or the T-VOL of a Version 1 relationship by using other
solutions.
8
About Version 1 Operations