Performing Failback During Federated Live Migration

Overview
Perform the following steps to fail back during Federated Live Migration (FLM) on a stand-alone
Linux application host with Device Mapper for Linux.

Done

! Warning: These steps pertain only to the specified host and multipath driver used in
this procedure. Do not use these steps for a different host or multipath driver!
This procedure is based on content from the following EMC technical documentation:
EMC Solutions Enabler Symmetrix Migration CLI 7.6 Product Guide
EMC Solutions Enabler Symmetrix Array Management CLI 7.6 Product Guide
EMC Solutions Enabler Symmetrix Array Controls CLI 7.6 Product Guide
These documents can be obtained from EMC Online Support at:
http://support.EMC.com

1.

Verify that the FLM session is in the state permitting failback

From the Solutions Enabler control host:

Use the symrcopy query command to verify that the FLM pairs status is either CopyInProg or
Copied.
symrcopy -f ors_pairs query
Device File Name

: ors_pairs

Control Device
Done
------------------------------Protected
SID:symdev
Tracks
(%)
------------------ -----------000194900275:207C
29728
78
000194900275:207D
28970
79
000194900275:207E
29852
78
000194900275:207F
28573
79
Total
Track(s)
MB(s)
. . .

Remote Device

Flags

----------------------------------- ------- -------------Identification

RI CDSHUTZ

000194900307:206C

SD X..XXM. CopyInProg

000194900307:206D

SD X..XXM. CopyInProg

000194900307:206E

SD X..XXM. CopyInProg

000194900307:206F

SD X..XXM. CopyInProg

--------117123
7320.2

(Remote Device Specification Identifier)

D = Device Name, W = LUN WWN, World Wide Name.

Flags:
(C): X
.
(D): X
.

=
=
=
=

The
The
The
The

background
background
session is
session is

CTL <=> REM

-------------------------------- -- ------- --------------

Legend:
R: (Remote Device Vendor Identification)
S = Symmetrix, C = Clariion, . = Unknown.
I:

Status

copy setting is active for this pair.

copy setting is not active for this pair.
a differential copy session.
not a differential copy session.

(S): X =
. =
(H): X =
. =
(U): X =
. =
(T): M =
R =
S =
(Z): X =
. =
(*): The

2.

The session is pushing data to the remote device(s).

The session is pulling data from the remote device(s).
The session is a hot copy session.
The session is a cold copy session.
The session has donor update enabled.
The session does not have donor update enabled.
The session is a migration session.
The session is a RecoverPoint session.
The session is a standard ORS session.
The session has front-end zero detection enabled.
The session does not have front-end zero detection enabled.
failed session can be reactivated.

Fail back the FLM session and verify the failback

From the Solutions Enabler control host:

Use the symrcopy failback -migrate command to fail back the FLM session for the devices
specified by the FLM pair file.
# symrcopy -f ors_pairs failback -migrate
'Failback' operation execution is in progress for the device list
in device file 'ors_pairs'. Please wait...
'Failback' operation successfully executed for the device list
in device file 'ors_pairs'.

Use the symrcopy query command to verify that the status of the FLM pairs is Failedback.
# symrcopy -f ors_pairs query
Device File Name

: ors_pairs

Control Device
Remote Device
Flags
Status
Done
---------------------------- --------------------------- ------- -------------- ---Protected
SID:symdev
Tracks
Identification
RI CDSHUTZ CTL <=> REM
(%)
------------------ --------- ------------------------ -- ------- -------------- ---000194900275:207C
0 000194900307:206C
SD X..XXM.
Failedback
N/A
000194900275:207D
0 000194900307:206D
SD X..XXM. Failedback
N/A
000194900275:207E
0 000194900307:206E
SD X..XXM. Failedback
N/A
000194900275:207F
0 000194900307:206F
SD X..XXM. Failedback
N/A
Total
Track(s)
MB(s)
. . .

3.

--------304520
19032.5

Verify failback on the application host

