That is a good way to segregate the type of data. to bad you dont have more disks so you can make yourself a separate Raid 1/0 group and make LUN's for the Exchange and SQL logs in it since those tend to be your high I/O lun's.
If you don't have the disks then 3 lun's will be fine
me personally, no i would not. i would have multiple lun's each dedicated to a different application. I dont have any expereince with Hyper-V but in a normal FC SAN config, it is bet to have multiple luns. Exchange can have a big performance hit depending on your user base. if you have the mailbox storage groups as well as the log files on the same lun with the addition to SQL data/logs, you can possibly run into performance problems as your environment grows.
first i would make sure you are not exceeding the limited of supported VMs per LUN. I don't know what Microsoft recommends but VMware its 10-15 VMs per LUN. The more VMs you have per LUN the more locking is happening ..performance gets worse because of that. You also have to look at IOPS requirements, do the drives that comprise that raid group satisfy I/O requirements for those VM/applications ? I am not very familiar with AX platform, is there Navisphere Analyzer for AX that you could look at disk/array stats and see whats' going on ?
You migth also want to check out some of the Best Practice guides stored on this forum in the Documents tab - some of these will take about best Practice for setting up LUNs for different applications.
kenn2347
3 Apprentice
•
542 Posts
0
June 1st, 2010 14:00
That is a good way to segregate the type of data. to bad you dont have more disks so you can make yourself a separate Raid 1/0 group and make LUN's for the Exchange and SQL logs in it since those tend to be your high I/O lun's.
If you don't have the disks then 3 lun's will be fine
dynamox
9 Legend
•
20.4K Posts
0
June 1st, 2010 07:00
I would start out with this relatively new tool from Microsoft
http://technet.microsoft.com/en-us/library/ee941122%28WS.10%29.aspx
http://www.microsoft.com/downloads/details.aspx?FamilyId=89d80c15-0082-4fef-a4fc-fefa463bed08&displaylang=en
kenn2347
3 Apprentice
•
542 Posts
0
June 1st, 2010 10:00
me personally, no i would not. i would have multiple lun's each dedicated to a different application. I dont have any expereince with Hyper-V but in a normal FC SAN config, it is bet to have multiple luns. Exchange can have a big performance hit depending on your user base. if you have the mailbox storage groups as well as the log files on the same lun with the addition to SQL data/logs, you can possibly run into performance problems as your environment grows.
gary2010
3 Posts
0
June 1st, 2010 10:00
Thanks for your post. Its more the configuration of the AX4 i am concerned about.
Should all the VM's be placed on one LUN ?
If you had to run Exchange 2007, SQL 2005 and multipe data server would you do it with a raid5 one LUN setup.
dynamox
9 Legend
•
20.4K Posts
0
June 1st, 2010 10:00
first i would make sure you are not exceeding the limited of supported VMs per LUN. I don't know what Microsoft recommends but VMware its 10-15 VMs per LUN. The more VMs you have per LUN the more locking is happening ..performance gets worse because of that. You also have to look at IOPS requirements, do the drives that comprise that raid group satisfy I/O requirements for those VM/applications ? I am not very familiar with AX platform, is there Navisphere Analyzer for AX that you could look at disk/array stats and see whats' going on ?
gary2010
3 Posts
0
June 1st, 2010 14:00
Thanks
I have been thinking of changing the configuration to 3 LUNS one for operating systems one for databases and one for log files what do you think?
kelleg
4 Operator
•
4.5K Posts
0
June 1st, 2010 14:00
You migth also want to check out some of the Best Practice guides stored on this forum in the Documents tab - some of these will take about best Practice for setting up LUNs for different applications.
glen