onsdag 29. august 2012

How to size the Windows paging file

Much can be said, but the simple rule is: check the peak commit charge under actual load and determine the proper pagefile that way. If you would like som expert advice in more detail read this Microsoft KB and also Mark Russinovich's Blog. Here is a quote from his blog:
To optimally size your paging file you should start all the applications you run at the same time, load typical data sets, and then note the commit charge peak (or look at this value after a period of time where you know maximum load was attained). Set the paging file minimum to be that value minus the amount of RAM in your system (if the value is negative, pick a minimum size to permit the kind of crash dump you are configured for). If you want to have some breathing room for potentially large commit demands, set the maximum to double that number.
You can use Process Explorer to find Peak Commit Charge.

DPM: SAN without hardware VSS provider

Enable per node serialization. This is done by adjusting this registry key:
HKLM\Software\Microsoft\Microsoft Data Protection Manager\2.0\Configuration\MaxAllowedParallelBackups

Simply change the DWORD value Microsoft Hyper-V from the default of 3 to 1. To finish off restart DPM server and modify Protection Groups for virtual servers.

For more detailed description, read this technet article and this.