Virtual LUN Migration to Configured Devices

 

Topic

Managing Storage

Selections

Select a platform: Symmetrix VMAX

Select preferred management interface: Solutions Enabler SYMCLI

Select a task: Virtual LUN migration to configured devices

 

 

Contents

·            Virtual LUN Migration to Configured Devices. 3

 


 

 

·       Virtual LUN Migration to Configured Devices

 

Overview

Virtual LUN migration involves moving data from source devices to equally-sized pre-configured target devices, or to drives containing free space equal to the source devices. Virtual LUN migrations are non-disruptive to host applications, as well as local and remote replication.

 

A virtual LUN migration may be may be initiated in the following circumstances:

 

  • Traditional data management involves moving data to a lower tier as it ages and becomes less critical to the business. RAID protection might also change as the data ages.

 

  • Emerging tiered storage configurations include moving data continuously during the lifecycle, either to optimize price/performance or respond to cyclical business changes.

 

This procedure is based on content from the following EMC manual:

  • EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide, v7.0

 

You can download the guide from EMC Online Support (registration required): https://support.EMC.com

 

 

1.   

Determine the Disk Group to which the migration should be performed.

To list all physical drives in a Symmetrix array, sorted by Disk Group, enter the following command:

 

   symdisk –sid SymmID list –by_diskgroup

 

where:

 

SymmID = The ID of a specific Symmetrix the symdisk command is to be executed against.

 

For example, to list all physical drives available on a Symmetrix with an ID of  000000012345, sorted by Disk Group, execute the following command:

 

symdisk –sid 12345 list –by_diskgroup

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID                 : 000000012345

Disks Selected               : 240

 

                                                        Capacity(MB)

Ident  Symb Int TID Vendor     Type       Hypers   Total    Free    Actual

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

 

Disk Group 0:

 

DF-7A  07A    C   0 SEAGATE    T300155         0        0        0   279140

DF-7A  07A    C   2 SEAGATE    T300155        63   279140   194293   279140

DF-7A  07A    C   4 SEAGATE    T300155        60   279140   177651   279140

DF-7A  07A    C   6 SEAGATE    T300155        62   279140   182092   279140

DF-7A  07A    C   8 SEAGATE    T300155        67   279140   185253   279140

...

DF-10D 10D    D   1 SEAGATE    T300155        63   279140   194293   279140

DF-10D 10D    D   3 SEAGATE    T300155        62   279140   182691   279140

DF-10D 10D    D   5 SEAGATE    T300155        65   279140   179162   279140

DF-10D 10D    D   7 SEAGATE    T300155        58   279140   142692   279140

DF-10D 10D    D   9 SEAGATE    T300155        66   279140   179169   279140

DF-10D 10D    D   B SEAGATE    T300155        64   279140   184670   279140

 

Disk Group 1:

 

DF-7A  07A    C   C SATAHGST   N01THGK        21   953870   919264   953870

DF-7A  07A    C   E SATAHGST   N01THGK        15   953870   918501   953870

DF-7A  07A    D   B SATAHGST   N01THGK        22   953870   906665   953870

DF-7A  07A    D   D SATAHGST   N01THGK         9   953870   927315   953870

...

DF-9D  09D    D   C SATAHGST   N01THGK        24   953870   912929   953870

DF-9D  09D    D   E SATAHGST   N01THGK        16   953870   914117   953870

DF-10D 10D    C   C SATAHGST   N01THGK        21   953870   919264   953870

DF-10D 10D    D   D SATAHGST   N01THGK        20   953870   915434   953870

 

Note that in the output shown above, Disk Group 0 contains 300 GB (15,000 RPM) Fibre Channel Drives, while Disk Group 1 contains 1TB (7,200 RPM) SATA drives.

 

This procedure illustrates how to migrate data stored on six R1 devices to configured RAID 5 7+1 space on SATA drives.

 

 

2.   

Verify that target devices of the desired protection type and capacity exist
To determine if there are sufficient configured devices of the desired protection type and capacity in a particular Disk Group, enter the following command:

 

symdev –sid SymmID list –disk_group GroupID –migr_tgt –emulation EmulationType [-raid1] | [-raid5 [-protection <3+1 | 7+1>]] | [-raid6 [-protection <6+2 | 14+2>]] –cap Capacity

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

