POWERMAXOS 10 DATA

MOBILITY – OPEN-
MINIMALLY DISRUPTIVE
MIGRATION (O-MDM)

PARTICIPANT GUIDE

PARTICIPANT GUIDE
 PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant Guide

© Copyright 2023 Dell Inc Page 2

Table of Contents

PowerMaxOS 10 Data Mobility Overview 4

Data Migration Introduction 4
Non-Disruptive Migration 6
Minimally Disruptive Migrations 8
Open-Minimally Disruptive Migrations 9
O-MDM Migration States and Process Flow 10

O-MDM Migration Session Phases 11

Presenting Source Array Devices 11
Scanning the SAN Environment for Devices Using the CLI 11
Scanning the SAN Environment for Devices Using Unisphere 12
Create an O-MDM Migration Session 13
Cutover an O-MDM Migration Session 20
Commit an O-MDM Migration Session 22

Appendix 27

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant Guide

© Copyright 2023 Dell Inc Page 3

 PowerMaxOS 10 Data Mobility Overview

PowerMaxOS 10 Data Mobility Overview

Data Migration Introduction

Data Mobility is the common term used to reflect a broad set of use
cases for data migration. The use cases include Non-Disruptive (NDM),
Minimally Disruptive (MDM), and Open-Minimally Disruptive Migrations
(O-MDM).

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 4

 PowerMaxOS 10 Data Mobility Overview

NDM Configuration

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 5

 PowerMaxOS 10 Data Mobility Overview

Migration Facilities Between a Source and Target Array

Source Migration Enginuity Target Enginuity

Type Level Level

VMAX O-MDM 5876 PowerMax 6079

2500/8500

Unity, O-MDM N/A PowerMax 6079

XtremIO, or 2500/8500
any FC
connected
Dell storage
or supported
third party
array

VMAX3, NDM or 5977 or PowerMax 6079

VMAX-AF, MDM 5978 2500/8500
PowerMax

Deep Dive: Review the Environment and system

requirements topic in Dell PowerMaxOS 10.0.0.0 Release
Notes for information about deprecated environments.

Non-Disruptive Migration

Non-Disruptive Migration (NDM):

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 6

 PowerMaxOS 10 Data Mobility Overview

NDM1 is defined as a one time movement of data from a source array to a

target.

During a Non-Disruptive Migration, application access2 to data being

migrated from the source array is uninterrupted.

NDM works with most modern Operating Systems (OS). The DELL
Technologies PowerMax 2500/8500 2000/8000 Simple Support Matrix
contains a list of compatible Operating Systems and storage platforms.
Supported NDM configurations cover approximately 70% of all open
systems I/O stacks.

NDM management tools for PowerMax:

• Data Mobility—for PowerMax 2500/8500
• Symcli
• Unisphere/REST
• PowerPath Migration Enabler

Important: Supported data movement technologies include

SRDF and Open Replicator between source and target
arrays in a migration session.

1 NDM uses SRDF/metro in Pass-Through mode. In this mode, the

application host can access data on both source and target devices while
the migration is in progress.
2 Single host configurations that accessed migrated data on the old array

need to now reference the data on the new array. LUN addresses may
change moving to the new array.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 7

 PowerMaxOS 10 Data Mobility Overview

To view the session states for a non-disruptive migration, reference the

Dell Solutions Enabler 10.0.0 Array Controls and Management CLI User
Guide and go to the section Non-Disruptive Migration operational
restrictions and state reference. To learn about the control operations,
click the same link and reference the section Non-Disruptive Migration
control operations.

Minimally Disruptive Migrations

Minimally disruptive migrations (MDM) require the administrator to shut

down all applications running on the source side volumes before issuing
the cutover command. The command3 runs after the create operation
completes.

MDM uses the same SRDF data movement technology as NDM.

However, MDM covers all open systems I/O stacks.

To learn about the control operations and session states for MDM, view
Dell Solutions Enabler 10.0.0 Array Controls and Management CLI User
Guide and reference the NDM Updates section. MDM and NDM Updates
refer to the same thing.

3 The cutover command makes the target devices visible to the host.
Updates made to data on the target array are replicated back to the
source array via the Data Mobility replication pathway. Upon successful
completion of a cutover operation, the administrator must perform a host
rescan (or host reboot) and restart the application. New LUNs that have
been discovered must be verified prior to restarting the application.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 8

 PowerMaxOS 10 Data Mobility Overview

