Backing up and restoring HP Systems Insight Manager 6.3 database in a Windows Environment
16
1. Using the file management utility of your choice, save the configuration files listed in Table 1. For
each occurrence of <SIM>, substitute the actual path name where Systems Insight Manager is
installed (such as C:\Program Files\HP\Systems Insight Manager).
Note:
You must use a tool that preserves file permissions (such as the Windows
Backup tool) while saving directories and files.
2. Open the <SIM>/config/database.props file and check the property value for
hp.database.username. A user with DBA privilege must conduct the backup and restore
process.
3. Save any existing user-supplied (custom) files contained in the Systems Insight Manager directory
tree such as TDEFs, MIBs, login prompt, and actions.
4. Save the OpenSSH Keys from <OpenSSH Install path>\etc folder.
5. Save any custom support packs used by the VCRM.
6. Save any data files corresponding to any plug-in utilities used with Systems Insight Manager. Refer
to the documentation of the applicable plug-in utility for actual file names/locations.
7. Back up the Oracle data files (refer to Oracle documentation for detailed information).
Note:
Follow below steps from 8 to 16 only if you are using Oracle 11g as Systems Insight
Manager
database.
8. Oracle 11g exp utility to export tables does not export tables that are empty. As a result, while
exporting the Systems Insight Manager database using Oracle 11g exp utility, tables without any
data rows do not get exported.
9. Set ORACLE_SID=dbname.
10. To work around this problem, identify empty tables, using the below commands in sqlplus
Sqlplus <dbuser>/<dbpassword> where dbuser is the username used by Systems Insight
Manager to connect to the Systems Insight Manager database and dbpassword is the
password for this user.
11. It is possible that in your Oracle database, statistics are not updated. You might need to get
statistics updated before you proceed further.
Todothis,enter:
exec
dbms_stats.gather_schema_stats(‘<dbuser>’,dbms_stats.auto_sam
ple_size);
Note that in the query, you should use dbuser in uppercase. For example, if the dbuser is
‘hpsim’, use ‘HPSIM’ in the query above, as that is how it is stored in the database.