Windows Clusters (2003, 2008) Federated Live Migration

 

Topic

Managing Federated Live Migrations

Selections

Select an operating system: Windows Clusters (2003, 2008)

 

 

Contents

·            Preparing SAN to Support Federated Live Migration. 3

·            Migrating Data Using Federated Live Migration. 11

·            Performing Failback During Federated Live Migration. 23

·            Removing External Identity and Geometry following Federated Live Migration. 30

 


 

·       Preparing SAN to Support Federated Live Migration

 

 

Overview

Perform the following steps to prepare the SAN to support Federated Live Migration (FLM).

 

! 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 SymmetrixArray Controls CLI 7.6 Product Guide
  • EMC Federated Live Migration Technical Overview Technical Notes

 

These documents can be obtained from EMC Online Support at:

 http://support.EMC.com

 

All SYMCLI commands listed in this procedure can be executed from the Solutions Enabler Control Host.

 

1.   

Verify that the application host and source devices are configured to support FLM

Identify the application host where FLM will be used.

 

Validate that the platform (host type), operating system, host bus adapter, driver, infrastructure software (multipath solution), server LVM, and file system are supported in the FLM Simple Support Matrix.

 

Identify the source devices for FLM migration. Record the source director WWNs for use in step 3 (Configure SAN zoning for the FLM migration). Record the FA port settings to ensure that they are the same for all source ports and are configured identically for the target FA ports in step 2.

 

Important: Observations of host_passive/host_active change performance suggest limiting the number of source devices on a single host participating in an FLM session to 32 devices.

 

Use the symdev command to identify the source device (0720, 075F, 076B, and 07E9) FA director ports. The director ports for multiple devices used by the same application should be the same. For example for device 720:

 

symdev -sid 76 list -range 720:720 -multiport

 

Symmetrix ID: 000187490076

 

                      M U L T I - P O R T      D E V I C E S

 

     Device Name           Directors                   Device

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

                                                                        Cap

Physical            Sym  SA :P DA :IT  Config        Attribute    Sts   (MB)

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

 

                    0720       01B:D8  2-Way Mir     N/Grp'd  (M) RW    3750

Not Visible            - 14C:0      -  -             -            -        -

Not Visible            - 14C:1      -  -             -            -        -

 

Use the symcfg list command to identify the FA director port WWNs.

 

symcfg -sid 76 list -fa 14c -p 0

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

 

    FA-14C  0    5006048ACB37C70D  Yes      No           Yes

 

symcfg -sid 76 list -fa 14c -p 1

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

 

    FA-14C  1    5006048ACB37C72D  Yes      No           Yes

 

Use the symcfg list -v command to identify the port flag settings for each of the source and target FA ports. Make note of these port flag settings.

 

symcfg -sid 76 list -fa 14c -p 0 -v

 

Symmetrix ID: 000187490076

Time Zone   : Eastern Standard Time

 

    Product Model                        : 1000S-M2

    Symmetrix ID                         : 000187490076

. . .

          SCSI Flags

            {

              Negotiate_Reset(N)           : Disabled

              Soft_Reset(S)                : Disabled

              Environ_Set(E)               : Disabled

              HP3000_Mode(B)               : Disabled

              Common_Serial_Number(C)      : Enabled

              Disable_Q_Reset_on_UA(D)     : Enabled

              Sunapee(SCL)                 : Disabled

              Siemens(S)                   : Disabled

              Sequent(SEQ)                 : Disabled

              Avoid_Reset_Broadcast(ARB)   : Disabled

              Server_On_AS400(A4S)         : Disabled

              SCSI_3(SC3)                  : Enabled

              SPC2_Protocol_Version(SPC2)  : Enabled

              SCSI_Support1(OS2007)        : Enabled

            }

 

          Fibre Specific Flags

            {

              Volume_Set_Addressing(V)     : Disabled

              Non_Participating(NP)        : Disabled

              Init_Point_to_Point(PP)      : Enabled

              Unique_WWN(UWN)              : Enabled

              VCM_State(VCM)               : Enabled

              OpenVMS(OVMS)                : Disabled

              AS400(AS4)                   : Disabled

              Auto_Negotiate(EAN)          : Enabled

            }

 

Note: Different host operating systems present the FA flags differently. Refer to the E-Lab™ matrix for the available port flags for your host.

 

HBA port flags can be set on a per-initiator basis or by host name. Therefore, it is necessary to check for port overrides.

 

For 5875 source arrays:

Use the symaccess show command to identify any applicable port overrides for the application host WWNs.

 

symaccess -sid 517 show flm_ig -type init -detail

 

Symmetrix ID          : 000187490076

 

Initiator Group Name  : flm_ig

Last update time      : 10:21:16 AM on Wed Nov 21,2012

 

Group last update time: 10:21:16 AM on Wed Nov 21,2012

 

Port Flag Overrides   : Yes

  Enabled             : SPC2_Protocol_Version(SPC2)

  Disabled            : N/A

Consistent Lun        : No

 

   Originator Port wwn  : 21000024ff3e93d0

   User-generated Name  : 21000024ff3e93d0/21000024ff3e93d0

   FCID Lockdown        : No

   Heterogeneous Host   : No

   Port Flag Overrides  : Yes

     Enabled            : SPC2_Protocol_Version(SPC2)

     Disabled           : N/A

   CHAP Enabled         : N/A

   Type                 : Fibre

 

For 5671 and 5773 source arrays:

Use the symmaskdb list -v command to identify any applicable port overrides for the application host WWNs.

 

symmaskdb list db -sid 76 -v

 

Symmetrix ID            : 000187490076

 

Database Type           : Type5

Last updated at         : 04:28:16 PM on Mon Jan 31,2011

 

. . .

 

Director Identification : FA-14C

Director Port           : 0

 

. . .

 

   Originator Port wwn  : 10000000c953f9f3

   Type                 : Fibre

   User-generated Name  : win_flm/10000000c953f9f3

   Visibility           : No

   FCID Lockdown        : No

   Lun Offset           : No

   Heterogeneous Host   : No

   Port Flag Overrides  : Yes

     Enabled            : SPC2_Protocol_Version(SPC2) 

     Disabled           : N/A

   Dynamic Addressing   : N/A

   Authentication State : N/A

   Devices              : 0720 075F 076B 07E9

 

