Server 2008 R2 Server PageFile.sys is Huge

We currently have a HP Server running Windows 2008 R2. It  has 2 X5570 CPUs and 120 GB Ram. The server acts as one of our Hyper V Servers . The C Drive  which acts as the OS is 136GB in size and I have noticed that there is only 1GB Free. The reason why this is because I can see that there is a pagefile.sys which is currently 119 GB in size!
I would appreciate if someone could advise what to do in this situation.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What are your paging file settings at? Can you take a screenshot?

From System Control Panel Applet\Advanced System Settings\Performance Settings\Advanced\Virtual Memory\Change...

It is recommended to be 1.5 times the amount of Physical RAM on the system. You might also check this registry key:
GenieMasterAuthor Commented:
Thanks for your prompt response. It looks quite large.
I am not sure if this is because of the Hyper V  Virtual Servers as we have 8 Hyper V Servers and we allocated on average about 12 GB RVirtual Memory Settingsam to each server or is this not the reason?
Yeah that's nuts, if each one is 12 GB Ram the paging file should only be around 18GB. Maybe its taking all of them and counting it as one server. You may want to set it individually.


How much ram total between all of the servers?

Also, you may want to check this MSDN article on Optimizing Performance on Hyper-V:
HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

GenieMasterAuthor Commented:
The D Drive that holds all of the Hyper V Servers, there are 8 Virtual Servers all set to 12Gb. So I assumed that at worse scenario if all Hyper V server were running then it would consume 96GB Ram (8 x 12gb each) then I assume the main server 2008 operating server that hosts the virtual servers would consume a little (this is currently showing the page file of 122869mb. If I manually set the  paging file to 18GB/18432MB then it would not affect the actual virtual servers?
I would try 18 on each or double check your memory settings based on that msdn article. As it is now it seems like each one of the servers thinks it has all of the ram of the server. Either that or, if possible, expand their disk space to allow for that big of a paging file but that seems pretty wasteful. I guess it just depends how much work their doing.
If "auto manage" is grabbing 100GB of HDD for swap, then it's not smart enough to understand your VM environment.  Turn it down manually.

Why leave it on auto?  The 1.5xRAM rule-of-thumb does not apply in a VM environment.  Chances are, your VMs already have a C: drive of their own, with a pagefile.sys for it's own paging.  You don't need to double-provision swap space for them.

You need to subtract your VMs from the equation.  Hyper-V doesn't page for it's guests.  The guests page for themselves, in their own OS.   If you have 128GB physically installed, and 96GB of that is VMs, then your host's OS really only has 64GB of it's own RAM.

Are you running any other roles/applications on your host besides as a hypervisor?  Normally, you shouldn't be.  So that extra RAM is doing nothing.  Why reserve swap space for it?  In a well-provisioned environment, you'll never reach anywhere near 100% of your physical RAM.

In all likelihood, you're swapping a few hundred MB for the host.  But, if you try to reduce your page file size (taking it off "auto"), then the host will request a reboot.

Do you have another host onto which you can move your machines?  Or do you have a maintenance window when the guests can go down?  (I'm not a Hyper-V guy, so I'm used to vMotion to live migrate the guests onto another host.)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.