aix - mpio-gpfs - 02 - flm migration

MigratingDataUsingFLM_smc.001 Migrating Data Using Federated Live Migration

OverviewPerform the following steps to migrate data using Federated Live Migration (FLM) on a GPFS cluster or stand-alone AIX application host with Native MPIO.! 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 Federated Live Migration Technical Overview EMC Host Connectivity Guide for IBM AIXThese documents can be obtained from EMC Online Support at:

http://support.EMC.comAll SYMCLI commands listed in this procedure can be executed from the Solutions Enabler control host.

( Done

1. Create the FLM sessionFrom the Solutions Enabler control host:

Use a pair file in the format of a standard ORS pull session to specify the FLM source and target devices.

## FLM PAIR FILE

##

## COLUMN1: FLM Target [ VMAX - 5876 ]

## COLUMN2: FLM Source [ DMX - 5671 ]

symdev=000192602624:04CA symdev=000187490076:014E

symdev=000192602624:04CB symdev=000187490076:014F

symdev=000192602624:04CC symdev=000187490076:0150symdev=000192602624:04CD symdev=000187490076:0151Use the symrcopy create hot pull -migrate command to create a NoCopy FLM session with the devices specified by the FLM pair file.

# symrcopy -f aix_flm create hot -pull -migrate -host_type aix mp_type NATIVE'Create' operation execution is in progress for the device listin device file 'aix_flm'. Please wait...

'Create' operation successfully executed for the device list

in device file 'aix_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 FLM source devices. FLM VMAX target devices assume the external geometry of FLM source device (if necessary).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 will be externally displayed on FA 07F:2 and FA 08F:3.(

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

# symrcopy -f aix_flm queryDevice File Name : aix_flm

Control Device Remote Device Flags Status Done

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

Protected

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

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

000192602624:04CA 14370 000187490076:014E SD ...XXM. Created N/A

000192602624:04CB 14370 000187490076:014F SD ...XXM. Created N/A

000192602624:04CC 14370 000187490076:0150 SD ...XXM. Created N/A

000192602624:04CD 14370 000187490076:0151 SD ...XXM. Created N/A

Total ---------

Track(s) 57480

MB(s) 3592.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.

3. Verify the external identity, and optional external geometry, on the FLM VMAX target devicesFrom 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 filter a specific range of devices. # symdev -sid 624 list -range 04CA:04CD -identitySymmetrix ID: 000192602624 Device FLG External Identity

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

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

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

04CA Not Visible 2-Way Mir RW XX 000187490076 0014E 760014E000 898

04CB Not Visible RAID-5 RW XX 000187490076 0014F 760014F000 898

04CC Not Visible 2-Way Mir RW XX 000187490076 00150 7600150000 898

04CD Not Visible RAID-5 RW XX 000187490076 00151 7600151000 898

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

(

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

# symaccess -sid 624 create view -name aix_flm_mv -ig aix_flm_ig -pg aix_flm_pg -sg aix_flm_sgUse the symaccess show view command to verify that the target devices are properly configured in the Auto-provisioning Group.# symaccess -sid 624 show view aix_flm_mvSymmetrix ID : 000192602624Masking View Name : aix_flm_mv

Last updated at : 01:49:30 PM on Tue May 24,2011

Initiator Group Name : aix_flm_ig

Host Initiators

{

WWN : 10000000c96ef1d7 [alias: aix_flm/10000000c96ef1d7] WWN : 10000000c9538be2 [alias: aix_flm/10000000c9538be2]

}

Port Group Name : aix_flm_pg

Director Identification

{

FA-8E:1

FA-9E:0

}

Storage Group Name : aix_flm_sg

Sym Dev Host

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

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

04CA 08E:1 Not Visible 1 898

09E:0 Not Visible 104CB 08E:1 Not Visible 2 898

09E:0 Not Visible 204CC 08E:1 Not Visible 3 898

09E:0 Not Visible 304CD 08E:1 Not Visible 4 898

09E:0 Not Visible 4 -------

Total Capacity 3592(

5. Perform a host SCSI rescan to discover the VMAX target device paths presented as DMX source devicesFrom the application host:

Perform a host SCSI rescan to discover and configure the VMAX target device paths presenting DMX source device external identity. Reference the EMC Host Connectivity Guide for IBM AIX for the appropriate LUN scan procedures and considerations.

# cfgmgrIf applicable, repeat the preceding procedure on all the nodes in the cluster.

(

6. Verify the external device identity of the VMAX target device paths From the application host:Use lspath to verify that the target paths have been configured as alternate paths to the source devices. If any paths are missing, examine the cause before continuing.

# lspath -l hdisk17 -F "name path_id parent connection status"hdisk17 0 fscsi1 500009720836f5d9,1000000000000 Enabledhdisk17 1 fscsi1 500009720836f5dd,1000000000000 Enabledhdisk17 2 fscsi0 50000973000485d8,6000000000000 Enabledhdisk17 3 fscsi0 50000973000485dc,6000000000000 Enabled

(

7. Activate the FLM sessionFrom 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.

# symrcopy -f aix_flm activate -migrate'Activate' operation execution is in progress for the device listin device file 'aix_flm'. Please wait...

'Activate' operation successfully executed for the device list


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.

(

8. Verify the FLM pair status


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

# symrcopy -f aix_flm queryDevice File Name : aix_flm Control Device Remote Device Flags Status Done

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

Protected


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

000192602624:04CA 13272 000187490076:014E SD X..XXM. CopyInProg 7

000192602624:04CB 13273 000187490076:014F SD X..XXM. CopyInProg 7

000192602624:04CC 13273 000187490076:0150 SD X..XXM. CopyInProg 7

000192602624:04CD 13273 000187490076:0151 SD X..XXM. CopyInProg 7

Total ---------

Track(s) 53091

MB(s) 3318.2. . .

(

9. Verify the cutover on the application host

From the application host:

Use iostat to verify the cutover. I/O will be present on the target path.

# iostat -m hdisk17 2System configuration: lcpu=12 drives=67 ent=0.50 paths=139 vdisks=1tty: tin tout avg-cpu: % user % sys % idle % iowait physc % entc 0.0 85.2 0.8 2.8 77.9 18.5 0.0 6.5Disks: % tm_act Kbps tps Kb_read Kb_wrtnhdisk17 31.0 4476.0 114.0 3124 606Paths: % tm_act Kbps tps Kb_read Kb_wrtnPath3 0.0 0.0 0.0 0 0Path2 31.0 4476.0 114.0 3124 606Path1 0.0 0.0 0.0 0 0Path0 0.0 0.0 0.0 0 0

(

10. Monitor the FLM session


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


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

Protected


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

000192602624:04CA 11101 000187490076:014E SD X..XXM. CopyInProg 22

000192602624:04CB 11108 000187490076:014F SD X..XXM. CopyInProg 22

000192602624:04CC 11107 000187490076:0150 SD X..XXM. CopyInProg 22

000192602624:04CD 11106 000187490076:0151 SD X..XXM. CopyInProg 22

Total ---------

Track(s) 44422

MB(s) 2776.4. . .

(

11. Verify that the FLM session status is Copied


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


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

Protected


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

000192602624:04CA 0 000187490076:014E SD X..XXM. Copied 100

000192602624:04CB 0 000187490076:014F SD X..XXM. Copied 100

000192602624:04CC 0 000187490076:0150 SD X..XXM. Copied 100

000192602624:04CD 0 000187490076:0151 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.

# symrcopy -f aix_flm verify -copiedAll device(s) in the list are in 'Copied' state.

(

12. Terminate the FLM session


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 will no longer receive donor update writes, and fail back to the source device is no longer possible.

# symrcopy -f aix_flm terminate -migrate'Terminate' operation execution is in progress for the device listin device file 'aix_flm'. Please wait...

'Terminate' operation successfully executed for the device list


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.

(

13. Remove the source devices masking recordsFrom 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 624 delete view -name aix_flm_mv -unmapUse 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 624 list -type storage -devs 04CA:04CDSymmetrix ID : 000192602624Symm Dev View

Dev Storage Group Name Count Count

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

04CA aix_flm_sg 4 0

04CB aix_flm_sg 4 0

04CC aix_flm_sg 4 004CD aix_flm_sg 4 0Use the symdev list noport command to verify that the source devices are not mapped. Use range to filter a specific range of devices.# symdev -sid 624 list -range 04CA:04CD -noportSymmetrix ID: 000192602624 Device Name Directors Device

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

Cap

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

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

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

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

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

04CD 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.

# symmask -sid 076 -wwn 10000000c9538be2 -dir 3b -p 0 remove devs 014E:0151# symmask -sid 076 -wwn 10000000c96ef1d7 -dir 14b -p 1 remove devs 014E:0151# symmask -sid 076 refreshSymmetrix FA/SE directors updated with contents of SymMask Database 000187490076Use the symmaskdb list assignment command to verify that the source devices are no longer masked to the application host.

# symmaskdb -sid 76 list assignment -devs 014E:0151Symmetrix ID : 000187490076Device Identifier Type Dir:P

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

014E 500009720829011d FIBRE FA-3B:0

5000097208290120 FIBRE FA-14B:1014F 500009720829011d FIBRE FA-3B:0

5000097208290120 FIBRE FA-14B:10150 500009720829011d FIBRE FA-3B:0

5000097208290120 FIBRE FA-14B:10151 500009720829011d FIBRE FA-3B:0

5000097208290120 FIBRE FA-14B:1In this example, the only source-device masking remaining is the storage-to-storage masking, which facilitates the FLM migration.

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

# symmask -sid 076 -dir 3b -p 0 -wwn 500009720829011d remove devs 014E:0151# symmask -sid 076 -dir 14b -p 1 -wwn 5000097208290120 remove devs 014E:0151# symmask -sid 076 refreshSymmetrix FA/SE directors updated with contents of SymMask Database 000187490076Use the symmaskdb list assignment command to verify that the source devices are no longer masked.

# symmaskdb -sid 076 list assignment -devs 014E:0151No device masking database records could be found for the specified input parametersUse rmdev to remove the source device files from AIX before removing masking.# rmdev -dl hdisk5hdisk5 deleted# rmdev -dl hdisk6hdisk6 deleted# rmdev -dl hdisk7hdisk7 deleted# rmdev -dl hdisk8hdisk8 deleted# rmdev -dl hdisk12hdisk12 deleted# rmdev -dl hdisk13hdisk13 deleted# rmdev -dl hdisk14hdisk14 deleted# rmdev -dl hdisk15hdisk15 deleted

(

14. Perform a host SCSI rescan From the application host:

Perform a host SCSI rescan to remove the source paths.# cfgmgrIf applicable, repeat the preceding procedure on all the nodes in the cluster.

15. Remove the source device pathsFrom the application host:

Use rmpath to remove the source device paths. # rmpath -l hdisk17 -d -w 500009720836f5d9,1000000000000 -dpath Deleted# rmpath -l hdisk17 -d -w 500009720836f5dd,1000000000000 -d path Deleted

(

16. Verify that the source device paths are removed

From the application host:

# lspath -l hdisk17 -F "name path_id parent connection status"

hdisk17 2 fscsi0 50000973000485d8,6000000000000 Enabled

hdisk17 3 fscsi0 50000973000485dc,6000000000000 Enabled

(

(Table of ContentsMigratingDataUsingFLM_smc.001

aix - mpio-gpfs - 02 - flm migration

Documents