Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment

Transcription

1 Technical white paper Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment Table of contents Abstract 2 Introduction 2 Saving and restoring data files 2 Saving and restoring files where Systems Insight Manager is installed using a Microsoft SQL database 3 Saving HP SIM configuration files and SQL server data files 3 Saving and restoring files where Systems Insight Manager is installed using Microsoft SQL Server 2005 Express, Microsoft SQL Server 2005, or Microsoft SQL server 2008 Standard/Enterprise. 6 Saving and restoring files for an Oracle database 12 Backing up the Systems Insight Manager database 14 Restoring data files for use with Oracle 16 Restoring the database 17 For more information 20

2 Abstract HP Systems Insight Manager is a flexible management utility for an enterprise environment employing HP ProLiant, HP BladeSystem Integrated Manager in HP Insight Control, HP Storage, and HP Integrity solutions. The system database and configuration files used by Systems Insight Manager should be backed up regularly to allow recovery from a catastrophic system failure or an instance of corrupted files. This paper provides step-by-step instructions to back up the Systems Insight Manager data files and perform a restore if a software reinstallation becomes necessary on a system running Microsoft Windows operating system. This paper assumes that readers: Are familiar with IT administration policies and procedures Are familiar with the operating system platform implemented by their data center Have reviewed the HP SIM Installation and Configuration Guide for Microsoft Windows systems Introduction Systems Insight Manager is the foundation for the HP unified infrastructure management strategy. HP SIM provides hardware-level management for HP ProLiant, HP Integrity, and HP 9000 servers; HP BladeSystems; and HP Storage MSA/EVA/XP storage arrays all from a single console in the data center or in a remote location. Server and storage information for a network is kept in a database compiled by HP SIM. The system administrator should back up this database and associated configuration files regularly to allow for a smooth reinstallation or restore process if a catastrophic equipment or software failure should occur. Additional reference data is available in the form of on-line man pages, which provide quick command-line access to specific topics such as Systems Insight Manager commands and parameters. The Systems Insight Manager documents listed previously, the man pages, and additional Systems Insight Manager support documents are available at the Systems Insight Manager information library at the following URL: Note: This paper describes the backup and restoration of a same system for fault insurance purposes only. It does not apply to system migration or software upgrades. For migration information, refer to the migration white papers at Saving and restoring data files Systems Insight Manager can use one of three databases on a system running the Microsoft Windows operating system: Microsoft SQL Server Database Engine Microsoft SQL Server 2005 Express Oracle database Microsoft SQL Server 2005 Microsoft SQL Server

3 Saving and restoring files where Systems Insight Manager is installed using a Microsoft SQL database This section describes saving (backing up) and restoring files used with a Microsoft SQL database. Saving HP SIM configuration files and SQL server data files Microsoft SQL Enterprise Manager has built-in utilities for backing up the database, including an automated procedure. HP recommends viewing the Help files provided by the SQL Enterprise Manager to gain a complete understanding of this procedure. Note: HP recommends stopping the Systems Insight Manager service to ensure that the discovery and data collection processes do not occur during the save; however, you can leave the HP SIM service running during the save process. To save Systems Insight Manager configuration and Systems Insight Manager database using Microsoft SQL Enterprise Manager, proceed as follows: 1. Using the file management tool of your choice, save the directories and/or 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. Table 1. Configuration files to back up Directory or file <SIM>\config\ hp\sslshare\ <SIM>\logs\mx.log <SIM>\patch bin\servercert.pem bin\cliclientconfig.cfg <SIM>\installpsp <SIM>\swmaint <SIM>\output Description Directory of configuration files Shared openssl certificate directory Audit log file Program updates (required if you want to reinstall HP SIM), this may be empty Certificate used by the Command Line Interface (CLI) CLI configuration file (if existing) (if existing) (optional) Contains job result output 2. Save any existing user-supplied (custom) files contained in the Systems Insight Manager directory tree such as tool definition files (TDEFs), Management Information Bases (MIBs), login prompt, and actions. 3. Save the OpenSSH Keys from the <OpenSSH Install path>\etc folder. 4. Save any custom support packs used by the HP Version Control Repository Manager (VCRM). 5. Save any data files corresponding to any plug-in utilities used with Systems Insight Manager. See the documentation of the applicable plug-in utility for actual file names/locations. 6. From the Windows Start menu, open Microsoft SQL Enterprise Manager. 7. In the tree displayed in the left panel, expand the Microsoft SQL Servers branch and SQL server group. If the server is not listed where the HP SIM database is located, you can invoke the Register SQL Server Wizard by right-clicking SQL server group and selecting New SQL Server Registration to bring up the Register SQL Server Wizard window (figure 1). This procedure assumes the desired server is already listed and that the wizard is not required. 3