GroupID = The ID of the Disk Group that information is to be collected for.

EmulationType = The emulation type that devices information is to be collected for must use.

Capacity = The minimum capacity that devices information is to be collected for must contain.

 

For example, to see if there are sufficient migration target devices in Disk Group 1 on a Symmetrix with an ID of 000000012345 with a capacity of 8,631 MB free space that are using FBA emulation and the protection type RAID 5 7+1, execute the following command:

 

symdev –sid 12345 list –disk_group 1 -migr_tgt -emulation fba -raid5 -prot 7+1 -cap 8631

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

       Device Name           Directors                 Device

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

                                                                          Cap

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

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

 

0ACC Not Visible          ???:? 09D:DC  RAID-5       N/Grp'd      RW    8631

0ACD Not Visible          ???:? 07B:CD  RAID-5       N/Grp'd      RW    8631

0ACE Not Visible          ???:? 08B:DB  RAID-5       N/Grp'd      RW    8631

0ACF Not Visible          ???:? 10B:CC  RAID-5       N/Grp'd      RW    8631

0AD0 Not Visible          ???:? 10A:CB  RAID-5       N/Grp'd      RW    8631

0AD1 Not Visible          ???:? 07A:CE  RAID-5       N/Grp'd      RW    8631

0AE6 Not Visible          ???:? 10A:DC  RAID-5       N/Grp'd      RW    8631

0AE7 Not Visible          ???:? 09B:CD  RAID-5       N/Grp'd      RW    8631

0AE8 Not Visible          ???:? 09A:DD  RAID-5       N/Grp'd      RW    8631

0AE9 Not Visible          ???:? 08B:CC  RAID-5       N/Grp'd      RW    8631

0AEA Not Visible          ???:? 09D:CB  RAID-5       N/Grp'd      RW    8631

0AEB Not Visible          ???:? 09D:DE  RAID-5       N/Grp'd      RW    8631

0C00 Not Visible          ???:? 09C:CC  RAID-5       N/Grp'd      RW    8631

0C01 Not Visible          ???:? 10A:CB  RAID-5       N/Grp'd      RW    8631

0C02 Not Visible          ???:? 10A:DC  RAID-5       N/Grp'd      RW    8631

0C03 Not Visible          ???:? 08B:DB  RAID-5       N/Grp'd      RW    8631

0C04 Not Visible          ???:? 08C:CD  RAID-5       N/Grp'd      RW    8631

0C05 Not Visible          ???:? 07A:CE  RAID-5       N/Grp'd      RW    8631

0C06 Not Visible          ???:? 07C:CC  RAID-5       N/Grp'd      RW    8631

0C07 Not Visible          ???:? 09D:CB  RAID-5       N/Grp'd      RW    8631

0C08 Not Visible          ???:? 08A:DC  RAID-5       N/Grp'd      RW    8631

0C09 Not Visible          ???:? 09A:DD  RAID-5       N/Grp'd      RW    8631

0C0A Not Visible          ???:? 07B:CD  RAID-5       N/Grp'd      RW    8631

0C0B Not Visible          ???:? 09D:DE  RAID-5       N/Grp'd      RW    8631

0C0C Not Visible          ???:? 10B:CC  RAID-5       N/Grp'd      RW    8631

0C0D Not Visible          ???:? 07D:CB  RAID-5       N/Grp'd      RW    8631

0C0E Not Visible          ???:? 10C:DC  RAID-5       N/Grp'd      RW    8631

0C0F Not Visible          ???:? 07A:DB  RAID-5       N/Grp'd      RW    8631

0C10 Not Visible          ???:? 09B:CD  RAID-5       N/Grp'd      RW    8631

0C11 Not Visible          ???:? 07D:DE  RAID-5       N/Grp'd      RW    8631

0C12 Not Visible          ???:? 08B:CC  RAID-5       N/Grp'd      RW    8631

0C13 Not Visible          ???:? 07B:CB  RAID-5       N/Grp'd      RW    8631

0C14 Not Visible          ???:? 08C:DC  RAID-5       N/Grp'd      RW    8631

0C15 Not Visible          ???:? 09C:DD  RAID-5       N/Grp'd      RW    8631

0C16 Not Visible          ???:? 09D:CD  RAID-5       N/Grp'd      RW    8631

