About the migration project model

Nondisruptive Migration User Guide

Part Number

A nondisruptive migration can be a lengthy undertaking depending on the amount of data to be moved. To assist you in this process, the HCS nondisruptive migration workflow uses a model that divides a migration project into jobs, as illustrated in the following diagram.

A migration project consists of:

  • The selected source and target storage systems
  • Port mappings that allow host I/O paths to be switched between source storage system and the target
  • External path settings that define the physical connections between the two storage systems
  • One or more jobs that divide the total number of volumes to be migrated into logical, manageable units

A migration project might consist of a few jobs that take a day each to complete, or many jobs to be run over the course of weeks. When you have designed and created a set of jobs, you execute each one using the same step-by-step procedure under the guidance of the HCS nondisruptive migration workflow. (HCS also provides tabular and graphical displays to help you keep track of the progress of individual jobs or the entire project.)

Migrating a large number of volumes is time-consuming and can affect performance. The most critical decision is how to divide the source volumes into a series of migration jobs. Depending on the complexity of your environment, this can be as simple as defining a job according to the host or organization with which the volumes are associated. Jobs are the core element of your migration planning effort.