- More files are open than the memory cache manager can handle. As a result, the cache manager has exhausted the available paged pool memory.
- The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is exhausted).
- On the Windows 2003 server in question, 2 Registry Keys (PoolUsageMaximum, PagedPoolSize) may be created to fine-tune how the operating system manages Paged Pool Memory.
- First create PoolUsageMaximum regkey and set to DWORD value = 60. If that does not work, try value = 40. If that works, increase the value by 25% until it stops working. Go back to last working value.
- If backups are still failing, use PagedPoolSize with DWORD (hex) value = FFFFFFFF. Do not set this to any other value if you are using the /3GB switch. If you are running /3GB and /PAE together, do not set this setting without extensive testing.
References: http://seer.entsupport.symantec.com/docs/295563.htm
http://support.microsoft.com/kb/304101/en-us
No comments:
Post a Comment