0C17 Not Visible          ???:? 10B:CE  RAID-5       N/Grp'd      RW    8631

0C18 Not Visible          ???:? 10D:CC  RAID-5       N/Grp'd      RW    8631

0C19 Not Visible          ???:? 09B:CB  RAID-5       N/Grp'd      RW    8631

0C1A Not Visible          ???:? 09B:DC  RAID-5       N/Grp'd      RW    8631

0C1B Not Visible          ???:? 07C:DB  RAID-5       N/Grp'd      RW    8631

0C1C Not Visible          ???:? 07D:CD  RAID-5       N/Grp'd      RW    8631

0C1D Not Visible          ???:? 08B:CE  RAID-5       N/Grp'd      RW    8631

0C1E Not Visible          ???:? 08D:CC  RAID-5       N/Grp'd      RW    8631

0C1F Not Visible          ???:? 10C:CB  RAID-5       N/Grp'd      RW    8631

0C20 Not Visible          ???:? 07B:DC  RAID-5       N/Grp'd      RW    8631

0C21 Not Visible          ???:? 10D:DD  RAID-5       N/Grp'd      RW    8631

0C22 Not Visible          ???:? 10A:CD  RAID-5       N/Grp'd      RW    8631

0C23 Not Visible          ???:? 10C:DE  RAID-5       N/Grp'd      RW    8631

 

Note that this example shows that there are sufficient devices to complete the migration.

 

 

3.   

Identify how the source devices are protected

Prior to performing the actual migration, examine one of the devices being used to store the data that is to be migrated to determine how the data is currently being protected. To identify how a single device is protected, execute the following command:

 

symdev –sid SymmID show SymDevName

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

SymDevName = The specific Symmetrix device that information is to be obtained for.

 

For example, to display device information about Symmetrix device 0BE8 on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev -sid 12345 show be8

 

When this command is executed, examine the following information in the output produced:

    Device Physical Name     : /dev/rdsk/emcpower35c

 

    Device Symmetrix Name    : 0BE8

    Device Serial ID         : 5400BE8000

    Symmetrix ID             : 000000012345

 

    Device Group Name        : app01

    Device Logical Name      : DEV001

...

 

    Number of RAID Groups    : 1

 

...

 

    Device Configuration     : RDF1+Mir

...

 

 

    Mirror Set Type          : [RAID-1,R2 Remote,N/A,N/A]

 

...

 

    RAID Group Information

        {

        Mirror Number                            : 1

        RAID Type                                : RAID-1

        Device Position                          : Primary

        Protection Level                         : 2

        RAID Group Service State                 : Normal

        Failing Member Mask                      : N/A

        Hyper Devices:

            {

            Device : 0BE8

                {

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

                 Disk     DA       Hyper       Member        Disk

                DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)

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

                09A:D1    431    10    8768    1 RW         0   279140

                07A:D1    430     9    8768    2 RW         0   279140

                }

            }

        }

...

 

In this example, the output of the symdev show command indicates that device 0BE8 is locally protected by a single RAID1 primary RAID group, is configured in Disk Group 0, and is being remotely protected.

 

 

4.   

Validate the potential success of the migration

To validate the potential success of a configured device migration, execute the following command:

 

symmigrate –name SessionName –g DgName -tgt_dsk_grp DskGrp

-tgt_config <-tgt_unprotected| -tgt_raid1 | -tgt_raid5 -tgt_prot

<3+1 | 7+1> | -tgt_raid6 -tgt_prot <6+2 | 14+2>> validate [-outfile

OutputFile] -noprompt

 

where:

 

SessionName = The name to assign the migration session.

DgName = The name of the device group that contains the migration source devices.

DskGrp = The Disk Group that contains the migration target devices.

OutFile = The name that is to be assigned to a file that will be created and populated with exact device pairs that can be used to perform the actual migration.

 

For example, to test the potential success of a migration of data stored on devices identified by a device group named “app01” and generate a device file named “dev_pairs.txt” that contains exact device pairs that can be used for subsequent migration operations, execute the following command:

 

symmigrate -name mig_01 -g app01 -tgt_dsk_grp 1 -tgt_config

-tgt_raid5 -tgt_prot 7+1 validate -outfile dev_pairs.txt -noprompt

 

