Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RAM Size enough?

Status
Not open for further replies.

hup

IS-IT--Management
Jan 22, 2002
11
SG
Hi,
I'm currently running the exchange 5.5 on a HPNetserver LC2 with the RAM size of 192MB. CPU is PII 266. My platform is NT4 with SP6.
The RAM usage keep increasing (view from NT task manager performance) without release the unused portion. I have to restart the system every 3-4days.

Is the RAM size big enough for 40 active users? Otherwise why the RAM usage keep increasing? Is it due to my configuration problem?

Regards,
Hup
 
Hi, If you run Performance Optimiser you can Limit the memory that MS Exchange can use. This will stop it running away with RAM assuming it is not selected at present.
 
Hi Mike,

Thanks for the help. I went to my event log it show that my NT got crushdump error.
 
Install SP4 and post store roll-up. If you have the same problem call and get it debugged. Don't limit Exchange... Dan
Microsoft Exchange Support @ Microsoft
 
HI.

How much RAM does Exchange use when you restart it after 4 days?

* One of the main factors for RAM usage of Exchange is the size of the Public & Private stores.
So, decreasing those can have many benefits like reducing load and the server, significant reduce in disaster recovery times, and many more.
Bye simply deleting "Deleted Items" on outlook exit and archiving old "Sent Items" Once/Twice a month, you can greatly decrease private store size.

* Adding 256MB 512MB or 1GB RAM to your server will do just good to it.

* I also agree with Dan - apply SP4 on the server, etc.

* As a temporary work-around, until you solve the problem, you can schedule a CMD file to restart Exchange services every X days, so it can be done automaticaly at 6:00 AM (and if Exchange fails to restart, you fix it first thing in the morning by restarting the whole server.
Here is a sample CMD file, you MUST debug and edit it to your needs, like adding NET START lines for other services that depend on Exchange (connectors, AV products, content filters):

REM - NET STOP NavExchange /YES
REM - NET STOP MSExchangeINS /YES
REM - NET STOP MSExchangeDXA /YES
NET STOP MSExchangeIMC /YES
NET STOP MSExchangeES /YES
NET STOP MSExchangeMTA /YES
NET STOP MSExchangeIS /YES
NET STOP MSExchangeDS /YES
NET STOP MSExchangeSA /YES

NET START MSExchangeSA
NET START MSExchangeDS
NET START MSExchangeIS
NET START MSExchangeMTA
NET START MSExchangeES
NET START MSExchangeIMC
REM - NET START MSExchangeDXA
REM - NET START MSExchangeINS
REM - NET START NavExchange

Bye
Yizhar Hurwitz
 
Ok... So I ran Exchange 5.5 on Dual P200's. They were rock solid and would sit at 100% all day serving 1500 users. If the box just started doing this for no reason and the stores aren't growing it is probably a bug and bugs are a free fix. Just trying to save you some time and frustration. Dan
Microsoft Exchange Support @ Microsoft
 
Hi Dan and Yizhar Hurwitz,
Everytime I after I restart, the RAM size of approx. 100MB is used up.
I'll try on your method. Thank you very much for your time and advice.

Hup :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top