HP Application Recovery Manager software A.06.10 Administrator's guide (March 2008)

Objects and their mirror configurations during backup and restore sessions are kept
in XPDB for replica set rotation and instant recovery. Only LDEV pairs recorded in
XPDB can be used for instant recovery.
XPDB resides on the Cell Manager in:
• HP-UX: /var/opt/omni/server/db40/xpdb
• Windows: AppRM_home\db40\xpdb
Configuring the integration
In a cluster environment, the backup system must not be in the same cluster with the
application system. The backup system also cannot be virtual server of a cluster. It
can only be a cluster node.
Before you start configuration, make sure you met the prerequisites described in
“Introduction” on page 65. In addition, do the following:
Connect the application and backup systems to the same XP.
Primary LDEVs (P-VOLs) must be connected to the application system and each have
1-3 paired disks (S-VOLs) assigned. Mirrored LDEVs (S-VOLs) must be connected to
the backup system.
HP-UX LVM mirroring: Use the physical volume groups mirroring of LDEVs to ensure
that each logical volume is mirrored to an LDEV on a different I/O bus. This
arrangement is called PVG-strict mirroring. Disk hardware must be already configured,
so that the mirror copy disk is connected to the system on a different bus (not the bus
used for the primary copy).
For more information on LVM mirroring, see the HP-UX Managing Systems and
Workgroups manual.
To configure the integration:
• Set XP command devices. See “Command device handling” on page 67.
• If needed, set the XP LDEV exclude file. See “XP LDEV exclude file” on page 68.
Command device handling
XP command devices are needed by processes requiring access to XP. The information
about command devices is kept in XPDB for the purpose of eliminating duplicate
instance usage and over-allocation.
• Whenever a session is started, Application Recovery Manager queries XPDB for
a list of command devices. If there is none (default behavior when the first session
Administrator's guide 67