pctech321
2 Iron

how to reconfigure BCVs from Meta ???

Jump to solution
hi...

we left whole bunch of unallocated Meta BCVs at local site with app 17G , with
each meta member of app 4G each ( total 4 mem in meta ), and we need to add some devices whcih are
9G each on local site to existing device group ( Timefiner/SRDF ) ..as i said BCVs are of larger size
even if we break the meta bcvs we can see BCVs of 4 G each..how to reconfigure
these sizes to pair with stand devices ...is there any configure solution for me or only EMC CE can do that??????

thank you...
Labels (1)
0 Kudos
1 Solution

Accepted Solutions
xe2sdc
4 Germanium

Re: how to reconfigure BCVs from Meta ???

Jump to solution
This is my BCV:

1626 Not Visible ***:* 06A:CF BCV N/Asst'd RW 8723

Now let's look where is it in the backend ...

clst06/root> symdev -sid 619 show 1626

Device Physical Name : Not Visible

Device Symmetrix Name : 1626
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0619

Attached VDEV TGT Device : N/A

...

Device Capacity
{
Cylinders : 18608
Tracks : 279120
512-byte Blocks : 17863680
MegaBytes : 8723
KiloBytes : 8931840
}

Device Configuration : BCV (Non-Exclusive Access)

...

Mirror Set Type : [Data,N/A,N/A,N/A]

Mirror Set DA Status : [RW,N/A,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] : [06A, C, F]
Disk Director Volume Number : 268 (0x10B)
Hyper Number : 9
Disk Capacity : 139814m
Disk Group Number : 3
}


You can see that my beloved BCV is located on Disk 06A:CF .. let's dig into the disk:

clst06/root> symdisk -sid 619 show 06A:CF

Symmetrix ID : 000xxxxx0619
Director : DF-6A
Interface : C
Target ID : F
Disk Group Number : 3

Vendor ID : SEAGATE
Product ID : SX3146707FC
Product Revision : C146LDF
Serial ID : 3KS0CMVD

Disk Blocks : 286339876
Block Size : 512
Actual Disk Blocks : 286749475
Total Disk Capacity (MB) : 139814
Free Disk Capacity (MB) : 81
Actual Disk Capacity (MB) : 140014
Hot Spare : False

Failed Disk : False


Hypers (24):
{
# Vol Emulation Dev Type Mirror Status Cap(MB)
--- ---- ---------------- ---- ------------- ------ -------------- --------
24 283 FBA 0844 RAID-5 1 Ready 2819
1 260 FBA 1226 Data 1 Ready 8723
2 261 FBA 12A6 Data 1 Ready 8723
3 262 FBA 1326 Data 1 Ready 8723
4 263 FBA 13A6 Data 1 Ready 8723
5 264 FBA 1426 Data 1 Ready 8723
6 265 FBA 14A6 Data 1 Ready 8723
7 266 FBA 1526 Data 1 Ready 8723
8 267 FBA 15A6 Data 1 Ready 8723
9 268 FBA 1626 Data 1 Ready 8723
10 269 FBA 16A6 Data 1 Ready 8723
11 270 FBA 1726 Data 1 Ready 8723
12 271 FBA 17A6 Data 1 Ready 8723
13 272 FBA 180A RAID-5 1 Ready 2914
14 273 FBA 182A RAID-5 1 Ready 2914
15 274 FBA 184A RAID-5 1 Ready 2914
16 275 FBA 186A RAID-5 1 Ready 2914
17 276 FBA 188A RAID-5 1 Ready 2914
18 277 FBA 18AA RAID-5 1 Ready 2914
19 278 FBA 18CA RAID-5 1 Ready 2914
20 279 FBA 18EA RAID-5 1 Ready 2914
21 280 FBA 190A RAID-5 1 Ready 2914
22 281 FBA 192A RAID-5 1 Ready 2914
23 282 FBA 194A RAID-5 1 Ready 2914
}



You can see that our device is the ninth (look carefully at its line and note the 9 at the beginning) so its neighbor are devices 15A6 and 16A6 .. In my example I can delete 1626 and 16A6, obtaining a single big "gap" and create a new volume in the gap. Again in my example, since both the devices are 18608 cyls in size, I can delete them and create a 37216 cyls device.

Cheers !
0 Kudos
15 Replies
xe2sdc
4 Germanium

Re: how to reconfigure BCVs from Meta ???

Jump to solution
Generally speaking, both (you and the CE) can do that .. But it depends on a lot of factors ...

