No you need to remove RDF protection before expanding metavolumes on both sides. And when you expanded both metavolumes (you don't need to preserve data on R2 since you'll soon run a full establish) you can create RDF pair again. Note that creating a new pair requires a full establish.
1.Suspend the RDF link between R1 - R2 devices 2.set dev 0BAD attribute=no dyn_rdf; 3.extend R1 4.extend R2 5.set dev 0BAD attribute=dyn_rdf; 6.Resume RDF link between R1 - R2 devices
Are you using static or dynamic RDF ?? In case you have static RDF you have to "convert" your devices (use symconfigure to change protection of affected devices). In case you have dynamic RDF, you can use the "symrdf deletepair" command. The command you pasted can be used to remove dyn_rdf attribute but requires you already broke existing dynamic pair between 0BAD and its remote device (I guess it's BEEF)
0. add new metamembers on both sides attribute=dyn_rdf (use symconfigure on both sides) 1. suspend RDF link between R1 - R2 devices (symrdf susp) 2. break RDF pair between R1 - R2 devices (symrdf deletepair) 3. extend R1 (use symconfigure and a BCV to protect data) 4. extend R2 (use symconfigure and forget about data) 5. create RDF pair between R1 and R2 (use symrdf createpair) 6. run a full establish from R1 to R2 devices.
ok, before I add hypers to the existing meta I will need to change the device types from RAID-5 to RDF1+R-5 is that correct or is that done when the create pair is established?
0.add new metamembers on both sides attribute=dyn_rdf (use symconfigure on both sides)
The meta I want to expand is device type RDF1+R-5... the new hypers I want to add to this meta are RAID-5, but are r1 + r2 capable. Do I need to run a convert dev xxx to RDF1+R-5 on the hypers before I add them to the meta I want to extend?
Can you please post full output of "symdev -sid xxx show 0BAD" and "symrdf -sid xxx -dynamic list" ?? I can't understand if you are using dyn_rdf or static RDF.
Ok your pair is a dynamic pair. Thus you don't need to use symconfigure and convert between RAID5 and RDF1+R-5. You need to follow the steps I suggested above ..
Your metavolume is RAID1+R-5 becouse it's in a RDF pair. As soon as you issue "symrdf deletepair" (with appropriate options) you'll have a plain RAID5 device with dyn_rdf attribute enabled, thus you can add new members (if they already have dyn_rdf attribute as I suggested in step 0) and when you have a bigger metavolume on both sides you can issue a "symrdf createpair" to have your RDF1+R-5 device.
Device Symmetrix Name : 15CA Device Serial ID : N/A Symmetrix ID : 00019010xxxx
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID : EMC Product ID : SYMMETRIX Product Revision : 5772 Device WWN : 6006048000019010xxxxxxxxxxxxxxxx Device Emulation Type : FBA Device Defined Label Type: N/A Device Defined Label : N/A Device Sub System Id : 0x0016 Cache Partition Name : DEFAULT_PARTITION
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 (4): { ----------------------------------------------------------------- POWERPATH DIRECTOR PORT L --------- ---------- ---- -------- ---- PdevName Type Type Num Sts VBUS TID SYMM ----------------------------------------------------------------- Not Visible N/A FA 07B:0 RW 000 00 001 Not Visible N/A FA 08B:0 RW 000 00 006 Not Visible N/A FA 09B:0 RW 000 00 006 Not Visible N/A FA 10B:0 RW 000 00 015 }
Meta Configuration : Striped Meta Stripe Size : 960k (1 Cylinders) Meta Device Members (5) : { ----------------------------------------------------------------- BCV DATA RDF DATA ---------------------------- --------------------- Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair Dev (MB) Tracks Tracks State Tracks Tracks State ----------------------------------------------------------------- --> 15CA 32768 - - N/A 0 0 Synchro 15CB 32768 - - N/A 0 0 Synchro 15CC 32768 - - N/A 0 0 Synchro 15CD 32768 - - N/A 0 0 Synchro 15CE 32768 - - N/A 0 0 Synchro ----------------------------------------------------------------- 163838 - - 0 0 }
Mirror Set Type : [RAID-5,R2 Remote,RAID-5,N/A]
Mirror Set DA Status : [RW,RW,RW,N/A]
Mirror Set Inv. Tracks : [0,0,0,0]
Back End Disk Director Information { Hyper Type : RAID-5 Hyper Status : Ready (RW) Disk [Director, Interface, TID] : [N/A,N/A,N/A] Disk Director Volume Number : N/A Hyper Number : N/A
Hyper Type : R2 Remote Hyper Status : Ready (RW) Disk [Director, Interface, TID] : [N/A,N/A,N/A] Disk Director Volume Number : N/A Hyper Number : N/A
Hyper Type : RAID-5 Hyper Status : Ready (RW) Disk [Director, Interface, TID] : [N/A,N/A,N/A] Disk Director Volume Number : N/A Hyper Number : N/A }
RAID-5 Device Information { Number of Tracks in a Stripe : 4 Overall Ready State of RAID-5 Device : Ready Overall WriteProtect State of RAID-5 Device : Enabled Member Number of the Failing Device : None Member Number that Invoked the Spare : None Disk Director (DA) that Owns the Spare : Inv Copy Direction : N/A RAID-5 Hyper Devices (7+1): { Device : 15CA (M) { --------------------------------------------------------- Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca --------------------------------------------------------- 02A:D1c 2744 52 4687 1 RW N/A 3 4 15A:C1c 1283 52 4687 5 RW N/A 3 4 01B:D1c 2633 52 4687 4 RW N/A 3 4 16B:C1c 1396 52 4687 8 RW N/A 3 4 02C:D1c 2763 52 4687 3 RW N/A 3 4 15C:C1c 1281 52 4687 7 RW N/A 3 4 01D:D1c 2650 52 4687 6 RW N/A 3 4 16D:C1c 1396 52 4687 2 RW N/A 3 4 } Device : 15CB (m) { --------------------------------------------------------- Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca --------------------------------------------------------- 01A:Ce 676 53 4687 5 RW N/A 3 4 02A:C1b 1159 53 4687 6 RW N/A 3 4 15B:De 2028 53 4687 8 RW N/A 3 4 16B:D1b 2641 53 4687 7 RW N/A 3 4 01C:Ce 677 53 4687 1 RW N/A 3 4 02C:C1b 1177 53 4687 2 RW N/A 3 4 15D:De 1922 53 4687 4 RW N/A 3 4 16D:D1b 2642 53 4687 3 RW N/A 3 4 } Device : 15CC (m) { --------------------------------------------------------- Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca --------------------------------------------------------- 15A:D1b 2513 53 4687 6 RW N/A 3 4 16A:De 2025 53 4687 5 RW N/A 3 4 01B:C1b 1163 53 4687 7 RW N/A 3 4 02B:Ce 678 53 4687 8 RW N/A 3 4 15C:D1b 2530 53 4687 2 RW N/A 3 4 16C:De 2046 53 4687 1 RW N/A 3 4 01D:C1b 1180 53 4687 3 RW N/A 3 4 02D:Ce 678 53 4687 4 RW N/A 3 4 } Device : 15CD (m) { --------------------------------------------------------- Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca --------------------------------------------------------- 15A:Ce 678 53 4687 6 RW N/A 3 4 16A:C1b 1163 53 4687 5 RW N/A 3 4 01B:De 2028 53 4687 7 RW N/A 3 4 02B:D1b 2648 53 4687 8 RW N/A 3 4 15C:Ce 676 53 4687 2 RW N/A 3 4 16C:C1b 1179 53 4687 1 RW N/A 3 4 01D:De 2045 53 4687 3 RW N/A 3 4 02D:D1b 2647 53 4687 4 RW N/A 3 4 } Device : 15CE (m) { --------------------------------------------------------- Disk DA Hyper Member Spare Disk
RDF Link Configuration : GigE RDF Link Domino : Disabled Prevent Automatic RDF Link Recovery : Disabled Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : Ready (RW) Device RA Status : Ready (RW) Device Link Status : Ready (RW)
Device Suspend State : N/A Device Consistency 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 ) : Synchronized
Number of R1 Invalid Tracks : 0 Number of R2 Invalid Tracks : 0
RDFA Information: { Session Number : 1 Cycle Number : 0 Number of Devices in the Session : 261 Session Status : Inactive
Session Consistency State : N/A Minimum Cycle Time : 00:00:30 Average Cycle Time : 00:00:00 Duration of Last cycle : 00:00:00 Session Priority : 33
Tracks not Committed to the R2 Side: 0 Time that R2 is behind R1 : 00:00:00 R2 Image Capture Time : N/A 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 } }
dynamox
9 Legend
•
20.4K Posts
0
April 9th, 2009 14:00
please mark Stefano's answers as correct/helpful. This is a very common topic that will benefit a lot of people.
Thanks
xe2sdc
4 Operator
•
2.8K Posts
0
April 6th, 2009 02:00
Note that creating a new pair requires a full establish.
Message was edited by:
Stefano Del Corno
Blazer87
21 Posts
0
April 6th, 2009 06:00
Steps:
1.Suspend the RDF link between R1 - R2 devices
2.set dev 0BAD attribute=no dyn_rdf;
3.extend R1
4.extend R2
5.set dev 0BAD attribute=dyn_rdf;
6.Resume RDF link between R1 - R2 devices
Does that about cover it?
Blazer87
21 Posts
0
April 6th, 2009 06:00
Is this the correct syntax for removing RDF protection?
set dev 0BAD attribute=no dyn_rdf;
xe2sdc
4 Operator
•
2.8K Posts
0
April 6th, 2009 06:00
In case you have static RDF you have to "convert" your devices (use symconfigure to change protection of affected devices). In case you have dynamic RDF, you can use the "symrdf deletepair" command.
The command you pasted can be used to remove dyn_rdf attribute but requires you already broke existing dynamic pair between 0BAD and its remote device (I guess it's BEEF)
xe2sdc
4 Operator
•
2.8K Posts
0
April 6th, 2009 06:00
1. suspend RDF link between R1 - R2 devices (symrdf susp)
2. break RDF pair between R1 - R2 devices (symrdf deletepair)
3. extend R1 (use symconfigure and a BCV to protect data)
4. extend R2 (use symconfigure and forget about data)
5. create RDF pair between R1 and R2 (use symrdf createpair)
6. run a full establish from R1 to R2 devices.
Blazer87
21 Posts
0
April 6th, 2009 07:00
before I add hypers to the existing meta I will need to change the device types from RAID-5 to RDF1+R-5 is that correct or is that done when the create pair is established?
xe2sdc
4 Operator
•
2.8K Posts
0
April 6th, 2009 07:00
Blazer87
21 Posts
0
April 6th, 2009 08:00
0.add new metamembers on both sides attribute=dyn_rdf (use symconfigure on both sides)
The meta I want to expand is device type RDF1+R-5... the new hypers I want to add to this meta are RAID-5, but are r1 + r2 capable. Do I need to run a convert dev xxx to RDF1+R-5 on the hypers before I add them to the meta I want to extend?
xe2sdc
4 Operator
•
2.8K Posts
0
April 6th, 2009 08:00
xe2sdc
4 Operator
•
2.8K Posts
1
April 6th, 2009 09:00
Your metavolume is RAID1+R-5 becouse it's in a RDF pair. As soon as you issue "symrdf deletepair" (with appropriate options) you'll have a plain RAID5 device with dyn_rdf attribute enabled, thus you can add new members (if they already have dyn_rdf attribute as I suggested in step 0) and when you have a bigger metavolume on both sides you can issue a "symrdf createpair" to have your RDF1+R-5 device.
Blazer87
21 Posts
0
April 6th, 2009 09:00
thanks so much for the help.... I wasn't involved with the setup so trying to get up to speed...
-thanks again
Blazer87
21 Posts
0
April 6th, 2009 09:00
Device Physical Name : Not Visible
Device Symmetrix Name : 15CA
Device Serial ID : N/A
Symmetrix ID : 00019010xxxx
Attached BCV Device : N/A
Attached VDEV TGT Device : N/A
Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5772
Device WWN : 6006048000019010xxxxxxxxxxxxxxxx
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0016
Cache Partition Name : DEFAULT_PARTITION
Device Block Size : 512
Device Capacity
{
Cylinders : 174760
Tracks : 2621400
512-byte Blocks : 335539200
MegaBytes : 163838
KiloBytes : 167769600
}
Device Configuration : RDF1+R-5 (Meta Head,
Non-Exclusive Access)
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 (4):
{
-----------------------------------------------------------------
POWERPATH DIRECTOR PORT L
--------- ---------- ---- -------- ----
PdevName Type Type Num Sts VBUS TID SYMM
-----------------------------------------------------------------
Not Visible N/A FA 07B:0 RW 000 00 001
Not Visible N/A FA 08B:0 RW 000 00 006
Not Visible N/A FA 09B:0 RW 000 00 006
Not Visible N/A FA 10B:0 RW 000 00 015
}
Meta Configuration : Striped
Meta Stripe Size : 960k (1 Cylinders)
Meta Device Members (5) :
{
-----------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- ---------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
-----------------------------------------------------------------
--> 15CA 32768 - - N/A 0 0 Synchro
15CB 32768 - - N/A 0 0 Synchro
15CC 32768 - - N/A 0 0 Synchro
15CD 32768 - - N/A 0 0 Synchro
15CE 32768 - - N/A 0 0 Synchro
-----------------------------------------------------------------
163838 - - 0 0
}
Mirror Set Type : [RAID-5,R2 Remote,RAID-5,N/A]
Mirror Set DA Status : [RW,RW,RW,N/A]
Mirror Set Inv. Tracks : [0,0,0,0]
Back End Disk Director Information
{
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : R2 Remote
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
Hyper Type : RAID-5
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [N/A,N/A,N/A]
Disk Director Volume Number : N/A
Hyper Number : N/A
}
RAID-5 Device Information
{
Number of Tracks in a Stripe : 4
Overall Ready State of RAID-5 Device : Ready
Overall WriteProtect State of RAID-5 Device : Enabled
Member Number of the Failing Device : None
Member Number that Invoked the Spare : None
Disk Director (DA) that Owns the Spare : Inv
Copy Direction : N/A
RAID-5 Hyper Devices (7+1):
{
Device : 15CA (M)
{
---------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca
---------------------------------------------------------
02A:D1c 2744 52 4687 1 RW N/A 3 4
15A:C1c 1283 52 4687 5 RW N/A 3 4
01B:D1c 2633 52 4687 4 RW N/A 3 4
16B:C1c 1396 52 4687 8 RW N/A 3 4
02C:D1c 2763 52 4687 3 RW N/A 3 4
15C:C1c 1281 52 4687 7 RW N/A 3 4
01D:D1c 2650 52 4687 6 RW N/A 3 4
16D:C1c 1396 52 4687 2 RW N/A 3 4
}
Device : 15CB (m)
{
---------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca
---------------------------------------------------------
01A:Ce 676 53 4687 5 RW N/A 3 4
02A:C1b 1159 53 4687 6 RW N/A 3 4
15B:De 2028 53 4687 8 RW N/A 3 4
16B:D1b 2641 53 4687 7 RW N/A 3 4
01C:Ce 677 53 4687 1 RW N/A 3 4
02C:C1b 1177 53 4687 2 RW N/A 3 4
15D:De 1922 53 4687 4 RW N/A 3 4
16D:D1b 2642 53 4687 3 RW N/A 3 4
}
Device : 15CC (m)
{
---------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca
---------------------------------------------------------
15A:D1b 2513 53 4687 6 RW N/A 3 4
16A:De 2025 53 4687 5 RW N/A 3 4
01B:C1b 1163 53 4687 7 RW N/A 3 4
02B:Ce 678 53 4687 8 RW N/A 3 4
15C:D1b 2530 53 4687 2 RW N/A 3 4
16C:De 2046 53 4687 1 RW N/A 3 4
01D:C1b 1180 53 4687 3 RW N/A 3 4
02D:Ce 678 53 4687 4 RW N/A 3 4
}
Device : 15CD (m)
{
---------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca
---------------------------------------------------------
15A:Ce 678 53 4687 6 RW N/A 3 4
16A:C1b 1163 53 4687 5 RW N/A 3 4
01B:De 2028 53 4687 7 RW N/A 3 4
02B:D1b 2648 53 4687 8 RW N/A 3 4
15C:Ce 676 53 4687 2 RW N/A 3 4
16C:C1b 1179 53 4687 1 RW N/A 3 4
01D:De 2045 53 4687 3 RW N/A 3 4
02D:D1b 2647 53 4687 4 RW N/A 3 4
}
Device : 15CE (m)
{
---------------------------------------------------------
Disk DA Hyper Member Spare Disk
DA :IT Vol# Num Cap(MB) Num Status Status Grp# Ca
---------------------------------------------------------
01A:D1b 2507 53 4687 5 RW N/A 3 4
02A:De 2022 53 4687 6 RW N/A 3 4
15B:C1b 1163 53 4687 8 RW N/A 3 4
16B:Ce 675 53 4687 7 RW N/A 3 4
01C:D1b 2526 53 4687 1 RW N/A 3 4
02C:De 2040 53 4687 2 RW N/A 3 4
15D:C1b 1177 53 4687 4 RW N/A 3 4
16D:Ce 674 53 4687 3 RW N/A 3 4
}
}
}
RDF Information
{
Device Symmetrix Name : 15CA
RDF Type : R1
RDF (RA) Group Number : 2 (01)
Remote Device Symmetrix Name : 15CA
Remote Symmetrix ID : 00019010xxxy
R2 Device Is Larger Than The R1 Device : False
RDF Pair Configuration : Normal
RDF STAR Mode : False
RDF Mode : Synchronous
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 : GigE
RDF Link Domino : Disabled
Prevent Automatic RDF Link Recovery : Disabled
Prevent RAs Online Upon Power ON : Enabled
Device RDF Status : Ready (RW)
Device SA Status : Ready (RW)
Device RA Status : Ready (RW)
Device Link Status : Ready (RW)
Device Suspend State : N/A
Device Consistency 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 ) : Synchronized
Number of R1 Invalid Tracks : 0
Number of R2 Invalid Tracks : 0
RDFA Information:
{
Session Number : 1
Cycle Number : 0
Number of Devices in the Session : 261
Session Status : Inactive
Session Consistency State : N/A
Minimum Cycle Time : 00:00:30
Average Cycle Time : 00:00:00
Duration of Last cycle : 00:00:00
Session Priority : 33
Tracks not Committed to the R2 Side: 0
Time that R2 is behind R1 : 00:00:00
R2 Image Capture Time : N/A
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
}
}
C:\ECC\scripts>
15CA 15CA R1:2 RW RW RW S..1 0 0 RW WD Synchronized
Message was edited by:
Stefano Del Corno
Removed box sn
xe2sdc
4 Operator
•
2.8K Posts
0
April 9th, 2009 08:00
Blazer87
21 Posts
0
April 9th, 2009 08:00