4 Figure 1: Register SQL Server Wizard window 8. Select the server where the HP SIM database is located. From the Tools menu at the top, select Backup database. In the dialog box that appears, select the database named Insight_v*, and select Database-complete as the backup option. Figure 2: SQL Server Backup window 4

5 9. In the Destination field, click Add, select a location (such as disk or tape) for storing the backup copy of database, and then click OK to initiate the backup. Restoring Systems Insight Manager configuration files and SQL server data files from a backup 1. If reinstalling Systems Insight Manager, for instructions refer to the HP Systems Insight Manager Installation and Configuration Guide for Microsoft Windows, available at: If not performing a reinstallation of Systems Insight Manager, then proceed to step 5. Note: You must reinstall HP SIM with the same user account used previously. If a local account was used, the host name must also remain the same. 2. Reinstall the WMI mapper, OpenSSH (and previous keys used), and SMH components if needed. 3. Reinstall any backup up custom files (TDEFs, MIBs, login prompt, and other actions) under the Systems Insight Manager directory tree, and any custom support packs used by VCRM. Note: The Systems Insight Manager installation procedure includes loading VCRM on a Windows CMS. 4. Reinstall any plug-in utilities (and associated files and databases) used with Systems Insight Manager. You can reinstall using Systems Insight Manager integrated installer, the management DVD, or standalone installer. 5. Stop the Systems Insight Manager Service if it is running, along with any Systems Insight Manager plug-in applications such as HP Insight Control performance management. 6. Using the file management tool of your choice, restore the directories and files listed in Table 1. For each occurrence of <SIM>, substitute the actual path name where Systems Insight Manager is installed. If offered, be sure that the Always replace the file on disk option is selected. Note: You must use a tool that preserves file permissions (such as the Windows Backup tool) while restoring directories and files. 7. From the Windows Start menu on a Windows console, open Microsoft SQL Enterprise Manager. 8. In the tree displayed in the left panel, expand the Microsoft SQL Servers branch and SQL Server group. 9. Select the server where the Systems Insight Manager database is located. From the Tools menu, select Restore Database. The Restore Database box appears as displayed in figure 3. Figure 3: Restore Database box 5

6 10. From the Restore as Database list, select the name of the restored Systems Insight Manager database (such as Insight_v*), and then select Database as the type of Restore. 11. From the Show backups of database list, choose the backup set to use, and then click OK. The database is restored with a dialog box indicating the progress as shown in figure 4. Figure 4: Restoring the backup set 12. Open the command line window and type mxconfigrepo c to check for database errors. Use the command mxconfigrepo f to fix any errors, and run the command mxconfigrepo c once again as a final check. 13. Start the Systems Insight Manager service and any plug-in application. Saving and restoring files where Systems Insight Manager is installed using Microsoft SQL Server 2005 Express, Microsoft SQL Server 2005, or Microsoft SQL server 2008 Standard/Enterprise. Microsoft SQL Server 2005 Express allows backing up both data files. Install SQL server client components. Note: Go to: to download client components. Saving Systems Insight Manager configuration files and SQL server data files Microsoft SQL Server Enterprise Manager has built-in utilities for backing up the database, including an automated procedure. HP recommends viewing the help files provided by the SQL Enterprise Manager to gain a complete understanding of this procedure. Note: HP recommends stopping the Systems Insight Manager service to ensure that the discovery and data collection processes do not occur during the save; however, you can leave the HP SIM service running during the save process if desired. 6

