About configuration definition file formats, About creating copy pair configuration definitions, Server.agent.rm.culdevform values – HP XP Racks User Manual
Page 150
About configuration definition file formats
New configuration definition files (HORCM configuration files) can be generated in either
HORCM_LDEV format or HORCM_DEV format. Replication Manager allows you to specify the format
for new configuration definition files using the
server.agent.rm.pairDefinitionForm
and
server.agent.rm.cuLdevForm
properties in the Device Manager agent
server.properties
file. (For detailed property file descriptions, see the HP P9000 Command View Advanced Edition
Suite Software Administrator Guide.)
By default, new configuration definition files are generated in the HORCM_DEV format. To change
the default format to HORCM_LDEV, set the value of
server.agent.rm.pairDefinitionForm
to
HORCM_LDEV
.
Table 8 server.agent.rm.cuLdevForm values
Example
HORCM_LDEV format (Decim-
al/Hex)
Value of server.agent.rm.
cuLdevForm
15067
3A:DB
0x3ADB
Decimal
Hex(CU:LDEV)
Hex
Empty (Default)
Invalid value
DECIMAL
CULDEV
HEXA
To maintain consistency of configuration definition file formats, Replication Manager does not allow
creation of configuration definition files with mixed formats. However, Replication Manager supports
pre-existing configuration definition files that have mixed formats. When new copy pairs are added
to an existing copy group, Replication Manager confirms the existing file format of the configuration
definition file and applies the same format for the new copy pairs. If new copy pairs are added to a
pre-existing configuration definition file that has mixed formats (HORCM_LDEV and HORCM_DEV
formats), Replication Manager determines the format for the new copy pairs using the
server.agent.rm.pairDefinitionForm
property in the Device Manager agent
server.properties
file.
Related topics
About creating copy pair configuration definitions
Replication Manager allows you to create copy pair configuration definitions in open systems where
the storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000 and in mainframe
systems where the storage system type is XP12000/XP10000/SVS200 or XP24000/XP20000.
There are some requirements to be satisfied before creating copy pair configuration definitions. For
information on copy pair configuration requirements, see “
” on page 151. If the defined configuration does not satisfy these requirements, an error will
occur when the copy pair configuration task is executed.
In mainframe systems, there are additional prerequisites for pair configuration. For details about
prerequisites for pair configuration in mainframe systems, see “
Prerequisites for pair configuration
The maximum number of copy pairs that can be specified differs depending on the storage system
and copy type. For details on this number, see the relevant storage system manual. For information
Managing pair life cycle
150