IBM Support

Using network attached tape or optical devices with Migrate While Active

News


Abstract

Details on how to use network attached tape or optical devices with Migrate While Active.

Content

Db2 Mirror
Using network attached tape or optical devices with Migrate While Active
 

Migrate While Active supports saving to and restoring from a list of user specified tape devices or the name of an optical device. If these devices are network attached, use the guidance on this page to aid you in configuring and preparing those devices for use by Migrate While Active during the migration process.

During the configuration of Migrate While Active, you can provide the list of up to 32 tape devices or the name of an optical device. Per device name, you can specify up to 75 volume names. If more than one device is specified, the save will be done in serial-parallel format using a media definition. If you are using a tape media library device for the serial-parallel save, you can add the same tape media library device name multiple times, up to the number of available device resources within the tape media library device. You must verify that all of the tape devices and tape media library device resources are available to be used before adding them to the list.

Saving the source node
 

During the migration, you will be instructed to put the source node into restricted state before the system save. After putting the source node into restricted state, you will need to start TCP/IP and an interface so the network attached devices are useable while in restricted state. Use the following CL commands to do this.

  • STRTCP STRSVR(*NO) STRIFC(*NO) STRPTPPRF(*NO) STRIP6(*NO)
  • STRTCPIFC INTNETADR('x.x.x.x')

The device(s) you want Migrate While Active to use during the system save must be varied on and usable before calling the Work with Migration Status (WRKMIGSTS) CL command and selecting option 1 to start the automated save of the source node.


Back to top

Restoring the copy node
 

After the install of the operating system on the copy node completes, the copy node remains in restricted state. All network configuration settings and device descriptions from the source node were restored during the install. In order to access your network attached devices, you will need to create and start a TCP/IP interface. You also might need to correct the device descriptions of your tape or optical devices to point at the correct resource names.

The device(s) you want Migrate While Active to use during the restore must be varied on and usable before calling the Work with Migration Status (WRKMIGSTS) CL command and selecting option 10 to start the automated restore on the copy node.

First, use the following CL commands and menus to clear TCP/IP config on the copy node.

  • CFGTCP
    • From the Configure TCP/IP menu, select option 1 (Work with TCP/IP interfaces). Type option 4 (Remove) next to all interfaces except *LOOPBACK and press Enter. Press Enter again to confirm your choices for removal. Press F12 to return to the Configure TCP/IP menu.
    • From the Configure TCP/IP menu, select option 2 (Work with TCP/IP routes). Type option 4 (Remove) next to all routes and press Enter. Press Enter again to confirm your choices for removal. Press F12 to return to the Configure TCP/IP menu.
  • WRKLIND
    • Type option 4 (Delete) next to all line descriptions and press Enter. Press Enter again to confirm your choices for deletion.

Next, use the following CL commands to create and start a single IP address on the copy node.

  • CRTLINETH LIND(<lind>) RSRCNAME(CMNxx)
  • ADDTCPIFC INTNETADR('x.x.x.x') LIND(<lind>) SUBNETMASK('x.x.x.x')
  • ADDTCPRTE RTEDEST(*DFTROUTE) SUBNETMASK(*NONE) NEXTHOP('x.x.x.x') BINDIFC(*NONE)
  • STRTCP STRSVR(*NO) STRIFC(*NO) STRPTPPRF(*NO) STRIP6(*NO)
  • STRTCPIFC INTNETADR('x.x.x.x')

If using a virtual tape library (VTL), use the following CL commands to run SQL statements to configure it. Additional information about iSCSI VTL and the SQL statements used to configure can be found here: IBM i Removable Media: Support for iSCSI VTL.

  • RUNSQL SQL('CALL QSYS2.ADD_ISCSI_TARGET(
                   TARGET_NAME      => ''iqn.2000-03.com.swvtl:vtl.vtltest.test-47'',
                   TARGET_HOST_NAME => ''vtltest.aaa.demo.aaa.com'',
                   TARGET_PORT      => 3260,
                   INITIATOR_CHAP_NAME   => ''username'',
                   INITIATOR_CHAP_SECRET => ''ChapSecretPW'')') NAMING(*SQL)
  • RUNSQL SQL('CALL QSYS2.CHANGE_IOP(IOP=>''ISCSI'', OPTION=>''IPL'')') NAMING(*SQL)

Then, use one of the following CL commands to change your device descriptions to point to the correct resources.

  • CHGDEVMLB DEVD(TAPMLBxx) RSRCNAME(MLByy)
  • CHGDEVTAP DEVD(TAPxx) RSRCNAME(TAPyy)
  • CHGDEVOPT DEVD(OPTxx) RSRCNAME(OPTyy)

Finally, vary on the devices using the following CL command.

  • VRYCFG CFGOBJ(xxxxx) CFGTYPE(*DEV) STATUS(*ON)


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;7.5.0;7.6.0"}]

Document Information

Modified date:
22 September 2025

UID

ibm17178562

Page Feedback