System requirements

Nondisruptive Migration User Guide

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

The following tables list the hardware, software, and configuration requirements for nondisruptive migration.

Table. Hardware requirements

Source storage systems

Target storage systems

Model

Microcode

Model

Microcode

USP V/VM

60-08-51-XX/XX or later

VSP G1000

80-02-0X-XX/XX or later

VSP Nx00 models

--

VSP Gx00 models

83-03-0X-XX/XX or later

VSP Fx00 models

83-04-02-XX/XX or later

VSP G1500 and VSP F1500

80-05-0X-XX/XX or later

VSP 1, 2

70-06-33-XX/XX or later

VSP 5000 series

--

VSP G1000

80-03-1X-XX/XX or later

VSP G1500 and VSP F1500

80-05-0X-XX/XX or later

HUS VM

73-03-44-XX/XX or later

VSP 5000 series --

VSP Nx00 models

--
VSP Gx00 models 83-03-0X-XX/XX or later

VSP Fx00 models

83-04-02-XX/XX or later

VSP G1000

80-04-00-XX/XX or later

VSP G1500 and VSP F1500

80-05-0X-XX/XX or later

Notes

  1. VSP storage systems that include either of the following resources are not supported:
    • A resource group created in HCS
    • A resource to which data was migrated by using a virtual ID
  2. A service engagement is required for migrating data from volumes that were previously migrated to VSP.
  3. For the latest information about supported storage systems, see the nondisruptive migration support matrix at https://support.hitachivantara.com/en_us/interoperability.html
  4. If a virtual storage machine with the same model and serial number as the migration source storage system exists in the storage system other than the target storage system, the migration will not succeed.
Table. System requirements

Item

Requirements

Licenses

Source storage system: No additional licenses required

Target storage system:

  • Nondisruptive migration
  • Resource Partition Manager
  • ShadowImage (if migrating copy pair configurations)

HCS roles and resource groups

To perform all nondisruptive migration tasks, the user must be assigned the Admin role and be a member of the All Resources group. (For details on the functions accessible with the Modify role, see the Hitachi Command Suite User Guide.)

Note: Lesser roles will restrict access to some functions (and in some cases prevent them from being displayed in the GUI).

Host server

The host server connected to the source storage system must be supported by the target.

For the latest information about supported host OS and multipath software, see the nondisruptive migration support matrix at https://support.hitachivantara.com/en_us/interoperability.html.

Caution: The procedures for operating a server are established by the standards and specifications of the vendor. Server behavior is affected by factors such as the OS, multipath software, HBAs, drivers, switches, and cable connections. Before starting a migration, we strongly recommend that you investigate and test server behavior (for example, when adding alternate paths to the target storage system or when recognizing devices).

Management server

You must have a management server running Hitachi Command Suite. For details about the management server system requirements, such as supported operating systems, see Hitachi Command Suite System Requirements.

The management server requires the following licenses:

  • Device Manager
  • Hitachi Tiered Storage Manager

Pair management server

If you plan to migrate copy pair configurations, the following must be installed on the pair management server:

  • Device Manager agent 8.1.1 or later
  • CCI 01-32-03/XX or later

Source volumes

The following volumes can be used as migration source volumes:

  • Emulation type: OPEN-V or OPEN-3/8/9/E/K/L
  • Volume type: internal, external, LUSE. For details about external volumes, see External volumes.
  • Maximum capacity: 4 TB (8,589,934,592 blocks)

    For migrations over 4 TB, contact your Support representative.

  • Maximum number of source volumes per storage system: see Target volumes
  • Dynamic Provisioning virtual volumes

    When you migrate the data from a Dynamic Provisioning virtual volume, the target volume does not take over the page assignment status of the source volume. Therefore, you must use pools with a capacity consistent with the pool capacity of the source virtual volumes.

  • Dynamic Tiering virtual volumes

    Dynamic Tiering volumes can be used as migration target volumes. Verify that any target destination pool has free capacity consistent with the total allocated capacity of the source volumes. (After migration you may be able to reduce capacity with the Zero Page Reclamation feature.)

  • ShadowImage primary volumes. For details, see Requirements for migrating existing copy pair configurations.
  • TrueCopy primary volumes are not supported by the HCS nondisruptive migration workflow. For details, see TrueCopy volumes.
  • Universal Replicator primary volumes are not supported by the HCS nondisruptive migration workflow. For details, see Universal Replicator volumes.

Data on the following volumes cannot be migrated:

  • Unallocated volumes
  • Mainframe volumes
  • Multiplatform volumes
  • Command devices
  • Secondary volumes of ShadowImage, TrueCopy, or Universal Replicator
  • Virtual volumes of Thin Image or Copy-on-Write Snapshot
  • Volumes on which Data Retention Utility is set
  • Volumes on which Database Validator is set
  • DP-VOLs with Product ID OPEN-0V (created using Dynamic Provisioning version 60-02-04 or earlier on USP V/VM)
  • Internal volumes with Product ID OPEN-0V (containing data migrated using Volume Migration from a DP-VOL created using Dynamic Provisioning version 60-02-04 or earlier on USP V/VM)

Target volumes

The following volumes can be used as migration target volumes:

  • Emulation type: OPEN-V
  • Maximum capacity: 4 TB (8,589,934,592 blocks)

    For migrations over 4 TB, contact your Support representative.

  • Volume type: internal, external, Dynamic Provisioning virtual volume
  • Maximum number of target volumes per storage system:

    • VSP G200: 2,047
    • VSP G/F350: 16,383
    • VSP G/F370: 32,767
    • VSP G400, G600, VSP F400, F600, VSP N400, N600: 4,095
    • VSP G/F700: 49,151
    • VSP N800, VSP G800, VSP F800: 16,383
    • VSP G/F900: 65,279
    • VSP 5000 series, VSP G1x00, and VSP F1500: 65,279

    If the target storage system is already in use, the LDEV IDs available for migration target volumes are limited. (LDEV IDs that are already in use cannot be used for migration target volumes.)

The following volumes cannot be used as migration target volumes:

  • Mainframe volumes
  • Thin Image pair volumes

    Nondisruptive migration does not support Thin Image pair volumes. If you are using Thin Image in the source storage system, you must re-create the Thin Image pairs on the target storage system after data migration is complete.

  • Dynamic Provisioning pool volumes
  • Volumes on which Cache Residency Manager is set
  • Deduplication system data volumes