HP XP P9000 Replication Manager Software 7.6.0-00 Application Agent CLI User Guide

Setting up operation mode when automatically selecting copy groups
Usually, Application Agent automatically selects the secondary volume used as a backup destination.
However, when Application Agent is copying data to multiple secondary volumes by locking the copy
group, one generation might be given different generation numbers. To avoid restoring data with a
generation number that does not always refer to the same generation, you can specify that a backup
operation will cause an error if a generation number does not always refer to the same generation.
In a remote copy backup session, a generation number (MU#s) that does not always refer to the same
generation causes an error regardless of this parameter definition.
Table 33 Parameter in the RAID Manager-linkage definition file (DEFAULT.dat) (settings for operation
mode when automatically selecting copy groups)
Specifiable values
(default)
DescriptionParameter
DISABLE or
ENABLE
(ENABLE)
Specify operations if, within a
session, a generation number
(MU#) does not always refer to
the same generation due to
automatic selection of the copy
group during backup at a local
site.
Disagreement of pair identifiers
causes an error when ENABLE
is specified.
When DISABLE is specified or
this parameter is omitted, a
warning message for a
generation number that does not
always refer to the same
generation is output while the
backup continues. However, it
is possible that the restoration of
this backup may fail.
CONFIRM_GENERATION_IDENTICAL
Notes on starting and stopping RAID Manager
When a Application Agent command is executed, a RAID Manager instance is used. The procedures
used to start and stop a RAID Manager instance vary depending on whether the RAID Manager
instance is active or inactive when the command is executed. Determine which method to use to start
the RAID Manager instance, after taking into consideration your operation style.
If RAID Manager is inactive when a Application Agent command is executed:
When a command is executed, the command internally starts the RAID Manager instance.
When the command terminates, the instance that was started by the command also stops.
If RAID Manager is active when a Application Agent command is executed:
Application Agent uses the active RAID Manager instance. Even when the command terminates,
the RAID Manager instance does not stop.
When multiple commands are to be executed in a series, you should start RAID Manager before-
hand to eliminate unnecessary repetitions of RAID Manager startup and stopping.
Preparation for using Application Agent128