IBM Support

Copy node software and storage requirements for partition mirroring

News


Abstract

Follow these procedures to set up the copy node before an IBM i Migrate While Active migration that uses the partition mirroring method.

Content

Db2 Mirror

Copy Node - Technology Refresh Requirements
 
Migrating using partition mirroring requires a minimum level of licensed internal code (LIC) be installed on the copy node before beginning a migration. The source and copy node must be installed with matching levels of LIC.
 
The following table describes the minimum IBM i Technology Refresh (TR) level required to use the partition mirroring method of migration for each supported release. A Technology Refresh can be downloaded and installed using standard procedures and tools.

IBM i 7.6IBM i 7.5IBM i 7.4
Not yet supportedTR7TR12


Methods for installing LIC on the copy node
 
For additional information about installing LIC on a new logical partition, see Installing Licensed Internal Code on a new logical partition.
 
Some options for installing LIC on the copy node before beginning a migration using partition mirroring include:

  • Use a recent SAVSYS or full system save of the source node
     
    Tip:  Install the latest Db2 Mirror PTF group and all recommended fixes for the copy node (table below) on the source node before the save. Then follow the instructions for installing LIC on a new logical partition.
  • Download and use an IBM provided image that meets the minimum requirements.
     
    Tip:  Download the latest IBM i TR resave and then follow the instructions for installing LIC on a new logical partition. Then apply all recommended fixes for the copy node (table below).
  • Use a preinstalled version of LIC (manufacturing preinstall or cloud image deploy) that meets the minimum requirements.
     
    Tip:  Verify the required TR level and all recommended fixes for the copy node (table below) are installed.


NOTE:  A LIC only install is acceptable, meaning that you are not required to install the full IBM i operating system on the copy node. However, if the image used to install the copy node does not contain the recommended fixes for the copy node (table below), then you must install the full IBM i operating system so you can then apply the recommended fixes.


Back to top

Copy Node - Recommended Fixes 
 
The fixes in the table below should be applied on both the copy node and the source node before beginning a migration using partition mirroring. 

External Availability Known IssuesIBM i 7.6
Fix Info		IBM i 7.5
Fix Info		IBM i 7.4
Fix Info
7/11/2025DT444768MJ06502MJ06500MJ06479
7/15/2025DT444167N/AN/AMJ06430
7/17/2025DT446107N/AN/AMJ06529
7/18/2025DT444213N/AN/AMJ06435
8/12/2025DT445921N/AN/AMJ06561
8/12/2025DT447191N/AN/AMJ06722
8/12/2025DT447894N/AN/AMJ06777
10/22/2025DT453719MJ07745MJ07738MJ07677
10/27/2025DT446029N/AN/AMJ06527
10/27/2025DT450687N/AMJ07195MJ07194
10/27/2025DT452480N/AMJ07474MJ07473
10/27/2025DT452563N/AMJ07475MJ07476
11/07/2025DT452737N/AMJ07551MJ07604
12/05/2025DT455897N/AMJ08090MJ08091


Back to top

Copy Node - Storage Requirements

The storage capacity assigned to SYSBAS on the copy node must be equal to or greater than the amount of allocated (used) storage of SYSBAS on the source node. The individual disk unit sizes and types do not need to match. The number of disk units does not need to match.

If the source node has one or more user auxiliary storage pools (ASPs), then you must configure the same user ASPs (2-32) on the copy node before starting partition mirroring. Partition mirroring replicates SYSBAS and all basic user ASPs together.

If the full IBM i operating system is installed on the copy node, you can use Navigator for i to configure disk units on the copy node. Follow the instructions here: Adding a disk unit or disk pool.

If only LIC is installed on the copy node, you must use Dedicated Service Tools (DST) to configure disk units on the copy node. Follow the instructions here: Adding disk units to an existing auxiliary storage pool.


Back to top

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0;7.5.0;7.6.0;and future releases"},{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSIEMH6","label":"IBM i Migrate While Active"},"ARM Category":[{"code":"a8m0z0000001hExAAI","label":"DB2 Mirror"},{"code":"a8m0z0000000C4BAAU","label":"IBM i"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.4.0"}]

Document Information

Modified date:
18 December 2025

UID

ibm17236013

Page Feedback