. . .

 

 

2.   

Identify and configure the target devices

Identify the FLM target array. The FLM target array must run Enginuity™ 5875 and higher to support FLM. In this example, Symmetrix ID (SID) 000194900275 is used.

 

Identify the target FA ports for the front-end interface to the application host. These ports will become active at the start of the FLM migration. In this example, FA ports FA07E:0 and FA08E:0 are used.

 

Ensure that the port settings for these ports are identical to the source port settings recorded in step 1, including setting any hba_flags or ig_flags overrides with the symaccess command.

 

Identify the target FA director port WWNs to be used for zoning in step 3 with the symcfg list command.

 

symcfg -sid 75 list -fa 7e -p 0

. . .

    Dir    Port  WWN                VCM      Volume Set   Pnt to Pnt

                                    Enabled  Addressing

 

    FA-7E   0    50000972c0044d18   Yes      No           Yes

 

symcfg -sid 75 list -fa 8e -p 0

. . .

    FA-8E   0    50000972c0044d1c   Yes      No           Yes

 

Identify the target devices for FLM migration. FLM target devices must be of equal or larger capacity than the FLM source devices identified in step 1. Identify one target device for each source device. In this example, devices 0328, 0329, 032A, and 032B are used.

 

Map, but do not mask, the target devices to the identified target ports.

 

symconfigure -sid 75 -cmd "map dev 328:32b to dir 7e:0 lun=1; map dev 328:32b to dir 8e:0 lun=1;" commit

 

! WARNING: Unlike when using Open Replicator for a non-FLM session, FLM target devices should not be added to any Auto-provisioning masking views at this point!

 

Configure zoning to make the target FA ports visible to the application host initiator ports.

 

3.   

Configure SAN zoning for the FLM migration

For each fabric, create a zone from the FLM target FA ports, which are identified in step 2, to the FLM source FA ports, which are identified in step 1. One-to-one zoning should be specified.

 

The FLM source devices must be visible to each FLM target FA port where the FLM target devices are mapped.

 

The following example is an excerpt of the Connectrix® Manager Zoning verification screen with the two zones defined.

.

zoning

 

 

4.   

Add migration device masking for the FLM target FA ports to access the FLM source devices

 

For 5875 source arrays:

Use the symaccess add devs command to add FLM target visibility for the source devices.

 

symaccess -sid 76 -name ors_ig –type initiator create

 

symaccess -sid 76 -name ors_ig -wwn 50000972c0044d18 –type initiator add

 

symaccess -sid 76 -name ors_ig -wwn 50000972c0044d1c –type initiator add

 

symaccess -sid 76 create view –name ors_mv –sg flm_sg –pg flm_pg ig ors_ig

 

 

Use the symaccess show command to verify that the FLM source devices are masked to the application host and the FLM target array.

 

symaccess -sid 76 -type storage show flm_sg

 

Symmetrix ID                : 000187490076

 

Storage Group Name          : flm_sg

Last update time            : 01:29:35 PM on Thu Sep 20,2012

Group last update time      : 01:29:35 PM on Thu Sep 20,2012

 

   Number of Storage Groups : 0

   Storage Group Names      : None

 

   Devices                  : 0720,075F,07B6,07E9

 

   Masking View Names

     {

       ors_mv

       flm_mv

     }

 

For 5671 and 5773 source arrays:

Use the symmask add devs command to add FLM target visibility for the source devices.

 

symmask -sid 76 -dir 14c -p 0 -wwn 50000972c0044d18 add devs 0720,075F,07B6,07E9

 

symmask -sid 76 -dir 14c -p 1 -wwn 50000972c0044d1c add devs 0720,075F,07B6,07E9

 

Use the symmask refresh command on the FLM source array to trigger all records within the database to be pushed out to the local directors.

 

symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the FLM source devices are masked to the application host and the FLM target array.

 

symmaskdb -sid 76 list assignment -devs 0720,075F,07B6,07E9

 

Symmetrix ID : 000187490076

 

Device  Identifier        Type   Dir:P

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

0720    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

075F    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

07B6    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

07E9    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

        10000000c953f9f3  FIBRE  FA-14C:0,FA-14C:1

 

5.   

Verify FLM migration visibility of the FLM source devices from each FLM target FA port

Use the symsan command for each FLM target FA port identified in step 2 to confirm that the remote LUNs are visible.

 

symsan -sid 75 -dir 7e -p 0 list -sanports -detail

 

Symmetrix ID: 000194900275

 

      Flags                                Num                              Remote

DIR:P   I   Vendor        Array            LUNs Remote Port WWN             DIR:P

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

07E:0   .   EMC Symmetrix 000187490076        5 5006048ACB37C70D            14C:0

 

Legend:

 Flags: (I)ncomplete : X = record is incomplete, . = record is complete.

 

 

symsan -sid 75 -dir 7e -p 0 -wwn 5006048ACB37C70D list -sanluns

 

Symmetrix ID:      000194900275

Remote Port WWN:   5006048ACB37C70D

 

      ST

       A

       T  Flags  Block   Capacity   LUN   Dev  LUN

DIR:P  E ICRTHS  Size      (MB)     Num   Num  WWN

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

07E:0 WD ...F.X    512          45     0  07ED 6006048000018749007653594D374544

07E:0 RW ...F.X    512        3750     6  0720 6006048000018749007653594D373230

07E:0 RW ...F.X    512        3750    36  075F 6006048000018749007653594D373546

07E:0 RW ...F.X    512        3750    6C  07B6 6006048000018749007653594D374236

07E:0 RW ...F.X    512         938    96  07E9 6006048000018749007653594D374539

 

Legend:

 Flags: (I)ncomplete : X = record is incomplete, . = record is complete.

        (C)ontroller : X = record is controller, . = record is not controller.

        (R)eserved   : X = record is reserved, . = record is not reserved.

        (T)ype       : A = AS400, F = FBA, C = CKD, . = Unknown

        t(H)in       : X = record is a thin dev, . = record is not a thin dev.

        (S)ymmtrix   : X = Symmetrix device, . = not Symmetrix device.

 

 

symsan -sid 275 -dir 8e -p 0 list -sanports -detail

 

Symmetrix ID: 000194900275

 

      Flags                                Num                              Remote

