HP Insight Dynamics 6.2 Integrity CMS Installation and Configuration Guide

B Back up the CMS configuration
The upgrade process is not reversible. To revert to a previous installation of the software, you
must restore the previous CMS configuration as well as any remote databases used by the
software. Therefore, HP recommends that you make a backup of your current installation before
upgrading the software.
Back up your existing CMS configuration prior to upgrading the software
The upgrade process is not reversible. To revert to a previous installation of the software, you
must restore the previous CMS configuration as well as any remote databases used by the
software. Therefore, HP recommends that you make a backup of your current installation before
upgrading the software.
Procedure B-1 Backing up your HP ID-VSE for Integrity CMS configuration
To make a complete backup of your HP ID-VSE for Integrity configuration, perform the following
steps:
1. 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. Stop the running gWLM daemon by entering the following command:
gwlmcmsd --stop
b. Stop the running Application Discovery server by entering the following command:
/opt/amgr/bin/cms_stop
c. Stop HP SIM by entering the following command:
/opt/mx/bin/mxstop
d. Back up the gwlm remote database on the Oracle server using Oracle Enterprise Manager
or Oracle Recovery Manager. This database is used by multiple ID-VSE for Integrity
applications.
e. Back up any remote database tables used by other SIM applications, if necessary. Other
HP SIM applications may have their own specific backup requirements. See the
documentation for those applications for specific instructions.
f. Back up the HP SIM remote database using Oracle Enterprise Manager or Oracle
Recovery Manager. The HP SIM remote database name begins with “Insight_v”, followed
by a version number.
2. Make a full backup of the CMS. Performing a full backup of an HP-UX server may require
booting the server in a lower init state or stopping additional system services, so that all
configuration files can be read in a stable condition. Consult your backup software
documentation for specific requirements.
Procedure B-2 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.
2. Restore the remote database tables.
3. Restart the server.
Back up your existing CMS configuration prior to upgrading the software 43