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

M-VOL Fence Level (Synchronous only): Select the fence level for the new pair(s) (default = Never).
•
Data: the M-VOL will be fenced (reject write operations) when the MCU cannot successfully
execute an update copy operation for any reason. This setting is functionally equivalent to the
CRIT(YES-ALL) parameter for the CESTPAIR command.
•
Status: the M-VOL will be fenced only if the MCU is not able to change the R-VOL status to
suspended when an update copy operation fails. This setting is functionally equivalent to the
CRIT(YES-PATHS) parameter for the CESTPAIR command.
•
Never: the M-VOL will never be fenced. This setting is functionally equivalent to the CRIT(NO)
parameter for the CESTPAIR command.
For further information on the CESTPAIR CRIT parameter and its two modes of operation,
CRIT(YES-PATHS) and CRIT(YES-ALL).
Initial Copy Parameters: Select the initial copy options for the new pair(s).
•
Initial Copy (default = Entire Volume):
Entire Volume = copy the data in all M-VOL tracks to R-VOL. This setting is functionally
equivalent to the MODE=COPY parameter for the CESTPAIR command. ◦
◦ None = do not copy any M-VOL data to R-VOL. This setting is functionally equivalent to
the MODE=NOCOPY parameter for the CESTPAIR command.
CAUTION: The user must ensure that the M-VOL and R-VOL are already identical when using
the No Copy setting.
•
Copy Pace: desired maximum number of tracks to be copied at one remote I/O during the
initial copy operation (default = 15):
◦ 15 Tracks. This setting is functionally equivalent to the PACE=2-255 parameter for the
CESTPAIR TSO command.
◦ 3 Tracks. This setting is functionally equivalent to the PACE=1 parameter for the CESTPAIR
command.
•
Priority: priority (scheduling order) of the initial copy operations (1-256). The default setting
is 32. The CESTPAIR TSO command does not support the initial copy priority option. When
CESTPAIR is used to establish TrueCopy for Mainframe pairs, the initial copy operations are
performed in the order that the CESTPAIR commands are issued.
If the time out error occurs during the Add Pair operation, the copy operation may not be
executed correctly in the order that you have set with the Priority parameter. The time out error
may be caused by the CU configuration or a remote copy path error. Review the error, release
the pair with the error, and then retry the Add Pair operation.
•
Difference Management: Select Auto, Cylinder or Track as the basis for managing the
differential data. The default is Auto. When you select Auto, either Cylinder or Track is selected
depending upon the basis size of the logical volume image.
•
CFW Data: Specifies whether the CFW data will be copied to the R-VOL:
Copy to R-VOL: the MCU will copy the CFW data to the R-VOL. ◦
◦ Only M-VOL: the MCU will not copy the CFW data to the R-VOL. This setting is
recommended for two reasons: (1) copying the CFW data impacts subsystem performance,
(2) CFW data is typically used for temporary files (for example, sort work datasets) which
are not usually required for disaster recovery.
When you create a TrueCopy for Mainframe pair, and if you select only M-VOLL for the CFW
data option, the data set which is updated by CFW in M-VOL cannot be used in R-VOL. To
use this data set in R-VOL, release a TrueCopy for Mainframe pair, and format the data set.
146 Performing TrueCopy for Mainframe Pair Operations