DIR:P   I   Vendor        Array            LUNs Remote Port WWN             DIR:P

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

08E:0   .   EMC Symmetrix 000187490076        5 5006048ACB37C72D            14C:1

. . .

 

symsan -sid 275 -dir 8e -p 0 -wwn 5006048ACB37C72D list -sanluns

 

Symmetrix ID:      000194900275

Remote Port WWN:   5006048ACB37C72D

 

      ST

       A

       T  Flags  Block   Capacity   LUN   Dev  LUN

DIR:P  E ICRTHS  Size      (MB)     Num   Num  WWN

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

08E:0 WD ...F.X    512          45     0  07ED 6006048000018749007653594D374544

08E:0 RW ...F.X    512        3750     6  0720 6006048000018749007653594D373230

08E:0 RW ...F.X    512        3750    36  075F 6006048000018749007653594D373546

08E:0 RW ...F.X    512        3750    6C  07B6 6006048000018749007653594D374236

08E:0 RW ...F.X    512         938    96  07E9 6006048000018749007653594D374539

. . .

 

 

6.   

Adjust the ORS ceiling on the FLM target FA ports to the recommended values

Use the symrcopy list ceiling command to list the current ceiling settings.

 

symrcopy -sid 275 list ceiling

 

Symmetrix ID: 000194900275

 

    Symmetrix Remote Copy Bandwidth Ceiling

 

                   Max   Set   Actual

            Dir:P  (MB)  (%)    (MB)

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

            07E:0   150  NONE       0

            07E:1   150  NONE       0

            08E:0   150  NONE       0

            08E:1   150  NONE       0

            07F:0   150  NONE       0

            07F:1   150  NONE       0

            08F:0   150  NONE       0

            08F:1    80  NONE       0

            07G:0   300  NONE       0

            07G:1   300  NONE       0

            08G:0   150  NONE       0

            08G:1   150  NONE       0

 

The default ceiling value is NONE. For FLM, EMC recommends setting the ceiling limits for the target FA ports for a 5671 source array to 20 percent, and to 40 percent for a 5773 and higher source array.

 

Use the symrcopy set ceiling command to set the ceiling for the target FA ports.

 

 

symrcopy -sid 275 -dir 7e -p 0 set ceiling 20

 

'Set Ceiling' operation execution is in progress

'Set Ceiling' operation successfully executed

 

symrcopy -sid 275 -dir 8e -p 0 set ceiling 20

 

'Set Ceiling' operation execution is in progress

'Set Ceiling' operation successfully executed

 

Use the symrcopy list ceiling command to verify that the ceiling settings are set as recommended.

 

symrcopy -sid 275 list ceiling

 

Symmetrix ID: 000194900275

 

    Symmetrix Remote Copy Bandwidth Ceiling

 

                   Max   Set   Actual

            Dir:P  (MB)  (%)    (MB)

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

            07E:0   150    20       0

            07E:1   150    20       0

            08E:0   150    20       0

            08E:1   150    20       0

            07F:0   150  NONE       0

            07F:1   150  NONE       0

            08F:0   150  NONE       0

            08F:1    80  NONE       0

            07G:0   300  NONE       0

            07G:1   300  NONE       0

            08G:0   150  NONE       0

            08G:1   150  NONE       0

 

7.   

Create an FLM pair file

Use a text-editing tool to create a pair file in the format of a standard Open Replicator pull session to specify the FLM source and target devices.

 

In this pair file example, the first column should contain the FLM target device using either the format symdev=<array_id>:<device_id> or wwn=<device_wwn>.


The second column should contain the FLM source device using either the format
symdev=<array_id>:<device_id> or wwn=<device_wwn>.

 

## FLM PAIR FILE

##

## COLUMN1: FLM Target [ VMAX - 5875 ]

## COLUMN2: FLM Source [ DMX  - 5671 ]

 

symdev=000194900275:0328 symdev=000187490076:0720

symdev=000194900275:0329 symdev=000187490076:075F

symdev=000194900275:032A symdev=000187490076:07B6

symdev=000194900275:032B symdev=000187490076:07E9

 

This file will be used to manage the FLM migration.

 

 

 

 

·       Migrating Data Using Federated Live Migration

 

 

Overview

Perform the following steps to migrate data using Federated Live Migration (FLM) on a Clustered Windows application host with EMC PowerPath® 5.x.

 

! 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!

 

Note: FLM migration for the Windows cluster quorum has been tested and is supported. This document provides steps for migrating the quorum with or without the use of FLM, however, it is recommended that a backup of the quorum is performed prior to executing either option.

 

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 76 Product Guide
  • EMC Solutions Enabler Symmetrix Array Controls CLI 7.6 Product Guide
  • EMC PowerPath for Windows Installation and Administration Guide
  • EMC Federated Live Migration Technical Overview Technical Notes

 

These documents can be obtained from EMC Online Support at:

 http://support.EMC.com

 

 

8.      

Create the FLM session

From the Solutions Enabler control host:

 

Use a pair file, formatted as you would a standard ORS pull session pair file, to specify the FLM source and target devices.

 

## FLM PAIR FILE

##

## COLUMN1: FLM Target [ VMAX - 5876 ]

## COLUMN2: FLM Source [ DMX  - 5671 ]

 

symdev=000194900275:0328 symdev=000187490076:0720

symdev=000194900275:0329 symdev=000187490076:075F

symdev=000194900275:032A symdev=000187490076:07B6

symdev=000194900275:032B symdev=000187490076:07E9

 

Use the symrcopy create –pull -migrate command with the –mp_type parameter PPath to create a NoCopy FLM session with the devices specified by the FLM pair file. The –mp_type parameter is required for –host_type Windows.

 

C:\> symrcopy -f win_flm create -pull -migrate -host_type windows -mp_type ppath

 

'Create' operation execution is in progress for the device list

in device file 'win_flm'. Please wait...

 

'Create' operation successfully executed for the device list

in device file 'win_flm'.

 

Executing this command  performs the following:

·     FLM VMAX ® target devices are set to passive host access mode.

·     FLM VMAX target devices assume the external identity of the FLM source devices.

·     FLM VMAX target devices assume the external geometry of the FLM source devices (if necessary).

 

