Unsolved
This post is more than 5 years old
8 Posts
0
1877
December 15th, 2009 02:00
Hyper and Metavolume question
Hi all,
I have a questions related to carving the disks intially. I am bit newbie to symmetrix and confused with the inital setup of DMX-4.
1. Do we have the same hyper for each disks or can hyper be set different for each drive or is it only different as per the size of drive ?
2. When do we set the hypers , i mean at what stage , is it during the initial bin file configuration by CE?
3. Is it possible to change the hyper size of a particular disks?
4. Once the hypers are set/carved , what is the next step in presenting the LUNS to hosts, do we have to create RAID groups like Clarrions?
5. Why is people mostly asking expected application IOPS and block size when configuring hypers , are they related? How?
Sorry abt too much questions but i would appreicate your responses as it will get me a clear picture and help me with carving of this dmx4.
Regards,
kavanspace
0 events found
Quincy561
1.3K Posts
0
December 15th, 2009 03:00
1) You can make the logical volumes any size you like. However for ease of use and performance it is better to have logical volumes that are either all the same size, or only a few sizes. Generally smaller numbers of larger logicals is better than huge numbers of smaller hypers for performance.
2) You can have only a small number of gatekeepers defined on the Symm, and create all the volumes with SMC or the CLI if you want.
3) You can delete a logical volume and re-create a new one, but depending on what you are trying to do, you won't be able to because of contiguous space on the physical
4) Once you create a logical, you map it to the host. There is no set raid type for a given disk in Symmetrix. You could have every available raid type on a given set of disks. This is not a best practice however. We generally recommend that you not mix all raid types on a given disk.
5) Generally a disk can give a specific number of IOPs depending on the speed. For example, we suggest using around 150 IOs/sec for a 15k drive as a planning maximum. This will scale until you reach the limit of the backend CPU. If you need more details, I suggest you speak with one of the performance folks on your EMC account team for answers about your workload.
kavanspace1
8 Posts
0
December 15th, 2009 04:00
Hi Quincy,
Thanks for the reply. It did cleared some of my confusioin but i have few other questions .
In your post is logical volumes = hypers or is logical volume = meta luns or is it just a general LUN ?
Thanks
Quincy561
1.3K Posts
0
December 15th, 2009 04:00
The term "hyper" in Symmetrix can be confusing. What it refers to is a physical split or partition on a physical disk. So a RAID1 logical volume will have 2 hypers on two disks. A 3+1 raid5 logical will have 4 hypers on 4 disks, etc.
A meta volume is simply a collection of symm logical volumes put together and presented to the host as one volume.
In my post I was only talking about standard logical volumes, not meta volumes, but everything would still apply if you put metas on top of that.
Quincy561
1.3K Posts
0
January 24th, 2013 12:00
For virtual provisioned systems, the disk hypers are independent of the host facing volumes. It is important to follow best practices when carving up the data devices which should only have to be done once.
DineshPunyani
54 Posts
0
January 24th, 2013 12:00
Who will do Task of Creating Hypers (physical split or partition on a physical disk) on Newly Purchased Disks on VMAX ? Is it going to be EMC or Customer himself ?
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
January 24th, 2013 12:00
We do it ourselves (customer)
DineshPunyani
54 Posts
0
January 24th, 2013 13:00
Thanks for Quick response.
We will carve data devices following same practice which we did for other THIN Pools. But Before doing that i need to create hypers on Newly purchased SATA disks. But i am creating Hypers for the first time. If someone can share the procedure to create Hypers on new disks with me then it will be very helpful.
We have a alreay existing SATA Disk Group on VMAX and I have checked Hypers on one disk are 49 in number.
Details of one exising USED Disk are below:
Director : DF-7A
Interface : C
Target ID : 0
Spindle ID : 2D0
External WWN : N/A
Disk Group Number : 1
Disk Group Name : SATA_PROD
Disk Location : Internal
Technology : SATA
Speed (RPM) : 7200
Form Factor : 3.5
Vendor ID : SATAHGST
Product ID :
Product Revision :
Serial ID :
Disk Blocks : 3677203921
Block Size : 520
Actual Disk Blocks : 3677203921
Total Disk Capacity (MB) : 1823565
Free Disk Capacity (MB) : 39
Actual Disk Capacity (MB) : 1823565
Rated Disk Capacity (GB) : 2000
Spare Disk : False
Spare Coverage : N/A
Encapsulated : False
Disk Service State : Normal
Hypers (49):
{
# Vol Emulation Dev Type Mir Mbr Status Cap(MB)
--- ----- ---------------- ---- ------------- --- --- -------------- --------
1 1 VAULT_DEVICE 0000 Data 1 N/A N/A 5200
2 2 FBA 0115 RAID-6 1 2 Ready 37882
3 3 FBA 011E RAID-6 1 3 Ready 37882
4 4 FBA 0127 RAID-6 1 4 Ready 37882
5 5 FBA 0130 RAID-6 1 5 Ready 37882
6 6 FBA 0139 RAID-6 1 6 Ready 37882
7 7 FBA 0142 RAID-6 1 7 Ready 37882
8 8 FBA 014B RAID-6 1 8 Ready 37882
9 9 FBA 0154 RAID-6 1 1 Ready 37882
10 10 FBA 015D RAID-6 1 2 Ready 37882
11 11 FBA 0166 RAID-6 1 3 Ready 37882
12 12 FBA 016F RAID-6 1 4 Ready 37882
13 13 FBA 0178 RAID-6 1 5 Ready 37882
14 14 FBA 0181 RAID-6 1 6 Ready 37882
15 15 FBA 018A RAID-6 1 7 Ready 37882
16 16 FBA 0193 RAID-6 1 8 Ready 37882
17 17 FBA 019C RAID-6 1 1 Ready 37882
18 18 FBA 01A5 RAID-6 1 2 Ready 37882
19 19 FBA 01AE RAID-6 1 3 Ready 37882
20 20 FBA 01B7 RAID-6 1 4 Ready 37882
21 21 FBA 01C0 RAID-6 1 5 Ready 37882
22 22 FBA 01C9 RAID-6 1 6 Ready 37882
23 23 FBA 01D2 RAID-6 1 7 Ready 37882
24 24 FBA 01DB RAID-6 1 8 Ready 37882
25 25 FBA 01E4 RAID-6 1 1 Ready 37882
26 26 FBA 01ED RAID-6 1 2 Ready 37882
27 27 FBA 01F6 RAID-6 1 3 Ready 37882
28 28 FBA 01FF RAID-6 1 4 Ready 37882
29 29 FBA 0208 RAID-6 1 5 Ready 37882
30 30 FBA 0211 RAID-6 1 6 Ready 37882
31 31 FBA 021A RAID-6 1 7 Ready 37882
32 32 FBA 0223 RAID-6 1 8 Ready 37882
33 33 FBA 022C RAID-6 1 1 Ready 37882
34 34 FBA 0235 RAID-6 1 2 Ready 37882
35 35 FBA 023E RAID-6 1 3 Ready 37882
36 36 FBA 0247 RAID-6 1 4 Ready 37882
37 37 FBA 0250 RAID-6 1 5 Ready 37882
38 38 FBA 0259 RAID-6 1 6 Ready 37882
39 39 FBA 0262 RAID-6 1 7 Ready 37882
40 40 FBA 026B RAID-6 1 8 Ready 37882
41 41 FBA 0274 RAID-6 1 1 Ready 37882
42 42 FBA 027D RAID-6 1 2 Ready 37882
43 43 FBA 0286 RAID-6 1 3 Ready 37882
44 44 FBA 028F RAID-6 1 4 Ready 37882
45 45 FBA 0298 RAID-6 1 5 Ready 37882
46 46 FBA 02A1 RAID-6 1 6 Ready 37882
47 47 FBA 02AA RAID-6 1 7 Ready 37882
48 48 FBA 02B3 RAID-6 1 8 Ready 37882
49 49 FBA 02BC RAID-6 1 1 Ready 37882
}
New Disks in New Disk Group are below:
Disks Selected : 22
Disk Group : 11
Disk Group Name : DISK_GROUP_011
Disk Location : Internal
Technology : SATA
Speed (RPM) : 7200
Form Factor : 3.5
Capacity(MB)
Ident Symb Int TID Vendor Type Hypr Total Free Actual
------ ---- --- --- ---------- ---------- ---- ---------- ---------- ----------
DF-5A 05A C 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-5A 05A D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6A 06A C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-11A 11A D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-12A 12A C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-12A 12A D 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-5B 05B C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6B 06B C 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6B 06B D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-11B 11B C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-11B 11B D 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-12B 12B D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-5C 05C C 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-5C 05C D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6C 06C C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-11C 11C D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-12C 12C C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-5D 05D C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6D 06D C 18 SATAST C02TMSP 0 1823565 1823565 1823565
DF-6D 06D D 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-11D 11D C 17 SATAST C02TMSP 0 1823565 1823565 1823565
DF-12D 12D D 17 SATAST C02TMSP 0 1823565 1823565 1823565
---------- ---------- ----------
Total 40118420 40118420 40118420
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
January 24th, 2013 13:00
https://community.emc.com/message/630554
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
January 24th, 2013 13:00
for pools you create TDATs from disk groups and then add TDATs to your pool. Best practice 8 TDATs per physical spindle.
Quincy561
1.3K Posts
0
January 24th, 2013 14:00
If you are adding drives to an existing VP pool, you should make the TDATs the same as the other drives, that way when you re-balance, the workload will be evenly distributed across all the drives.
Zikas
278 Posts
0
January 24th, 2013 15:00
Hi kavanspace,
the steps that Quincy mentioned are the correct steps and are the correct answer to your question.
Also at number 8 Dynamox's answer 8 TDAT's per physical disks are the Best Practice.
Quincy561
1.3K Posts
1
January 25th, 2013 06:00
First thing, 22 isn't a multiple of 8, so you can only use 16 of these drives for 6+2, you need 24 to get 3 RAID groups.
For 16 drives, 2 are for parity, so 12 disks contain data. So 1823565 * 12 = 21882780MB or 21369.9GB.
Since the largest volume is ~240GB, you will need to create about 88 hypers on the 16 drives.
You would be best to match the size and number of TDATs to what you have in the existing thin pool.
DineshPunyani
54 Posts
0
January 25th, 2013 06:00
We have 22 new SATA Disks of Actual Size :1823565 MB. We have Existing Thin Pool which contain RAID-6(6+2) TDATs and Each TDAT is of SIZE: 238710 CYL.
Can someone please tell me how many TDATs i can create out of free 22 New SATA Disks ? I want to use this disk group completely for existing Thin Pool.
Count
Size (cyl)
Group
Mirror Type
Special Type
????
238710
11
RAID6(6+2)
TDAT
DineshPunyani
54 Posts
0
January 27th, 2013 01:00
Hi All,
Thank you very much for answering my queries.
I am able to do math after knowing that how hyper stuff is calculated and how it works.
Now I need to check with my management that “How many new SATA Disks were ordered 22 or 24 ?”
As per my knoweldge they ordered 24 but i think EMC CE has marked 2 of them as HotSpare in VMAX and rest 22 are kept in Disk Group-11.