Prepare for the migration from a 4 xx or 5 xx server

If you cannot install V5R4 of i5/OS™ on your source iSeries™ server, you can still migrate your data by saving your source server and then performing a full server recovery onto the target server. This topic describes how to prepare to migrate your data from a 4 xx or 5 xx server to the new target server.

Before you begin this procedure, be sure you have completed these prerequisite tasks:

Then, to prepare to migrate your data from a 4 xx or 5 xx server, perform these tasks:

Related concepts
Preventive service planning (PSP) information
Plan the migration
Console
Scenarios: Data migration
Related tasks
Perform the migration
Create logical partitions
Clean up disk storage space
Ensure you have required fixes (program temporary fixes or PTFs)
Collect performance data
Print a new system configuration list
Print the system configuration for logical partitions
Save spooled files
Complete the migration from a 4 xx or 5 xx server
Related reference
GO SAVE
Related information
Backup and Recovery Guide

Prepare target server

  1. Verify that the target server is set up and is running with only the Licensed Internal Code and the operating system (i5/OS) installed (feature code 0205).
  2. If you are configuring a server with logical partitions, you must create logical partitions on the target server and then install the Licensed Internal Code and i5/OS on each secondary partition. Allow at least two additional hours to do this for each partition.
  3. Ensure that your console is set up and ready.
    Note: If you are using a twinaxial console on the source server and using Operations Console on the target server, ensure that you have a twinaxial controller for any twinaxial devices you plan to run from the target server.
  4. Perform disk unit management (for example, manage disk protection and disk configuration). To do this, you can use the Work with Disk Units option from the Dedicated Service Tools display. For information, see the chapter that contains Procedures for configuring disks and disk protection in the Backup and Recovery Guide.
  5. Make sure that you have a copy of the distribution media for the target server.

Prepare source server

  1. Clean up the source server as follows:
    1. Use the Work with Line Descriptions command (WRKLIND) to view and delete unused lines and line descriptions.
    2. Use the Work with Device Descriptions command (WRKDEVD) to delete unused device descriptions.
      Note: You can use the Work with Line Descriptions and Work with Device Descriptions commands to view and verify that all of the descriptions listed are in use. If you are sure one is not in use, delete it. If you are not sure, you should leave it.
    3. Clean up disk storage space.
  2. Ensure you have required fixes (program temporary fixes or PTFs).
  3. Collect performance data.

    This gives you a basis for comparing performance before and after the data migration.

  4. On the i5/OS command line, enter RTVSYSINF.

    When you run this command, you will need to specify the library to use. Typically, you should specify the QUPGRADE library. If this library does not exist, create it with the Create Library (CRTLIB) command.

  5. Print your server configuration information as follows:
    1. On the i5/OS command line, enter PRTSYSINF and then print the resulting spooled file. This prints reports of the hardware resources, software resources, system values, installed fixes (program temporary fixes or PTFs), and other configuration information.
    2. Print a new system configuration list and keep this list for future reference.
    3. On the i5/OS command line, enter WRKDEVD. Use option 6 (Print) to print the device descriptions.
    4. On the i5/OS command line, enter WRKCTLD. Use option 6 (Print) to print the controller descriptions.
    5. If you have a partitioned server, print the system configuration for logical partitions.
    6. If necessary, save spooled files.

      For more information, see Save spooled files in the Information Center.

    7. Job scheduler entries will not be restored on the target server. Use the print option on the Work with Job Scheduler Entries (WRKJOBSCDE) command to record your current job scheduler entries so you can manually re-create them on the target server.
  6. Save the entire server using option 21 of the GO SAVE command. Make sure that you specify the following options:
    1. Vary off the network server...*ALL
    2. Unmount file systems..........Y
      Note: It is recommended that you have two copies of the backup media.

The next step is to Complete the migration from a 4 xx or 5 xx server.