HP XP Array Manager Software User Manual
Page 80
•
A copy group must consist of pair volumes for the same application. When a copy group consists
of more than one pair volume and there are pair volumes for different applications in the copy
group, an unexpected backup or restoration might be performed.
•
When using Business Copy, configure the pair volume in the storage system. When using Continu-
ous Access Software, configure the pair volume between the storage systems.
•
Application Agent operates the pair volumes for Business Copy, Fast Snap, Snapshot, Continuous
Access Software or Continuous Access Journal.
•
Application Agent cannot back up or restore volumes paired by Flex Copy or Auto LUN.
•
Depending on the version of RAID Manager, the model of the storage system, and the version of
the microcode, the functionality for acquiring the copy type of the pair volume (copy group) might
not be supported. Because of this, Application Agent might not be able to correctly recognize
whether the copy type of a pair volume (copy group) is supported, since the copy type cannot be
retrieved. Thus, if you configure a system in which Flex Copy pair volumes and Business Copy,
Fast Snap, or Snapshot pair volumes co-exist, since the Flex Copy pair volumes (copy groups) are
not supported, make sure that they are disregarded as backup or restoration targets, by locking
them with the drmcgctl command.
•
When using Continuous Access Software, do not enter an MU number in the MU# setting in the
RAID Manager configuration definition file (
horcm
n
.conf
). If
0
is defined for the MU# setting,
volume information for the Continuous Access Software pair will not be stored in the dictionary
map when you execute a
drm
XX
display
#
command with the
-refresh
option specified.
Therefore, the volume information cannot be displayed by the Application Agent command, and
the pair volume cannot be backed up.
#
drm
XX
display
indicates the
drmfsdisplay
,
drmsqldisplay
, or
drmexgdisplay
command.
•
When using Continuous Access Journal, define
h0
(
h
and a generation number) for the MU#
setting in the RAID Manager configuration definition file (
horcm
n
.conf
). If
0
is defined for MU#,
the Continuous Access Journal information will not be stored in the dictionary map when you execute
a
drm
XX
display
command with the
-refresh
option specified. Therefore, volume information
cannot be displayed by the Application Agent command, and the pair volume cannot be backed
up.
•
When using Continuous Access Software or Continuous Access Journal, make sure that you start
the RAID Manager instance that manages the secondary volume (the RAID Manager instance that
manages the primary volume when you are executing the command in a backup server) in advance.
•
The RAID Manager configuration definition file (
horcm
n
.conf
) of a RAID Manager instance that
links with Application Agent must satisfy the following conditions:
• The RAID Manager configuration definition file (
horcm
n
.conf
) must be in the Windows dir-
ectory (
%windir%
).
The environment variable
HORCM_CONF
cannot be used to change the location of the RAID
Manager configuration definition file (
horcm
n
.conf
).
• The instance number (n) in the RAID Manager configuration definition file name (
horcm
n
.conf
)
must include only numeric characters. Also, note that 0 must not be placed before numeric
characters.
Examples of valid file names:
horcm1.conf
,
horcm120.conf
Examples of invalid file names:
horcm001.conf
,
horcmA20.conf
•
When using Continuous Access Software or Continuous Access Journal, make sure that you create
a pair before executing a Application Agent command. If you do not, the pair volume cannot be
backed up.
Application Agent system configurations
80