changing LUN configuration from standard to bcv

are the following commands the answer to my question ?:


symconfigure reserve -sid 2143 convert dev 09FF to BCV+R-5 preview
symconfigure reserve -sid 2143 convert dev 09FF to BCV+R-5 prepare
symconfigure reserve -sid 2143 convert dev 09FF to BCV+R-5 commit

yes and no

the commands you wrote are wrong (strictly speaking).

1) create a file named however you want (eg howeveryouwant.txt) containing the following line:

convert dev 09FF to BCV+R-5;

2) from your shell issue the following command and check for errors.

symconfigure -sid 2143 -f howeveryouwant.txt preview

3) if no errors raised from the previous command, issue the following:

symconfigure -sid 2143 -f howeveryouwant.txt commit

The Prepare step is usually suggested but in this specific context we can skip it almost safetly.

Have fun with symconfigure if you have the needed license

ok its working fine.
Just another question:

i'm preparing a clone as follows and would like to know if i can group all luns (05FF,060F,...,066F) under the same logicaldevicename DEV001 instead of having a ldevname per device ? (i'm i supposed to create a meta lun before ?)

Standard (STD) Devices (8):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
DEV001 /dev/rdsk/c46t10d2 05FF (M) RW 157500
DEV002 /dev/rdsk/c46t10d3 060F (M) RW 157500
DEV003 /dev/rdsk/c46t10d4 061F (M) RW 157500
DEV004 /dev/rdsk/c46t10d5 062F (M) RW 157500
DEV005 /dev/rdsk/c46t10d6 063F (M) RW 157500
DEV006 /dev/rdsk/c46t10d7 064F (M) RW 157500
DEV007 /dev/rdsk/c46t11d0 065F (M) RW 157500
DEV008 /dev/rdsk/c46t11d1 066F (M) RW 157500
}

BCV Devices Locally-associated (8):
{
--------------------------------------------------------------------
Sym Cap
LdevName PdevName Dev Att. Sts (MB)
--------------------------------------------------------------------
BCV001 N/A 0A0F (M) RW 157500
BCV002 N/A 0A1F (M) RW 157500
BCV003 N/A 0A2F (M) RW 157500
BCV004 N/A 0A3F (M) RW 157500
BCV005 N/A 0A4F (M) RW 157500
BCV006 N/A 0A5F (M) RW 157500
BCV007 N/A 0A6F (M) RW 157500
BCV008 N/A 0A7F (M) RW 157500
}

ok.

i only wanted to simplify the symclone establish command by issuing only one line command instead of as many lines as number of devices.

You have a different name for each and every device you can map on the frontend .. If you want a single logical name for different devices you have to form a meta. But forming a meta means that the hosts will no longer be able to see the different devices. They will see a single bigger device.
Could you explain better what do you want to do ??

That doesn't really seem to be a "fly in the ointment" to me. To me it says that Clones can do everything a BCV can do (and more).

i know symmir but understood that symclone was an evolution of symmir ...

Yeah, that what everybody's telling me, but why is a BCV faster in copying the data ? They're both made up of the same components....

It has to be able to. EMC uses Clone to emulate BCVs for RAID5 devices. Therefore the clone has to be able to support every feature of a BCV.

There, another reason not to use clones or emulated clones / bcvs.

But still, if you don't have capacity probs, I would use (at least) 2 sets of clones to be able to fall back to the other clone and take advantage of the fact that a clone is immediately available when you activate it.

IMHO a clone is a more advanced version of a BCV.
The BCV is only usable as soon as you split it. You can only split it, if all data has been copied.
A Clone is usable as soon as you activate it, copying can still be done in the background, so yes, a clone is more advanced. furthermore a Clone doesn't cost you a mirror position on you STD.

So it sounds like you just need to issue your commands against the device group instead of the individual devices.

Just to be clear, you don't need the target device to be a BCV if you intend to use clone. Its quite possible to clone from a R5 standard device to another R5 standard device.

Under the covers, TimeFinder/Clone works in a very different way to TimeFinder/Mirror (traditional BCVs). Clones do not require a "mirror position", which *is* required for a BCV, hot spare, or SRDF copy.

The only fly in the ointment is that RAID5 BCVs are actually emulated using clones. Traditional BCVs can only be unprotected or mirrored (and with or without SRDF), but cannot be RAID5.

Hope that's of some use!

Well.... one thing: can a clone do a reverse split ?
For the rest I agree !

But then again, can you do a reverse split with a clone ? This particular one is pretty useful when you have a BCV established and you corrupted your date. By doing a reverse split, the BCV is split off of the STD and the BCV is restored to the state it was in before the establish.
I don't know.... is a clone capable of doing this ?