The FLM VMAX target FA ports externally display a two-port offset for FLM target devices. As an example, VMAX devices mapped to FA 07F:0 and FA 08F:1 are externally displayed on FA 07F:2 and FA 08F:3.

 

! Warning: Cluster Shared Volumes (CSVs) are not supported devices in a Federated Live Migration session. Verify that CSVs are not included in the previous pair file!

 

 

9.      

Verify the created FLM session

From the Solutions Enabler control host:

 

Use the symrcopy query command to verify that the FLM pairs are listed as migration sessions in the Created state. The value of M for type (T) in the Flags column indicates that the session is an FLM migration session.

 

C:\> symrcopy -f win_flm query

 

Device File Name      : win_flm

 

       Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328      60000 000187490076:0720        SD ...XXM. Created         N/A

000194900275:0329      60000 000187490076:075F        SD ...XXM. Created         N/A

000194900275:032A      60000 000187490076:07B6        SD ...XXM. Created         N/A

000194900275:032B      15000 000187490076:07E9        SD ...XXM. Created         N/A

 

Total              ---------

  Track(s)            195000

  MB(s)              12187.5

 

Legend:

R:  (Remote Device Vendor Identification)

  S = Symmetrix, C = Clariion, . = Unknown.

 

I:  (Remote Device Specification Identifier)

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

 

Flags:

(C): X = The background copy setting is active for this pair.

     . = The background copy setting is not active for this pair.

(D): X = The session is a differential copy session.

     . = The session is not a differential copy session.

(S): X = The session is pushing data to the remote device(s).

     . = The session is pulling data from the remote device(s).

(H): X = The session is a hot copy session.

     . = The session is a cold copy session.

(U): X = The session has donor update enabled.

     . = The session does not have donor update enabled.

(T): M = The session is a migration session.

     R = The session is a RecoverPoint session.

     S = The session is a standard ORS session.

(Z): X = The session has front-end zero detection enabled.

     . = The session does not have front-end zero detection enabled.

(*): The failed session can be reactivated.

 

 

10.   

Verify the external identity, and optional external geometry, on the FLM VMAX target devices

From the Solutions Enabler control host:

 

Use the symdev list –identity command to verify that the target devices are now presenting the identity of the source devices. Use –range to specify a range of devices.

 

C:\> symdev -sid 275 list -identity -range 0328:032B

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

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

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

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

 

0328 Not Visible TDEV          RW  XX  000187490076   00720 7600720000     3750

0329 Not Visible TDEV          RW  XX  000187490076   0075F 760075F000     3750

032A Not Visible TDEV          RW  XX  000187490076   007B6 76007B6000     3750

032B Not Visible TDEV          RW  XX  000187490076   007E9 76007E9000      938

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

All the fields listed under the External Identity column for each device must match the associated source devices. In this example, the value of X under (I)dentity and (G)eometry in the FLG column indicates that the FLM target devices have both user-defined external identity and geometry.

 

 

11.   

Mask VMAX target devices to the application host

From the Solutions Enabler control host:

 

Use the symaccess command to create or modify a masking view to add application-host visibility for the VMAX target devices with Symmetrix® DMX™ source external identity.

 

C:\> symaccess –sid 275 create view -name win_flm_mv -sg win_flm_sg -pg win_flm_pg  -ig win_flm_ig

 

Use the symaccess show view command to verify that the target devices are properly configured in the Auto-provisioning Group.

 

C:\> symaccess -sid 275 show view win_flm_mv

 

Symmetrix ID          : 000194900275

 

Masking View Name     : win_flm_mv

Last updated at       : 12:36:37 PM on Tue Jan 04,2011

 

Initiator Group Name  : win_flm_ig

 

   Host Initiators

     {

       WWN  : 210000e08b1e45f9

     }

 

Port Group Name       : win_flm_pg

 

   Director Identification

     {

       FA-7E:0

       FA-8E:0

     }

 

Storage Group Name    : win_flm_sg

 

Sym Dev                                 Host

Name    Dir:P  Physical Device Name      Lun  Attr  Cap(MB)

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

0328    08E:0  Not Visible                 1           8631

        07E:0  Not Visible                 1

0329    08E:0  Not Visible                 2           8631

        07E:0  Not Visible                 2

032A    08E:0  Not Visible                 3           8631

        07E:0  Not Visible                 3

032B    08E:0  Not Visible                 4           8631

        07E:0  Not Visible                 4

                                                    -------

Total Capacity                                        34524

 

 

12.   

Perform  a host SCSI rescan to discover the VMAX target device paths presented as DMX source devices

Perform a host SCSI rescan to discover and configure the VMAX target device paths presenting as DMX source external device identity in PowerPath.

 

From the first node of the application cluster:

 

1. Click Start.

2. Click Run.

3. Type devmgmt.msc to open the Device Manager.

4. Right-click the root of the device tree (generally noted by the name of the host), and select Scan for hardware changes.

You may also perform a rescan from the command line by issuing the following commands:

C:\>diskpart

DISKPART>rescan

 

Note: Repeat this procedure on all the nodes in the cluster.

 

 

13.   

Verify the external device identity of the VMAX target device paths, and save the PowerPath configuration

Repeat the following on all the nodes in the application cluster:

 

Use powermt display dev=all to verify that the target paths have been configured as alternate paths to the source devices.

 

Because of the two-port offset, the FLM target device paths are displayed on the storage interfaces ending either in C or D.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun6    c5t10d6   FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun6    c5t11d6   FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun1     c5t4d1    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun1     c5t6d1    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun54   c5t10d54  FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun54   c5t11d54  FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun2     c5t4d2    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun2     c5t6d2    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun108  c5t10d108 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun108  c5t11d108 FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun3     c5t4d3    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun3     c5t6d3    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=1

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun150  c5t10d150 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun150  c5t11d150 FA 14cB   active  alive      1      0

   5 port5\path0\tgt4\lun4     c5t4d4    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun4     c5t6d4    FA  8eC   active  alive      0      0

 

If any path, other than the expected paths, reports a dead state, examine the cause before continuing.

 

After confirming that the target paths are available for all migration source devices on all cluster nodes, use powermt save command to save the running PowerPath configuration.

 

C:\> powermt save

 

 

14.   

Activate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy activate -migrate command to activate the FLM session with the devices specified by the FLM pair file.

 

