HPE IMC Windows Migration Guide

Transcription

1 HPE IMC Windows Migration Guide Part number: Software version: The information in this document is subject to change without notice. Copyright 2017 Hewlett Packard Enterprise Development LP

2 Contents Introduction 1 Restrictions and guidelines 1 Procedure 2 Back up the IMC database on the old server 2 Setting up the new environment 4 License the new IMC server 6 Restore the database 6 i

3 Introduction This document describes how to migrate IMC and its database using DBman, the IMC database backup/restore process. In summary, the procedure is that a new IMC server and database are installed, the IMC license is transferred, and the database backup taken from the old server is restored on the new server. Restrictions and guidelines This document describes the migration process for a single IMC master server, not including UAM or IMC modules installed in a distributed environment. Consideration should be given to changing the IP address of the IMC server. If this is done, all network devices will need to be reconfigured wherever they use the IMC IP address, for example SNMP trap destination and sflow destination addresses. This is not covered in the document. Note: The Database Space and Data Export functions are not available on DMA when the database is installed on a remote server. Figure 1 Database Space Figure 2 Data Export In this example, the new environment has IMC installed on the main server and the database is installed on a remote server. The steps to restore the database are the same if using a local database in the new environment. In the old environment, IMC and the database may be on the same server or a remote server. In both environments: IMC must be the same version and the database must be the same type, that is, both environments must be installed either with Microsoft SQL or MySQL. Database restore to a different database type is not supported. The database and OS variants may be different (Standard or Enterprise). The database can be the same or a newer version. Please check compatibility of different database versions with the vendor s documentation. 1

4 Procedure Back up the IMC database on the old server 1. Delete file $imc\dbman\etc\unba.skip. DBman does not support backing up database unba_slave. You can move the file away from the IMC installation directory. Figure 3 Deleting unba.skip file 2. Launch the Intelligent Deployment Monitoring Agent, click Configure, and then select all files in Local Backup. This will back up all databases and configuration files. 2

5 Figure 4 Configure backup 3. Click Backup and select the desired folder. Figure 5 Manual database back up 3

6 4. Check that the backup is complete. Note: The database names are listed in the Configure page, for example aclm_db. There are some additional files, these are required by dbman restore operation. Figure 6 Database and configuration files backup 5. Copy the complete contents of the old backup folder, including database,.dat,.conf, and.zip files to the new IMC server. Setting up the new environment 1. Install the database on the new database server by following the IMC manual. Check the IMC readme. The database and OS versions must be supported by your IMC version. 2. Install IMC on the main server. Make sure the IMC version, installed components, and system time are the same on the new and the original servers. The OS version of the new IMC server may be more recent than the old server. Check the readme to see if it is supported by your IMC version. The new database must be the same type (vendor) as the old database. For example, it is not possible to restore a Microsoft SQL backup to an Oracle server. The database version may be different, as long as it s newer and compatible with the old version. Please consult the database manual. 3. Install DMA on the new database server. Enter the install folder of the IMC installation package. 4. Right-click the installslave.bat script, and then select Run as Administrator from the shortcut menu. 4

7 Figure 7 Executing the installation file The Address of Master page opens, as shown in Figure 8. Figure 8 Configuring the IMC server IP address 5. Enter the IP address of the IMC server, and then click OK. The Checking Database Connectivity dialog box opens, as shown in Figure 9. Figure 9 Checking Database Connectivity 5

8 License the new IMC server If the server is not licensed, after the database is restored, IMC will allow three logons to the admin account for a limited period of half an hour. This feature can be used to test the database restore before the new server is licensed. For full database access, the new IMC needs be licensed. Call HPE Support to transfer your license to the new server. Provide details of your license and the new serial number, obtained by clicking the Activate link on the login page. Restore the database From the Deployment Monitoring Agent on the new IMC server, make a full back up of the new database environment. You will use these new filenames to rename and restore the old backup. 6

9 Figure 10 New database backup files Copy all original backup files from the old server to the new IMC server. Rename each old backup file with the name of the new backup file. In this step, ensure to rename all.db files and all of the following configuration files:.dat,.dat.ok,.conf, and.zip. For example: The old backup would be renamed to the new backup. The old backup is now fully renamed. 7

10 You are now ready to restore the old backup on the new server: 1. Delete file unba.skip from the new server, as shown in Figure Open the Intelligent Deployment Monitoring Agent, click Restore, and then click Locally Restore. Figure 11 Restoring a database (1) Figure 12 Restoring database (2) 3. Select as the target database the folder of the renamed files and then all the displayed files. Although they are not shown in the dialog box for selection, all the renamed configuration files,.zip and.dat, must be in this folder or the restore will fail. Click OK. 8

11 Figure 13 Selecting all of the database 4. In the confirmation dialog box that opens, click No. Figure 14 Confirmation dialog box A message appears to show the execution results. Figure 15 Execution results 5. Start IMC and log on. 9