Migrating configuration definition files

Nondisruptive Migration User Guide

Version
9.6.0
Audience
anonymous
Part Number
MK-92RD8086-11

For the migration job, selected configuration definition files can be migrated for use on the target storage system.

  • Source volumes must be unallocated.
  • Target secondary volumes must be allocated.
  1. On the Mobility tab, select Migration Projects.
  2. Expand the tree for a source storage system, and select a migration job.
  3. On the Copy Pair Configuration Migration Workflow tab, click Migrate Config Files.
  4. Click Add/Remove Config Files.
    Note: The configuration definition file to be migrated must be specified in HORCM_LDEV format. Files in which HORCM_LDEVG is defined cannot be migrated and does not appear in the list.
  5. Click Add and Remove to populate the list of configuration definition files to be migrated, and then click OK.
  6. (Optional) Update the task name and provide a description.
  7. (Optional) Expand Schedule to specify the task schedule.
    You can schedule the task to run immediately or later. The default setting is Now. If the task is scheduled to run immediately, you can select View task status to monitor the task after it is submitted.
  8. Click Submit.
    If the task is scheduled to run immediately, the process begins.
  9. Confirm this task is Completed for the migration job.
Configuration definition files are migrated for use on the target storage system. HORCM instances for the migrated configuration definition files are restarted. If a HORCM instance is running on the source storage system, the configuration definition file is migrated to the target storage system.