HP StorageWorks Application Recovery Manager Administrator's Guide (T4395-96004, February 2008)

Appendix B
Known Application Recovery Manager Issues and Workarounds
Appendix BB-8
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.
• After a long period of continuous operations, the OmniInet process
memory usage on the backup server can grow very large.
Workaround:
1. Check that there are no sessions running on the client.
2. Restart OmniInet (Application Recovery Manager Inet) in the
Control Panel -> Administrative Tools -> Services
window or using the command line command net stop/start.
•If you select the Non-strict configuration check mode and your
database configuration files and directories are not installed directly
on a drive (for example, c:\) but in a directory on this drive, the
configuration check during backup or instant recovery fails.
Consequently, the backup or instant recovery session also fails. The
check fails even if all directories belong to the writer’s components.
Workaround:
— Use only the Strict or Disabled configuration modes.
— Install the database directly on a drive.