IBM manual OS/400 data migration, Figure B-35 Using Metro Mirror to migrate from ESS to DS8000

Note: It is important to ensure that both the Metro Mirror or Global Copy source and target copies are not assigned to the iSeries at the same time as this is an invalid configuration. Careful planning and implementation is required to ensure this does not happen, otherwise unpredictable results may occur.

M

e

t r

o

M

i r

r

o

r

Figure B-35 Using Metro Mirror to migrate from ESS to DS8000

The same setup can also be used if the ESS LUNs are in an IASP, although the iSeries would not require a complete shutdown since varying off the IASP in the ESS, unassigning the ESS LUNs, assigning the DS8000 LUNs and varying on the IASP would have the same effect.

Clearly, you must also take into account the licensing implications for Metro Mirror and Global Copy.

Note: This is a special case of using Metro Mirror or Global Copy and will only work if the same iSeries is used, along with the LSU to attach to both the original ESS and the new DS8000. It is not possible to use this technique to a different iSeries.

OS/400 data migration

It is also possible to use native OS/400 functions to migrate data from existing disks to the DS8000, whether the existing disks are internal or external. When you assign the new DS8000 logical volumes to the iSeries, initially they are non-configured (see “Adding volumes to iSeries configuration” on page 376 for more details). If you add the new units and choose to spread data, OS/400 will automatically migrate data from the existing disks onto the new logical units.

You can then use the OS/400 command STRASPBAL TYPE(*ENDALC) to mark the units to be removed from the configuration as shown in Figure B-36 on page 402. This can reduce the

Appendix B. Using DS8000 with iSeries 401