Warning: Applications must be shut down before issuing

create -offline (with no -precopy), cutover or the
cancel commands.

Open-Minimally Disruptive Migrations

Open-Minimally Disruptive Migrations (O-MDM) is a new migration option

in PowerMaxOS 10. Data movement with O-MDM is managed by Open
Replicator (ORS). O-MDM works with all open systems I/O stacks and
SCSI block storage4.

O-MDM supports all SCSI block transfer arrays, Operating Systems, and
multi-pathing software supported by ORS. Storage support includes
VMAX, PowerMax, Dell Storage, and qualified 3rd party arrays. Multi-
pathing software support includes MPIO, PowerPath, and others
supported by ORS.

Source devices presented to the PowerMax front-end FA ports can be

verified using the SYMCLI5.

4 O-MDM allows any SCSI block storage array to migrate data to the
PowerMax 2500 or 8500. ORS transfers data from an external array using
World Wide Name (WWN) designated FBA block source devices. Since
ORS works with block transfers, it relieves any requirement for SRDF as
the transport mechanism.
5 The SYMCLI command symsan lists port and LUN WWNs as seen from

a specific array director and port. This is used to validate that the zoning
between the port and target is correct. It does not require an Open

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 9

 PowerMaxOS 10 Data Mobility Overview

O-MDM Migration States and Process Flow

The migration states for O-MDM start at the Pre and Post Migration point
in the diagram. If the create -san -offline command processes
correctly, the green arrows identify the path for a successful migration.

Click the image to review the list of steps and their definition.

Replicator session. Use this command to display remote port WWNs, and
LUN WWNs seen behind a remote port WWN.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 10

 O-MDM Migration Session Phases

O-MDM Migration Session Phases

Presenting Source Array Devices

Shown here is an environment setup for O-MDM. ORS is the fundamental

technology that supports O-MDM.

Click the diagram to learn about the environment.

Scanning the SAN Environment for Devices Using the

CLI

The symsan command displays the WWNs that a source array is granted
access to on remote array ports.

The symsan command verifies the SAN configuration without disruption to

the remote application and without creating an ORS session. To ensure
that the create command can proceed, the process verifies that the
requirements are met. The process also ensures that the target array has
sufficient storage available to duplicate the application storage.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 11

 O-MDM Migration Session Phases

Run the symsan command with the sanports option to list the remote
ports visible to the source array.

The web version of this content contains an interactive activity.

Scanning the SAN Environment for Devices Using

Unisphere

Unisphere includes a migration utility that can be used to scan for remote
volumes and report their WWNs.

Once logged into the Unisphere application:

1. Select Data Protection.

2. Select Migrations.
3. Click Scan in the SAN WWNS tab.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 12

 O-MDM Migration Session Phases

Create an O-MDM Migration Session

O-MDM Create Migration Phase

Create Phase Process:

1. The administrator must identify the source WWNs, the target array ID,
and an existing target array initiator group.
2. The create command first verifies that the environmental
requirements, rules, and restrictions are met to ensure that the
migration can proceed. To learn more about the requirements, rules,
and restrictions, view Dell Solutions Enabler 10.0.0 Array Controls and
Management CLI User Guide. It should be noted that the information in
the CLI user guide is for NDM; however, there is a difference for O-
MDM. Where differences exist, the restrictions table takes priority.
3. The storage configuration of the application is copied to the target
array. Equivalently provisioned devices are created on the target
system. After the storage configuration of the application is duplicated
on the target array, the create operation concludes.
4. The migration immediately enters the CutoverReady state. The
administrator must shut down the application before a cutover
operation can be issued. After the cutover command starts, data
migration begins.
5. The ORS command symrcopy activate -session <session
name> does not start until the CutoverReady state is reached.
6. If the create action fails, cancel the migration with a symdm cancel
command. Canceling the migration removes the target side storage
provisioning that the create operation performed.

Choose the Remote Volumes

In the example shown, three LUNs are discovered and displayed with their
WWNs on a PowerStore array.

Clicking Create establishes the environment for creating a migration

session.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 13

 O-MDM Migration Session Phases

Create a Migration with Unisphere

Create a migration by configuring the following items:

