In regard to: Re: [Networker] client backup time, Alan Maxwell said (at...:

While I like this query, this fits the problem, i.e.
if a client is backing up savesets in parallel this only shows the
amount of time per save set.
There is no way to tell the elapsed time of ALL savesets, since numerous
of the savesets listed
would have been running at the same time.

You're right that there's no built in way to tell how long it took a
client to backup all its volumes, but it would be possible to get that
info since the data you need is being stored.

It also wouldn't be terribly difficult to do, if you don't expect the
reporting program to be able to detect when a client has been run multiple
times since the savetime you specify.  It's more difficult (but still
possible) if you want the program to detect when a client has run multiple
times and output separate reports for each time the client ran.  If you
have clients that use continuation savesets, that also adds additional
complexity.

I've done stuff similar to this in the past, but I've never tried to
answer this particular question.  I'm mostly concerned with how long it
takes individual savesets to back up.

Tim

Run mminfo -r "client,sscreate(30),sscomp(30),level,totalsize" -c
clientname -q "savetime>=mm/dd/yyyy"


-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Alan Maxwell
Sent: Thursday, August 17, 2006 5:25 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] client backup time

Has anyone ever developed a way to find out historically how much time
a backup client takes to backup?

In the logs only the group times seem to be tracked, client save sets
are tracked but not the client itself.

Also confounding the issue is , in the group log, individual saveset
elapsed time is listed, but if running

parallel , mutliple savesets run at the same time, so this doesn't help
much.




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
wit 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

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
wit 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

--
Tim Mooney                                           Tim.Mooney AT ndsu DOT edu
Information Technology Services                      (701) 231-1076 (Voice)
Room 242-J6, IACC Building                           (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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
wit 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