We just got a new vmax with 3 flavors of disk, (EFD, FC, SATA). I am new to EMC and was wondering what is the best way to architect how the disk layout is configured for presenting storage to our hosts for optimal performance. We would like to use virtual provisioning, is there a "best practice" when configuring your hypers to gain optimal performance? Need some assistance here to understand how tracks and cylinders play into the configuration.
If you cannot find these documents on PowerLink I have both Best Practices documents I can send you if you would like to post your email address or I can put on EMC FTP site.
Create a standard TDAT size that fits best for all 3 types of storage.
You want your TDAT's as large as you can get them to make use of the the most space in the physical disk (usually 2-4 TDAT's fit in the disk well for mirrored pairs).
Then create three separate pools such as (just examples, name then whatever you want)
shared_450_efd
shared_450_fc
shared_1000_sata
Now create your various TDEVS, these can be any size you wish. For the sake of administration you may want to pick a small handfull of "standard sizes" but it is by no means required.
If you want to use these devices just like regular devices then when you bind them to the pool you will want to "preallocate" the entire lun size. Otherwise they act like thin devices.
We've been really impressed with virtual provisioning so far. It's nice to see all disks working together with low overhead. I don't think I will go back to a traditional "hyper" model.
I'm also not much of a GUI guy and the VP stuff lends really well to scripting and capacity planning.
Virtual provisioning brings in some new terms. You still have your physical drive configuration of some raid type right; raid-1/5 etc. On that you then create data devices; data devices are not host presentable and is what you place into the virtual pool. You then create a thin device which you bind to a pool and that is host presentable. TDAT I believe they are referring to a thin data device which is the host presentable device.
I agree with the preallocation ,which is what I have done, it completely negates the thin "unfriendly" application arguement. One very nice thng in using the GUI is I created a template for a data warehouse environment and used that in creating the devices. Once the template is created it you only fill in two fields and are then creating devices; makes a fast process a bit faster.
f he is going to create virtual provisioning FAST isnt going to help him right now; he will need to wait for FAST/VP. FAST works on the classic lun and not the virutally provisioned (thin luns); please correct me if I have this wrong.
Booyah2
2 Intern
•
185 Posts
711
1
Posted May 21st, 2010 08:00
You may find EMC's new product called FAST a perfect fit for your environment, it automatically tiers your storage as you define.
Refer to the following document on Powerlink: "Implementing Fully Automated Storage Tiering (FAST) for Symmetrix V-Max."
There is a Thin Provisioning Best Practice document on PowerLink that will answer your questions for this product.