virtuallun migrationtoraidsatadriveunconfiguredspace

Title

VirtualLUNMigrationtontoRAIDSATAunconfiguredspace_sym001 Virtual LUN Migration to RAID SATA unconfigured space

OverviewVirtual LUN migration is from source devices to equally-sized target devices, or disks with free space equal to the source devices. A migration will not disrupt hosts or internal applications.

A virtual LUN migration 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. Protection might 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 manuals: EMC Solutions Enabler Symmetrix Array Controls CLI Product Guide, v7.0This document can be obtained from the EMC Powerlink website at:http://Powerlink.EMC.com

( Done

1. Determine the diskgroup where the migration should be performed.

Use the symdisk command to list all physical drives in the array sorted by diskgroup. In the output shown below, diskgroup 0 contains 300 GB (15,000 RPM) Fibre Channel Drives, while diskgroup 1 contains 1TB (7,200 RPM) SATA drives.

symdisk list -by_diskgroup -sid 54

Symmetrix ID : 000192601254

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 953870Use the symdisk command, as show below, to list the proposed target diskgroup (in this case diskgroup 1), to determine if there is sufficient freespace in the diskgroup, and sufficient DAs and physical drives to support RAID5 7+1 devices.

symdisk list -sid 54 -disk_group 1


Disks Selected : 56

Capacity(MB)


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





DF-8A 08A C B SATAHGST N01THGK 18 953870 908690 953870

DF-8A 08A C D SATAHGST N01THGK 21 953870 864817 953870

DF-8A 08A D C SATAHGST N01THGK 24 953870 912929 953870

DF-8A 08A D E SATAHGST N01THGK 9 953870 931691 953870








DF-7B 07B C B SATAHGST N01THGK 19 953870 908682 953870

DF-7B 07B C D SATAHGST N01THGK 20 953870 864825 953870

DF-7B 07B D C SATAHGST N01THGK 24 953870 912929 953870

DF-7B 07B D E SATAHGST N01THGK 9 953870 935629 953870

DF-8B 08B C C SATAHGST N01THGK 22 953870 914880 953870

DF-8B 08B C E SATAHGST N01THGK 15 953870 918501 953870

DF-8B 08B D B SATAHGST N01THGK 22 953870 906665 953870

DF-8B 08B D D SATAHGST N01THGK 9 953870 927315 953870








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

DF-7C 07C D B SATAHGST N01THGK 20 953870 915160 953870

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

DF-8C 08C C B SATAHGST N01THGK 20 953870 904297 953870

DF-8C 08C C D SATAHGST N01THGK 21 953870 864817 953870

DF-8C 08C D C SATAHGST N01THGK 24 953870 912929 953870

DF-8C 08C D E SATAHGST N01THGK 15 953870 918501 953870







DF-7D 07D C B SATAHGST N01THGK 20 953870 904297 953870

DF-7D 07D C D SATAHGST N01THGK 21 953870 864817 953870




DF-8D 08D D B SATAHGST N01THGK 20 953870 915434 953870

DF-8D 08D D D SATAHGST N01THGK 9 953870 927315 953870






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

(

2. Identify the proposed target diskgroup

Use The symdisk command shown below to list the proposed target diskgroup (in this case diskgroup 1), to determine if there is sufficient freespace in the diskgroup, and sufficient DAs and physical drives to support RAID5 7+1 devices.

symdisk list -sid 54 -disk_group 1


Disks Selected : 56

Capacity(MB)


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






















DF-8B 08B D B SATAHGST N01THGK 22 953870 906665 953870










DF-7C 07C D B SATAHGST N01THGK 20 953870 915160 953870

















DF-8D 08D D B SATAHGST N01THGK 20 953870 915434 953870

DF-8D 08D D D SATAHGST N01THGK 9 953870 927315 953870






DF-10D 10D D D SATAHGST N01THGK 20 953870 915434 953870Prior to migrating the device, the output of the symdev show command of one of the devices as shown below identifies that the device is locally protected by a single RAID1 primary RAID group, configured in diskgroup 0, as well as being remotely protected.

symdev show be8 -sid 54

Device Physical Name : /dev/rdsk/emcpower35c

Device Symmetrix Name : 0BE8

Device Serial ID : 5400BE8000


Device Group Name : app01 Device Logical Name : DEV001

Number of RAID Groups : 1

Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC

Product ID : SYMMETRIX

Product Revision : 5874

Device WWN : 60000970000192601254533030424538

Device Emulation Type : FBA

Device Defined Label Type: N/A

Device Defined Label : N/A

Device Sub System Id : 0x0150

Cache Partition Name : DEFAULT_PARTITION

Device Block Size : 512

Device Capacity

{

Cylinders : 9206

Tracks : 138090

512-byte Blocks : 17675520

MegaBytes : 8631

KiloBytes : 8837760

}

Device Configuration : RDF1+Mir

Device is WORM Enabled : No

Device is WORM Protected : No

SCSI-3 Persistent Reserve: Disabled

Dynamic Spare Invoked : No

Dynamic RDF Capability : RDF1_OR_RDF2_Capable

STAR Mode : No

STAR Recovery Capability : None

STAR Recovery State : NA

Device Service State : Normal

Device Status : Ready (RW)

Device SA Status : Ready (RW)

Front Director Paths (3):

{

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

POWERPATH DIRECTOR PORT LUN

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

PdevName Type Type Num Sts VBUS TID SYMM Host

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

/dev/rdsk/emcpower35c PARENT FA 07E:0 RW 000 00 0B3 000

c1t5000097208139918d1s2 CHILD FA 07E:0 RW 000 00 0B3 000

c2t5000097208139959d1s2 CHILD FA 07F:1 RW 000 00 001 000

}

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

Mirror Set DA Status : [RW,RW,N/A,N/A]

Mirror Set Inv. Tracks : [0,0,0,0]

Back End Disk Director Information

{

Hyper Type : RAID-1

Hyper Status : Ready (RW)

Disk [Director, Interface, TID] : [N/A,N/A,N/A]

Disk Director Volume Number : N/A

Hyper Number : N/A

Mirror Number : 1

Hyper Type : R2 Remote




Hyper Number : N/A

Mirror Number : 2

}

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

}

}

}