Think to symdevs like slices of your disk .. If you want to build a bigger slice, you need two smaller slices whose sum is at least the size of the slice you want to create. And they also need to be adjacent, one close to the other. With BCVs it's easy to find the size of your existing devices since a "symdisk -sid xxx -v -hyper show 01D:04" will tell you the list of devices that belong to disk 01D:04 .. And "symdev -sid xxx show 0BAD" will tell you where the BCV device 0BAD is in the backend.

If you are a lucky man and your devices (the existing meta members) are layed out in a lucky way, you can delete the existing devices and create new ones, using symconfigure. But you have to find at first where your devices are spread in the backend.

I'll show you later the output of symdev and symdisk in my environment :-) .. Right now we have a faulted DWDM link .. :D
0 Kudos
xe2sdc
4 Germanium

Re: how to reconfigure BCVs from Meta ???

Jump to solution
This is my BCV:

1626 Not Visible ***:* 06A:CF BCV N/Asst'd RW 8723

Now let's look where is it in the backend ...

clst06/root> symdev -sid 619 show 1626

Device Physical Name : Not Visible

Device Symmetrix Name : 1626
Device Serial ID : N/A
Symmetrix ID : 000xxxxx0619

Attached VDEV TGT Device : N/A

...

Device Capacity
{
Cylinders : 18608
Tracks : 279120
512-byte Blocks : 17863680
MegaBytes : 8723
KiloBytes : 8931840
}

Device Configuration : BCV (Non-Exclusive Access)

...

Mirror Set Type : [Data,N/A,N/A,N/A]

Mirror Set DA Status : [RW,N/A,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] : [06A, C, F]
Disk Director Volume Number : 268 (0x10B)
Hyper Number : 9
Disk Capacity : 139814m
Disk Group Number : 3
}


You can see that my beloved BCV is located on Disk 06A:CF .. let's dig into the disk:

clst06/root> symdisk -sid 619 show 06A:CF

Symmetrix ID : 000xxxxx0619
Director : DF-6A
Interface : C
Target ID : F
Disk Group Number : 3

Vendor ID : SEAGATE
Product ID : SX3146707FC
Product Revision : C146LDF
Serial ID : 3KS0CMVD

Disk Blocks : 286339876
Block Size : 512
Actual Disk Blocks : 286749475
Total Disk Capacity (MB) : 139814
Free Disk Capacity (MB) : 81
Actual Disk Capacity (MB) : 140014
Hot Spare : False

Failed Disk : False


Hypers (24):
{
# Vol Emulation Dev Type Mirror Status Cap(MB)
--- ---- ---------------- ---- ------------- ------ -------------- --------
24 283 FBA 0844 RAID-5 1 Ready 2819
1 260 FBA 1226 Data 1 Ready 8723
2 261 FBA 12A6 Data 1 Ready 8723
3 262 FBA 1326 Data 1 Ready 8723
4 263 FBA 13A6 Data 1 Ready 8723
5 264 FBA 1426 Data 1 Ready 8723
6 265 FBA 14A6 Data 1 Ready 8723
7 266 FBA 1526 Data 1 Ready 8723
8 267 FBA 15A6 Data 1 Ready 8723
9 268 FBA 1626 Data 1 Ready 8723
10 269 FBA 16A6 Data 1 Ready 8723
11 270 FBA 1726 Data 1 Ready 8723
12 271 FBA 17A6 Data 1 Ready 8723
13 272 FBA 180A RAID-5 1 Ready 2914
14 273 FBA 182A RAID-5 1 Ready 2914
15 274 FBA 184A RAID-5 1 Ready 2914
16 275 FBA 186A RAID-5 1 Ready 2914
17 276 FBA 188A RAID-5 1 Ready 2914
18 277 FBA 18AA RAID-5 1 Ready 2914
19 278 FBA 18CA RAID-5 1 Ready 2914
20 279 FBA 18EA RAID-5 1 Ready 2914
21 280 FBA 190A RAID-5 1 Ready 2914
22 281 FBA 192A RAID-5 1 Ready 2914
23 282 FBA 194A RAID-5 1 Ready 2914
}



You can see that our device is the ninth (look carefully at its line and note the 9 at the beginning) so its neighbor are devices 15A6 and 16A6 .. In my example I can delete 1626 and 16A6, obtaining a single big "gap" and create a new volume in the gap. Again in my example, since both the devices are 18608 cyls in size, I can delete them and create a 37216 cyls device.

