We had been experiencing ssid errors abound on Networker 7.2.2 on large volumes 
(SAN and local storage) on Windows 2003/2000 full backups for some time.

At this point we have been told that we are one of a very few clients who are 
experiencing a WINDOWS problem that is connected with the amount of paged pool 
allocated when backing up large volumes.  After a few months and 3 techs, I 
finally spoke with someone who worked with me from EMC to narrow this down to 
this particular issue and after setting the page pool to maximum and the 
trimming of paged pool at 40%, along with lowering both the server parallelism 
and savegrp parallelism, it looks like we might be on the verge of solving the 
problem.

Having said all of that, after reading far more about paged pool and memory 
caching than I ever wanted to know,  it appears that Windows 2003 paged pool 
max is roughly 900 megs, but Windows 2003 x64 paged pool max is 1 T.   

1.  Is there anyone else who has experienced this paged pool issue with 
Networker Server on Windows 2003 server?

2. Is there anyone who is running Networker Server 7.2.x or 7.3.2 jumbo (which 
seems to be the consensus of most stable 7.3.x version) on Windows 2003 x64 and 
what have your experiences been?  We are considering upgrading to this to solve 
all this paged pool nonsense.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER