Migrating data from an eServer i5 400 or iSeries host system to the DS6000

Use the following information as a guide to determine how to migrate data from an IBM eServer i5 or iSeries host system to the DS6000™.

When you create the eServer i5 or iSeries volume, you can create it as a protected or unprotected volume. This creation enables you to see the protected and unprotected models. Unprotected models can be software mirrored.

DS6000 supports 2107 device types with model A81-A87 (unprotected) and A01-A07 (protected) and you need a level of i5/OS or OS/400 that supports these. The model numbers correspond to 8.56 GB (A01/A81), 17.54 GB (A02/A82), 35.16 GB (A05/A85), 36 GB (A03/A83), 70.56 GB (A84/A04),141.12GB (A86/A06), and 282.25 GB (A87/A07).

IBM eServer i5 or iSeries hosts require a separate device address for each drive in the subsystem. The DS6000 meets this requirement by reporting unique addresses for each virtual drive that is defined to the eServer i5 or iSeries host. Up to a maximum of 32 LUNS per iSeries fibre-channel adapter are supported by the DS6000. If the multipathing option (only available on i5/OS, V5R3 and above) is selected, then a maximum of 16 LUNs per adapter is recommended.

Because the eServer i5 or iSeries host does not support 7133 drawers, you have no existing 7133 drawers to reformat. If you have an existing disk subsystem that you are replacing with a DS6000, you must migrate the data to the DS6000. Use your existing host utilities for the data migration.

You can select from several methods to migrate data to the DS6000:

You can use the logical add and remove functions.
You can use save methods and restore methods with tape devices.

You can also use these methods if you remove an existing disk subsystem before you install the DS6000.

Note: From a DS6000 logical configuration viewpoint, all iSeries volumes are RAID 5 and are protected. When you create the iSeries volume, you can create it as a protected or unprotected volume. This creation enables you to see the protected and unprotected models. Unprotected models can be software mirrored.