Discussion on:
View:
Show:
Another good one is that with the /3GB switch enabled, many software packages will not install, some even as small as WinZip. Running setup.exe results in "insufficient memory" errors. It's a nagging pain in the butt.
Using the /3G boot.ini switch also causes installation issues for numerous other software installs. Notably Backup Exec, NetBackup, McAfee, etc.
I also had to add "/userva 3030" as well. When I switched to Exchange 2003 I had to use /3GB just to get it to work on a Server 2003 OS. Exchange 2003 worked fine with Server 2000 when it came out but I had a ton of problems getting it to be stable on Server 2003 after appling Exchange SP1. But to Microsoft's credit, they had a Exchange Tech work with us for a couple days and it has been stable since.
Curious, how much physical memory did you actually have in the server? What server side antivirus solution did you have running at the time?
I've had to run a couple of recoveries over the years 2000 and 2003, but they always had 4 GB of RAM plus using Trend with the exchange stores excluded from AV scanning and never experienced an issue with using other temp workspace.
I've had to run a couple of recoveries over the years 2000 and 2003, but they always had 4 GB of RAM plus using Trend with the exchange stores excluded from AV scanning and never experienced an issue with using other temp workspace.
I could have used your post 4 weeks ago when I encountered this exact same problem. I had to
shell out $$ to MS for this offical answer:
The CopyFileEx and CopyFile functions are used by all of the standard file-copy utilities that are included with Windows NT 4.0 and Windows 2000.? Because these functions use buffered I/O, the maximum size of a file that you can copy depends on the amount of paged-pool memory that is available at the start of the copy procedure and whether the Physical Address Extensions (PAE) kernel which allows access to memory above 4 gigabytes [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is required for each megabyte (MB) of file size that is opened for buffered I/O. Because there are two files involved in a copy procedure, 2 KB of paged pool are required for each MB in the source file.
In our case we are transferring 85GB of data which will require 80MB if Paged Pool memory. As we are using the /3GB switch, the total paged pool memory available for the system is 128MB only. This is the reason why we are running out of paged pool memory. To resolve this issue, I recommend you to boot the server without the /3GB switch and perform the copy operation. Once the copy is finished, you can put the /3GB switch again and then boot the server and resume normal operation.
shell out $$ to MS for this offical answer:
The CopyFileEx and CopyFile functions are used by all of the standard file-copy utilities that are included with Windows NT 4.0 and Windows 2000.? Because these functions use buffered I/O, the maximum size of a file that you can copy depends on the amount of paged-pool memory that is available at the start of the copy procedure and whether the Physical Address Extensions (PAE) kernel which allows access to memory above 4 gigabytes [GB] is in use. With the standard kernel, 1 kilobyte (KB) of paged pool is required for each megabyte (MB) of file size that is opened for buffered I/O. Because there are two files involved in a copy procedure, 2 KB of paged pool are required for each MB in the source file.
In our case we are transferring 85GB of data which will require 80MB if Paged Pool memory. As we are using the /3GB switch, the total paged pool memory available for the system is 128MB only. This is the reason why we are running out of paged pool memory. To resolve this issue, I recommend you to boot the server without the /3GB switch and perform the copy operation. Once the copy is finished, you can put the /3GB switch again and then boot the server and resume normal operation.
I am also running 4gig of memory, but am using Sophos AV also with the Exchnage directory excluded.
Without the /userva 3030, for some reason my HP DL380 was running out of drive space due to the swapfile growing and growing to consume the entire free space. Now it stays at 1.6 to 2 gig at peak.
Without the /userva 3030, for some reason my HP DL380 was running out of drive space due to the swapfile growing and growing to consume the entire free space. Now it stays at 1.6 to 2 gig at peak.
If you checj the readme with the exchange service pack you will find that userva=3030 is nolonger the recommended value but is lower at, from memory here, userva=2986.
Also why are you using the Copy or Xcopy commands? To move the DB files. You should use eseutil /y option as this uses a more efficient methord by creating its own large buffer thus avaiding the pagepool problem and speeds up the process by about 1/3rd.
Also why are you using the Copy or Xcopy commands? To move the DB files. You should use eseutil /y option as this uses a more efficient methord by creating its own large buffer thus avaiding the pagepool problem and speeds up the process by about 1/3rd.
Checking the post installation/optimisation steps on the Exchange 2003 SP2 CD still recommends that the USERVA switches still be set at 3030 does anyone have the MS article number to hand the suggests otherwise.
The information was in the SP1 Readme
"Event 9665: Update to recommended memory settings for running Exchange Server 2003 SP1 on Windows Server 2003.
When you are running Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM, it is recommended that you set the SystemPages registry key to zero. This recommendation contrasts with the recommendation for Windows 2000 Server, which is to set SystemPages to a value between 24000 and 31000.
The recommended memory settings for Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM are as follows:
If you host mailboxes or public folders on a server with more than 1 GB of RAM, make sure that the boot.ini file contains the /3GB switch.
When you use the /3GB switch, add the /userva switch to the boot.ini file and set the switch to a value between 2970 and 3030.
When you use the /3GB switch, set the hexadecimal value of the following registry key to 0x00040000:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\HeapDeCommitFreeBlockThreshold
Set the decimal value of the following registry key to zero:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemPages
If you set SystemPages to the Windows 2000 Server recommended value of between 24000 and 31000, an Event 9665 will appear in the event log.
See url below for full text
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx
"Event 9665: Update to recommended memory settings for running Exchange Server 2003 SP1 on Windows Server 2003.
When you are running Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM, it is recommended that you set the SystemPages registry key to zero. This recommendation contrasts with the recommendation for Windows 2000 Server, which is to set SystemPages to a value between 24000 and 31000.
The recommended memory settings for Exchange 2003 SP1 on Windows Server 2003 with more than 1 GB of RAM are as follows:
If you host mailboxes or public folders on a server with more than 1 GB of RAM, make sure that the boot.ini file contains the /3GB switch.
When you use the /3GB switch, add the /userva switch to the boot.ini file and set the switch to a value between 2970 and 3030.
When you use the /3GB switch, set the hexadecimal value of the following registry key to 0x00040000:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\HeapDeCommitFreeBlockThreshold
Set the decimal value of the following registry key to zero:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\SystemPages
If you set SystemPages to the Windows 2000 Server recommended value of between 24000 and 31000, an Event 9665 will appear in the event log.
See url below for full text
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx
This post was a lifesaver! I lost half my weekend and was just about to call MS. I think it is a bug and they should at least put a warning about large file transfers after implementing the switch.
This was indeed a lifesaver. We were stuck after hours doing defrags of our mailstores, and were then stuck when we couldn't overwrite the originals with a filecopy of the defragged version from another drive.
I'd buy you a beer.
I'd buy you a beer.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