1. The volumes to migrate from the source array
2. The Storage Group for the target volumes
3. The hosts that are involved in the migration
4. The ports to be used in the migration

Go to: To practice establishing the environment for

migration in the create phase with Unisphere, click here.

Running the symdm create Command

Application data migrations are performed using the symdm command.

Migrations from a qualified array to a PowerMax 2500/8500 preserve

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 14

 O-MDM Migration Session Phases

application availability throughout the process. The exception is when the

-offline option is used with the create argument. Starting a migration
requires the symdm create command.

The following are new options for the symdm command to support O-
MDM:
• -san – Specifies the migration to be an Open Data Migration.
• -file – Specifies the file name that contains a list of source side
device WWNs to be migrated.
− File example: src_wwn_list.fil
o 68CCF09800BEBBD5F41208CB90C79C3B
68CCF09800C2F3EA510E7BFF4B1E670E
• -tgt_sg – Specifies the target storage group name that is created for
the target devices. This name is used for other target-side masking
objects. These objects include the port group if it does not exist, and
any masking view created during the migration.
• -tgt_ig – Specifies the target side initiator group that contains host
application initiators mapped to both the PowerMax and source side
arrays.

Deep Dive: A full explanation of the symdm command with

its arguments and options can be found in the Dell Solutions
Enabler 10.0.0 Array Controls and Management CLI User
Guide.

Creating a Migration Session Using the CLI

Data Mobility uses the symdm create -san -offline command to

create an O-MDM migration session and processes the following:
1. A file containing a list of source device WWNs to be migrated

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 15

 O-MDM Migration Session Phases

2. Creation of target devices, associated SGs, and front-end host

mappings at the target side
3. Target devices that are created on the PowerMax are rounded up to
the nearest cylinder size

The following is from the CLI interaction:

Use the following command to create a data migration session using a file
for devices to be migrated, storage group OMDM_DEMO_SG, and initiator
group OMDM_INIT_GRP. Type symdm create -san -offline -file
src_wwn_list.fil -tgt_sid 349 -tgt_sg OMDM_DEMO_SG -tgt_ig
OMDM_INIT_GRP -nop

A DM 'Offline SAN Create' operation is in progress for storage group

'OMDM_DEMO_SG'. Please wait...

Analyze Configuration...................................................Started.
Source Array:4R02643
Target Array:000120200349
Analyze Configuration...................................................Done.
Creating Device(s)......................................................Started.
Creating Device(s) on Target............................................Done.
Update target SG Device(s)..............................................Started.
Update target SG Device(s)..............................................Done.
Create Storage Group(s) on Target.......................................Started.
Create Storage Group(s) on Target.......................................Done.
Create Port Group(s) on Target..........................................Started.
Create Port Group(s) on Target..........................................Done.
Start Data Replication..................................................Started.
Start Data Replication..................................................Done.

The DM 'Offline Create' operation successfully executed for storage group

'OMDM_DEMO_SG'.

To view the status of the Storage Group used in the create command,
the list command is used. Type symdm -sid 349 list.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 16

 O-MDM Migration Session Phases

Symmetrix ID : 000120200349
Total
Flg Source Target Capacity Done
Storage Group OS Array Array State (GB) (%)
------------- -- ------ ------ ------------ ------ ------
OMDM_DEMO_SG XX 4R02643 000120200349 CutoverReady 100.0 N/A

Legend:
Flags:
(O)ffline: X = Offline, . = N/A
(S)AN: X - SAN, . = N/A

A successful run of the symdm create -san -offline command

results in a device or devices being created on the target in a new SG.
New Port Groups are also created. After the application storage
configuration is duplicated on the target array, the create operation
concludes by connecting source-side devices to corresponding target-side
devices. The connection uses a replication pathway and starts the data
migration. A cancel command, if required, can be used to cancel the
migration and undo the target-side storage provisioning that is done by the
create operation.

O-MDM Recover Exception Process

If a process phase such as the create command fails, either a recover

or cancel action can be taken.

If a failure is corrected, the symdm recover command may be run after

correcting the cause of the failure. The recover command may be used
for failures in symdm create, cutover, commit or cancel.
Recover puts the migration in the proper state so that the migration may
be repeated or resumed.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 17

 O-MDM Migration Session Phases

If a session fails in Unisphere, the More

