smbcs
asked on
Low disk space and page file size
I have a windows 2003 server running as a domain controller with a 10GB drive on the system drive that is running critically low on disk space - less than 100MB. The server has 1 GB RAM and a page file set on the system drive
Initial: 1536MB
Max: 3072MB
There is also a manually set page file for the D Drive as 1536MB initial and MAX.
My question is, to get a little more life out of the server, is it ok to reduce the system drive page file to the minimum allowed (as suggested by a colleage), and increase the D Drive page file.
There is nothing else I can move or delete on the system drive. Exchange database has been moved. Windows uninstall files have been moved. Temp files removed etc.
Please advise on the best solution other than rebuilding the server, as I was of the optinion that the initial page file size should be 1.5 times the RAM size and stored on the system drive!
Thanks
Initial: 1536MB
Max: 3072MB
There is also a manually set page file for the D Drive as 1536MB initial and MAX.
My question is, to get a little more life out of the server, is it ok to reduce the system drive page file to the minimum allowed (as suggested by a colleage), and increase the D Drive page file.
There is nothing else I can move or delete on the system drive. Exchange database has been moved. Windows uninstall files have been moved. Temp files removed etc.
Please advise on the best solution other than rebuilding the server, as I was of the optinion that the initial page file size should be 1.5 times the RAM size and stored on the system drive!
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i think it's not ideal to install DC on raid 5 for boot disk. you should use raid 1 (mirror).
but it shouldn't be a problem with this setup...
but it shouldn't be a problem with this setup...
ASKER
Unfortunately it is a system that I have taken over. Not the most ideal. Infact a poor setup. But there is not much else I can do at this stage other than manage the problem. I will be looking in the near future to upgrade to a new server, but require the options above to get the server by until a new server can be financed and implemented.
is there another disk on the server with free space? is there anything on drive C that you could mount on a folder on the other disk or logical volume?
so, if you have something on C that needs to retain the path C, you could mount that folder on the logical volume with free space
http://support.microsoft.com/kb/307889
so, if you have something on C that needs to retain the path C, you could mount that folder on the logical volume with free space
http://support.microsoft.com/kb/307889
Is this a terminal server?
If not, what is taking up the space?
I would strongly recommend you review my document on boot drive size - www.lwcomputing.com/tips/static/bootdrivesize.asp - I have about 20 things you can/should move off the C: drive - some I'm willing to bet you haven't thought of (like ServicePackFiles and DLLCache). I also discuss the pagefile. While it is best to have it on a different set of spindles, if there are no different set of spindles to put it on, then put it on the same set, but a different logical drive.
In my opinion, for a STANDARD (Non-SBS server) 10 GB for Windows Server 2003 is fine (unless it's a terminal server). If this were an SBS server than it's a *LITTLE* lean, but still not TERRIBLE. And if it's a Terminal Server, then, because of it's nature, I would use the maximum size available for C:.
If not, what is taking up the space?
I would strongly recommend you review my document on boot drive size - www.lwcomputing.com/tips/static/bootdrivesize.asp - I have about 20 things you can/should move off the C: drive - some I'm willing to bet you haven't thought of (like ServicePackFiles and DLLCache). I also discuss the pagefile. While it is best to have it on a different set of spindles, if there are no different set of spindles to put it on, then put it on the same set, but a different logical drive.
In my opinion, for a STANDARD (Non-SBS server) 10 GB for Windows Server 2003 is fine (unless it's a terminal server). If this were an SBS server than it's a *LITTLE* lean, but still not TERRIBLE. And if it's a Terminal Server, then, because of it's nature, I would use the maximum size available for C:.
yeah, back to basics, have you run disk cleanup? there are probably some temp files created by RDP connections and you could compress some old files also
this has been very useful
what has been very useful?
?
i was asking Tbaba what had been very useful
yeh... i know... i wondering too... :)
ASKER
Hi Peoples,
Thanks for the detailed information. Most of the information had already been done apart from a few things (including moving the page file itself). I actually had a look at one of my test servers running SBS, and found that I had already set it up a long time ago with the page file on a different drive to the sys drive. And yes, it works fine! In fact moving the page file to another drive also solves another issue for me, with increasing the RAM from 1GB to 2GB, as the server currently is struggling with only 1GB.
So Moday I shall do the following. Change the sys drive to 16MB min and max, and put the new page file on the second hdd.
I had several good answers to this, so I increased the points to 500 and shall distribute accordingly.
Thanks again.
Thanks for the detailed information. Most of the information had already been done apart from a few things (including moving the page file itself). I actually had a look at one of my test servers running SBS, and found that I had already set it up a long time ago with the page file on a different drive to the sys drive. And yes, it works fine! In fact moving the page file to another drive also solves another issue for me, with increasing the RAM from 1GB to 2GB, as the server currently is struggling with only 1GB.
So Moday I shall do the following. Change the sys drive to 16MB min and max, and put the new page file on the second hdd.
I had several good answers to this, so I increased the points to 500 and shall distribute accordingly.
Thanks again.
So you're saying that my web page that I linked to provided no useful information that wasn't already posted?
ASKER
Yes, I am so sorry... I just forgot to post points to you. I am not sure how I can withdraw the points and post some to you also.
Ok, don't worry about it... I've got MANY points and if it were just a simple error, I can live without those from this question.
-Lee
-Lee
This discussion has been useful. including all the links, i've beena able to increase free disk space on system partition on one of my SBS servers to 66%!! Clients happy, and I'm happy, thanks guys
ASKER
To clarify. The best solution (provided all other avenues have been exhausted), is to set the c:drive to Min and Max of 16MB, and increase the size on D: drive to the recommended settings of Min - 1536MB, and a Max of 3072MB or larger.
Are there any performance issues associated with this setup? And it is fine to run this on a raid5 setup and the same physical drive partitions.
Furthermore, this should allow me to up the RAM on the server to 2GB+, as 1 GB is a little unresponsive and I thought I was limited to the page file on the system drive vs disk space available.
Thanks again. Much appreciated