(In this example, the migration session is assigned the name “mig_01” and the target of the migration is a set of devices in Disk Group 1 that are using RAID 5 7+1 protection.)

 

When this command is executed, you should see output that looks something like this:

 

'Validate' operation execution is in progress for the device group 'app01'. Please wait...

 

STARTING a Migrate 'VALIDATE' operation.

 

SELECTING the list of Source devices:

 

  Devices: 0BE8, 0BE9, 0BEA, 0BEB, 0BEC, 0BED, 0BEE, 0BEF, 0BF0,

           0BF1, 0BF2, 0BF3 [SELECTED]

 

    Validate Migration......................................Started.

    Validate Migration......................................Done.

 

The Migrate 'VALIDATE' operation SUCCEEDED.

 

'Validate' operation successfully executed for the device group 'app01'.

 

Additionally, the contents of the output file produced (“dev_pairs.txt”), which will contain the recommended device pairings for performing the migration, should look something like this:

 bec 0ad0,0ad1,0ae8,ae6

 bf0 0acc,0ace,acf,0acd

 beb 0c03

 bea 0c02

 be9 0ae9

 be8 0ae7

 

This file can be used “as is”, or its contents can be edited as needed. It is important to note that in this example, four individual devices were selected as the target devices for the metadevices being migrated,.

 

 

5.   

Start the migration operation

When the proposed migration has been successfully validated it can be “established”, which causes the migration operation to be executed. To establish a device migration, execute the following command:

 

symmigrate –sid SymmID –name SessionName –f DevFile establish –v

-noprompt

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name to assign the migration session.

DevFile = The name of a file that contains exact device pairs that are to be used to perform the migration.

 

For example, to establish (initiate) the migration of data stored on a Symmetrix with an ID of 000000012345 using device pairing information stored in a file named “dev_pairs.txt”, execute the following command:

symmigrate –sid 12345 -name mig_01 –f dev_pairs.txt establish

-v –noprompt

 

When this command is executed, you should see output that looks something like this:

 

'Establish' operation execution is in progress for the device list in device file 'dev_pairs.txt'. Please wait...

 

STARTING a Migrate 'ESTABLISH' operation.

 

PAIRING of Source and Target Devices:

 

  Devices: 0BEC-0AD0, 0BEE-0AD1, 0BED-0AE8, 0BEF-0AE6, 0BF0-0ACC, 0BF1-0ACE, 0BF3-0ACF, 0BF2-0ACD, 0BEB-0C03, 0BEA-0C02, 0BE9-0AE9, 0BE8-0AE7

 

    Establish Migration...................................Started.

    Establish Migration...................................In Progress.

    Establish Migration...................................Done.

 

The Migrate 'ESTABLISH' operation SUCCEEDED.

 

'Establish' operation successfully executed for the device list in device file 'dev_pairs.txt'.

 

 

6.   

Run an initial query to verify that the migration operation has been started

Run an initial query to verify that the migration operation has been started (i.e., that the migration session is in the “SyncInProg” state) by executing the following command:

 

symmigrate –sid SymmID –name SessionName query -detail

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name assigned to the migration session that is to be queried.

 

For example, to query the status of a migration session named “mig_01” that was initiated for a Symmetrix with an ID of 000000012345, execute the following command:

 

symmigrate –sid 12345 –name mig_01 query –detail

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection Session

                                                            Name

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

0BE8 0AE7   134761 SyncInProg      2      01 RAID-5(7+1)    mig_01         

0BE9 0AE9   132842 SyncInProg      3      01 RAID-5(7+1)    mig_01         

0BEA 0C02   132522 SyncInProg      4      01 RAID-5(7+1)    mig_01          

0BEB 0C03   136344 SyncInProg      1      01 RAID-5(7+1)    mig_01         

0BEC 0AD0   539627 SyncInProg      2      01 RAID-5(7+1)    mig_01         

0BF0 0ACC   539838 SyncInProg      2      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks    1615934

 MB(s)      100996

 Done(%)         2

 

 

7.   

Monitor the migration by automatically querying the operation at a given interval

Automatically query the operation at a given interval to monitor the migration operation by executing the following command:

 

symmigrate –sid SymmID –name SessionName query –detail –i Interval

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name assigned to the migration session that is to be queried.