Actions menu offers the option to
recover the session.

O-MDM Recover Exception Process Using the CLI

The following is from the CLI interaction:

This CLI Walkthrough is an example of a recovery from a failed create.

To restart a failed session from the point where it stopped, use

the symdm recover command shown. Typesymdm recover -sid 349 -sg
OMDM_DEMO_SG -nop

A DM 'Recover' operation is in progress for storage group

'OMDM_DEMO_SG'. Please wait.
Analyze Configuration Started.
Source
SID:4R02643
Target
SID:000120200349
Analyze Configuration Done.
Create Storage Group(s) on Target Not Needed.
Duplicate Device(s) on Target Not Needed.
Create Initiator Group(s) on Target Not Needed.
Create Port Group(s) on Target Not Needed.
Setup Data Replication Started.
Setup Data Replication Done.
Recover Data Replication Started.
Recover Data Replication Done.
Create Masking View(s) on Target Started.
Create Masking View(s) on Target Done.
Update Device State Started.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 18

 O-MDM Migration Session Phases

Update Device State Done.

The DM 'Recover' operation successfully executed for storage
group 'OMDM_DEMO_SG'

O-MDM Cancel Exception Process

If a failure cannot be corrected, the symdm cancel command may be run

to terminate the session. The cancel command restores the application
storage environment to it's pre-migration settings. Resources that are
configured for the application on the target are removed.

If a session fails in Unisphere, the More

Actions menu offers the option to cancel
the migration session.

O-MDM Cancel Exception Process Using the CLI

The following is from the CLI interaction:

The CLI Walkthrough below is an example of a cancel operation.

The symdm cancel command is used to terminate a migration and

release all of the resources used by the session. Typesymdm cancel -sid
349 -sg OMDM_DEMO_SG -nop

A DM 'Cancel' operation is in progress for storage group '

OMDM_DEMO_SG'.
please wait...
Analyze Configuration Started.
Source
SID:4R02643
Target
SID:000120200349
PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant
Guide

© Copyright 2023 Dell Inc Page 19

 O-MDM Migration Session Phases

Checking Target devices for 10 Not Needed.

Analyze Configuration Done.
Remove Data Replication Started.
Remove Data Replication Done.
Remove Port Group(s) on Target Started.
Remove Port Group(s) on Target Done.
Remove Initiator Group(s) on Target Started.
Remove Initiator Group(s) on Target Done.
Remove Storage Group(s) on Target Started.
Remove Storage Group(s) on Target Done.
Rollback update of target SG Device(s) Started.
Rollback update of target SG Device(s) Done.
Remove Duplicate Device(s) on Target Started.
Wait for deallocation to complete Started.
Wait for deallocation to complete 0
Wait for deallocation to complete Done.
Remove Duplicate Device(s) on Target In Progress.
Remove Duplicate Device(s) on Target Done.
The DM 'Cancel' operation successfully executed for storage group
'OMDM_DEMO_SG'

Cutover an O-MDM Migration Session

Session Cutover

Cutover steps:
1. Verify that the create phase completed successfully.
2. Shut down the source side applications.
3. Run the cutover command.
4. Restart the applications at the target site.

The following is from the CLI interaction:

Use the cutover command to move application activity to the target
(remote) side. Type symdm cutover -sid 349 -sg OMDM_DEMO_SG -
nop

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 20

 O-MDM Migration Session Phases

A DM 'Cutover' operation is in progress for storage group

'OMDM_DEMO_SG'. Please wait...

Analyze
Configuration..........................................Started.
Source SID:4R02643
Target SID:000120200349
Checking Source devices for IO.........................Started.
Checking Source devices for IO.........................Done.
Analyze Configuration..................................Done.
Preparing Devices for Host discovery...................Started.
Cutover................................................Started.
Cutover................................................Done.
Preparing Devices for Host discovery...................Done.
Create Masking View(s) on Target.......................Started.
Create Masking View(s) on Target.......................Done.

The DM 'Cutover' operation successfully executed for storage

group 'OMDM_DEMO_SG'.

To view the current status of the Storage Group "OMDM_DEMO-SG" use

the symdm list command.

Symmetrix ID : 000120200349
Total
Flg Source Target Capacity Done
Storage Group OS Array Array State (GB) (%)
------------- -- ------------ ------------ -------- ------- ----
OMDM_DEMO_SG XX 4R02643 000120200349 Migrating 100.0 79