C:\> symrcopy -f win_flm activate -migrate

 

'Activate' operation execution is in progress for the device list

in device file 'win_flm'. Please wait...

 

'Activate' operation successfully executed for the device list

in device file 'win_flm'.

 

Executing this command performs the following:

·     FLM VMAX target devices are set to active host access mode.

·     FLM DMX source devices are set to passive host access mode.

·     FLM session is set to Copy mode.

 

 

15.   

Verify the FLM pair status

From the Solutions Enabler control host:

 

Use the symrcopy query command to verify that the FLM pair’s status is either CopyInProg or Copied.

 

C:\> symrcopy -f win_flm query

 

 

 

 

 

     

 Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328      56252 000187490076:0720        SD X..XXM. CopyInProg        6

000194900275:0329      57358 000187490076:075F        SD X..XXM. CopyInProg        4

000194900275:032A      56592 000187490076:07B6        SD X..XXM. CopyInProg        5

000194900275:032B      12077 000187490076:07E9        SD X..XXM. CopyInProg       19

 

Total              ---------

  Track(s)            182279

  MB(s)              11392.4

.  .  .

 

 

16.   

Verify the cutover on the application host

From a node in the application cluster:

 

Use powermt display dev=all to verify the cutover. Activate sets the target devices to host access mode active and the source devices to host access mode passive.

 

Because of the two-port offset, the FLM target device paths are displayed on storage interfaces ending either in C or D.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun6    c5t10d6   FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun6    c5t11d6   FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun1     c5t4d1    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun1     c5t6d1    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun54   c5t10d54  FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun54   c5t11d54  FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun2     c5t4d2    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun2     c5t6d2    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun108  c5t10d108 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun108  c5t11d108 FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun3     c5t4d3    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun3     c5t6d3    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun150  c5t10d150 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun150  c5t11d150 FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun4     c5t4d4    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun4     c5t6d4    FA  8eC   active  alive      0      0

 

If any path, other than the expected paths, reports a dead state, examine the cause before continuing.

 

 

17.   

Monitor the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy query command to query the status of the FLM migration for the devices specified by the FLM pair file. The pair’s status will be either CopyInProg or Copied.

 

C:\> symrcopy -f win_flm query

 

Device File Name      : win_flm

       Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328      45580 000187490076:0720        SD X..XXM. CopyInProg       24

000194900275:0329      45399 000187490076:075F        SD X..XXM. CopyInProg       24

000194900275:032A      45411 000187490076:07B6        SD X..XXM. CopyInProg       24

000194900275:032B        550 000187490076:07E9        SD X..XXM. CopyInProg       96

Total              ---------

 

  Track(s)            136940

  MB(s)               8558.8

. . .

 

 

18.   

Verify that the FLM session is Copied

From the Solutions Enabler control host:

 

Use the symrcopy query command to query the status of the FLM migration for the devices specified by the FLM pair file, and confirm the copy is complete. The status of the pairs will be Copied.

 

C:\> symrcopy -f win_flm query

 

Device File Name      : win_flm

 

       Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328          0 000187490076:0720        SD X..XXM. Copied          100

000194900275:0329          0 000187490076:075F        SD X..XXM. Copied          100

000194900275:032A          0 000187490076:07B6        SD X..XXM. Copied          100

000194900275:032B          0 000187490076:07E9        SD X..XXM. Copied          100

 

Total              ---------

  Track(s)                 0

  MB(s)                  0.0

. . .

 

Use the symrcopy verify command to confirm that all pairs are in a Copied state.

 

C:\> symrcopy -f win_flm verify

 

All device(s) in the list are in 'Copied' state.

 

 

19.   

Terminate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy terminate -migrate command to terminate and finalize the FLM migration for the devices specified by the FLM pair file.

 

Note: Once the session is terminated, the DMX source device no longer receives Donor Update writes. As a result, you no longer have the ability to fail back to the old source device.

 

C:\> symrcopy -f win_flm terminate -migrate

 

'Terminate' operation execution is in progress for the device list

in device file 'win_flm'. Please wait...

 

'Terminate' operation successfully executed for the device list

in device file 'win_flm'.

 

Terminating the FLM session performs the following:

·     ORS hot pull, donor update session is terminated.

·     FLM source devices remain in a passive host access mode.

·     FLM target devices remain in an active host access mode.

 

 

20.   

Remove masking for the source devices

From the Solutions Enabler control host:

 

For 5875 source array:

Use the symaccess command to delete or modify a masking view to remove application-host visibility for the VMAX source devices. Use the -unmap flag when deleting or modifying the masking view to unmap the devices as part of the Auto-provisioning change.

 

# symaccess -sid 076 delete view -name win_flm_mv -unmap

 

Use the symaccess list command to verify that the source devices have been removed from all masking views. The view count should be zero (0) for each FLM source device.

 

# symaccess -sid 076 list -type storage -devs 0720,075F,07B6,07E9

 

Symmetrix ID          : 000192602076

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

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

0720   win_flm_mv                            4      0

075F  win_flm_mv                            4      0

07B6  win_flm_mv                            4      0

07E9  win_flm_mv                            4      0

 

Use the symdev list –noport command to verify that the source devices are not mapped. Use –range to filter on a specific range of devices.

 

# symdev -sid 076 list -range 04CA:04CD -noport

 

Symmetrix ID: 000192602076

 

        Device Name           Directors                  Device

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

                                                                           Cap

Sym  Physical               SA :P DA :IT  Config        Attribute    Sts   (MB)

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

 

0720 Not Visible            ???:? 10B:C8  2-Way Mir     N/Grp'd      RW     898

075F Not Visible            ???:? 10A:D4  RAID-5        N/Grp'd      RW     898

07B6 Not Visible            ???:? 10D:D1  2-Way Mir     N/Grp'd      RW     898

07E9 Not Visible            ???:? 07D:D4  RAID-5        N/Grp'd      RW     898

 

For 5671 and 5773 source arrays:

Use the symmask remove devs command to remove application-host visibility for the source devices.

 

C:\> symmask -sid 076 -dir 14c -p 0 -wwn 10000000c953f9f3 remove devs 0720,075F,07B6,07E9

 

C:\> symmask -sid 076 -dir 14c -p 1 -wwn 10000000c953f9f3 remove devs 0720,075F,07B6,07E9

 

