Unsolved
This post is more than 5 years old
1 Rookie
•
36 Posts
0
1197
July 27th, 2012 00:00
VNX Inyo , Flash 1st and MS SQL
Hi
Usually we recommend in our best practice to use RAID 1/0 for tempdb and logs.
By using FAST VP with Inyo it becomes possible to have mixed RAID Group
in a storage pool and Flash 1st will use SSD by default and then auto tiering.
There is also a possibility to force a LUN on the highest priority then it
Will be associated with SSD part in RAID10.
Could we recommend to create one storage with mixed RAID Group with MS SQL,
tempdb and Logs will associate to the highest SSD RAID 10 tier
regards
No Events found!
Michael_Morris
18 Posts
2
July 27th, 2012 04:00
Hi watelet
Inyo does indeed offers us the chance to further simple storage design through the ability to use different RAID types within a single storage pool. For example one pool with;
For MS SQL Server, Tempdb and log files are generally not candidates for SSD technology due to the sequential nature of their I/O patterns, as such there is no need set set the FAST VP policies for these LUNs to lock them to the highest tier. Better that we use the excellent I/O capability of SSDs to service the I/O requirements of the SQL Server data files.
I'd recommend leaving the FAST VP policies to auto-tier, especially until you fully understand the I/O workloads and LUN relocation patterns that are occurring on the array.
If you want to fully guarantee performance yes separating logs, tempdb is a good answer but if you want a simple single storage pool for you environment then the new features in Inyo offers this.
Michael
Principal Solutions Engineer
EMC Solutions Group (ESG) | Strategic Solutions Mid-Range Application Engineering
dwatelet
1 Rookie
•
36 Posts
0
July 27th, 2012 07:00
Thanks Michael,
Michael_Morris
18 Posts
1
July 27th, 2012 08:00
No problem watelet, just remember that if you want the simpler solution you need to accept the need to possibly provision more drives to compensate for the mixture in I/O activity that may occur in the pool. If you have a particular application that requires guaranteed performance the simplest answer can be to seperate to its own pool, or in the case of MS SQL move the logs or tempdb that may be causing issues to dedicated spindles, say a RAID 1/0 2+2.
At the end of the day we need to balance simplicity with common sense to produce the lowest spindle count to service application performance.