virtuallunmigrationtoraidsatadriveconfiguredspace_sym01

Title

Virtual LUN MigrationtoRAIDSATAconfigured space_sym001 Virtual LUN Migration to RAID SATA configured space

Overview.

Virtual 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 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 manual: 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

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

In the following example, the six R1 devices will be migrated to configured space on SATA drives.

To determine which diskgroup to perform the migration to, the symdisk command can be used to list all physical drives in the array sorted by diskgroup. In the below output 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 953870

(

2. Determine required configured devices of protection and capacity exist When it is determined that diskgroup1 contains the SATA drives, use the symdev command to determine if there are sufficient configured devices of the required protection and capacity in the diskgroup.

The results of the symdev command list all migration target eligible devices in diskgroup1, of protection level RAIDS7+1 and capacity 8,631 MB

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

Symmetrix ID: 000192601254

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 there are sufficient devices to complete the migration.

(

3. Verify the device is protected by a single RAID1 primary RAID groupBefore migrating the device, review the output of the symdev show command against one of the devices to show 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

}

}

(

4. Test the potential success of the migrationOnce the devices to be migrated, and the diskgroup to migrated to, have been identified, along with the desired protection type, the migration can be submitted to the array.

Run the symmigrate validate command to test the potential success of the migration. The outfile option is also used to generate a device file containing exact device pairs which can be used for the subsequent symmigrate establish.In the following example, the migration session name being used is mig_01.symmigrate -name mig_01 -g app01 -tgt_dsk_grp 1 -tgt_raid5 -tgt_prot 7+1 -tgt_config validate -outfile dev_pairs.txt

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

The results of the output file contain the recommend device pairings for performing the migration.cat dev_pairs.txt

bec 0ad0,0ad1,0ae8,ae6

bf0 0acc,0ace,acf,0acd

beb 0c03

bea 0c02

be9 0ae9

be8 0ae7

The file can be used as is, or can be edited as needed. Note that in this instance for the metadevices being migrated, four individual devices were selected as the target devices.

When the proposed migration is successfully validated it can then be established, thereby executing the migration.In the following example, the device file generated by the symmigrate validate command is used to specify the devices to be migrated.

symmigrate -name mig_01 f dev_pairs.txt sid 54 establish -nop -v

'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'.Run an initial query of the migration to show the migration session state as being SyncInProg. The query will also show the target device being used for the migration.

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 0AE7 134761 SyncInProg 2 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(%) 2While the devices are migrating it is possible to use them in normal replication functions, such as SRDF. Here, a symrdf suspend command is run, as the migration data transfer process continues.

# symrdf -g app01 suspend -force v -nopAn RDF 'Suspend' operation execution is

in progress for device group 'app01'. Please wait...

RDF Source (R1) group 'app01'

STARTING an RDF 'SUSPEND' operation.

Scanning device(s) for a 'SELECT ALL DEVS' operation (SOURCE).

Device: 0BE8 (Remote Device: 1640) [SELECTED]

Device: 0BE9 (Remote Device: 1641) [SELECTED]

Device: 0BEA (Remote Device: 1642) [SELECTED]

Device: 0BEB (Remote Device: 1643) [SELECTED]

Device: 0BEC (Remote Device: 1644) [SELECTED]

Device: 0BEE (Remote Device: 1647) [SELECTED]

Device: 0BED (Remote Device: 1646) [SELECTED]

Device: 0BEF (Remote Device: 1645) [SELECTED]

Device: 0BF0 (Remote Device: 1648) [SELECTED]

Device: 0BF1 (Remote Device: 164B) [SELECTED]

Device: 0BF3 (Remote Device: 1649) [SELECTED]

Device: 0BF2 (Remote Device: 164A) [SELECTED]

Suspend RDF link(s).......................................Started.

Suspend RDF link(s).......................................Done.

The RDF 'SUSPEND' operation SUCCEEDED.

The RDF 'Suspend' operation successfully executed for

device group 'app01'.

Run a symrdf query of the devices to show that the suspend was successful.

# symrdf -g app01 query

Device Group (DG) Name : app01

DG's Type : RDF1

DG's Symmetrix ID : 000192601254 (Microcode Version: 5874)

Remote Symmetrix ID : 000192601201 (Microcode Version: 5874)

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

Source (R1) View Target (R2) View MODES

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

ST LI ST

Standard A N A

Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair

Device Dev E Tracks Tracks S Dev E Tracks Tracks MDAE STATE

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

DEV001 0BE8 RW 0 0 NR 1640 WD 0 0 A... Suspended

DEV002 0BE9 RW 0 0 NR 1641 WD 0 0 A... Suspended

DEV003 0BEA RW 0 0 NR 1642 WD 0 0 A... Suspended

DEV004 0BEB RW 0 0 NR 1643 WD 0 0 A... Suspended

DEV005 0BEC RW 0 0 NR 1644 WD 0 0 A... Suspended

DEV006 0BF0 RW 0 0 NR 1648 WD 0 0 A... Suspended

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

Track(s) 0 0 0 0

MB(s) 0.0 0.0 0.0 0.0

Legend for MODES:

M(ode of Operation) : A = Async, S = Sync, E = Semi-sync, C = Adaptive Copy

D(omino) : X = Enabled, . = Disabled

A(daptive Copy) : D = Disk Mode, W = WP Mode, . = ACp off

(Consistency) E(xempt): X = Enabled, . = Disabled, M = Mixed, - = N/A

(

5. 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).

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




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







Total --------

Tracks 1234826

MB(s) 77176.6

Done(%) 25

Copy rate : 238.1 MB/S

Estimated time to completion : 00:05:24




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







Total --------

Tracks 1101060

MB(s) 68816.2

Done(%) 33






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







Total --------

Tracks 960699

MB(s) 60043.7

Done(%) 42



Note that while the migration is in the SyncInProg state, the output of a symdev show command shows the device being migrated is 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 Serial ID : 5400BE8000


Device Group Name : app01 Device Logical Name : DEV001


... Device Configuration : RDF1+Mir


Device 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,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 Type : R2 Remote




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

Device Position : Primary

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

}

}

}

...While the migration is progressing, 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.

symdev show ae7 -sid 54

Device Physical Name : Not Visible

Device Symmetrix Name : 0AE7

Device Serial ID : N/A



Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC

Product ID : SYMMETRIX

Product Revision : 5874

Device WWN : 60000970000192601254533030414537

Device Emulation Type : FBA

Device Defined Label Type: N/A

Device Defined Label : N/A

Device Sub System Id : 0x0182

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 : RAID-5

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 Status : Not Ready (NR)

Device SA Status : N/A (N/A)

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

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



{

Hyper Type : RAID-5

Hyper Status : Not Ready (NR)



Hyper Number : N/A

Mirror Number : 1

}


{

Mirror Number : 1

RAID Type : RAID-5

Device Position : Primary (Donor)

Protection Level : 7+1



Hyper Devices:

{

Device : 0AE7

{

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



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

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

}

}

}

(

6. Verify the session status changes to MigratedRun 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




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

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






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



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

(

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

(

8.

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

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

virtuallunmigrationtoraidsatadriveconfiguredspace_sym01

Documents