I suspect 7.5 has a similar bug as I have in 7.3.3 on Solaris 10. 

If a group is not allowed to complete an abort on the first abort command sent 
i.e. you do  it again to get the group to complete the server keeps some sort 
of memory of that client having sessions running and wont run anymore sessions 
than the what was killed up to the client parallelism at the time of being 
killed i.e. four running sessions on a parallelism of 4 and all future backups 
of the client queue, three running sessions on a parallelism of 4 and 1 session 
will run in the future

Only way to clear it I have found is to restart networker on the server.




t0nypx wrote:
> Has anybody seen this before.
> 
> I am running networker7.5 on Solaris10 and am backing up various hosts 
> (windows/linux/solaris).  
> 
> Recently I have noticed that a backup group starts and yet at random, a 
> client within that group will just queue, and queue, and queue (it never 
> runs).  However - If the client runs the backup from itself it runs fine.
> 
> The only way around this I have found is to restart 'networker' on both 
> storage nodes and the backup server itself.  Once I have done this it works 
> fine, but then after a few days another server will have the same issue?
> 
> Any suggestions?
> 
> t0npyx


+----------------------------------------------------------------------
|This was sent by kit.cunningham AT krisanya.com DOT au via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

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