Thanks alot!!! I'll try it...

Rodney Riggins
Audit Network Administration
(916) 845-7492


-----Original Message-----
From: Matthew Bourne [mailto:mbourne2001 AT LYCOS.CO DOT UK]
Sent: Wednesday, March 19, 2003 9:05 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] Index's not backing up


Hi,

This happened recently for us - the root of the problem turned out to be
the "client priority" attribute for the NetWorker server itself.  By giving
the NetWorker server client resource the highest priority, 1, I resolved
the issue.

I suspect that what was happening was this:
The "max parallelism" value for the server was being reached, taken up
entirely by client saveset streams
Every time a client had backed up all its savesets, the server attempted to
back up the index saveset for that client
Because there was effectively "no room at the inn" the index saveset
eventually timed out

Anyhow, setting the client priority =1 for the server itself fixed the
problem.

Regards,
Matthew

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=