Online Migration with Configuration Manager service templates prerequisites

Ops Center Automator Non-disruptive Migration Guide
Version
11.0.x
Audience
anonymous
Part Number
MK-99AUT004-03

Create Online Migration Pair

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • When integrating with Cisco FC switches:

    Data Center Network Manager (DCNM) 7.1, 11.5

  • When integrating with Brocade FC switches:

    Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

  • Ops Center Administrator v10.1.0-00 or later

Setup prerequisites

  • At least one remote path using FC or iSCSI has been defined for the storage systems of the migration source and the migration target used in this service.
  • The path group, including the previous remote path, has been set up.
  • A pool has been created in the migration target storage system.
  • A VSM in the migration target storage system has been duplicated from the VSM (resource group) in the migration source volume.
  • At least one Configuration Manager server has been added to Web Service Connection.
  • The storage systems registered in Configuration Manager have the same credentials.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
    • Storage Administrator (Initial Configuration)
  • The migration source volumes must not have any remote copy pairs configured.
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
  • For user-defined roles, a role with both of the following permissions is required:
    • Fabric=O(Observe) or OM(Observe and Modify)
    • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • For DCNM, verify that the registered user is assigned the network-admin role.

If you want to run multiple tasks concurrently, see Additional prerequisites for multiple runs.

Create Online Migration Pair for Multiple Hosts

Software prequisites

  • Ops Center API Configuration Manager v10.7.0-00 or later
  • When integrating with Cisco FC switches:

    Data Center Network Manager (DCNM) 7.1, 11.5

  • When integrating with Brocade FC switches:

    Fabric OS (FOS) 8.2.2d, 8.2.3a, 8.2.3c1, 9.0.1b, 9.0.1e1, 9.1.0b

  • Ops Center Administrator v10.7.0-00 or later

Setup prerequisites

  • The Create Online Migration Pairs for Multiple Hosts must be the same version (VV.RR) as the Create Online Migration Pair service.
  • When multiple hosts are selected, they must not have the same volume allocated to them.
  • At least one remote path using FC or iSCSI has been defined for the storage systems of the migration source and the migration target used in this service.
  • The path group, including the previous remote path, has been set up.
  • A pool has been created in the migration target storage system.
  • A VSM in the migration target storage system has been duplicated from the VSM (resource group) in the migration source volume.
  • At least one Configuration Manager server has been added to Web Service Connection.
  • The storage systems registered in Configuration Manager have the same credentials.
  • Verify that the common credentials used to access all storage systems are assigned the following roles:
    • Security Administrator (View & Modify)
    • Storage Administrator (Provisioning)
    • Storage Administrator (Remote Copy)
    • Storage Administrator (Initial Configuration)
  • The migration source volumes must not have any remote copy pairs configured.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • The migration source volumes must not have any remote copy pairs configured.
  • Create a web service connection for DCNM or FOS.
  • For FOS, the user ID cannot be a user using RADIUS/LDAP access authentication.
  • For FOS, verify the following:
    • FOS REST API is enabled.
    • Fabric name is set.
    • Ops Center Automator and FC switches are in the same LAN.
    • Ops Center Automator and FC switches are not connected via a proxy.
  • For FOS, verify that the registered user is assigned the following roles:
    • For the default Fabric OS roles one of the following roles is required:
      • Admin
      • FabricAdmin
      • ZoneAdmin
    • For user-defined roles, a role with both of the following permissions is required:
      • Fabric=O(Observe) or OM(Observe and Modify)
      • Zoning=OM(Observe and Modify)
  • For Brocade FC switches with VirtualFabric feature enabled, the Virtual Fabric ID of the fabric to be operated is included in the Role-LF List for the user ID.
  • For DCNM, verify that the registered user is assigned the network-admin role.
  • If you already have Ops Center Administrator installed, you must import the Ops Center Administrator server certificate in the Ops Center Automator truststore, to use the host selection feature.
  • If you enable the Use Diskless Quorum option, an unused common Quorum ID must exist for both the source and target.
  • If you do not enable the Use Diskless Quorum option, you must create a Quorum disk to be used with global-active device.

If you want to run multiple tasks concurrently, see Additional prerequisites for multiple runs.

Migrate Data for Online Migration Pair

Software prerequisites

Setup prerequisites

  • Submit the service as a user with the same permissions as the user who submitted the Create Online Migration Pair service.
  • The target storage systems scheduled for migration must be registered in the same API Configuration Manager that was used when running the Create Online Migration Pair service and the API Configuration Manager must be registered in Web Service Connections.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • After the Create Online Migration Pair task that you select in the Edit/Submit Service window completes, you cannot make any changes to the configuration of the target resources before running the task.
  • The migration source volumes must not have any remote copy pairs configured.

If you want to run multiple tasks concurrently, see Additional prerequisites for multiple runs.

Clean up Online Migration Pair

Software prequisites

Ops Center API Configuration Manager v10.7.0-00 or later
Ops Center API Configuration Manager v10.7.0-00 or later

Setup prerequisites

  • Submit the service as a user with the same permissions as the user who submitted the Create Online Migration Pair service.
  • The target storage systems scheduled for cleanup must be registered in the same API Configuration Manager that was used when running the Create Online Migration Pair service and the API Configuration Manager must be registered in Web Service Connections.
  • Each source/target storage system must not be registered in more than one Configuration Manager.
  • The ports used by Configuration Manager for communications between the primary and secondary sites must be open when a remote copy is performed. For details, see "Ports used during remote copy operations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
  • If you want to clean up a failed task due to an error instead of the task that was completed, remove the cause of the error and then submit the service.
  • After the Create Online Migration Pair task that you select in the Edit/Submit Service window completes or fails, you cannot make any changes to the configuration of the target resources before running the task.

    If you want to run multiple tasks concurrently, see Additional prerequisites for multiple runs.