7 Saving Systems Insight Manager configuration and Systems Insight Manager database using Microsoft SQL Enterprise Manager 1. Using the file management tool of your choice, save the directories and 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). 2. Save any existing user-supplied (custom) files contained in the Systems Insight Manager directory tree such as tool definition files (TDEFs), Management Information Bases (MIBs), login prompt, and actions. 3. Save the OpenSSH Keys from the <OpenSSH Install path>\etc folder. 4. Save any custom support packs used by VCRM. 5. Save any data files corresponding to any plug-in utilities used with Systems Insight Manager. See the documentation of the applicable plug-in utility for actual file names/locations. Backing up the HP SIM database: 1. From the Windows, select Start Microsoft SQL Server 2005 SQL Server Management Studio Express. 2. The SQL Server 2005 window is displayed as in figure 5. Figure 5: SQL Server Click Connect. 4. Click Database, select the database named Insight_v* right click on Insight_v* tasks backup and a window pops up as in figure In the destination field, click Add, select a location (such as disk or tape) for storing the backup copy of database, and then click OK to initiate the backup. 6. Let us call this SIMDB1, the backup would be SIMDB1.bak. 7

8 Figure 6: Backup database Restoring Systems Insight Manager configuration files and SQL server 2005 data files from a backup 1. Uninstall Systems Insight Manager. This would uninstall Systems Insight Manager but will leave behind SIMDB1 as shown in figure 7. Figure 7: SIMDB1 8

9 2. Reinstall Systems Insight Manager. This would create a new blank database with a new name, let us call this SIMDB2 as shown in figure 8. Figure 8: SIMDB2 for instructions refer to the HP Systems Insight Manager Installation and Configuration Guide for Microsoft Windows, available at: If not performing a reinstallation of Systems Insight Manager, then proceed to step 6. Note: You must reinstall Systems Insight Manager with the same user account used previously. If a local account was used, the host name must also remain the same. Perform the remaining steps after the backup or restore is complete. 3. Reinstall the WMI mapper, OpenSSH (and previous keys used), and SMH components if needed. 4. Reinstall any backup up custom files (TDEFs, MIBs, login prompt, and other actions) under the HP SIM directory tree, and any custom support packs used by VCRM. Note: The HP SIM installation procedure includes loading VCRM on a Windows CMS. 5. Reinstall any plug-in utilities (and associated files and databases) used with Systems Insight Manager. You can reinstall using Systems Insight Manager integrated installer, the management DVD, or standalone installer. 6. Stop the HP Systems Insight Manager service in Windows services as this service would hold a live connection with the database and restoration will not happen unless this service is stopped, as shown in figure 9. Figure 9: Stop SIM services 7. Using the file management tool of your choice, restore the directories and files listed in Table 1. For each occurrence of <SIM>, substitute the actual path name where Systems Insight Manager is installed. If offered, be sure that the Always replace the file on disk option is selected. 9

10 Note: You must use a tool that preserves file permissions (such as the Windows Backup tool) while restoring directories and files. 8. Run mxgetdbinfo on the Systems Insight Manager system and make note of the database name used by Systems Insight Manager as shown in figure 10. Figure 10: Database used by HP SIM 9. From the Windows, select Start Microsoft SQL Server 2005 SQL Server Management Studio Express. 10. The SQL Server Management Studio Express console is displayed as in figure Click on Connect. 12. Delete SIMDB1 that is left around from the previous un-installation. 13. Restore the backed up file created from SIMDB1. For example, SIMDB1.bak, to the new database that Systems Insight Manager created in step 2. For example, SIMDB Expand the Database tree, select the SIMDB2 database created in step 13, and right click on tasks restore database as shown in figure

