HP Matrix Operating Environment 7.0 Integrity CMS Installation and Configuration Guide (7.0 and 7.1)

a. Stop the HP Capacity Advisor data collection service on 6.0 or later as follows:
• For a Insight Dynamics 6.* CMS, stop the HP Capacity Advisor Linux Agentless
Collection daemon by entering the following command:
/sbin/init.d/hp_capad_service stop
• For a Matrix OE 7.0 and later CMS, stop the HP Capacity Advisor Data Service
daemon by entering the following command:
/sbin/init.d/hp_cpdata_service stop
b. Stop the running gWLM daemon by entering the following command:
/opt/gwlm/bin/gwlmcmsd –-stop
c. Stop the running Application Discovery server by entering the following command:
/opt/amgr/bin/cms_stop
d. Stop Systems Insight Manager by entering the following command:
/opt/mx/bin/mxstop
7. Back up the remote database tables. If you are using the default PostgreSQL database, skip
this step. This step only applies if you are using a remote Oracle database. To back up the
remote database, use the following steps:
a. Back up the gWLM remote database on the Oracle server using Oracle Enterprise Manager
or Oracle Recovery Manager. This database is used by multiple Matrix OE for HP-UX
applications.
b. Back up any remote database tables used by other SIM applications, if necessary. Other
Systems Insight Manager applications may have their own specific backup requirements.
See the documentation for those applications for specific instructions.
c. Back up the Systems Insight Manager remote database using Oracle Enterprise Manager
or Oracle Recovery Manager. The Systems Insight Manager remote database name
begins with “Insight_v”, followed by a version number.
8. Make a full backup of the CMS. For example, the Ignite-UX make_net_recovery (1M)
command is a good way to back up the server to a network based system recovery archive.
See the “Backing up your system ” section of the HP-UX 11i v3 Installation and Update Guide
at http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?
contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&
prodTypeId=18964&prodSeriesId=3367813 for the make_net_recovery (1M) man
page. Ensure that you include all the application directories and files in the following list in
the backup image to preserve the Matrix OE and Systems Insight Manager installed files and
local database.
• /etc/opt
• /opt
• /var/opt
Also consult your backup software documentation for any other specific requirements.
9. Proceed with the upgrade and keep the following in mind:
• Do not restart Matrix OE services at this time.
• Follow any upgrade preparation instructions provided with the new version of Systems
Insight Manager.
After completing these steps see “Install the software on the CMS” (page 11),to install the software,
and then see “After upgrading from a previous version” (page 17) for additional steps you should
perform.
Procedure 17 Restoring your CMS configuration from backup
If you need to restore the CMS configuration that was saved using the preceding procedure, use
the following sequence:
1. Restore the server files from the full backup.
Back up your existing CMS configuration prior to upgrading the software 37