Cheers !
0 Kudos
Highlighted
MarcT2
2 Iron

Re: how to reconfigure BCVs from Meta ???

Jump to solution
Note that you can only "delete" volumes on a DMX or above. What happens is "NULL" volumes are created in place of the deleted volumes, and the backend space is freed up. This prevents the volume numbers changing.

Earlier generation Symmetrix (ie 5.5 and below) don't support NULL volumes. The CE can sometimes remove devices from the end of the bin. Its also possible for a CE to do other volume removes offline, but this can result in volume renumbering unless the bin is padded out with additional gatekeepers.

Marc
xe2sdc
4 Germanium

Re: how to reconfigure BCVs from Meta ???

Jump to solution
Marc maybe I misunderstood your words but AFAIK you don't have "null" volumes .. You simply have gaps in the sequence of splits. Since the introduction of DMX (as you noted) we are allowed to have gaps in the sequence of devices in both the symdev output (from the customer point of view) and inside each and every drive (in the backend). Before DMX, removing a volume required an offline of the whole box and the GK padding you already mentioned. But deleting two devices will give a single big gap if the devices are adjacent. Maybe the null devices you are talking about are simply placeholder to allow gaps in symdev output (the Volume Map in symwin).

In the following example, you can see that devices from 2123 to 21DA are bigger then surrounding devices. We had 5 smaller devices, deleted them and created 4 new (bigger) devices in the single gap that we got deleting old devices. Since the new devices were only slightly larger then the old ones, we wasn't able to use all the gap and this is the reason for the big gap you find between 21DA and 1433. Since we are using RAID5 in the following example, math isn't that easy since you have an overhead for each and every device (slice of disk).


clst06/root> symdisk -sid 104 -v -gaps -hyper show 1a:d9

Symmetrix ID : 000xxxxx0104
Director : DF-1A
Interface : D
Target ID : 9
Disk Group Number : 4

Vendor ID : IBM
Product ID : IX35L146EFDY10-0
Product Revision : IBM146F
Serial ID : ECW2URYC

Disk Blocks : 286339876
Block Size : 512
Actual Disk Blocks : 286749475
Total Disk Capacity (MB) : 139814
Free Disk Capacity (MB) : 4264
Actual Disk Capacity (MB) : 140014
Hot Spare : False

Failed Disk : False


Hypers (43):
{
# Vol Emulation Dev Type Mirror Status Cap(MB)
--- ---- ---------------- ---- ------------- ------ -------------- --------
1 480 FBA 0FBD RAID-5 1 Ready 2883
2 481 FBA 0FE5 RAID-5 1 Ready 2883
3 482 FBA 100B RAID-5 1 Ready 2883
4 483 FBA 1031 RAID-5 1 Ready 2883
5 484 FBA 1DD8 Data 1 Ready 8632
6 485 FBA 10C9 RAID-5 1 Ready 2883
7 486 FBA 10EF RAID-5 1 Ready 2883
8 487 FBA 1115 RAID-5 1 Ready 2883
9 488 FBA 113B RAID-5 1 Ready 2883
10 489 FBA 1161 RAID-5 1 Ready 2883
11 490 FBA 1187 RAID-5 1 Ready 2883
12 491 FBA 11AD RAID-5 1 Ready 2883
13 492 FBA 11D3 RAID-5 1 Ready 2883
14 493 FBA 11F9 RAID-5 1 Ready 2883
15 494 FBA 121F RAID-5 1 Ready 2883
16 495 FBA 1245 RAID-5 1 Ready 2883
17 496 FBA 126B RAID-5 1 Ready 2883
18 497 FBA 1291 RAID-5 1 Ready 2883
19 498 FBA 12B7 RAID-5 1 Ready 2883
20 499 FBA 168E RAID-5 1 Ready 2883
21 500 FBA 16A3 RAID-5 1 Ready 2883
22 501 FBA 16BE RAID-5 1 Ready 2883
23 502 FBA 16DF RAID-5 1 Ready 2883
24 503 FBA 2123 RAID-5 1 Ready 2914
25 504 FBA 2160 RAID-5 1 Ready 2914
26 505 FBA 21A0 RAID-5 1 Ready 2914
27 506 FBA 21DA RAID-5 1 Ready 2914
- - N/A - GAP - N/A 2762
28 507 FBA 1433 RAID-5 1 Ready 2883

29 508 FBA 1459 RAID-5 1 Ready 2883
30 509 FBA 147F RAID-5 1 Ready 2883
31 510 FBA 14A5 RAID-5 1 Ready 2883
32 511 FBA 14CB RAID-5 1 Ready 2883
33 512 FBA 14F1 RAID-5 1 Ready 2883
34 513 FBA 1945 RAID-5 1 Ready 2883
35 514 FBA 196D RAID-5 1 Ready 2883
36 515 FBA 1993 RAID-5 1 Ready 2883
37 516 FBA 1F40 Data 1 Ready 8632
38 517 FBA 1330 RAID-5 1 Ready 2914
39 518 FBA 2258 RAID-5 1 Ready 2819
40 519 FBA 228F RAID-5 1 Ready 2819
41 520 FBA 1A9D RAID-5 1 Ready 2883
42 521 FBA 1AC3 RAID-5 1 Ready 2883
43 522 FBA 1AE9 RAID-5 1 Ready 2883
- - N/A - GAP - N/A 1501
}
0 Kudos
MarcT2
2 Iron