11 Figure 11: Restore database 15. In the Restore window, select Options. 16. In the right hand side screen under Restore options select Overwrite existing database and make it checked as shown in figure In the option below that says Restore Database Files as, change the names of the mdf and ldf files in the Data and Log Files option to match with the complete path names to SIMDB2. Since we have selected SIMDB1.bak backup file, these file names would point to SIMDB1 mdf and ldf files. Figure 12: Restore options and renaming files Note: We need to change these manually to be SIMDB2.mdf and SIMDB2_log.ldf explicitly for Database to get restore successfully. 11

12 18. Now do the restore by clicking on OK button. This should be completed successfully without any warnings or errors as shown in figure 13. Figure 13: Restoring database 19. Open the command line window and enter mxconfigrepo -c to check for database errors. Use the command mxconfigrepo -f to fix any errors. 20. Run the command mxconfigrepo -c again as a final check. 21. Start the HP SIM service and any plug-in application. 22. Verify that the data is restored successful. Saving and restoring files for an Oracle database The following procedures describe backing up and restoring data files for a system using an Oracle database with Systems Insight Manager. A user with Oracle Database Administrator (DBA) privileges must conduct the backup and restore processes. Saving data files for use with Oracle To save (back up) Oracle database files, use the following procedure: Note: HP recommends stopping the HP SIM service to ensure that the discovery and data processes do not occur during the save; however, you can leave the HP SIM service running during the save process. 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. 12

13 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. To do this, enter: exec dbms_stats.gather_schema_stats( <dbuser>,dbms_stats.auto_sample_size); Note that in the query, you should use dbuser in uppercase. For example, if the dbuser is hpsim, use "HP SIM" in the query above, as that is how it is stored in the database. The query would look like: exec dbms_stats.gather_schema_stats( HPSIM,dbms_stats.auto_sample_size); 12. After making sure statistics is up to date, run the query to locate empty tables: Select table_name from dba_tables where owner= <dbuser> and num_rows=0; Note that in the query, you should use dbuser in uppercase. For example, if the dbuser is hpsim, use "HP SIM" in the query above, as that is how it is stored in the database. The query would look like: Select table_name from dba_tables where owner= HPSIM and num_rows=0; Select table_name from dba_tables where owner= hpsim and num_rows=0; may not work. 13. If there are any tables returned by the query above, you have empty tables that will not be exported by Oracle 11g exp utility. 14. A workaround for this problem. For each of the empty tables, running the below command would make the table visible to Oracle 11g exp utility and therefore get exported as expected. Alter table <table_name> allocate extent; 13

14 15. There could be several tables that are empty. To generate a convenient script that includes all of the empty tables, Enter: Sqlplus <dbuser>/<dbpassword> >set echo off; >set feedback off; >set heading off; >set pagesize 0; >spool fix_empty_tables.sql; >select alter table table_name allocate extent; from dba_tables where owner=<dbuser> and num_rows=0; >spool off; >quit; 16. The output of the above script is spooled to the file fix_empty_tables.sql in the current directory where you executed sqlplus from. If you want this file to be spooled to a different location, specify in the spool statement above the location where you want it to be spooled to. For example, C:\temp. The statement above would change in this case, to: spool C:\temp\fix_empty_tables.sql 17. Using sqlplus, run the generated sql file using the below commands: Sqlplus <dbuser>/<dbpassword> >@fix_empty_tables.sql; >quit; 18. Running the script would alter all of the empty tables. If the script fix_empty_tables.sql is located at C:\temp, then you would specify the full path in the command above. For example, instead you would C:\temp\fix_empty_tables.sql 19. Export using the Oracle 11g exp utility. None of the tables will be skipped this time. Backing up the Systems Insight Manager database 1. Login to the Oracle Management server. At the Oracle server console command line, enter the following command: set ORACLE_SID=dbname Where dbname is the database to be saved. 14