Interval = The interval (in seconds) at which the migration session is to be queried automatically.

 

For example, to query the status of a migration session named “mig_01” that was initiated for a Symmetrix with an ID of 000000012345 every 30 seconds, execute the following command:

symmigrate –sid 12345 –name mig_01 query –detail –i 30

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8 0AE7   106068 SyncInProg     23      01 RAID-5(7+1)    mig_01         

0BE9 0AE9    86735 SyncInProg     37      01 RAID-5(7+1)    mig_01         

0BEA 0C02    83720 SyncInProg     39      01 RAID-5(7+1)    mig_01         

0BEB 0C03   107973 SyncInProg     21      01 RAID-5(7+1)    mig_01         

0BEC 0AD0   412575 SyncInProg     25      01 RAID-5(7+1)    mig_01         

0BF0 0ACC   437755 SyncInProg     20      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks    1234826

 MB(s)     77176.6

 Done(%)        25

 

 

Copy rate                      :    238.1 MB/S

Estimated time to completion   : 00:05:24

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8 0AE7    96127 SyncInProg     30      01 RAID-5(7+1)    mig_01         

0BE9 0AE9    69726 SyncInProg     49      01 RAID-5(7+1)    mig_01         

0BEA 0C02    66420 SyncInProg     51      01 RAID-5(7+1)    mig_01          

0BEB 0C03    98292 SyncInProg     28      01 RAID-5(7+1)    mig_01         

0BEC 0AD0   367864 SyncInProg     33      01 RAID-5(7+1)    mig_01         

0BF0 0ACC   402631 SyncInProg     27      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks    1101060

 MB(s)     68816.2

 Done(%)        33

 

 

Copy rate                      :    253.3 MB/S

Estimated time to completion   : 00:04:31

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8 0AE7    85989 SyncInProg     37      01 RAID-5(7+1)    mig_01         

0BE9 0AE9    52959 SyncInProg     61      01 RAID-5(7+1)    mig_01         

0BEA 0C02    49128 SyncInProg     64      01 RAID-5(7+1)    mig_01         

0BEB 0C03    88267 SyncInProg     36      01 RAID-5(7+1)    mig_01         

0BEC 0AD0   324254 SyncInProg     41      01 RAID-5(7+1)    mig_01         

0BF0 0ACC   360102 SyncInProg     34      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks     960699

 MB(s)     60043.7

 Done(%)        42

 

 

Copy rate                      :    258.0 MB/S

Estimated time to completion   : 00:03:52

 

It is important to note that after the second iteration of the query is performed, an estimated time to completion is included with the output, along with the current data transfer rate.

 

During the migration operation, the session status will change from SyncInProg to Synchronized, to MigrInProg, and finally to Migrated. These changes will look something like this:

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8  N/A    10756 SyncInProg     92      01 RAID-5(7+1)    mig_01         

0BE9  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEA  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEB  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEC  N/A    19554 SyncInProg     96      01 RAID-5(7+1)    mig_01         

0BF0  N/A    10702 SyncInProg     98      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks      41012

 MB(s)      2563.2

 Done(%)        97

 

 

Copy rate                      :    106.5 MB/S

Estimated time to completion   : 00:00:24

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BE9  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEA  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEB  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BEC  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

0BF0  N/A        0 Synchronized  100      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks          0

 MB(s)         0.0

 Done(%)       100

 

...

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

0BE9  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

0BEA  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

0BEB  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

0BEC  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

0BF0  N/A        0 MigrInProg    100      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks          0

 MB(s)         0.0

 Done(%)       100

 

 

Symmetrix ID: 000000012345

 

           Invalid    Status    Done   TGT

Src  Tgt    Tracks  SRC => TGT   (%) Dsk Grp TGT Protection   Session Name

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

0BE8  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

0BE9  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

0BEA  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

0BEB  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

0BEC  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

0BF0  N/A        0 Migrated      100      01 RAID-5(7+1)    mig_01         

 

Total     --------

 Tracks          0

 MB(s)         0.0

 Done(%)       100

 

 

8.   

Identify how the source devices are protected during migration (optional)

While a migration is in the SyncInProg state, the device being migrated is locally protected by two separate RAID groups – the primary RAID group which the device started with, and a secondary RAID group to which the device is being migrated.

