HPE IMC DBA User Database to IMC User Database Restoration Configuration Examples Part number: 5200-1335 Software version: IMC PLAT 7.2 (E0403) The information in this document is subject to change without notice. Copyright 2016 Hewlett Packard Enterprise Development LP
Contents Introduction 1 Configuration restrictions and guidelines 1 Example: Restoring dba user databases to IMC user databases 1 Network requirements 1 Software version used 2 Backing up the IMC databases on Server A 2 Restoring the backup database files to the Server B 5 Troubleshooting 8 WSM component cannot be loaded 8 Incorrect NTA server IP address 8 i
Introduction This document provides an example for restoring dba user databases to IMC user databases. On IMC PLAT 3.20-R2602 and earlier versions, database backup and restoration can only be performed in the database system, and some of the databases use the database username of dba (called dba user databases). On IMC PLAT 3.20-R2606P13 and later versions, DBMan (the Environment tab) is added to the Intelligent Deployment Monitoring Agent for users to perform database backup and restoration operations, and dba user databases are changed to IMC user databases. On an IMC system that was upgraded from 3.20-R2602 or earlier versions to 3.20-R2606P13, to back up the databases to an external IMC server installed with IMC PLAT 3.20-R2606P13, you must use the DBATool to restore the dba user databases to IMC user databases. Configuration restrictions and guidelines When you use the DBATool to restore the dba user databases to IMC user databases, follow these restrictions and guidelines: The DBATool is only available for IMC PLAT 3.20-R2606P13 and later versions. In IMC distributed deployment, when you restore database files to a standby IMC server cluster, make sure the Intelligent Deployment Monitoring Agent is disabled on the master and all subordinate IMC servers in the primary IMC server cluster. Other non-dba user databases must also be restored by using the DBATool. Restoring non-dba user databases by using the Intelligent Deployment Monitoring Agent might cause some IMC features to malfunction. Example: Restoring dba user databases to IMC user databases Network requirements An IMC server (Server A) is installed with IMC PLAT 3.20-R2602. Another IMC server (Server B) is installed with IMC PLAT 3.20-R2606P13. You are required configure Server B to be the backup server of Server A. Perform the following tasks: Upgrade IMC PLAT 3.20-R2602 to IMC PLAT 3.20-R2606P13. Use DBMan to back up the databases on Server A. Restore the backup database files of Server A to Server B by using the DBATool. 1
Software version used Server OS Database Primary IMC server Standby IMC server Windows SQL Server IMC PLAT 3.20-R2606P13 (or later versions) upgraded from IMC PLAT 3.20-R2602 (or earlier versions) IMC server installed with the same IMC Platform version as that is currently running on the primary IMC server Backing up the IMC databases on Server A 1. Open the Intelligent Deployment Monitoring Agent on Server A. As shown in Figure 1, DBMan (the Environment tab) is not provided. Figure 1 Intelligent Deployment Monitoring Agent without DBMan 2. Upgrade IMC PLAT 3.20-R2602 to IMC PLAT 3.20-R2606P13. For information about the configuration procedures, see HPE IMC deployment guides. 3. Restart the Intelligent Deployment Monitoring Agent on IMC Server A. As shown in Figure 2, the Environment tab is added, providing database backup and restore functions at the bottom of the tab. 2
Figure 2 Intelligent Deployment Monitoring Agent with DBMan embedded 4. On the Environment tab, click Configure. The Automatic Backup and Restore Configuration dialog box appears. As shown in Figure 3, the Database for Backup & Restore area displays all the databases on Server A, some of which have a database username of dba. 3
Figure 3 Databases on Server A 5. Click OK to update DBMan configurations and return to the Environment tab. 6. Click Backup. The Select database backup path dialog box appears. 7. Select a database backup path and click OK. The system starts to back up the database files. 4
Figure 4 Selecting the database backup path 8. On the Message box that appears, click OK. Figure 5 Message box Restoring the backup database files to the Server B 1. Copy and paste the backup database files from the Server A to the Server B. Databases with file names containing dba are dba user databases. 5
Figure 6 Database files to be restored 2. Copy the dbatool.exe file to the \imc\dbman\bin directory of the IMC installation path on Server B. The DBATool is included in DBMan on IMC servers installed with IMC PLAT 5.0 (E0101) or later versions. To restore databases to such servers, skip this step and directly execute the dbman -dba2imc "Backup File Location + Backup Filename" command. Figure 7 DBATool path 3. Open the Intelligent Deployment Monitoring Agent on Server B. 4. On the Environment tab, click Configure. The Automatic Backup and Restore Configuration dialog box appears. 6
As shown in Figure 8, the Database for Backup & Restore area displays all the databases on Server B. Unlike the databases on the Server A (see Figure 3), none of the databases of Server B use the database username dba. Figure 8 Automatic backup and Restore Configuration 5. Use the DBATool to restore the backup databases files of Server A to Server B. a. Open the command line window, and enter the \imc\dbman\bin directory of the IMC installation path, (the directory where the DBATool is located), as shown in Figure 9. Figure 9 Entering the directory where the DBATool is located b. Execute the dbatool -dba2imc "Backup File Location + Backup Filename" command to restore the backup database file one by one to Server B. For example, to restore the aclm database file, execute the dbatool -dba2imc "C:\Users\Administrator\Destop\bak\aclm_db_2013012_145022_full.db" command (see Figure 10), where C:\Users\Administrator\Destop\bak is the location of the backup aclm database file, and aclm_db_2013012_145022_full.db is the backup file name. 7
Figure 10 Restoring the aclm database successfully 6. Restart IMC. Troubleshooting WSM component cannot be loaded Symptom Solution In IMC distributed deployment where the WSM component is deployed on a subordinate IMC server, after I restore the WSM database file to the standby IMC server and log in to IMC, the system prompts that the WSM component cannot be loaded. To resolve the problem, first upgrade the WSM component to IMC WSM 5.0 (E0101) or a later version, and then use the DBATool to restore the WSM database file to the standby IMC server. Incorrect NTA server IP address Symptom In IMC distributed deployment where the NTA component is deployed on a subordinate IMC server, I restored the NTA database file to the standby IMC server. However, the IP address of the NTA server on the standby IMC server is incorrect. Figure 11 Incorrect NTA IP address Solution To resolve the problem: 8
1. Upgrade the NTA component to IMC NTA 5.0 (E0101H03) or a later version on the primary IMC server and then back up the database file. 2. Use the DBATool to restore the NTA database file to the standby IMC server cluster. 3. Locate the deploy\conf\server-addr_bak.xml file under the IMC installation path on the primary IMC server and subordinate IMC servers in the standby IMC server cluster, and change the IP address of the NTA server in the file to the IP address of the subordinate IMC server hosting the NTA component in the standby IMC server cluster. 9