Migrating online data with Configuration Manager

Ops Center Automator Non-disruptive Migration Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99AUT004-03

Setting up online migration consists of several steps. However, many of the steps are now automated when you use the Ops Center Automator Create Online Migration Pair, Migrate Data for Online Migration Pair, and Clean up Online Migration Pair services.



The following procedure provides the steps required to set up and migrate online data when using the service.

  1. If GAD is not set up, complete the steps in Setting up global-active device.
  2. Verify the setup prerequisites and required software listed in Online Migration with Configuration Manager service templates prerequisites and if you are planning on migrating to multiple hosts, Additional prerequisites for multiple runs. The setup prerequisites consist of creating various Ops Center Automator resources as well as setting secure communications between the Ops Center Administrator server and the Ops Center Automator server.
  3. Complete the following resource setup steps using either Command Control Interface (CCI) or Storage Navigator.
    For more information, see the Command Control Interface Command Reference.
    1. Register resources to the VSM.
    2. If you want to specify the source resource as Volumes, identify the volume to migrate.
    3. Delete any replication pairs in the source migration source volume.
      If a local/remote pair is set in the migration source volume, the GAD pair is not created.
  4. In Ops Center Automator, verify that the following web service connections exist. If not, create them as needed.
    Note: If you plan to set up secure communication between Ops Center Automator and any of the following servers, you must do so before you create the web service connection. For additional information, see "Importing certificates for web service connections" in the Hitachi Ops Center Automator Installation and Configuration Guide.
    • Web service connection to the Ops Center Administrator server where the migration source host is registered.
    • (Optionally) Web service connection to the Brocade Network Advisor (BNA) or Data Center Network Manager (DCNM) server.

    You complete this step one time and do not need to repeat it in the future.

    For more information, see Configuring Web Service Connections.

  5. In Ops Center Automator, complete the following steps:
    1. On the Services tab, select the Create Online Migration Pair service, and in the service preview pane, click Create Request.
    2. Configure the Create Online Migration Pair service by entering the required information. For more information on the required parameter settings, see Create Online Migration Pair: Service details.
      The configuration information you enter enables the service to complete the required tasks when you submit the Create Online Migration Pair service.
    3. Submit the service.
    The service completes the following actions:
    • Creates the zone information between the target storage and the host.
    • Allocates a path on the target volume that matches the path on the source volume.
    • Creates a diskless Quorum for use with Global-Active Device. Acquire and creates a free Quorum ID common to the source storage system and target storage system. If you want to enable the Use Diskless Quorum option, see Create Online Migration Pair: Service details.
    • Creates a Global-Active Device pair with Ops Center API Configuration Manager.
    • Reclaims zero pages of Global-Active Device S-Vol if the Run Zero Page Reclaim property is selected.

      After finishing the previous actions, the service pauses and waits for you to manually verify that you have completed the above tasks.

    Note: If you specify the same Source Storage and Target Storage in the Create Online Migration Pair service and submit multiple tasks at the same time, the tasks might fail. In this case, check the pair status of the specified Source Volume. If the Global-Active Device pair was created, run Clean up Online Migration Pair, and then resubmit the task.
  6. Switch the path from the source volume to the target volume so that the host recognizes the target volume path using one of the following methods.
    • Log in to the host and use the multipath management software to switch the path.
    • If the host is in a cluster configuration, use the cluster management software to change the settings.
  7. Return to the Ops Center Automator UI and do one of the following:
    • To resubmit the Create Online Migration Pair task if it failed or to cancel the migration, you must submit the Clean up Online Migration Pair service to delete the resources created in the target storage system. See Clean up Online Migration Pair: Service details for more information.
    • If the Create Online Migration Pair task completes successfully, you can submit the Migrate Data for Online Migration Pair service.
  8. In Ops Center Automator, complete the following steps:
    1. On the Services tab, select the Migrate Data for Online Migration Pair service, and in the service preview pane, click Create Request.
    2. Configure the Migrate Data for Online Migration Pair service by entering the required information. For more information on the required parameter settings, see Migrate Data for Online Migration Pair: Service details.
      The configuration information you enter enables the service to complete the required tasks when you submit the Migrate Data for Online Migration Pair service.
    3. Submit the service.
    The task starts running and with the following automated actions:
    • Deletes the Global-Active Device pair with Ops Center API Configuration Manager.
    • Unallocates the source volume and path with Ops Center API Configuration Manager.
    • Deletes the diskless Quorum if you are using diskless Quorum.
    • (Optionally) Deletes the source volume and the unnecessary Host Group using Ops Center API Configuration Manager.
      Note: Do not select this option during template configuration if you want to return to the original status if the migration fails.