DMX Disk Extension

1) if you an RDF protected volume and want to expand the volume, you have to REMOVE RDF protection. Thus you can't add a dyn_rdf device to existing meta.

2) attribute "dyn_rdf" means that your device may become either an R1 or an R2 device (when you create new pairs).

3) if you configure a device as RDF1_only capable, your symdev can become R1 when you create new pairs. But a RDF1_only capable device can NOT become an R2 device. This means also you can't swap dynamic pairs with "RDF1_only" or "RDF2_only" devices.
Note that when you list symdevs, they'll show up as RDF1 (or RDF2) if already in pairs (thus having thier respective R2 or R1). A symdev "dyn_rdf" enabled (but not bound to an RDF pair) will show up as either 2-way-mir or RAID5 or whatever protection you choose.

So,Do you want me to remove the RDf capable on existing Meta(0ed3) & the new hypers what ever am going to add(0d45,0d46) & once the disk extension is done again i can make it RDF Capable if required?

*Also let me kow do i need to Unmask & Unmap the device during this operation or can i proceed direvctly?

Excellent!!!!!!!!!!!!!!!!
Before winding up i have small query?
1. As stated earlier,can you plz clarify what syntax to be used for creating RDF1 capable & RDF1_or_RDF2 capable.
2.What will this syntax create then,si itRDF1 or the other?
*****************set device xxxx attribute=dyn_rdf**********************

Enabling attribute "dyn_rdf" means allowing a symdev to become either R1 or R2 (RDF1_or_RDF capable).

Usually it's suggested to always enable both behaviours (since it leaves a lot more options). If you want to enable only one of the behaviours, you can enable attribute "dyn_RDF1_only" or "dyn_RDF2_only" flags. Obviously you can enable only one of the three flags we mentioned.

And you've got the right syntax

Sound Good!

Hi
I tried extending the disk by following the steps sugested by tou,invain it gives me the below error.

T:\>symconfigure -sid 760 -f "c:\config\suresh\R320988\extend.txt" preview

Execute a symconfigure operation for symmetrix '000xxxxx0760' (y/ ) ? y

A Configuration Change operation is in progress. Please wait...

Establishing a configuration change session...............Established.

Error occurred while Defining change number 1:
The devices being acted on are a mixture of dynamic and Non dynamic DRDF
ices
Device 0D45 generated the failure

Terminating the configuration change session..............Done.

The configuration change session has failed.

**** I tried with below steps,No go.
1.Tried extending the disks,No go(0D45,0D46 & 0080 are RDF1_or_RDF2 Capable & OED3 is only RDF1 capable)
add dev 0d45:0d46 to meta 0ed3, protect_data=TRUE, bcv_meta_head=0080;
2.Unmask & Unmap the device (OED3) & then tried removing the rdf by using
----------------set device 0ed3 attribute=no dyn_rdf;----------------------------
it gives a message saying cannot perform this operation on a RDf device
3.Tried with below,No go
---------set device 0ed3 attribute=dyn_rdf;-----------
4.Tried converting the device to dynamic(Assuming this as a static RDF),No go
---------------convert rdf dev 0ed3 to dynamic;-------------------------

**********Plz let me know if the solution for this************************

Message was edited by:
Stefano Del Corno
removed box sn

sureshctr I'm sorry .. probably I assumed something that is clear to me but that may be not that clear ...

1) when you form (or expand) metavolumes, all metamembers MUST have exactly same flags.. You have some metamembers RDF1_capable and some other RDF1_or_RDF2_capable.

2) before deleting an RDF pair you have to split (or suspend) the RDF pair (you can find details in symcli documentation, look for "symrdf deletepair")

3) your symdev is already a dynamic RDF pair. the issue is that it's established with another (remote) volume.

4) same as above .. you can convert a static pair to a dynamic pair .. but you are already dynamic. you have to split (and deletepair) before expanding metavolume.

What should you do ??
At least you have to give new metamembers EXACTLY SAME FLAGS as existing metavolume. Later you can do the following:

symrdf -rdfg xxx -sid 760 -file pairfile susp
 
symrdf -rdfg xxx -sid 760 -file pairfile deletepair
 
symconfigure -sid 760 -file expand-meta.cmd -nop preview/prepare/commit
 
symconfigure -sid 444 -file expand-other-meta.cmd -nop preview/prepare/commit
 
symrdf -rdfg xxx -sid 760 -file pairfile createpair
 
symrdf -rdfg xxx -sid 760 -file pairfile -full establish

