This post is more than 5 years old
26 Posts
0
1110
June 16th, 2010 09:00
Clone STD Meta to THIN Meta
I have a VMAX where I want to clone from a STD META (native provisioned) to a THIN META.
Microcode Version (Number) : 5874 (16F20000)
Microcode Registered Build : 4
Microcode Date : 05.04.2010
Microcode Patch Date : 05.04.2010
Microcode Patch Level : 229
Symmwin Version : 182
I get this when I try to do a:
symclone -sid XXXX -f pairing.list establish -consistent -full
Devices: 034A(S) - 08B2(T) [(M) NOT PAIRED - META CFG MISMATCH]
Both devices seems to be configured the same from a config perspective:
034A:
Device Capacity
{
Cylinders : 297440
Tracks : 4461600
512-byte Blocks : 571084800
MegaBytes : 278850
KiloBytes : 285542400
}
Device Configuration : RAID-5 (Meta Head)
08B2:
Device Capacity
{
Cylinders : 297440
Tracks : 4461600
512-byte Blocks : 571084800
MegaBytes : 278850
KiloBytes : 285542400
}
Device Configuration : TDEV (Meta Head)
Any thoughts?
Aaron
dynamox
9 Legend
•
20.4K Posts
0
June 16th, 2010 11:00
i know with thick devices you have to match config layout, but could be that thick to thin requirement is still the same. I guess next thing i would try symclone to striped thin.
dynamox
9 Legend
•
20.4K Posts
0
June 16th, 2010 09:00
are meta members of each meta configured the same ? (number of members)
AaronMSTRCRD
26 Posts
0
June 16th, 2010 11:00
Meta Members are the same. (Config is striped vs concat though)
034A:
Meta Configuration : Striped
Meta Stripe Size : 960k (1 Cylinders)
Meta Device Members (8) :
{
----------------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- --------------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
----------------------------------------------------------------------
--> 034A 34856 0 0 Synchronized - - N/A
034B 34856 0 0 Synchronized - - N/A
034C 34856 0 0 Synchronized - - N/A
034D 34856 0 0 Synchronized - - N/A
034E 34856 0 0 Synchronized - - N/A
034F 34856 0 0 Synchronized - - N/A
0350 34856 0 0 Synchronized - - N/A
0351 34856 0 0 Synchronized - - N/A
----------------------------------------------------------------------
278850 0 0 - -
}
8B2:
Meta Configuration : Concatenated
Meta Device Members (8) :
{
----------------------------------------------------------------------
BCV DATA RDF DATA
---------------------------- --------------------------
Sym Cap Std Inv BCV Inv Pair R1 Inv R2 Inv Pair
Dev (MB) Tracks Tracks State Tracks Tracks State
----------------------------------------------------------------------
--> 08B2 34856 - - N/A - - N/A
08B3 34856 - - N/A - - N/A
08B4 34856 - - N/A - - N/A
08B5 34856 - - N/A - - N/A
08B6 34856 - - N/A - - N/A
08B7 34856 - - N/A - - N/A
08B8 34856 - - N/A - - N/A
08B9 34856 - - N/A - - N/A
----------------------------------------------------------------------
278850 - - - -
}
symcfg -sid XXX list -pool (only 5% utilized)
SATA TH FBA RAID-6(6+2) 1203179220 1203179220 64183272 1138995948 5 Ena
Aaron
AaronMSTRCRD
26 Posts
0
June 16th, 2010 12:00
Of course, a convert of a Thin Meta from concat to striped does not seem to be supported..... I guess this means a dissolve and new form? *sigh*
$ symconfigure -sid XXXX -cmd "convert meta 08b2 config=STRIPED, stripe_size=1920, protect_data=FALSE ;" commit
Execute a symconfigure operation for symmetrix 'XXXXXXXXXXXXX' (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 requested feature is not supported for this microcode or SYMAPI version
Terminating the configuration change session..............Done.
The configuration change session has failed.
$ symcli
Symmetrix Command Line Interface (SYMCLI) Version V7.1.0.0 (Edit Level: 1009)
built with SYMAPI Version V7.1.0.0 (Edit Level: 1009)
Aaron