From the application host:
Use multipath -l to verify the failback. The failback sets the target devices to host access
mode passive and the source devices to host access mode active. The passive target paths
should report that they are in a failed state. If any paths, other than the expected paths, report a
failed state, examine the cause before continuing.
Linux> multipath l
mpath23 (360060480000190300124533030313130) dm-23 EMC,SYMMETRIX
[size=8.0G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 4:0:0:16 sdax 67:16 [active][undef]
\_ 3:0:0:16 sdr 65:16 [active][undef]
\_ 3:0:1:16 sdcf 69:48 [failed][undef]

\_ 4:0:1:16 sddl 71:48 [failed][undef]

mpath1 (360060480000190300124533030313141) dm-1 EMC,SYMMETRIX
[size=8.0G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 3:0:0:26 sdab 65:176 [active][undef]
\_ 4:0:0:26 sdbh 67:176 [active][undef]
\_ 3:0:1:26 sdcp 69:208 [failed][undef]
\_ 4:0:1:26 sddv 71:208 [failed][undef]

4.

Terminate the FLM session

From the Solutions Enabler control host:

Use the symrcopy terminate -migrate command to terminate the FLM migration for the
devices specified by the FLM pair file.
# symrcopy -f ors_pairs terminate -migrate
'Terminate' operation execution is in progress for the device list
in device file 'ors_pairs'. Please wait...
'Terminate' operation successfully executed for the device list
in device file 'ors_pairs'.

Terminating the FLM sessions in a Failedback state performs the following:

ORS hot pull, donor update session is terminated.
FLM source devices remain in an active host access mode.
FLM target devices remain in a passive host access mode.
5.

Remove masking and mapping for the VMAX target devices

From the Solutions Enabler control host:
Use the symaccess command to delete or modify a masking view to remove application-host
visibility for the VMAX target devices. Use the -unmap flag when deleting or modifying the
masking view to unmap the devices as part of the Auto-provisioning change. The FLM target
devices must be unmapped to remove external identity and geometry.
# symaccess -sid 000194900275 delete view -name dm_flm_mv unmap
Use the symaccess list command to verify that the target devices have been removed from all
masking views. The view count should be zero (0) for each FLM target device.
# symaccess -sid 000194900275 list -type storage -devs 207c:207f
Symmetrix ID
Symm
Dev
---207C
207D
207E
207F

: 000194900275

Storage Group Name

-------------------------------dm_flm_sg
dm_flm_sg
dm_flm_sg
dm_flm_sg

Dev
Count
----4
4
4
4

View
Count
----0
0
0
0

Use the symdev list noport command to verify that the target devices are not mapped. Use
range to filter on a specific range of devices.
# symdev -sid 275 list -noport
Symmetrix ID: 000194900275
Device Name
Directors
Device
--------------------------- ------------- -------------------------------------

Cap
Sym Physical
SA :P DA :IT Config
Attribute
Sts
(MB)
--------------------------- ------------- ------------------------------------207C Not
207D Not
207E Not
207F Not
. . .

Visible
Visible
Visible
Visible

???:? 08A:D6
???:? 07A:C0
???:? 07B:D4
???:? NA:NA

2-Way Mir
RAID-5
RAID-6
TDEV

N/Grp'd
N/Grp'd
N/Grp'd
N/Grp'd

RW
(M) RW
RW
(M) RW

8631
34523
8631
34523

Clean up the operating system device tree after removing the masking. For every removed
target device path, run this command:
#echo 1 > /sys/block/<target device path>/device delete

Then rescan the operation-system device tree by running the following command to each
controller connecting with a VMAX target port. (Replace the <x> with the controller number.)
#echo - - - > /sys/class/scsi_host/host<x>/scan

6.

Verify that the target device paths are removed from the Device Mapper
configuration
From the application host:
Use multipath -l to verify that the target paths are no longer visible in the Device Mapper
configuration. The FLM source device paths should all report an active state. There should be
no FLM target paths visible. If the device states are not correct, examine the cause before
continuing.
Linux> multipath -l
. . .
mpath121 (36006048000018743037653594d464244) dm-23 EMC,SYMMETRIX
[size=18G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 1:0:0:46 sdav 66:240 [active][undef]
\_ 2:0:0:46 sdcz 70:112 [active][undef]
mpath168 (360060480000190102221533031303535) dm-138 EMC,SYMMETRIX
[size=9.2G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:212 sdif 134:240 [active][undef]
\_ 6:0:0:212 sdkg 66:320 [active][undef]
mpath153 (360060480000190102221533031303030) dm-123 EMC,SYMMETRIX
[size=938M][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 5:0:0:182 sdhq 134:0
[active][undef]
\_ 6:0:0:182 sdjr 65:336 [active][undef]
mpath94 (36006048000018743037653594d463630) dm-42 EMC,SYMMETRIX
[size=4.6G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=0][active]
\_ 2:0:0:9
sdbo 68:32
[active][undef]
\_ 1:0:0:9
sdk 8:160
[active][undef]

7.

Remove the external identity

From the Solutions Enabler control host:

Use the symconfigure command to remove the devices external identity. The identity must be
removed before the device can be used for another FLM session. The device having its external
identity removed must be unmapped, or the configuration change is rejected.
#
>
>
>
>
>

symconfigure
set dev 207C
set dev 207D
set dev 207E
set dev 207F
EOL

-sid 275
identity
identity
identity
identity

commit << EOL

= no identity;
= no identity;
= no identity;
= no identity;

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.
Processing symmetrix 000194900275
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Committing configuration changes..........................Started.
Committing configuration changes..........................Committed.
Terminating the configuration change session..............Done.
The configuration change session has successfully completed.

Use the symdev list -identity command to verify that the target devices are no longer
presenting the identity of the source devices. The external identity should now reflect the native
identity of the FLM target device.
# symdev -sid 275 list -identity
Symmetrix ID: 000194900275
Device
---------------------------------Sym Physical
Config
Sts
---------------------------------. . .
207C Not
. . .
207D Not
. . .
207E Not
. . .
207F Not
. . .

Visible 2-Way Mir

RW

.X

000194900275

00195 7500195000

8625

Visible RAID-5

RW

.X

000194900275

001FF 75001FF000

8625

Visible RAID-6

RW

.X

000194900275

00295 7500295000

8625

Visible TDEV

RW

.X

000194900275

002FF 75002FF000

8625

Legend:
Flags:
(I)dentity : X
.
(G)eometry : X
.

8.

FLG
External Identity
--- ---------------------------------------IG Array ID
Num
Ser Num
Cap (MB)
--- ----------------------------------------

=
=
=
=

The
The
The
The

device
device
device
device

has a non-native external identity set

does not have an external identity set
has a user defined geometry
does not have a user defined geometry

Remove the external geometry (if applicable)

Skip this step if external geometry is not set on the FLM target device.
From the Solutions Enabler control host:
Use the symconfigure command to remove the external geometry. The device having its
external geometry removed must be unmapped, or the configuration change is rejected.

#
>
>
>
>
>

symconfigure
set dev 207c
set dev 207D
set dev 207E
set dev 207F
EOL

-sid 275
geometry
geometry
geometry
geometry

commit << EOL

= no geometry;
= no geometry;
= no geometry;
= no geometry;

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.
Processing symmetrix 000194900275
Performing Access checks..................................Allowed.
Checking Device Reservations..............................Allowed.
Locking devices...........................................Locked.
Committing configuration changes..........................Started.
Committing configuration changes..........................Committed.
Terminating the configuration change session..............Done.
The configuration change session has successfully completed.

Use the symdev list identity command to verify that the target devices are no longer
presenting the geometry of the source devices. The flag should now indicate that user-defined
geometry is not set.
# symdev -sid 275 list -identity
Symmetrix ID: 000194900275
Device
---------------------------------Sym Physical
Config
Sts
----------------------------------

FLG
External Identity
--- ---------------------------------------IG Array ID
Num
Ser Num
Cap (MB)
--- ----------------------------------------

. . .
207C Not
207D Not
207E Not
207F Not
. . .

..
..
..
..

Visible
Visible
Visible
Visible

2-Way Mir
RAID-5
RAID-6
TDEV

Legend:
Flags:
(I)dentity : X
.
(G)eometry : X
.

9.

=
=
=
=

The
The
The
The

device
device
device
device

RW
RW
RW
RW

000194900275
000194900275
000194900275
000194900275

00195
001FF
00295
002FF

7500195000
75001FF000
7500295000
75002FF000

8631
34523
8631
34523

has a non-native external identity set

does not have an external identity set
has a user defined geometry
does not have a user defined geometry

Reset the FLM target devices host access mode to active

From the Solutions Enabler control host:
After the failback, the FLM target devices are left in a passive host access mode. Use the
symdev host_active command to change the host access mode from passive to active. Use
range to specify a range of devices.
# symdev -sid 275 host_active 207C
'Host Active' Device operation successfully completed for the device.
# symdev -sid 275 host_active 207D
'Host Active' Device operation successfully completed for the device.
# symdev -sid 275 host_active 207E
'Host Active' Device operation successfully completed for the device.
# symdev -sid 275 host_active 207F
'Host Active' Device operation successfully completed for the device.

Table of Contents