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

• 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 commands net stop
and net start.
• If you try to connect to the EVA SMIS-S provider through SSL on a non-SSL port
using the SMI-S agent or omnidbsmis command, the agent or command will
stop responding.
Workaround: None. Stop the process and reconnect to the proper (SSL) port.
Known non-Application Recovery Manager issues
and workarounds
Non-Application Recovery Manager issues related to installation or
upgrade
• After installation or upgrade to Application Recovery Manager A.06.10, Windows
may report that some application is not installed or that a reinstall is required.
The reason is an error in the Microsoft Installer upgrade procedure. Please read
the Microsoft Knowledge Base article Q324906 to solve the problem.
• On rare occasions, Windows may incorrectly report free disk space for an NTFS
volume that is mounted at a directory on an NTFS filesystem: instead of the NTFS
volume free space the amount of free space on the NTFS filesystem is reported.
In such cases, if you try to install Application Recovery Manager to the mounted
NTFS volume, the Application Recovery Manager Setup Wizard will not start the
installation if the amount of free space on the NTFS filesystem is smaller than the
minimum disk space installation requirement.
Workaround: free enough additional disk space on the NTFS filesystem by
removing unnecessary files.
Recognized issues and workarounds30