C:\> symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the source devices are no longer masked to the application host.

 

C:\> symmaskdb -sid 076 list assignment -devs 0720,075F,07B6,07E9

 

Symmetrix ID : 000187490076

 

Device  Identifier        Type   Dir:P

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

0720    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

075F    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

07B6    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

07E9    50000972c0044d18  FIBRE  FA-14C:0

        50000972c0044d1c  FIBRE  FA-14C:1

 

In this example, the only remaining source-device masking is the storage-to-storage masking, which facilitates the FLM migration.

 

Use the symmask remove devs command to remove the FLM target visibility for the source devices.

 

C:\> symmask -sid 076 -dir 14c -p 0 -wwn 50000972c0044d18 remove devs 0720,075F,07B6,07E9

 

C:\> symmask -sid 076 -dir 14c -p 1 -wwn 50000972c0044d1c remove devs 0720,075F,07B6,07E9

 

C:\> symmask -sid 076 refresh

 

Symmetrix FA/SE directors updated with contents of SymMask Database 000187490076

 

Use the symmaskdb list assignment command to verify that the source devices are no longer masked.

 

C:\> symmaskdb -sid 076 list assignment -devs 0720,075F,07B6,07E9

 

No device masking database records could be found for the specified input parameters

 

 

21.   

Perform  a host SCSI rescan, and remove the source device paths

Perform a host SCSI rescan to discover and configure the VMAX target device paths presenting DMX source device external identity in PowerPath.

 

From the first node of the application cluster:

 

1. Click Start.

2. Click Run.

3. Type devmgmt.msc to open Device Manager.

4. Right-click the root of the device tree (generally noted by the name of the host), and select Scan for hardware changes.

You may also perform a rescan from the command line by issuing the following commands:

C:\>diskpart

DISKPART>rescan

 

Note: Repeat this procedure on all the nodes in the cluster.

 

Once the rescan completes, use powermt display remove dev=all to remove the source paths from the PowerPath configuration. PowerPath only removes paths that Windows has identified as no longer accessible. The rescan ensures that Windows has an accurate assessment of the accessible devices.

C:\> powermt remove dev=all

 

Cannot remove device that is in use: c5t4d1

Cannot remove device that is in use: c5t4d2

Cannot remove device that is in use: c5t4d3

Cannot remove device that is in use: c5t4d4

Cannot remove device that is in use: c5t6d1

Cannot remove device that is in use: c5t6d2

Cannot remove device that is in use: c5t6d3

Cannot remove device that is in use: c5t6d4

 

Note: Repeat this procedure on all the nodes in the cluster.

 


22.   

Verify that the source device paths are removed, and save the PowerPath configuration

From the first node of the application cluster:

 

Use powermt display dev=all to verify that the source paths have been removed from PowerPath. The only paths displayed for each migrated device should be the VMAX target paths presenting DMX external device identity. All paths should be active and alive.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

 

 

 

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun1     c5t4d1    FA  7eC   active  alive      0      1

   5 port5\path0\tgt6\lun1     c5t6d1    FA  8eC   active  alive      0      1

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun2     c5t4d2    FA  7eC   active  alive      0      1

   5 port5\path0\tgt6\lun2     c5t6d2    FA  8eC   active  alive      0      1

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun3     c5t4d3    FA  7eC   active  alive      0      1

   5 port5\path0\tgt6\lun3     c5t6d3    FA  8eC   active  alive      0      1

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun4     c5t4d4    FA  7eC   active  alive      0      1

   5 port5\path0\tgt6\lun4     c5t6d4    FA  8eC   active  alive      0      1

 

The errors listed against each path indicate the state change during the cutover. Use powermt restore to have PowerPath check each path, and clear the errors.

 

C:\> powermt restore

 

Use powermt display dev=all to verify that there are no errors listed against any migrated device.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun1     c5t4d1    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun1     c5t6d1    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

 

 

 

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun2     c5t4d2    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun2     c5t6d2    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun3     c5t4d3    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun3     c5t6d3    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt4\lun4     c5t4d4    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun4     c5t6d4    FA  8eC   active  alive      0      0

 

After confirming that the configuration is error free, use powermt save to save the running PowerPath configuration.

 

C:\> powermt save

 

Note: Repeat this procedure on all the nodes in the cluster.

 

 

 

7Table of Contents

·       Performing Failback During Federated Live Migration

 

 

Overview

Perform the following steps to fail back during Federated Live Migration (FLM) on a Clustered Windows application host with EMC PowerPath 5.x.

 

! 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
  • EMC PowerPath for Windows Installation and Administration Guide
  • EMC Federated Live Migration Technical Overview Technical Notes

 

These documents can be obtained from EMC Online Support at:

 http://support.EMC.com

 

 

23.  

Verify that the FLM session is in a state permitting failback

From the Solutions Enabler control host:

 

Use the symrcopy query command to verify that the FLM pair’s status is either CopyInProg or Copied.

 

C:\> symrcopy -f win_flm query

 

Device File Name      : win_flm

 

       Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328      45580 000187490076:0720        SD X..XXM. CopyInProg       24

000194900275:0329      45399 000187490076:075F        SD X..XXM. CopyInProg       24

000194900275:032A      45411 000187490076:07B6        SD X..XXM. CopyInProg       24

000194900275:032B        550 000187490076:07E9        SD X..XXM. CopyInProg       96

 

Total              ---------

  Track(s)            136940

  MB(s)               8558.8

 

Legend:

R:  (Remote Device Vendor Identification)

  S = Symmetrix, C = Clariion, . = Unknown.

 

I:  (Remote Device Specification Identifier)

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

 

Flags:

(C): X = The background copy setting is active for this pair.

     . = The background copy setting is not active for this pair.

(D): X = The session is a differential copy session.

     . = The session is not a differential copy session.

(S): X = The session is pushing data to the remote device(s).

     . = The session is pulling data from the remote device(s).

(H): X = The session is a hot copy session.

     . = The session is a cold copy session.

(U): X = The session has donor update enabled.

     . = The session does not have donor update enabled.

(T): M = The session is a migration session.

     R = The session is a RecoverPoint session.

     S = The session is a standard ORS session.