Legend:
Flags:
(O)ffline: X = Offline, . = N/A
(S)AN: X - SAN, . = N/A

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 21

 O-MDM Migration Session Phases

Go to: To practice a session cutover with Unisphere, click

here.

Commit an O-MDM Migration Session

Commit an O-MDM Migration Phase

The commit process:

• Completes and terminates a migration. ORS donor updates from the
source devices are stopped and the migration session is terminated
• Removes application resources from the source array and releases
resources that were used for the migration
• Before issuing the commit command, a host rescan6 of the external
data paths should be run to access new LUNs on the target array

6 Rescans of LUN devices are performed for various operating systems.

Linux uses the iscsiadm utility to allow discovery and login to iSCSI
targets. If single sessions are to be rescanned, the command structure is
iscsiadm -m session -r sid# --rescan. Rescanning all logged in sessions
omits the -r sid# option.Windows environments use DISKPART. At the
DISKPART prompt, type RESCAN to scan for newly added disks.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 22

 O-MDM Migration Session Phases

− If dead paths exist, follow the rescan with a multipath or powerpath

command7 to cleanup the dead paths
• Start the application on the target array
− If the migration session did not move the identity of the LUNs,
reconfigure the application to access the new LUNs on the target
array
• Run the commit command

The following is from the CLI interaction:

Once the Cutover phase is in the CutoverSync state, the migration may be
committed.Run the commit command to complete and terminate the
migration. Type symdm commit -sid 349 -sg OMDM_DEMO_SG -nop

A DM 'Commit' operation is in progress for storage group

'OMDM_DEMO_SG'. Please wait...
Analyze Configuration...................................Started.
Source SID:4R02643
Target SID:000120200349
Analyze Configuration..................... .............Done.
Remove Data Replication.................................Started.
Remove Data Replication.................................Done.
The DM 'Commit' operation successfully executed for storage group
'OMDM_DEMO_SG'

Use the list command to display the migration status for the Storage
Group OMDM_DEMO_SG.

No DMs found.

7Cleaning up dead paths in Linux is done using the multipath -ll

command. To clear all dead paths from the command line without
confirmation via powermt use powermt check force.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 23

 O-MDM Migration Session Phases

Go to: To practice committing a migration session with

Unisphere, click here.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 24

 O-MDM Migration Session Phases

Protecting Migrated Devices

SRDF protection
• Target devices may have SRDF mirrors (R2 devices) added to them
after copying data to the target has started
• The mirrors added to the target devices are in Asynchronous, Adaptive
Copy, or Synchronous mode but cannot be:

− Enabled for Multi-Session Consistency (MSC) or Synchronous

SRDF Consistency
− Part of an SRDF/Star, SRDF/SQAR, or SRDF/Metro configuration
TimeFinder protection
• Source and target devices with TimeFinder sessions cannot be targets
of a TimeFinder copy operation during a migration session
− Example: TimeFinder sessions cannot copy data to source devices
being migrated
• If a migration session completes successfully, local TimeFinder
replications are allowed with source and target O-MDM devices

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 25

Appendix

Process States
Below is an image of the process states for Data Mobility and a
description of each step.

1. CreateInProg - Migration session is being created. The create

command has not run to completion with either a success or a failed
status.
2. CreateFailed - The create command has run to completion with a
failed status.
3. CancelInProg - The cancel command is in progress. The cancel
command has not run to completion with either a success or a failed
status.
4. CancelFailed - The cancel command has run to completion with a
failed status.
5. CutoverReady - The create command has run to completion with a
success status. Target devices are not masked to the host and the
source devices remain ready to the host.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 27

 Appendix

6. CutoverInProg - The cutover command is in progress and the

application is being moved to the target array. The cutover command
has not run to completion with either a success or a failed status.
7. CutoverFailed - The cutover command has run to completion with a
failed status.
8. Migrating - The cutover command succeeded. I/Os can be serviced by
devices on the target array.
9. MigrateFailed - This state occurs when migration is interrupted, as
might occur with a loss of the required DM connectivity between the
source and target arrays. The source WWN status field will be one of
the following: NDEF (not defined), NO_PATH (all target paths are
down), LUN_NR (indicates the source/target device LUN is not ready),
or WR_PROT (write protect set on the LUNs).
10. CutoverSync - The cutover command completed successfully. The
application is running on the target array, and all data has been
synchronized between the target and source arrays.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 28

 Appendix

