Wait a sec... Go read http://support.microsoft.com/default.aspx?scid=kb;en-us;266096&Product=e xch2k
This article, if you follow the logic, says that only 1GB of RAM is support with E2k on W2k standard. To use more than 1GB requires the /3GB switch in order to be supported, and that requires W2k advance. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gerod Serafin Sent: Thursday, September 16, 2004 3:03 PM To: Exchange Discussions Subject: RE: VM Fragmentation Issue Uh, wait a second there... This system can use that RAM. There is absolutely no reason to take that RAM out. If it had more than 4 GB then it would be ridiculous. But 1 GB is not the limit. Take a look at the following article: http://support.microsoft.com/default.aspx?scid=KB;EN-US;325044 "In some cases, event ID 9582 events do not indicate a problem with the virtual memory on the server, and the events can be ignored. However, in other situations, the lack of virtual memory may result in message-processing errors (indicated by event ID 12800 events) and decreased performance. If left unchecked, virtual memory fragmentation can result in severe performance degradation and unexpected behaviors. There is virtually no correlation between the amount of physical random access memory (RAM) that is installed in the computer and the amount of virtual memory. Because of this, you cannot resolve low virtual memory issues by adding more physical RAM. Additionally, virtual memory errors and virtual memory fragmentation issues are not limited to Active/Active server clusters. These issues also occur on Active/Passive server clusters and on stand-alone servers that are running Exchange 2003 or Exchange 2000." So, follow the direction in this article and keep an eye on the events and look for the 12800 events. The main problem with VM fragmentation was with Clusters that wouldn't failover. In your case you aren't doing that. Are your clients seeing any performance issues? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fyodorov, Andrey FTL Sent: Thursday, September 16, 2004 1:19 PM To: Exchange Discussions Subject: RE: VM Fragmentation Issue Why wouldn't you want to remove the 1GB or RAM that the system can't use? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 16, 2004 1:10 PM To: Exchange Discussions Subject: RE: VM Fragmentation Issue I'm on Windows Server SP4 and Exchange 2000 SP3 and no /3GB switch in the boot.ini. Any ideas? Removing 1GB of RAM doesn't seem like a viable option to me. John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerod Serafin Sent: Thursday, September 16, 2004 9:30 AM To: Exchange Discussions Subject: RE: VM Fragmentation Issue There have been a ton of fixes in the most recent service pack for Exchange 2000 so please make sure that you are running that. There are even more fixes in Exchange 2003 so if you have the opportunity to go there someday, it will help. Also, make sure that you don't have the /3GB switch enabled on your boot.ini unless you have Windows 2000 Advanced Server. http://support.microsoft.com/default.aspx?scid=KB;EN-US;266096 Says: "Note Do not add the /3GB switch if you are running Windows 2000 Server, Microsoft Small Business Server 2000, or Microsoft BackOffice Server 2000. If the /3GB switch has been added to the Boot.ini file on these operating systems, it must be removed because it can contribute to virtual memory fragmentation on these systems. This switch is designed for use only with Windows 2000 Advanced Server and later." -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, September 16, 2004 12:19 PM To: Exchange Discussions Subject: VM Fragmentation Issue Exchange 2000 Standard Windows 2000 Server 2GB RAM priv db: 10.9GB c: 3.15GB/15GB free d: 17GB/40GB free (Exchange db here) e: 27GB/48GB free I took over this system about 1.5 months ago. Back then I noticed this event in the log and noticed the virtual memory was low and only on c: drive. So I increased c: and added some one d: and e: bringing the total VM to 5.5GB. After restarting the system the memory usage history went from 50% down to 20%. Typically the store.exe runs at 1GB memory usage as well. So the performance was up and the event didn't come back. That was up until a few days ago. From what I understand, the fragmented vm can prevent Exchange from properly dismounting the information store so I want this corrected but my fix only seemed to delay the fragmentation. Any tips or help would be appreciated. Event 9582: The virtual memory necessary to run your Exchange server is fragmented in such a way that performance may be affected. It is highly recommended that you restart all Exchange services to correct this issue. John PS. I checked under the server and didn't find any gorbs or gobs :P _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang =english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe send a blank email to %%email.unsub%% Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
