Back Up Your Existing CMS Configuration Prior To Upgrading The Software

Procedure 2-6 Backing Up Your HP VSE Management Software CMS Configuration

To make a complete backup of your HP VSE Management Software 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:

   1. Stop the running gWLM daemon by entering the following command:

      gwlmcmsd --stop

   2. Stop the running Application Discovery server by entering the following command:

      /opt/amgr/bin/cms_stop

   3. Stop HP SIM by entering the following command:

      /opt/mx/bin/mxstop

   4. Back up the gwlm remote database on the Oracle server using Oracle Enterprise Manager or Oracle Recovery Manager. This database is used by multiple VSE Management Software applications.

   5. 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.

   6. 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 2-7 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.