HP Application Recovery Manager software A.06.10 - Product announcements, software notes, and references (March 2008)

session manager (BSM) process. In both cases, such behavior of the integration
agent is wrong.
Workaround: None.
Issues with MC/ServiceGuard
• If you export a physical node from the MC/ServiceGuard cluster, you cannot
import it back, as the cell_server file will be deleted. This file is shared among
all nodes of a cluster, so you need to recreate it.
Workaround: Run /opt/omni/sbin/install/omniforsg.ksh -primary
-upgrade.
Disk Array XP integration issues in a cluster environment
• In a cluster environment, if an instant recovery is performed on a different node
than backup (in case of a failover between the ZDB and instant recovery sessions),
the instant recovery fails with a similar error:
[Warning] From: [e-mail] "" Time:
2/19/2008 2:35:46 PM Failed to get command device from XPDB
for LDEV 8690.
The issue appears if different command devices are configured for each node.
Workarounds:
• Ensure that the same command device is used on both nodes.
• Use the omnidbxp command to manually add the missing command device.
See the HP Application Recovery Manager software command line interface
reference for details on how to add a command device using omnidbxp.
Other known issues
• Command omnistat -session [session ID] -detail sometimes displays
Restore started and Backup started incorrectly. This can result in both parameters
appearing to be identical.
• The following applications are not recommended to be installed together with
Application Recovery Manager on the same system: WebQoS, CyberSitter 2000,
NEC E-border AUTOSOCKS.
• If more than one omnidbutil -purge session is started, omnidbutil reports
that it cannot communicate with the Cell Manager. To avoid this, do not start
more than one session.
Product announcements, software notes, and references 29