Alternative Method for Gathering Data for Version Store Issues on Exchange Server 2007
By now, you have probably read the two previous blogs written by Nagesh Mahadev and Sushil Sharma on this subject. If you haven't read them lately (or bookmarked them), I urge you to do so now.
This blog is going to discuss alternative methods for collecting data for Exchange Server 2007 and how to setup a data collector set to collect performance data for Version Buckets Allocated and two scheduled tasks to dump the store running on Windows Server 2008.
As part of the data collection, it is important that you download the Exchange 2007/2010 Performance Data Collection Script as discussed in http://archive.msdn.microsoft.com/ExPerfwiz and run it as per instructions to start capturing Performance data.
Here is our Event ID 623 that we will be using in our example:
Event ID: 623
Task Category: Transaction Manager
MSExchangeIS (5828) SG4: The version store for this instance (1) has reached its maximum size of 155Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Our calculation is the same as it has been in the past: x/1024 *32 = y, where x is the number of version buckets allocated and y is the total Version Store memory. Now, we know that the maximum Version Store memory is 155Mb from the event above and we can therefore work out the maximum number of version buckets allocated. x= (155*1024)/32 so we can see that this is 4960.