15 Figure 14: Set Oracle database name 2. Enter the exp command and press Enter to accept the database backup. Table 2 lists the Oracle parameters that are listed and the recommended action. Table 2. Oracle Database parameters for Backup Parameter Username Password Action Enter the username of database and click Enter. (The Database user name used to install HP SIM). Enter the password of the database user and click Enter. Array fetch Buffer size Click Enter to select default of Export file BACKUP.DMP <Path\backup.dmp> 1) E(ntire) Database 2) U(sers) 3) T(ables) Export Grants (Yes/No) Export Table Data (Yes/No) Compress Extents (Yes/No) Enter the file name and the path to dump the database. Note: If a path is not provided, the.dmp file is placed under the users home directory. Type E and press Enter. Press Enter to select Yes. Press Enter to select Yes. Press Enter to select Yes. 15

16 Figure 15: Export 3. After selecting the default parameters, the database backup is initialized and a backup.dmp file is created at the specified location. Figure 16: Database backup.dmp Restoring data files for use with Oracle 1. If necessary, reinstall Systems Insight Manager as directed in the HP Systems Insight Manager Installation and Configuration Guide for Microsoft Windows systems available at the following URL: If not performing a reinstallation of HP SIM, then proceed to step 5. Note: You must reinstall Systems Insight Manager with the same user account that was used previously. 16

17 2. Reinstall the WMI mapper, OpenSSH (and previous keys used), and SMH components if needed. 3. Reinstall any backed up custom files (TDEFs, MIBs, login prompt, and other actions) under the HP SIM directory tree, and any custom support packs used by VCRM. Note: The HP SIM installation procedure includes loading the VCRM on a Windows CMS. 4. Reinstall any plug-in utilities (and associated files and databases) used with Systems Insight Manager. 5. If it is running, stop the Systems Insight Manager Service, along with any Systems Insight Manager plug-in applications such as performance management. 6. Reinstall Oracle as directed in Oracle documentation. 7. Using the file management tool of your choice, restore the directories and files listed in Table 2. For each occurrence of <SIM>, substitute the actual pathname 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 restoring directories and files. Table 3. Configuration files to restore for Oracle Directory or file <SIM>\config\ (see note) C:\hp\sslshare\ <SIM>\logs\mx.log <SIM>\patch <SIM>\bin\servercert.pem <SIM>\bin\cliclientconfig.cfg <SIM>\installpsp <SIM>\swmaint <SIM>\output Description Directory of configuration files Shared openssl certificate directory Audit log file Program updates (required if you want to reinstall HP SIM), this might be empty Certificate used by the Command Line Interface (CLI) CLI configuration file (if existing) (if existing) (optional) Contains job result output 8. Start the Systems Insight Manager service and any plug-in applications. Restoring the database To restore and recover the database, perform the following steps: 1. Login to the Oracle Management Server. At the Oracle server console, type the following command: set ORACLE_SID=<dbname> Where dbname is the database just created. 17

18 Figure 17: Set database name 2. Type the command imp and press Enter. Table 4 lists the Oracle database parameters that are offered and the recommended action to take. Table 4. Configuration files to restore for Oracle Parameter Username Password Export file BACKUP.DMP <Path\backup.dmp> Action Enter the username of database and click Enter. (The Database user name used to install HP SIM). Enter the password of the database user and click Enter. Enter the file name and the path to dump the database to restore and press Enter. Insert Buffer size Press Enter to select the default List contents of import file only (Yes\No) Ignore create error due to Object existence (Yes/No) Import Grants (Yes/No) Import Table Data (Yes/No) Import Entire export file (Yes/No) Username Table (T) Partition (T:P) Or if done (.) Press Enter to select No. Select Yes and press Enter. Press Enter to select Yes. Press Enter to select Yes. Press Enter to select No. Type the user name of the database and press Enter. Type the dot character (.) and press Enter to begin the database restoration. 18

19 Figure 18: Import database 3. Start the Systems Insight Manager service and any plug-in. 4. Verify that the data is restored successfully. 19

20 For more information For additional information about HP SIM, visit hp.com/go/hpsim. Get connected hp.com/go/getconnected Current HP driver, support, and security alerts delivered directly to your desktop Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle and/or its affiliates. 4AA4-4277ENW, Created December