(Z): X = The session has front-end zero detection enabled.

     . = The session does not have front-end zero detection enabled.

(*): The failed session can be reactivated.

 

 

24.  

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.

 

C:\> symrcopy -f win_flm failback -migrate

 

'Failback' operation execution is in progress for the device list

in device file 'win_flm'. Please wait...

 

'Failback' operation successfully executed for the device list

in device file 'win_flm'.

 

Use the symrcopy query command to verify that the status of the FLM pair is Failedback.

 

C:\> symrcopy -f win_flm query

 

Device File Name      : win_flm

 

       Control Device                  Remote Device      Flags      Status     Done

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

                   Protected

SID:symdev         Tracks    Identification           RI CDSHUTZ  CTL <=> REM    (%)

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

000194900275:0328      42267 000187490076:0720        SD X..XXM. Failedback      N/A

000194900275:0329      41775 000187490076:075F        SD X..XXM. Failedback      N/A

000194900275:032A      41972 000187490076:07B6        SD X..XXM. Failedback      N/A

000194900275:032B          0 000187490076:07E9        SD X..XXM. Failedback      N/A

 

Total              ---------

  Track(s)            126014

  MB(s)               7875.9

. . .

 

 

25.  

Verify failback on the application host

From the first node of the application cluster:

 

Use powermt display dev=all to verify the failback. The failback sets the target devices to host access mode passive and the source devices to host access mode active.

 

Because of the two-port offset, the FLM target device paths are displayed on the storage interfaces ending either in C or D.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun6    c5t10d6   FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun6    c5t11d6   FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun1     c5t4d1    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun1     c5t6d1    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun54   c5t10d54  FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun54   c5t11d54  FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun2     c5t4d2    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun2     c5t6d2    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun108  c5t10d108 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun108  c5t11d108 FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun3     c5t4d3    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun3     c5t6d3    FA  8eC   active  alive      0      0

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun150  c5t10d150 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun150  c5t11d150 FA 14cB   active  alive      0      0

   5 port5\path0\tgt4\lun4     c5t4d4    FA  7eC   active  alive      0      0

   5 port5\path0\tgt6\lun4     c5t6d4    FA  8eC   active  alive      0      0

 

If any path, other than the expected paths, reports a dead state, examine the cause before continuing.

 

 

26.  

Terminate the FLM session

From the Solutions Enabler control host:

 

Use the symrcopy terminate -migrate command to terminate the FLM session for the devices specified by the FLM pair file.

 

C:\> symrcopy -f win_flm terminate -migrate

 

'Terminate' operation execution is in progress for the device list

in device file 'win_flm'. Please wait...

 

'Terminate' operation successfully executed for the device list

in device file 'win_flm'.

 

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.

 

 


 

27.   

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. FLM target devices must be unmapped to remove the external identity and geometry.

 

C:\> symaccess –sid 275 delete view -name win_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.

 

C:\> symaccess -sid 275 list -devs 0328:032B -type storage

 

Symmetrix ID          : 000194900275

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

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

0328  win_flm_sg                            4      0

0329  win_flm_sg                            4      0

032A  win_flm_sg                            4      0

032B  win_flm_sg                            4      0

 

Use the symdev list –noport command to verify that the target devices are not mapped. Use –range to filter a specific range of devices.

 

C:\> symdev -sid 275 list –noport -range 0328:032B

 

Symmetrix ID: 000194900275

 

        Device Name           Directors                  Device

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

                                                                           Cap

Sym  Physical               SA :P DA :IT  Config        Attribute    Sts   (MB)

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

 

0328 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

0329 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

032A Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

032B Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

 

 


28.   

Perform a host SCSI rescan, and remove the VMAX target device paths

Perform a host SCSI rescan to discover if the VMAX target device paths are no longer present in PowerPath.

 

From the first node of the application cluster:

 

1. Click Start.

2. Click Run.

3. Type devmgmt.msc to open the Device Manager.

4. Right-click the root of the device tree (generally noted by the name of the host), and select Scan for hardware changes.

 

You may also perform a rescan from the command line by issuing the following commands:

C:\>diskpart

DISKPART>rescan

 

Once the rescan completes, use powermt display remove dev=all to remove the VMAX target paths from the PowerPath configuration. PowerPath only removes paths that Windows has identified as no longer accessible. The rescan ensures that Windows has an accurate assessment of accessible devices.

C:\> powermt remove dev=all

 

Cannot remove device that is in use: c5t10d108

Cannot remove device that is in use: c5t10d150

Cannot remove device that is in use: c5t10d54

Cannot remove device that is in use: c5t10d6

Cannot remove device that is in use: c5t11d108

Cannot remove device that is in use: c5t11d150

Cannot remove device that is in use: c5t11d54

Cannot remove device that is in use: c5t11d6

 

Note: Repeat this procedure on all of the nodes in the cluster.

 

 

29.   

Verify that the VMAX target device paths have been removed, and save the PowerPath configuration

From the first node of the application cluster:

 

Use powermt display dev=all to verify that the target paths have been removed.

 

C:\> powermt display dev=all

 

Pseudo name=harddisk14

Symmetrix ID=000187490076

Logical device ID=0720

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun6    c5t10d6   FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun6    c5t11d6   FA 14cB   active  alive      0      0

 

Pseudo name=harddisk15

Symmetrix ID=000187490076

Logical device ID=075F

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun54   c5t10d54  FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun54   c5t11d54  FA 14cB   active  alive      0      0

 

Pseudo name=harddisk16

Symmetrix ID=000187490076

Logical device ID=07B6

state=alive; policy=SymmOpt; priority=0; queued-IOs=0

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun108  c5t10d108 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun108  c5t11d108 FA 14cB   active  alive      0      0

 

Pseudo name=harddisk17

Symmetrix ID=000187490076

Logical device ID=07E9

state=alive; policy=SymmOpt; priority=0; queued-IOs=1

==============================================================================

---------------- Host ---------------   - Stor -   -- I/O Path -  -- Stats ---

### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors

==============================================================================

   5 port5\path0\tgt10\lun150  c5t10d150 FA 14cA   active  alive      0      0

   5 port5\path0\tgt11\lun150  c5t11d150 FA 14cB   active  alive      1      0

 

If any path, other than the expected paths, reports a dead state, examine the cause before continuing.

 

