Troubleshooting a migration job

Nondisruptive Migration User Guide

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

This topic describes the measures to take when a task fails during a migration job.

Note: After branching to an action table in step 9, be sure and return to step 10 when you are finished.
  1. On the Tasks & Alerts tab, click the link for the failed task to display the Task Details window.
  2. Identify the cause of the failure reported by the error message in the Task Information table and take the appropriate action.
  3. On the Mobility tab, select Target Storage Systems.
  4. Expand the tree, and then select the migration job corresponding to the failed task.
  5. On the Tasks tab, click the link for the failed task to display the Task Details window.
  6. Check the name of the failed subtask in the Task Status Detail table. (If the task does not have subtasks, the table does not appear.)
  7. On the Storage Systems tab, select the storage system and click Refresh Storage System.
  8. Go to the Resources tab and check the status of the volumes associated with the failed subtask. (For example, the task may have failed but the operation to change the volume status may have succeeded anyway.)
  9. Take the action(s) described for the failed step and subtask:

    Note: The action tables include Device Manager CLI commands that are abbreviated for reference and cannot be executed as shown. Click on the Example links in the tables for samples of complete commands. In addition, some commands require input that must be gathered from the GUI or other sources. See Obtaining input for Device Manager CLI commands for more information.
  10. Confirm the status using the commands in the "Check the configuration (CLI)" column of the action tables, or by using the GUI. (For example, when migrating a copy pair configuration, you can check the results on the Copy Pairs tab.)
  11. Update the status of the failed task as described in Changing the status of a failed migration job.

    Note: For a copy pair configuration migration task, you do not need to update the task status.
  12. From the Data Migration Actions menu, select the appropriate step to execute or repeat.

When a migration job fails at Step 1: Virtualize and Allocate Volumes

This topic describes the action to be taken when a task fails in Step 1 of a migration job.

Table. Actions for Virtualize and Allocate Volumes

Subtask name

Return to the previous state

Complete the task

Check the configuration (CLI)

Add LDEV ID

No action necessary.

N/A — return to previous state.

N/A

Add Host Group Number

Set External Paths

Delete the LUN path set for volume virtualization on the source storage system using the DeleteLun command.

Required parameter:

deletionoption=force

Example: DeleteLun

GetStorageArray
subtarget=LogicalUnit
lusubinfo=Path

Example: GetStorageArray.

Add Virtual ID

Delete the reserved virtual information on the target storage system using the ModifyVLDEV command.

Required parameter:

vldevoperation=unmapvid

Example: ModifyVLDEV

GetStorageArray
subtarget=VResourcePartitionUnit 
vrpusubinfo=VLDEV

Example: GetStorageArray

Virtualize Source Volumes

Delete the external volume on the target storage system using the DeleteExternalArrayGroup command.

Example: DeleteExternalArrayGroup

GetStorageArray
subtarget=ArrayGroup

Example: GetStorageArray

Allocate Target Volumes

No action necessary.

Add the host group to the target storage system port with the AddHostStorageDomain command.

Example: AddHostStorageDomain

Note: When data is being migrated from multiple storage systems and the target storage port is shared, specify a value of 88 for the hostmodeoption parameter. (This value can be specified when the hostmode parameter is set to HP).

GetStorageArray
subtarget=Port
portsubinfo=HostStorageDomain

Example: GetStorageArray

Add the WWN of the host to the host group of the target storage system port using the AddWWNForHostStorageDomain command.

Example: AddWWNForHostStorageDomain.

To check the WWN of the host:

GetHost

Example: GetHost

To check the WWN contained in the host group:

GetStorageArray
subtarget=HostStorageDomain
hsdsubinfo=WWN

Example: GetStorageArray

Cancel the allocated target volume using the DeleteLun command.

Example: DeleteLun

Allocate the target volume using the AddLun command.

Example: AddLun

GetStorageArray
subtarget=LogicalUnit
lusubinfo=Path

Examples: GetStorageArray

Add Label of Target Volume

No action necessary.

Set the label of the target volume using the AddLabel command.

Example: AddLabel

GetStorageArray
subtarget=LogicalUnit
lusubinfo=LDEV

Example: GetStorageArray

When a migration job fails at Step 2: Change Host I/O Paths

This topic describes the action to be taken when a task fails in Step 2 of a migration job.

Table. Actions for Change Host I/O Paths

Task name

Return to the previous state

Complete the task

Check the configuration (CLI)

Change Host I/O Paths

Check the error message in Task Details on the GUI, and then remove the cause of the error.

N/A

When a migration job fails at Step 3: Unallocate Source Volumes

This topic describes the action to be taken when a task fails in Step 3 of a migration job.

Table. Actions for Unallocate Source Volumes

Subtask name

Return to the previous state

Complete the task

Check the configuration (CLI)

Delete LUN Paths

Set the LUN path for the source storage system from the host using the AddLun command.

Example: AddLun

Delete the LUN path from the host to the source storage system using the DeleteLun command.

Required parameter: deletionoption=force

Example: DeleteLun

