Re: Pagefile on server with low space

Tech-Archive recommends: Fix windows errors by optimizing your registry



I appreciate the quick response!!

We cleaned up the C: drive as much as we could and the E: drive has
530GB of available space and it's currently used for apps and can't be
re-sized and I also don't have room to add another drive.

But your suggestion sounds good. So you are saying that I should make
the following modifications and I should be ok?

C: 1024 - 1024
E: 4096 - 4096

Sounds correct? Also, do you see any problems because this is a RAID 5
configuration?

REP



Anna Clark (remove this) wrote:
Hi REP:

The page file on C is largely useless. Only MS can read those dumps, and
how often are you going to get one? Elsewhere in "best practices" you will
see that MS recommends the page file and the OS on different spindles, much
less different partitions.

Having said that, if you create 2, windows will use the one that is least
busy, so maybe a 1 GB on C and a 4 GB on D?

Have you moved everything you can off drive C?

Can you put in another drive just for the page file?

You do not say how much room is on E, but can you resize the partitions?

--
Regards:

Anna Clark
Please do post the conclusion or solution
to your issue so that others may benefit.


"REP" <rphilibert@xxxxxxxxx> wrote in message
news:1169510764.294391.321550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ok, I've been researching the recommended pagefile settings and I'm
not able to find my specific situation.

My client was having low space on the C: drive of their server and they
adjusted the pagefile themselves from C: 4096 - 4096 to C: 1024 -
2046.

After doing so they get error messages when running performance monitor
where some objects don't show up and it mentions about extending the
pagefile size.

Here is the server configuration:
OS - 2003 Server
Proliant 740 server
RAM - 3GB
4 Drives configured as RAID 5
C: Drive 9GB total space / 4GB available space
E: Drive 530GB


I do want a pagefile on C: for a memory dump, but I don't want to
take up too much space on the C: drive. I'm also open to putting a
pagefile on the E: drive. Also, this is a RAID 5 configuration.

Any help would be appreciated

REP


.



Relevant Pages

  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Keep in mind that I have seen OEM drivers up there so given that you've blown that image away, I can't say for certain that the 'critical' was 100% pushed by Microsoft. ... External USB is no replacement for local drives. ... LOL I show my naivety here when I say that I showed great diligence in my blind application of any MS suggested resolution to "Critical Errors" on my Small Business Server Monitor Report. ... When I got the first BSOD, I booted from the orginal CD and chose to only restore the System files. ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... information to login to my server remotely to look around--hoping he could ... External USB is no replacement for local drives. ... stored on) and chose to only restore the System files. ... The "Cases" drive was actually a shared folder on an external ...
    (microsoft.public.windows.server.sbs)
  • Re: Disk Management Strategies...? (here we go again!)
    ... configured their test server in a similar fashion: three sets of RAID ... the RAID 1 array of two physical drives that I had planned). ... The other option for my configuration, of course, is two drives in RAID 1 ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... During the restore, the server rebooted without confirmation. ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... Before installing this server, my users were accustomed to storing all of ... The "Cases" drive was actually a shared folder on an external ... I mirrored the two drives ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)