Hello Team In exchange server 2007 SCC envirnment am getting the below alert from the Monitroring Tool. The number of 16MB or greater VM blocks available to the information store process is (0.00) which is below the threshold of (1.00). [Policy: WW-EXC2K7-LG-MB-ISVM16MBBlocks] The largest VM block size available to the information store process is (0.00) which is below the threshold of (16000000.00). [Policy: WW-EXC2K7-LG-MB-ISVMLargestBlock] I have checked the presesnce of the Event ID 9583 and 12800 which is not availble in the appilcation logs This is a VM issue i knowm but how to overcome the issue since i don't have the evidence of VM issue SCC with Act - Act - Passibe and this alert is coming on Passive. also, whenever the failover happnens , this alert is generating in passive i belive. since it is 2007 and there is no job for /3gb switch. correct if am wrong. Exchnage 2007 running on windows server 2008 with SP2. Any suggestion please ramakrishnan

Check the value of perfmon counter MSExchangeIS\VM Total Large Free Block Bytes Displays the sum in bytes of all the free virtual memory blocks that are greater than or equal to 16 MB. This counter monitors store memory fragmentation and forms a line that slopes down when memory is consumed. On a healthy server, the line should stay above 50 MB. Do you have 1.5 times RAM set as page file? Measure other counters for memory utilization and see if there are any other processes that are utilizng the memory too much. At no point should this value go below 50 MB.

Hi i have added the counter and the value is showing as 0.000. was anything going wrong on the boxramakrishnan

Continue monitoring this counter. It may be a backup or some other application if installed that could have been using the memory a lot. Check also which process is using memory more to understad the root cause if this continues to happen.

Continue monitoring this counter. It may be a backup or some other application if installed that could have been using the memory a lot. Check also which process is using memory more to understad the root cause if this continues to happen.