The following are known limitations or restrictions regarding an O-MDM migration:
- Target array must be PowerMax 2500/8500 (V4) Hardware.
- Source or donor array must be VMAX3, VMAX All Flash, PowerMax, other Dell storage, or supported third party array.
- Data migrations are often complex operations and require careful planning and execution of predetermined procedures. Failure to identify and perform necessary steps or work within supported configurations can result in data unavailability or loss.
- Source side WWNs must be 512 byte block size
- No more than 1,024 LUNs can be migrated in a single O-MDM session
- All initiators provisioned to an application on the source array must appear in the Login History Table (LHT) of the target array provided. The name of the port group must exist on the target array and have the initiators appear on the LHT for at least one port in the port group. These ports must be ACLX enabled FC ports.
- FCoE and iSCSI ports are not supported.
- The names of the masking groups that are being created as part of the migration must not exist on the target array.
- The SRP that will be used for target-side storage, whether specified or defaulted, must have enough free capacity to support the migration.
- The target array must be capable of supporting the additional devices that the migration will create to receive the source-side data.
- The target masking configuration of the migrated application must not be added.
- Changing the masking configuration after the start of the migration can cause the O-MDM controls to be disallowed.
- The only exceptions are:
- Changing the SLs or SRPs on the SG
- Changing the compression attribute on SG
- Adding Host IO limits on SG
- Adding more ports to the PG, only FC ports (not NVMe over FC) are supported
- After the migration has started copying the data to the target array, devices can have R1 mirrors added so they can be used for remote replication. Migration controls will evaluate the states of these devices when determining if the control can proceed.
- The R1 mirrors added to the target devices can be in Asynchronous, Adaptive Copy, or Synchronous Mode but:
- Cannot be enabled for MSC
- Cannot be part of a Star or SQAR configuration
- Cannot be enabled for Synchronous SRDF Consistency
- Cannot be part of an RDF/Metro configuration
- Devices in other SRDF groups paired with target devices cannot be the target of a data synchronization operation during the lifecycle of the migration session (that is, cannot copy data to devices being migrated).
- When the migration session reaches the complete state, LREP snapshot session will be allowed to be created on O-MDM target device.
- If a device has any association with the migration session, LREP snapshot session will be blocked from being created on O-MDM target device.