HP Storage Essentials V5.1 Installation Guide Second Edition (Linux Release) (T4283-96055, November 2006)

Installing the Management Server on Microsoft Windows48
5. The dbAdmin tool does the following when the file is imported:
a. Removes the APPIQ_SYSTEM account.
b. Creates an APPIQ_SYSTEM account.
c. Imports data into the APPIQ_SYSTEM account.
d. Determines the version of the management server the data is from.
e. Applies the upgrade script for the version detected. The upgrade script does not run if the
detected version is the same as the latest version. The upgrade script updates sequentially.
f. Upgrades and restores the CIM repository that was exported.
g. Restores File SRM from the exported files.
6. Sybase is not listed in the topology after you port the management server. Click Get Topology
(Discovery > Topology) or Get Details (Discovery > Details) to make the management
server aware of Sybase.
Upgrading the Management Server
Keep in mind the following:
• Refer to the release notes for upgrade path and late breaking information about upgrading the
management server.
• Complete the upgrade and its subsequent steps in one session, which may take several hours
depending on your network configuration. Completing the steps over several sessions will result
in incomplete data until all steps have been completed.
• When devices are discovered in HP SIM, the information concerning that device that is passed
from HP SIM to HP SE is the IP address and any user credential information that has been
entered within HP SIM. It is possible to have the DNS name instead of the IP Address passed
from HP SIM to HP SE by changing the StorageEssentialsSendIPAddress flag in the HP SIM
globalsettings.props file from True to false. This file can be found in the following directory
on the HP SIM management server:
[Installation_Directory]\config\globalsettings.props
• It is necessary to perform Discovery Data Collection/Get Details after you upgrade to
repopulate the database.
• By default, the Brocade switch provider is set to Fabric Access API after upgrading. See
”Important Information About Upgrading and Brocade Switches” on page 53 if your SAN
includes Brocade switches and you are upgrading to build 5.1.
• It is important to clear the client java cache after upgrading the management server.
• Additional steps are required after an upgrade, see the steps in this section for more
information.
• CLI clients earlier than the current revision are not supported.
• The upgrade lets you know about any customizations to configuration files that were made in
previous releases. You can view the differences that have been detected in an HTML file in the
%MGR_DIST%\logs directory.
Files backed-up and restored to their original location:
• All files in %MGR_DIST%\JBossandJetty\server\appiq\remoteScripts