After confirming the expected path states, use the powermt save command to save the running PowerPath configuration.

 

C:\> powermt save

 

Note: Repeat this procedure on all of the nodes in the cluster.

 

 

30.   

Remove the external identity

From the Solutions Enabler control host:

 

Use the symconfigure command to remove the device’s 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.

 

C:\> type remove_external_identity.txt

 

set dev 0328:032B identity = no identity;

 

C:\> symconfigure -sid 275 -f remove_external_identity.txt commit

 

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.

 

 

31.   

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.

 

C:\> type remove_external_geometry.txt

 

set dev 0328:032B geometry = no geometry;

 

C:\> symconfigure -sid 275 -f remove_external_geometry.txt commit

 

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.

 

 

32.   

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.

 

C:\> symdev -sid 275 host_active -range 0328:032B

 

'Host Active' operation succeeded for devices in RANGE 328:32B.

 

 

 

7Table of Contents

·       Removing External Identity and Geometry following Federated Live Migration

 

 

Overview

Perform the following steps to remove the external identity and geometry following a Federated Live Migration (FLM) on a Clustered Windows application host with EMC PowerPath 5.x.

 

! 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
  • EMC PowerPath for Windows Installation and Administration Guide
  • EMC Federated Live Migration Technical Overview Technical Notes

 

These documents can be obtained from EMC Online Support at:

 http://support.EMC.com

 

 

 

33.  

Shut down all host applications on the cluster nodes with a dependency on the VMAX FLM target devices presenting DMX source device external identity

From the first node of the application cluster:

 

In order to facilitate the removal of the external identity of the source DMX, all I/O to the VMAX FLM target devices must be halted.

 

Note: Repeat this procedure on all the nodes in the cluster.

 

 

34.  

Remove masking and mapping for the VMAX target devices

 

Note: If a cluster quorum disk was not part of the FLM migration, refer to the Microsoft Knowledge Base for procedures to change the quorum-disk designation, if necessary. If the quorum disk was migrated using FLM, proceed to the next step in this procedure.

 

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 the external identity and geometry.

 

C:\> symaccess –sid 275 delete view -name win_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.

 

C:\> symaccess -sid 275 list -devs 0328:032B -type storage

 

Symmetrix ID          : 000194900275

 

Symm                                    Dev    View

Dev   Storage Group Name                Count  Count

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

0328  win_flm_sg                            4      0

0329  win_flm_sg                            4      0

032A  win_flm_sg                            4      0

032B  win_flm_sg                            4      0

 

Use the symdev list –noport command to verify that the target devices are not mapped. Use –range to specify a range of devices.

 

C:\> symdev -sid 275 list –noport -range 0328:032B

Symmetrix ID: 000194900275

 

        Device Name           Directors                  Device

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

                                                                           Cap

Sym  Physical               SA :P DA :IT  Config        Attribute    Sts   (MB)

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

 

0328 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

0329 Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

032A Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

032B Not Visible            ???:?  NA:NA  TDEV          N/Grp'd      RW    8631

 

 

35.  

Perform  a host SCSI rescan, and remove the VMAX target device paths

Perform a host SCSI rescan to discover if the VMAX target device paths are no longer present in PowerPath.

 

From the first node of the application cluster:

 

1. Click Start.

2. Click Run.

3. Type devmgmt.msc to open the Device Manager.

4. Right-click the root of the device tree (generally noted by the name of the host), and select Scan for hardware changes.

You may also perform a rescan from the command line by issuing the following commands:

C:\>diskpart

DISKPART>rescan

 

Once the rescan completes, use powermt display remove dev=all to remove the source paths from the PowerPath configuration. PowerPath only removes paths that Windows has identified as no longer accessible. The rescan ensures that Windows has an accurate assessment of accessible devices.

C:\> powermt remove dev=all

 

Note: Repeat this procedure on all the nodes in the cluster.

 

 

36.  

Remove the external identity

From the Solutions Enabler control host:

 

Use the symconfigure command to remove the device’s 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.

 

C:\> type remove_external_identity.txt

 

set dev 0328:032B identity = no identity;

 

C:\> symconfigure -sid 275 -f remove_external_identity.txt commit

 

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.

 

C:\> symdev -sid 275 list -identity -range 0328:032B

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

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

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

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

 

0328 Not Visible TDEV          RW  .X  000194900275   00328 7500328000     3750

0329 Not Visible TDEV          RW  .X  000194900275   00329 7500329000     3750

032A Not Visible TDEV          RW  .X  000194900275   0032A 750032A000     3750

032B Not Visible TDEV          RW  .X  000194900275   0032B 750032B000      938

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

37.  

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.

 

C:\> type remove_external_geometry.txt

 

set dev 0328:032B geometry = no geometry;

 

C:\> symconfigure -sid 275 -f remove_external_geometry.txt commit

 

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 listidentity 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.

 

C:\> symdev -sid 275 list -identity -range 0328:032B

 

Symmetrix ID: 000194900275

 

              Device               FLG            External Identity

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

Sym  Physical    Config        Sts IG  Array ID       Num   Ser Num    Cap (MB)

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

 

0328 Not Visible TDEV          RW  ..  000194900275   00328 7500328000     8631

0329 Not Visible TDEV          RW  ..  000194900275   00329 7500329000     8631

032A Not Visible TDEV          RW  ..  000194900275   0032A 750032A000     8631

032B Not Visible TDEV          RW  ..  000194900275   0032B 750032B000     8631

 

Legend:

  Flags:

   (I)dentity : X = The device has a non-native external identity set

                . = The device does not have an external identity set

   (G)eometry : X = The device has a user defined geometry

                . = The device does not have a user defined geometry

 

 

38.  

Add mapping and masking for the native VMAX devices

From the Solutions Enabler control host:

 

Use the symaccess command to create or modify a masking view to add application-host visibility for the VMAX target devices with native identity.

 

C:\> symaccess –sid 275 create view -name win_flm_mv -sg win_flm_sg -pg win_flm_pg  -ig win_flm_ig

 

Use the symaccess show view command to verify that the target devices are properly configured in the Auto-provisioning Group.

 

C:\> symaccess -sid 275 show view win_flm_mv

 

Symmetrix ID          : 000194900275

 

Masking View Name     : win_flm_mv