Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide

Device Migration operations requirements

  • Each array must have a unique ID (sid).
  • The existing SRDF device and the new devices must be dynamic R1 or R2 capable.

PowerMaxOS and HYPERMAX OS

  • Devices that are part of an SRDF/Metro configuration cannot be migrated.
  • Adaptive copy write pending mode is not supported when the R1 side of the RDF pair is on an array running PowerMaxOS or HYPERMAX OS.

    For configurations where the R1 side is on an array running PowerMaxOS or HYPERMAX OS, and the R2 side is running Enginuity 5876, the mode of the new device pair is set to the RDF mode of the R1 device being replaced.

  • The Geometry Compatibility Mode (GCM) attribute allows devices on arrays running PowerMaxOS or HYPERMAX OS to be paired with devices on arrays running Enginuity 5876 that have an odd number of cylinders. When GCM is set, migration operations are subject to the following restrictions:
    • If the new device is on an array running PowerMaxOS or HYPERMAX OS:
      • If the R1 device is being replaced:

        If the existing R2 device is on an array running Enginuity 5876 with an odd number of cylinders, the migration is allowed if the new device can be made the same size using the GCM attribute.

        If the existing R2 device is on an array running PowerMaxOS or HYPERMAX OS with GCM set, the migration is allowed if the new device can be made the same size by setting the GCM attribute.

      • If the R2 is being replaced:

        If the existing R1 device is on an array running Enginuity 5876 with an odd number of cylinders, then the migration is allowed if the new device can be made the same size by setting the GCM attribute.

        If the existing R1 device is on an array running PowerMaxOS or HYPERMAX OS with GCM set, the migration is allowed if the new device can be made the same size by setting the GCM attribute.

  • If the new device is on an array running Enginuity 5876 and has an odd number of cylinders:
    • If the R1 is being replaced:

      If the existing R2 device is on an array running Enginuity 5876, the new device must be the same configured size.

      If the existing R2 device is on an array running PowerMaxOS or HYPERMAX OS with GCM set, the migration is allowed if the new device has the same GCM size as the R2 device.

    • If the R2 is being replaced:

      If the existing R1 device is on an array running Enginuity 5876, the new device must be the same configured size.

      If the existing R1 device is on an array running PowerMaxOS or HYPERMAX OS with GCM set, the migration is allowed if the new device has the same GCM size as the R1.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\