> Or so you hope.  If something is still where it was 5 or 10 
> minutes ago, it may be hung.

 We have some save-sets that take upwards of 13 to 15 hours to complete
(100+ GB).
 
 The thing that will change in the 5 or 10 minutes would be the rate
it's writing at and/or the amount of data written so far... (if they can
be captured ??).

 If via this methodology you can capture the fact that a session has
'hung' , tell me exactly what corrective actions you would take to
address it before the group completes ??? There's not much you can do
until that happens... And if the session is truly hung, it should
time-out eventually (and maybe get re-tried) before the group completes.
It may not get re-tried without some kind of human intervention... The
only solution I can think of is to have people very knowledgeable about
Networker 'actively monitoring' your backups from start to finish (i.e..
Operations), that can recognize a problem as soon as it occurs and take
immediate corrective action.

> -----Original Message-----
> From: Valdis.Kletnieks AT vt DOT edu [mailto:Valdis.Kletnieks AT vt DOT edu] 
> Sent: Tuesday, May 27, 2008 3:41 PM
> To: EMC NetWorker discussion; Goslin, Paul
> Subject: Re: [Networker] Save "Session" Info in GUI 
> translated to output
> 
> On Tue, 27 May 2008 15:21:30 EDT, "Goslin, Paul" said:
> >  I can't understand of what use this data would be... If it is 
> > possible to capture this data in text format, what could it be used 
> > for ? You would simply be getting a snapshot in time of the current 
> > save sessions running at that moment. Come back five minutes later, 
> > you now have a different picture compared to what it was before.
> 
> Or so you hope.  If something is still where it was 5 or 10 
> minutes ago, it may be hung.
> 
> >                                                    The number of 
> > current sessions is constantly in a state of change, as sessions 
> > complete, new ones start, until the work-list of all 
> save-sets for the 
> > entire group and all its clients is exhausted.... Then the group 
> > completes and triggers a savegroup completion event...
> 
> You need a snapshot of "now" to compare to several hours from 
> now if you're trying to tell if a backup is stalled or not.  
> Simply doing a 'ps' (or whatever Windows has) and seeing 
> "process running" isn't enough - there's a difference between 
> "process had written 23G at 3AM and 97G at 9AM" and "process 
> had written 23G at 3AM and 23G at 9AM"...
> 

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