Database migration

Edit online

Detailed procedure for migrating databases from legacy Identity Manager system to IBM Verify Identity Governance - Container.

Database migration

IBM Verify Identity Governance - Container supports data migration from legacy Identity Manager system.
Important: As a part of the migration process, it is important to note that the IBM Verify Identity Governance - Container currently only supports IBM DB2 and PostgreSQL databases.
CAUTION:
IBM Verify Identity Governance - Container supports TLS v1.2 and TLS v1.3. If you plan to use TLS v1.3, ensure that your external components (such as external LDAP, external PostgreSQL database, etc.) are also configured to use TLS v1.3. Note that IBM Verify Identity Governance - Container currently does not work with IBM DB2 database configured with TLS v1.3.
DB2 Universal Database migration

Use these steps to migrate DB2 Universal Database data to a version that IBM Verify Identity Governance - Container supports.

Determine the type of target DB2 database to use: If containerized DB2 is chosen and existing database is on Linux, then use DB2 “Click to Containerize” utility to move an existing DB2 database from Linux to a containerized environment with minimal effort. See this topic.

If On-Premise DB2 is chosen, then follow the instructions from Backup and Restore sections.

Backing up DB2 Universal Database data: DB2 Universal Database provides backup and restore commands. Use these commands to move data. Before you begin, ensure that the free disk space and virtual memory requirements are met. Additionally, ensure that adequate free disk space exists in the system temp directory. The target system must meet the hardware and software requirements for the IBM Verify Identity Governance - Container.

Ensure that you have the needed administrative authority.

Procedure:
  1. Close all connections to the Identity Manager database.
  2. To back up the Identity Manager database, see this documentation.

Next step is to install the new version of DB2 Universal Database.

Installing DB2 Universal Database and copying data to the target server environment

After you back up your data, use this task to update to the required level of DB2 database.

Before you begin, ensure that you have the needed administrative authority.

Procedure:
  1. On the target database server, ensure that the supported version of DB2 Universal Database is installed and working. This operation is a migration, ensure that you create the same database system user, for example, enrole. The user must have the same rights and privileges it had on the old system.
  2. Create the DB2 instance.
  3. Copy the contents of the Identity Manager database backup directory to the target server. For example: /data/db2. Ensure that the database instance owner you create has permission to read the target directory and sub files.
  4. To restore the Identity Manager database, see this documentation topic.
  5. Restart the DB2 server to reset the configuration.
If the db2stop command fails and the database remains active, enter the following commands:
  • force application all : This command deactivates the database.
  • db2start

Next step

After completing this step, proceed to the directory server migration.

[Optional]: You may also tune the database for optimal performance by applying the latest tuning settings. For more information, see the Performance tuning topic.