Stopping data migration

Virtual Storage Platform One SDS Cloud for Microsoft Azure Data Migration
Version
1.18.x
Audience
anonymous
Part Number
MK-24VSP1SDS032-02

After reviewing the operation method and so on, you can stop data migration as necessary by doing the following.

  • Required role: Service and Storage

  1. Stop I/O from the migration destination server to the virtual volumes.
  2. Forcibly stop copying the data to the initiator node.

    Detach the migration-target Azure managed disks from the Azure Virtual Machines of the initiator node by using the Azure portal.

    CAUTION:

    • If you detach the all migration-target Azure managed disks from the initiator node (Azure VM instance), data copying will result in an error and data copy will be forcibly stopped. In this case, an event log with messageId = KARS06367-E might be output. This is not a problem.

    • If the migration-target Azure managed disks cannot be detached, detach all the other migration-target Azure managed disks that can be removed. After confirming that all copy processing is stopped, perform maintenance blocking for the initiator node, and then detach the migration-target Azure managed disks (that could not be detached) while the instance is stopped. Then, perform maintenance recovery for the initiator node and go to step 4. For details about the maintenance procedures for the initiator node, .

  3. Verify the progress of data copy to see if all copying operations are stopped (no external volumes whose status is "Copying" exist).

    REST API: GET /v1/objects/external-volumes

  4. Use migrated volumes in the migration destination server and VSP One SDS Block. You can verify the volumes which have been migrated before migration stop as follows:
    1. See the list of event logs to verify whether event log KARS06307-I is output.

      When event log KARS06307-I is output, migrated volumes are displayed with their volume IDs indicated in the message.

      If event log KARS06307-I is not output, no volume has been migrated. In this case, go to step 5.

    2. Confirm the details about the migrated volumes.

      See Obtaining information about individual volumes in the VSP One SDS Block and SDS Cloud System Administration to obtain volume information with the obtained volume IDs.

    Note:

    To identity the migrated Azure managed disk, verify the nick name of the migrated volume. For the Azure managed disk whose disk name matches the obtained nick name, migration has been completed.

    The maximum number of characters for nickname is 64. If the number of characters for an Azure managed disk name exceeds 64, the ID and disk name of the migrated volume are output in the event log (KARS06307-I) as an external volume serial number. Identify the migrated Azure managed disk by referencing the output contents.

  5. Cancel allocation of the virtual volume to the migration destination server.

    See Canceling allocation of volumes to compute nodes (Cloud) in the VSP One SDS Block and SDS Cloud System Administration.

  6. Delete path information about the migration destination server.

    See Deleting path information about compute nodes (Cloud) in the VSP One SDS Block and SDS Cloud System Administration.

  7. Delete initiator information about the migration destination server.

    See Deleting information about the initiators for compute nodes in the VSP One SDS Block and SDS Cloud System Administration.

  8. Delete information about the migration destination server.

    See Deleting information about individual compute nodes in the VSP One SDS Block and SDS Cloud System Administration.

  9. Verify the ID of the initiator node.

    REST API: GET /v1/objects/storage-nodes

    CLI: storage_node_list

  10. Delete the external volumes and virtual volumes.

    Run the following command with the ID of the initiator node specified.

    REST API: POST /v1/objects/storage-nodes/<id>/actions/refresh-external-volumes/invoke

    Verify the job ID which is displayed after the command is run.

  11. Approximately 20 seconds later, verify that the external volumes and virtual volumes are created.

    Verify that the external volumes to be migrated and virtual volumes are no longer displayed (see Obtaining a list of external volume information).

    CAUTION:

    If the migration target external volume and virtual volume are displayed in step 11, collect a dump log and contact a support center. See Contact customer support for details.

  12. Verify the state of the job.

    Run either of the following commands with the job ID specified.

    REST API: GET /v1/objects/jobs/<jobId>

    CLI: job_show

    After running the command, if you receive a response indicating "Succeeded" as the state, the job is completed.

  13. Remove the initiator node.

    Do so according to Removing initiator nodes.

    Note:

    If you stop once and then resume data migration, perform the operation from step 1 of Confirming the capacity and number of migration-target Azure managed disks.