Clone Device Information

{

Source (SRC) Device Symmetrix Name : 0BE8

Source (SRC) Device Group Name : app01 Source (SRC) Composite Group Name : N/A

Target (TGT) Device Symmetrix Name : 0BF4

Target (TGT) Device Group Name : app01 Target (TGT) Composite Group Name : N/A

State of Session (SRC ====> TGT) : Copied

Percent Copied : 100%

Time of Last Clone Action : Sat Mar 7 13:13:35 2009

Clone State Flags : (Copy) (Diff)

Number of Prot. Tracks for SRC Device : 0

Number of Indir Tracks for TGT Device : 0

Number of Changed Tracks for SRC Device: 0

Number of Changed Tracks for TGT Device: 0

}

RDF Information

{


RDF Type : R1

RDF (RA) Group Number : 12 (0B)

Remote Device Symmetrix Name : 1640

Remote Symmetrix ID : 000192601201

R2 Device Is Larger Than The R1 Device : False

Paired with a Diskless Device : False

Paired with a Concurrent Device : False

Paired with a Cascaded Device : False

RDF Pair Configuration : Normal

RDF STAR Mode : False

RDF Mode : Asynchronous

RDF Adaptive Copy : Disabled

RDF Adaptive Copy Write Pending State : N/A

RDF Adaptive Copy Skew (Tracks) : 65535

RDF Device Domino : Disabled

RDF Link Configuration : Fibre

RDF Link Domino : Disabled

Prevent Automatic RDF Link Recovery : Enabled

Prevent RAs Online Upon Power ON : Enabled

Device RDF Status : Ready (RW)


Device RA Status : Ready (RW)

Device Link Status : Ready (RW)

Time of Last Device Link Status Change : Tue Mar 3 16:23:30 2009

Device Suspend State : N/A

Device Consistency State : Disabled

Device Consistency Exempt State : Disabled

RDF R2 Not Ready If Invalid : Disabled

Device RDF State : Ready (RW)

Remote Device RDF State : Write Disabled (WD)

RDF Pair State ( R1 R2 ) : Consistent

Number of R1 Invalid Tracks : 0

Number of R2 Invalid Tracks : 0

RDFA Information:

{

Session Number : 11

Cycle Number : 9003

Number of Devices in the Session : 6

Session Status : Active

Consistency Exempt Devices : No

Session Consistency State : Disabled

Minimum Cycle Time : 00:00:30

Average Cycle Time : 00:00:30

Duration of Last cycle : 00:00:30

Session Priority : 33

Tracks not Committed to the R2 Side: 0

Time that R2 is behind R1 : 00:00:52

R2 Image Capture Time : Sat Mar 7 13:37:14 2009

R2 Data is Consistent : True

R1 Side Percent Cache In Use : 0

R2 Side Percent Cache In Use : 0

Transmit Idle Time : 00:00:00

R1 Side DSE Used Tracks : 0

R2 Side DSE Used Tracks : 0

}

}