To identify how a single device is protected during a migration operation, execute the following command:

 

symdev –sid SymmID show SymDevName

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

SymDevName = The specific Symmetrix device that information is to be obtained for.

 

For example, to display device information about Symmetrix device 0BE8 on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev -sid 12345 show be8

 

When this command is executed, examine the following information in the output produced:

 

    Device Physical Name     : /dev/rdsk/emcpower35c

 

    Device Symmetrix Name    : 0BE8

    Device Serial ID         : 5400BE8000

    Symmetrix ID             : 000000012345

 

    Device Group Name        : app01

    Device Logical Name      : DEV001

...

 

    Number of RAID Groups    : 2

 

...

 

    Device Configuration     : RDF1+Mir

 

...

 

    Mirror Set Type          : [RAID-1,R2 Remote,RAID-5,N/A]

 

...

 

    Back End Disk Director Information

        {

        Hyper Type                             : RAID-1

        ...

 

        Hyper Type                             : RAID-5

        ...

        }

 

    RAID Group Information

        {

        Mirror Number                            : 1

        RAID Type                                : RAID-1

        Device Position                          : Primary

        Protection Level                         : 2

        RAID Group Service State                 : Normal

        Failing Member Mask                      : N/A

        Hyper Devices:

            {

            Device : 0BE8

                {

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

                 Disk     DA       Hyper       Member        Disk

                DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)

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

                09A:D1    431    10    8768    1 RW         0   279140

                07A:D1    430     9    8768    2 RW         0   279140

                }

            }

 

        Mirror Number                            : 3

        RAID Type                                : RAID-5

        Device Position                          : Secondary

        Protection Level                         : 7+1

        RAID Group Service State                 : Normal

        Failing Member Mask                      : N/A

        Hyper Devices:

            {

            Device : 0BE8

                {

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

                 Disk     DA       Hyper       Member        Disk

                DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)

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

                09C:CC    406    22    1253    1 RW         1   953870

                07A:CC    403    22    1253    2 RW         1   953870

                09A:CC    403    22    1253    3 RW         1   953870

                08D:CC    399    22    1253    4 RW         1   953870

                10D:CC    399    22    1253    5 RW         1   953870

                08B:CC    405    23    1253    6 RW         1   953870

                10B:CC    405    23    1253    7 RW         1   953870

                07C:CC    406    22    1253    8 RW         1   953870

                }

            }

        }

...

 

 

In this example, the secondary RAID group (RAID 5) can be seen as belonging to Disk Group 1, while the primary RAID group (RAID 1) belongs to Disk Group 0.

 

While a migration operation is in progress, the target device specified is shown to be a donor device. This indicates that it is providing the target storage for the migration. The donor status can be seen in the RAID Group Information section of the symdev show output of the target device.

 

For example, to look for donor status information for Symmetrix device 0AE7 on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev -sid 12345 show ae7

 

When this command is executed, examine the RAID Group Information section of the output produced:

...

 

    RAID Group Information

        {

        Mirror Number                            : 1

        RAID Type                                : RAID-5

        Device Position                          : Primary (Donor)

        Protection Level                         : 7+1

        RAID Group Service State                 : Normal

        Failing Member Mask                      : N/A

        Hyper Devices:

            {

            Device : 0AE7

                {

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

                 Disk     DA       Hyper       Member        Disk

                DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)

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

                09B:CD    317     9    1253    1 RW         1   953870

                07B:CD    317     9    1253    2 RW         1   953870

                08C:CD    313    10    1253    3 RW         1   953870

                10C:CD    313    10    1253    4 RW         1   953870

                08A:CD    318    10    1253    5 RW         1   953870

                10A:CD    318    10    1253    6 RW         1   953870

                07D:CD    313    10    1253    7 RW         1   953870

                09D:CD    313    10    1253    8 RW         1   953870

                }

            }

        }

...

 

 

9.   

Verify that all devices in the migration session are in the Migrated state.

Verify that all devices in the migration session have reached the “Migrated” state by executing the following command:

 

symmigrate –sid SymmID –name SessionName verify –migrated

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name assigned to the migration session that is to be queried.

 

For example, to verify that all devices in a migration session named “mig_01” that was initiated for a Symmetrix with an ID of 000000012345 has reached the “Migrated” state, execute the following command:

symmigrate –sid 12345 –name mig_01 verify –migrated

 

If the migration operation has completed when this command is executed, you should see output that looks like this:

All session(s) with name 'mig_01' are in 'Migrated' state.

 

 

10.  

Verify the source device’s RAID protection and physical storage has changed

When the migration operation is complete (i.e., all devices in the migration session have reached the “Migrated” state), verify that the RAID protection and physical storage has changed for one of the original devices by executing the following command:

 

symdev –sid SymmID show SymDevName

 

where:

 

SymmID = The ID of a specific Symmetrix the symdev command is to be executed against.

SymDevName = The specific Symmetrix device that information is to be obtained for.

 

For example, to display device information about Symmetrix device 0BE8 on a Symmetrix with an ID of 000000012345, execute the following command:

 

symdev -sid 12345 show be8

 

When this command is executed, examine the following information in the output produced:

 

    Device Physical Name     : /dev/rdsk/emcpower35c

 

    Device Symmetrix Name    : 0BE8

    Device Serial ID         : 5400BE8000

    Symmetrix ID             : 000000012345

 

    Device Group Name        : app01

    Device Logical Name      : DEV001

 

    Number of RAID Groups    : 1

 

    ...

 

    Device Configuration     : RDF1+R-5

 

    ...

 

    Mirror Set Type          : [RAID-5,R2 Remote,N/A,N/A]

 

    ...

 

    Back End Disk Director Information

        {

        Hyper Type                             : RAID-5

        ...

 

        }

 

    RAID Group Information

        {

        Mirror Number                            : 1

        RAID Type                                : RAID-5

        Device Position                          : Primary

        Protection Level                         : 7+1

        RAID Group Service State                 : Normal

        Failing Member Mask                      : N/A

        Hyper Devices:

            {

            Device : 0BE8

                {

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

                 Disk     DA       Hyper       Member        Disk

                DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)

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

                09C:CC    405    22    1253    1 RW         1   953870

                07A:CC    402    22    1253    2 RW         1   953870

                09A:CC    402    22    1253    3 RW         1   953870

                08D:CC    398    22    1253    4 RW         1   953870

                10D:CC    398    22    1253    5 RW         1   953870

                08B:CC    405    23    1253    6 RW         1   953870

                10B:CC    405    23    1253    7 RW         1   953870

                07C:CC    405    22    1253    8 RW         1   953870

                }

            }

        }

    ...

 

In this example, the output of the symdev show command indicates that device 0BE8 is now locally protected by a single RAID5 RAID group that is located on the SATA drives in Disk Group 1.

 

 

11.  

Terminate the migration session

Terminate the migration operation and remove the migration session from the Symmetrix by executing the following command:

 

symmigrate –sid SymmID –name SessionName terminate -v -noprompt

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name assigned to the migration session that is to be terminated.

 

For example, to terminate a migration session named “mig_01” that was initiated for a Symmetrix with an ID of 000000012345, execute the following command:

 

symmigrate -sid 12345 -name mig_01 terminate -v –noprompt

 

When this command is executed, you should see output that looks something like this:

 

'Terminate' operation execution is in progress for the session named 'mig_01'. Please wait...

 

STARTING a Migrate 'TERMINATE' operation.

 

SELECTING the list of Source devices:

 

  Devices:  [SELECTED]

 

    Terminate Migration.............................................Started.

    Terminate Migration.............................................Done.

 

The Migrate 'TERMINATE' operation SUCCEEDED.

 

'Terminate' operation successfully executed for the session named 'mig_01'.

 

 

12.  

Verify that  the migration session no longer exists

Run a query to verify that the migration session has been terminated by executing the following command:

 

symmigrate –sid SymmID –name SessionName query

 

where:

 

SymmID = The ID of a specific Symmetrix the symmigrate command is to be executed against.

SessionName = The name assigned to the migration session that is to be queried.

 

For example, to verify that a migration session named “mig_01” that was initiated for a Symmetrix with an ID of 000000012345 has been terminated, execute the following command:

 

symmigrate –sid 12345 –name mig_01 query

 

When this command is executed, you should see output that looks something like this:

 

Symmetrix ID: 000000012345

 

The device list with session name 'mig_01' does not have any session information.

 

The Virtual LUN migration is now complete.

 

 

7Table of Contents