GetHost
hostname=host-name
subtarget=LogicalUnit
lusubinfo=Path
pathsubinfo=HostInfo

Example: GetHost

Change Cache Mode

Change the cache mode on the target storage system to "cache through" using the ModifyExternalArrayGroup command.

Required parameter: cachemode=through

Example: ModifyExternalArrayGroup

Change the cache mode to "write sync" on the target storage system using the ModifyExternalArrayGroup command.

Required parameter: cachemode=writesync

Example: ModifyExternalArrayGroup

GetStorageArray
subtarget=ArrayGroup

Example: GetStorageArray

When migrating a copy pair configuration fails

This topic describes the action to be taken when a task for migrating a copy pair configuration fails.

You can resume the migration operation in the GUI for each step by returning to the state before the step was executed, or by completing the step:

Note: If there is a subtask completed in a step, you cannot restart the task from the point where the step has failed. In this case, you can resume the migration in the GUI by restarting the task after returning to the state before the step was executed, or by completing the step.
Table. Actions for Prepare Target Secondary Volumes

Subtask name

Return to the previous state

Complete the step

Check the configuration (CLI)

Add LDEV ID

No action necessary.

N/A — return to previous state.

N/A

Add Host Group Number

Add Virtual ID

Delete the virtual information reserved on the target storage system using the ModifyVLDEV command.

Required parameter:

vldevoperation=unmapvid

Example: ModifyVLDEV

GetStorageArray
subtarget=VResourcePartitionUnit
vrpusubinfo=VLDEV

Example: GetStorageArray

Create Target Secondary Volumes

Delete the volume on the target storage system. (If you are using an existing volume as the secondary volume, this is not necessary.)

GetStorageArray
subtarget=LogicalUnit

Example: GetStorageArray

Update Secondary Volume Relationship Information

No action necessary.

None

Set Paths for Target Secondary Volumes

Delete the host group on the target storage system using the DeleteHostStorageDomain command.

Example: DeleteHostStorageDomain

GetStorageArray
subtarget=HostStorageDomain

Example: GetStorageArray

Add Label of Target Secondary Volume

No action necessary.

Set the label of the target volume using the AddLabel command.

Example: Addlabel

GetStorageArray
subtarget=LogicalUnit
lusubinfo=LDEV

Example: GetStorageArray

Table. Actions for Allocate Secondary Volumes

Task name

Return to the previous state

Complete the task

Check the configuration (CLI)

Allocate Secondary Volumes Step

Troubleshoot the cause according to the error message displayed, then perform the steps for resetting the backup server WWN described in Allocating target secondary volumes.

None

Table. Actions for Migrate Config Files

Subtask name

Return to the previous state

Complete the task

Check the configuration (CLI)

Migrate Config Files

Check the error message, remove the cause of the failure, and then restart the task.

N/A — return to previous state.

None

Restart the Instance of CCI to be Migrated

Table. Actions for Create ShadowImage Pairs

Task name

Return to the previous state

Complete the task

Check the configuration (CLI)

Create ShadowImage Pairs

Check the error message in Replication Manager, and then remove the cause of the failure.

None

When a migration job fails at Step 4: Nondisruptive Migration

This topic describes the action to be taken when a task fails in Step 4 of a migration job.

Table. Actions for Nondisruptive Migration

Subtask name

Return to the previous state

Complete the task

Check the configuration (CLI)

Create Volumes

Delete the volume on the target storage system. (If you are using an existing volume, this is not necessary.)

N/A — return to previous state.

GetStorageArray
subtarget=LogicalUnit

Example: GetStorageArray

Migrate Data

No action necessary.

None

Zero Page Reclaim

When a migration job fails at Step 5: Unvirtualize Source Volumes

This topic describes the action to be taken when a task fails in Step 5 of a migration job.

Table. Actions for Unvirtualize Source Volumes

Subtask name

Return to the previous state

Complete the task

Check the configuration (CLI)

Unvirtualize Source Volumes

Proceed to the state where the task is completed, because this step is to be performed after data migration is complete.

Delete the external volume on the target storage system using the DeleteExternalArrayGroup command.

Example: DeleteExternalArrayGroup

GetStorageArray
subtarget=ArrayGroup

Example: GetStorageArray

Unallocate External Paths

Delete the LUN path set for volume virtualization using the DeleteLun command.

Required parameter:

deletionoption=force

Example: DeleteLun

GetStorageArray
subtarget=LogicalUnit
lusubinfo=Path

Example: GetStorageArray

If you change the status of a task without addressing the underlying problem

If you accidentally change the data migration status by clicking Waiting for Action (Manually recover) or Completed (Manually recover) in the Manually Change Task Status dialog box, the operation cannot be resumed from the GUI. For the affected volume, follow these steps:

  1. Delete the volume from the migration job as described in Canceling a volume from a migration job.
  2. Follow the procedures described in Backing out of a migration.
  3. Create a new job (and select the same volume) as described in Creating a migration job.
  4. Start the migration over at Step 1: Virtualize and allocate volumes.