(

symmigrate sid 54 name mig_01 query detailSymmetrix ID: 000192601254

Invalid Status Done TGT

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

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

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


0BEA N/A 138090 SyncInProg 0 01 RAID-5(7+1) mig_01

0BEB N/A 130604 SyncInProg 5 01 RAID-5(7+1) mig_01

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

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

Total --------

Tracks 1559235

MB(s) 97452.2

Done(%) 5

(

3. Use the devices in normal replication functions During the migration of the devices it is possible to use them in normal replication functions, such as TimeFinder/Clone.

The following example shows the results of running the symclone recreate command with-precopy, as the migration data transfer process continues. symclone -g app01 recreate precopy -nop

'Recreate' operation execution is in progress for

device group 'app01'. Please wait...

'Recreate' operation successfully initiated for device group

'app01'.Execute a symclone query on the devices as shown below to show that the recreate was successful.

symclone -g app01 query

Device Group (DG) Name: app01DG's Type : RDF1

DG's Symmetrix ID : 000192601254

Source Device Target Device State Copy

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

Protected Modified Modified

Logical Sym Tracks Tracks Logical Sym Tracks CGDP SRC TGT (%)

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

DEV001 0BE8 0 0 BCV001 0BF4 0 XXXX PreCopy 100

DEV002 0BE9 0 0 BCV002 0BF5 0 XXXX PreCopy 100

DEV003 0BEA 0 0 BCV003 0BF6 0 XXXX PreCopy 100

DEV004 0BEB 0 0 BCV004 0BF7 0 XXXX PreCopy 100

DEV005 0BEC 0 0 BCV005 0BF8 0 XXXX PreCopy 100

DEV006 0BF0 0 0 BCV006 0BFC 0 XXXX PreCopy 100

Total ------- -------- --------

Track(s) 0 0 0

MB(s) 0.0 0.0 0.0

Legend:

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

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

(G): X = The Target device is associated with this group.

. = The Target device is not associated with this group.

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

. = The Clone session is not a differential copy session.

(P): X = The pre-copy operation has completed one cycle

. = The pre-copy operation has not completed one cycleThe following example shows that the Clone session can also be activated during the Virtual LUN migration:symclone -g app01 activate -v -nop

'Activate' operation execution is in progress for

device group 'app01'. Please wait...

'Activate' operation successfully executed for device group

'app01'.symclone -g app01 query

Device Group (DG) Name: app01DG's Type : RDF1

DG's Symmetrix ID : 000192601254

Source Device Target Device State Copy

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

Protected Modified Modified

Logical Sym Tracks Tracks Logical Sym Tracks CGDP SRC TGT (%)

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

DEV001 0BE8 0 0 BCV001 0BF4 0 XXX. Copied 100

DEV002 0BE9 0 0 BCV002 0BF5 0 XXX. Copied 100

DEV003 0BEA 0 0 BCV003 0BF6 0 XXX. Copied 100

DEV004 0BEB 0 0 BCV004 0BF7 0 XXX. Copied 100

DEV005 0BEC 0 0 BCV005 0BF8 0 XXX. Copied 100

DEV006 0BF0 0 0 BCV006 0BFC 0 XXX. Copied 100

Total -------- -------- --------

Track(s) 0 0 0

MB(s) 0.0 0.0 0.0

Legend:

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

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

(G): X = The Target device is associated with this group.

. = The Target device is not associated with this group.

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

. = The Clone session is not a differential copy session.

(P): X = The pre-copy operation has completed one cycle

. = The pre-copy operation has not completed one cycle

(

4. Set a query to run automatically at the given intervalUse the symmigrate query command with the i interval options to allow for the query to be run automatically at the given interval (in seconds).

Note: The following example shows that after the second iteration of the query an estimated time to completion is included with the output, along with the current data transfer rate.

symmigrate sid 54 name mig_01 query detail i 30

Symmetrix ID: 000192601254



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







Total --------

Tracks 1433840

MB(s) 89615.0

Done(%) 13




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







Total --------

Tracks 1304806

MB(s) 81550.4

Done(%) 21

Copy rate : 237.2 MB/S

Estimated time to completion : 00:05:43




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







Total --------

Tracks 1174415

MB(s) 73400.9

Done(%) 29



Note that while the migration is in the SyncInProg state, the output of a symdev show command shows the device being migrated is i being locally protected by two separate RAID groups the primary RAID1 group which the device started with, and a secondary RAID5 group to which the device is being migrated. The secondary RAID group can be seen to belong to diskgroup 1, while the primary RAID group belongs to diskgroup 0.

# symdev show be8 -sid 54 Device Physical Name : /dev/rdsk/emcpower35c






... Device Configuration : RDF1+Mir





{

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


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


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



c2t5000097208139959d1s2 CHILD FA 07F:1 RW 000 00 001 000

}

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

Mirror Set DA Status : [RW,RW,RW,N/A]



{

Hyper Type : RAID-1




Hyper Number : N/A

Mirror Number : 1





Hyper Number : N/A

Mirror Number : 2

Hyper Type : RAID-5




Hyper Number : N/A

Mirror Number : 3

}


{

Mirror Number : 1

RAID Type : RAID-1


Protection Level : 2



Hyper Devices:

{

Device : 0BE8

{

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



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

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



Hyper Devices:

{

Device : 0BE8

{

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



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

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

}

}

}

...

(

5. Verify the session status changes to Migrated

At the end of the migration, the symmigrate query command will show the session status change from SyncInProg to Synchronized, to MigrInProg, and finally to Migrated.

Run the the symmigrate query command as shown below to show the session status changes from SyncInProg to Synchronized, to MigrInProg, and finally to Migrated.

symmigrate sid 54 name mig_01 query detail i 30




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


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



Total --------

Tracks 41012

MB(s) 2563.2

Done(%) 97






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



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

...




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

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




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

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

(

6. Verify all devices in a single session are at the Migration state.

Run the following command to determine if all the devices in a single session have reached the state of Migrated.

symmigrate name mig_01 sid 1254 verify -migrated All session(s) with name 'mig_01' are in 'Migrated' state.

(

7. RAID5 RAID group located on the SATA drives in diskgroup 1.

When the migration session reaches the Migrated status, the symdev show output shows that the devices migrated are now, once again, protected by a single local RAID group. However, the primary RAID group now is the RAID5 RAID group located on the SATA drives in diskgroup 1.

symdev show be8 -sid 54

Device Physical Name : /dev/rdsk/emcpower35c






...

Device Configuration : RDF1+R-5

...





{

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


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


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



c2t5000097208139959d1s2 CHILD FA 07F:1 RW 000 00 001 000

}

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

Mirror Set DA Status : [RW,RW,N/A,N/A]



{

Hyper Type : RAID-5




Hyper Number : N/A

Mirror Number : 1





Hyper Number : N/A

Mirror Number : 2

}


{

Mirror Number : 1

RAID Type : RAID-5


Protection Level : 7+1



Hyper Devices:

{

Device : 0BE8

{

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



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

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

}

}

}

...

8. Complete the migrationTo complete the migration, and to remove the migrations session from the Symmetrix, run the symmigrate terminate command as shown below.

symmigrate -sid 54 -name mig_01 terminate -v -nop

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

9. Verify that the session no longer existsExecute the following query to show that the session no longer exists:

symmigrate -sid 54 -name mig_01 query


The device list with session name 'mig_01' does not have any session information.The Virtual LUN migration is now complete.

(Table of Contents

ConfiguringDynamicSRDF_sym002

virtuallun migrationtoraidsatadriveunconfiguredspace

Documents