Planning data migration

The planning and methods of data migration for the DS6000™ vary by environment. The DS6000 supports over 90 operating systems. You can migrate data to a storage unit from these host and operating system environments.

When you plan for data migration, consider the following factors:

Note: The following lists do not cover every possibility. They provide a high-level view of some of the tools and factors that you can consider when moving data.

The system:
- Is it a z/Series or UNIX-based system? You might use IBM System Storage Remote Mirror and Copy functions such as Metro Mirror and Global Mirror or some variation of a logical volume manager.
- Is it z/OS? You will probably use DFDSS, though there are many choices.
- Is it VM? You might use DASD Dump Restore or PTAPE.
- Is it VSE? You might use the VSE fastcopy or ditto commands.
Your system administrator selects the data migration method that is the best compromise between efficiency and impact on the users of the system.
The storage unit:
- Are the storage units involved the same with the same level of licensed management code?
- Are the storage units different? In which case you want to ensure that the new configuration is large enough to accommodate the existing data. You also want to ensure that the virtual disks are similar in configuration to the disk drives that they are replacing.
Time and complexity involved:
- Typically data migration requires that updates or changes cease while the movement occurs. Also, depending on the amount of data that you are moving and your migrating method, data could be unavailable for an extended period of time, perhaps several hours.
- Could the complexity and time involved require the services of IBM through International Global Services? Contact your IBM representative for more information.