David,
>For example, I have a server that has 6 save sets: C, D, System State,
System DB, System Files, ASR. During the first 10 minute slice, nsr
reporter is showing me 8 sessions instead of 6. The next 10 minute slice
shows 8, and the third and fourth slices drop down to 4 each. Does your
logic also include control sessions? I wouldn't think that the index would
be backed up during the first 10 minutes, but maybe I'm wrong.
Yes, same logic does apply : do a mminfo -q "client=xxx,savetime>1day ago"
-r "sscreate(22),sscomp(22),name" -ot
Look at start/completion time. Same logic does apply : it reports 8 sessions
instead of 6 due to
overlap of the ending ones and the new started ones.
How more save sessions are small (finished in less than 10 min), how more
you will see behaviour
with higher session amount than existing one.
Cheers
Th
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of dfields
Sent: vendredi 17 juillet 2009 22:38
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] NSR Reporter
Theirry,
Wow. Thanks for the quick reply. I figured the source for this was huge.
I've written some perl scripts for my own reports, but nothing close to 200k
lines 8).
I did some more digging after I posted this by adding the individual entries
in the "by client" view for a particular time slot, and then compared that
to the same time slot on the over all active sessions view, and the totals
matched. What was throwing me was the counts, (a server with say, 5 save
sets was generating a count of 8 on the by client view). However, your
logic below kinda explains that, but I would expect somewhat different
behavior than what I'm seeing. Assuming all save sets start in the first 10
minute slice, I would expect the number shown to match the number of save
sets. However, if some stuff carries over to next 10 minute slice, I see
how your logic works (and I agree that it has to work that way).
For example, I have a server that has 6 save sets: C, D, System State,
System DB, System Files, ASR. During the first 10 minute slice, nsr
reporter is showing me 8 sessions instead of 6. The next 10 minute slice
shows 8, and the third and fourth slices drop down to 4 each. Does your
logic also include control sessions? I wouldn't think that the index would
be backed up during the first 10 minutes, but maybe I'm wrong.
Anyway, I think the tool is great. I'm looking forward to the next version.
I've thought about writing scripts to pull much of the same info that you do
and display the results with MRTG, but I never seem to have the time, and
your tool already pulls so much more information than I would have the time
to write scripts for.
Thanks again,
David
+----------------------------------------------------------------------
|This was sent by david.fields AT acs-inc DOT com 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
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
|