Please try to clarify every possible doubt before running above commands .. you may affect your environment thus please please please be carefull.

Oh in case I didn't warn you.. BE CAREFULL before running above mentioned commands ... I'll post soon commands to issue .. I need to better understand your environment.

sureshctr I'd love to see at least output of the following commands

symdev -sid 760 show 0ED3
 
symdev -sid760 show 0D45

NOTE: 0ED3 is RDF1 capable,but has no pairs.
C:\>psexec \\emcl001d symdev -sid 760 show 0ed3|more

remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com



Device Physical Name : Not Visible

Device Symmetrix Name : 0ED3
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0760

Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5671
Device WWN : 60060480000xxxxx076047544B454433
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0007
Cache Partition Name : N/A

Device Block Size : 512

Device Capacity
-- More -- symdev exited on emcl001d with error code 0.
{
Cylinders : 408980
Tracks : 6134700
512-byte Blocks : 392620800
MegaBytes : 191709
KiloBytes : 196310400
}

Device Configuration : 2-Way Mir (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_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 (2):
{
----------------------------------------------------------------------
POWERPATH DIRECTOR PORT LUN
--------- ---------- ---- -------- ---------
PdevName Type Type Num Sts VBUS TID SYMM Host
----------------------------------------------------------------------
Not Visible N/A FA 08B:1 RW 000 00 019 N/A
Not Visible N/A FA 09B:0 RW 000 00 019 N/A
}

Meta Configuration : Striped
Meta Stripe Size : 960k (2 Cylinders)
Meta Device Members (11) :
{
----------------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- --------------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
----------------------------------------------------------------------
--> 0ED3 17428 - - N/A - - N/A
0ED4 17428 - - N/A - - N/A
0ED5 17428 - - N/A - - N/A
0ED6 17428 - - N/A - - N/A
0ED7 17428 - - N/A - - N/A
0ED8 17428 - - N/A - - N/A
0ED9 17428 - - N/A - - N/A
0EDA 17428 - - N/A - - N/A
0EDB 17428 - - N/A - - N/A
0EDC 17428 - - N/A - - N/A
0EDD 17428 - - N/A - - N/A
----------------------------------------------------------------------
191709 - - - -
}

Mirror Set Type : [Data,Data,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 : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [11D, D, 8]
Disk Director Volume Number : 420 (0x1A3)
Hyper Number : 4
Disk Capacity : 285902m
Disk Group Number : 1

Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [02B, C, 8]
Disk Director Volume Number : 149 (0x94)
Hyper Number : 4
Disk Capacity : 285902m
Disk Group Number : 1
}

C:\>psexec \\emcl001d symdev -sid 760 show 0d45|more

PsExec v
1.92 - Execute processes remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com



Device Physical Name : Not Visible

Device Symmetrix Name : 0D45
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0760

Attached BCV Device : N/A

Attached VDEV TGT Device : N/A

Vendor ID : EMC
Product ID : SYMMETRIX
Product Revision : 5671
Device WWN : 60060480000xxxxx076053594D443435
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : 0x0006
Cache Partition Name : N/A

Device Block Size : 512

Device Capacity
{
Cylinders : 37180
Tracks : 557700
512-byte Blocks : 35692800
MegaBytes : 17428
KiloBytes : 17846400
}

Device Configuration : 2-Way Mir (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 : N/A (N/A)

Mirror Set Type : [Data,Data,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 : Data
-- More -- symdev exited on emcl001d with error code 0.
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [11A, D, 7]
Disk Director Volume Number : 400 (0x18F)
Hyper Number : 9
Disk Capacity : 285902m
Disk Group Number : 1

Hyper Type : Data
Hyper Status : Ready (RW)
Disk [Director, Interface, TID] : [05A, C, 8]
Disk Director Volume Number : 150 (0x95)
Hyper Number : 6
Disk Capacity : 285902m
Disk Group Number : 1
}



C:\>

Message was edited by:
Stefano Del Corno

removed symm sn

If your metavolume isn't paired, you have to give new metamembers EXACTLY SAME FLAGS as existing metavolume.

I guess it's easier to change the metavolume.. Remove dyn_rdf1_only attribute and add (with another symconfigure) dyn_rdf to your symdev 0ED3 ..

set device 03ED attribute=no dyn_rdf1_only;

set device 03ED attribute=dyn_rdf;

Now both existing metavolume and new members should have same attributes and you should be able to expand your metavolume.

Excellent!!!!
Its now Working.Thanks a lot.