Migrating a Db2 database from a Linux x86 system to a new Linux x86 system

By restoring an existing Db2 backup image from a Linux x86 system to a new instance on another Linux x86 system, you can effectively migrate a Db2 instance. This process applies whether moving to a new on-premises server instance or to a virtual machine (VM) instance that is hosted by a cloud provider.

Before you begin

This procedure assumes that you have completed the following prerequisite tasks:
  • You have created a target instance of Db2, either on an on-premises x86 server or on a cloud-hosted x86 VM.
  • You have configured access to your Db2 instance to match that of your source system. For example, if you want to maintain user authentication by using Kerberos and you are restoring your backup image to a cloud instance, ensure that the target system supports Kerberos.

The procedure also assumes that you are restoring your backup image onto a same-version Db2 instance, such as 11.5.9 to 11.5.9. You can upgrade your restored Db2 instance whether it resides on an on-premises system or a cloud server instance. For more information, see Upgrade essentials for Db2 servers.

When moving a Db2 database instance to a cloud instance, if you work with large object (LOB) data consider reconfiguring any table spaces and buffer pools that you use.
  • Separate LOB objects into a separate table space that is configured with file system caching enabled. This configuration improves the performance of insert operations with LOB data to your cloud instance.
  • Select storage devices based on the required input/output operations per second (IOPS) rating.
  • Place indexes into a separate buffer pool to ensure the pages stay in memory longer.
  • Place highly active tables into separate table spaces, with separate buffer pools.
  • Place interdependent tables in the same table space so they can be recovered as a group. Db2 native backup and recovery granularity is at the table space level.
  • Eliminate the use of SMS/DMS containers and move to Automatic Storage

About this task

There are several advantages to using the Db2 backup and restore commands to migrate a Db2 instance:
  • The data is moved at the physical level, so no decryption of data is required.
  • Many users are familiar with the backup and restore process.
  • Because the backup and restore feature is part of Db2, there is no additional licensing cost.
  • You do not have to restore a backup of the most current version of Db2 at the target. This is particularly appealing for users that are planning a move to the cloud but don't want to go through an upgrade as well. You just need to ensure that the cloud provider has a virtual server that can run your older version of Db2. If you choose to upgrade your moved Db2 instance at a later date, it can all be done on the cloud provider side.

Procedure

To migrate a Db2 database by using the BACKUP and RESTORE commands, see Backing up data and Using restore.