I have seen this type of behavior occur on Windows and Linux clients that lose 
access to their storage. On Linux, I typically find at least one save process 
that cannot be killed off. In NetWorker 7.6.3, the hardlimit attribute of the 
group resource can be set to kill the group after a certain number of minutes 
pass by. I have found that feature to work very nicely.

On 06 15, 2012, at 10:26 AM, Matthew Powell wrote:

> I have seen this on occasion here but it has mainly been on my windows
> server groups. I have not had this happen on the other flavors of OS. We are
> running Legato Networker 7.5.3 writing to a SAM/QFS file system on the back
> end. So it has nothing to do with the tape process b/c our networker servers
> never see any tape. The SAM/QFS back end takes care of the two copies for us
> so no overhead of cloning. I have always wondered if anyone else had seen
> this same type of thing. There is nothing in the logs of the clients or the
> group that say any error. I generally just stop and the restart the job and
> it fires right off.
> 
> 
> On 6/15/12 9:58 AM, "dave2 AT CAMBRIDGECOMPUTER DOT COM"
> <dave2 AT CAMBRIDGECOMPUTER DOT COM> wrote:
> 
>> Hi,
>> 
>> 
>> 
>> I've seen an issue at a few sites where there are backups in a running
>> group "stuck" in the "Waiting to Run" queue, with a state of state active,
>> but never seem to transition to a running state. In addition, the group
>> doesn't time out as it should‹in one case the backup admin notices after 3
>> days that she hasn't gotten success emails.
>> 
>> 
>> 
>> Anyone run into this and have any thoughts?
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> Dave
>> 
>> 
>> 
>> 
>> 
>> Dave Gold
>> 
>> Sr. Technical Consultant
>> 
>> Cambridge Computer Services
>> 
>> dgold AT cambridgecomputer DOT com
>> 
>> 781-250-3260
>> 
>> *Celebrating our 20th Anniversary*
> 
> -- 
> Matt Powell
> mtpowel AT clemson DOT edu
> Storage Administrator
> Clemson University
> 340 Computer Court
> Anderson, SC, 29625
> office: 864-656-0589
> cell: 864-247-2823