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

(see HP Matrix Operating Environment for HP-UX Installation
and Configuration Guide).
-b|--backup Back up the Matrix OE database, including gWLM and
Capacity Advisor data, to protect against loss of data.
Matrix OE must be initialized before you can perform a
backup. For information about initializing Matrix OE, see
the earlier description of the --initconfig option.
NOTE: This option is only available on a CMS running
HP-UX using the PostgreSQL database.
The backup is created in the directory specified by the -d
or --dir option. This directory must be initially empty or
must not yet exist.
The backup created by this command contains only Matrix
OE data. For information about backing up the HP SIM
database, refer to the HP white papers cited in the SEE ALSO
section.
If you are creating a backup in preparation for relocating
the CMS, HP recommends that you first undeploy all shared
resource domains (SRDs). This will make it easier to redeploy
the SRDs after the CMS is moved.
If you are using gWLM to manage any SRDs, execute the
following command on the CMS to ensure that your backup
includes up-to-date historic data:
gwlm history --flush
-s|--restore Restore the Matrix OE database from the backup in the
directory named by the -d or --dir option. Matrix OE
must be initialized before you can perform a restore,
therefore the --clobber or -F is also required in order to
replace the database. For information about initializing
Matrix OE, see the earlier description of the --initconfig
option.
NOTE: This option is only available on a CMS running
HP-UX using the PostgreSQL database.
HP SIM must be stopped when the restore operation is
performed. To stop HP SIM, execute the command mxstop
on the CMS. Use mxstart to restart HP SIM after the restore
operation is finished.
For information about restoring the HP SIM database, refer
to the HP white papers cited in the SEE ALSO section.
33