11. CommitInProg - The commit command is in progress. The commit

command has not run to completion with either a success or a failed
status.
12. CommitFailed - The commit command has run to completion with a
failed status.

O-MDM Configuration

The OMDM configuration items are defined in the following list:

• Application Host - The application host reads and writes the source
storage devices for the management of application data. Once the O-
MDM session is in the CutOver phase, target devices become host
visible and read-write activity takes place at the target. Updates on the
target are replicated back to the source array.
• Source Array - The array from which the storage configuration of the
application is copied to the target array, creating equivalently
provisioned devices at the target.
• PowerMax 2500/8500 - The source array attaches to the application
host. All migrations move data from the source devices to equivalent
target devices.
• Data Migration Direction - The source array may be either a VMAX3,
VMAX All Flash, PowerMax, Dell Storage, or a supported third-party
array. Source arrays must provide FBA devices for O-MDM migrations.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 29

 Appendix

• Control Host - Target devices, associated Storage Groups, and front-

end mapping are created during the create phase of the migration
process. The control host uses these storage entities to manage the
application storage after the cutover command is run. The control host
may use either Unisphere 10 or Solutions Enabler 10 for session
management.
− The maximum number of copy sessions that are supported for
Enginuity 5773 and later is 1024.
− One copy session is permitted per control device at one time.
• Source Devices - O-MDM source devices must have the following
characteristics:
− Devices are configured as FBA (512-byte blocks).The devices must
be mapped to Fibre Channel directors.
− All devices must be accessible through the SAN.Only World Wide
Name (WWN) identities are used with the storage devices.
• Target Devices - Target devices should be unmounted to any host
that has access to them during copying. Unmounting prevents potential
data corruption.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 30

 Appendix

Migration Restrictions

Restrictions

Source side Target side

Pre- • WWNs must be 512- • Storage must be PowerMax

Create byte blocks (FBA). 2500 or 8500.
• Migration session
cannot have more than
1024 LUNs.
• Storage must be
VMAX3, VMAX AF,
PowerMax, Dell
Storage, or supported
third-party array.

Pre- • Application initiators must

Migration appear in the Login History
Table for at least one port in
the port group on the target.
• Ports must be ACLX
enabled FC ports. FCoE and
iSCSI are not allowed.
• Migration masking group
names must not exist before
the migration.
• The SRP must have enough
capacity for the migration.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 31

 Appendix

Pre- Changing the masking

Commit information after the migration
starts can cause O-MDM
controls to be disallowed.
Exceptions:
• Changing Service Levels or
SRPs on the Storage Group
(SG)
• Changing the compression
attribute on the SG
• Adding host I/O limits on the
SG
• Adding more FC ports to the
Port Group

Create a Migration Session with Unisphere

The Online Course Contains an Interaction Here.

A practice simulation establishing the environment for migration in the

create phase with Unisphere.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 32

 Appendix

ORS Updates

1. Shut down the application before issuing the cutover command.

a. The cutover command makes the target devices visible to the

host.
b. Updates8 made to data on the target array are replicated back to
the source using one or more replication pathways.

O-MDM Cutover Phase for Data Migration

The cutover phase duplicates the source array storage group and
application data on the target. Application data access then switches from
the source array to the target array.

The Cutover process performs a target side host storage rescan after the
cutover processes successfully.
• Verify that new LUNs have been discovered.
– VMware example: #> esxcli storage core adapter rescan --all
• Reconfigure the application—if necessary—to use the new LUNs.

8Updates are performed using the ORS symrcopy -donor_update

command which protects against potential data loss due to SAN failures or
other connectivity issues.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 33

 Appendix

Cutover a Migration Session with Unisphere

The Online Course Contains an Interaction Here.

A practice simulation moving the application environment from the source

to the target using cutover in a migration with Unisphere.

Commit a Migration Session with Unisphere

The Online Course Contains an Interaction Here.

A practice simulation committing a migration session with Unisphere.

PowerMaxOS 10 Data Mobility – Open-Minimally Disruptive Migration (O-MDM) - Participant

Guide

© Copyright 2023 Dell Inc Page 34