On PhysicalDisk, for the Exchange log/data volumes, you want to look at "Avg. Disk Queue Length", "Current Disk Queue Length", and "Disk Transfers per Second".
The third will track the actual IOPS for that volume, the first two give you the average challenge you have meeting IO requests and give you a view of instantaneous bursts of high IO that you may need to address. Note that this includes all activity on those volumes, not just Exchange. This is actually more reasonable, because if you are using those disks for more than Exchange, you have even more of an IO challenge. That being said, IO requirements on Exchange 2010 (given proper memory sizing) are 90% less than they were in Exchange 2003. In Exchange 2013 (given proper memory sizing), IO requirements are _99%_ less than they were in Exchange 2003. If you want to look at only Exchange IO, then you examine the "MSExchange Databases ==> Instances" object and track individually for "I/O Database Reads/sec", "I/O Database Writes/sec", "I/O Log Reads/sec", "I/O Log Writes/sec". From: phil levine [mailto:plevin...@yahoo.com] Sent: Thursday, October 4, 2012 11:22 AM To: MS-Exchange Admin Issues Subject: Exchange IOPS In general what can I do to find out how many IOPS I am using in Exchange 2010? What should I set up in Perfmon to do this or is there anything else I can use to determine this? Thanks Phil --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