Re: how to reconfigure BCVs from Meta ???

Jump to solution
A "Null Device" is simply a volume which has been deleted, and the volume number (symdev number) hasn't been reused.

When you list volumes from Inlines they show up in yellow text as "Null Device", but it appears you can't see them from Solutions Enabler:

# symdev show FE -sid 1114

The operation cannot be completed because one or more devices are unconfigured

BR,
Marc
0 Kudos
pctech321
2 Iron

Re: how to reconfigure BCVs from Meta ???

Jump to solution
hi...

gaps flag is illegal ??? whats the problem is there no gaps on the disk or the SE version problem mine is V6.0.0.0 (EL: 623)

server1/root: / > symdisk -sid 1359 -v -gaps -hyper show 16d:dd
'-gaps': Illegal option.

and i check the whole unallocated BCVs configuration ..all contiguous of BCV devices on Disk are of same size 4251..
so No solution for BCV allocation of standard devices of size 9.06G .???

by all these we are planning to implement Recovery point next couple of weeks rather than SRDF ...by that we reclaim lot of BCVs space
right ???? if we confirm to move for RP ..can we convert BCVs to devices of RAID-5 protection type ????

thank you....
0 Kudos
MarcT2
2 Iron

Re: how to reconfigure BCVs from Meta ???

Jump to solution
I think you need to update your Solutions Enabler, 6.4.x is the latest and the -gaps flag definately works there.

The point is that if you delete several contiguous small volumes, you should be able to create a larger volume in the space. You may need to delete 3 consecutive 4251MB BCVs to create a 9GB volume in their place. To be honest though, you may be better off talking to your EMC CE to check this out and maybe do it via binfiles.

I don't know anything about Recover Point - but yes, you can change the BCVs into RAID5 volumes. Off the top of my head I don't know if you can convert them directly, but you can certainly delete them and create RAID5 volumes in their place. Again, an EMC CE will be able to look at your config and advise.

Hope that helps!
Marc
xe2sdc
4 Germanium

Re: how to reconfigure BCVs from Meta ???

Jump to solution
and i check the whole unallocated BCVs configuration
..all contiguous of BCV devices on Disk are of same
size 4251..
so No solution for BCV allocation of standard devices
of size 9.06G .???


Since the code uses cylinders when defining disks, I suggest you to use -cyl to show sizes in cyls and not in Mb.

by all these we are planning to implement Recovery
point next couple of weeks rather than SRDF ...by
that we reclaim lot of BCVs space
right ???? if we confirm to move for RP ..can we
convert BCVs to devices of RAID-5 protection type
????


You can't really "convert" your devs from BCV to RAID or viceversa. Syconfigure offers a "convert" command but it does not apply here. You have to delete old BCV devices and create new RAID devices. This may become a painful operation since when you delete 4 18000 cyls BCV device, you expect to create 3 RAID5 (3+1) devices, 18000 cyls each. But this wont work since RAID5 uses some more cyls for every slice so you'll be able to create only 2 RAID5 devices, wasting 33% of the space .. Nice shot :D

I cant' say anything about RP and BCVs since I don't really remember how is your infrastructure layed out. Please open a new thread and explain in a deeper detail both the infrastructure and your idea on the introduction of RP.
0 Kudos
pctech321
2 Iron

Re: how to reconfigure BCVs from Meta ???

Jump to solution
one last thing here....in order to do these configuration changes like
delete the devices and create a new ones..we need a downtime for symmetrix?

thank you ..
0 Kudos