Thierry -
Thanks for the extra info about my questions. It makes complete sense now.
Bryan B
-----Original Message-----
From: FAIDHERBE Thierry [mailto:thierry.faidherbe AT forem DOT be]
Sent: Wednesday, January 23, 2013 4:45 AM
To: Bowersock, Bryan
Cc: EMC NetWorker discussion
Subject: RE: [Networker] List alive ?
Hello Bryan,
Thanks for your so kind wording.
Inside nsr reporter, there are 2 level of details :
the first one is getting backup details such saveset creation time, duration,
size, ....
this is operated by the -q parameter.
the second level is getting data load overview (client, saveset, group, pool,
...)
This level keeps by default 1 year history. The -hdle param will allow you to
increase
the period but will require more mem.
Let's take a sample.
When scheduling daily the -q "4 weeks ago", you will get first level
details in a shifted window.
Eg using -q "15 Days ago"
We are 15/1. You run it and get 01/01 -> 15/1 details.
Tomorrow, 16/1. You run it and get 02/01 -> 16/1 details. 1/1 is dropt.
If you only schedule -q "1 Days ago", you will get 15/01 -> 16/01 details.
-> so keep scheduling -q "15 Days ago"
About data load graphs now.
We are 15/01/2013. You run it and get 15/01/2012 -> 15/01/2013 dataload.
Tomorrow, 16/1. You run it and get 16/01/2012 -> 16/01/2013 dataload.
In this case, 01/01/2013 dataload is kept. till 02/01/2014. (1 year default)
If you want to get per saveset data load overview, it is possible by adding
-per_ss_monitor parameter.
BTW, getting dataload evolution of Oracle Rman/SAP Backint/SQL/Exchange...
is not so easy. Rman and backing are generating random saveset names
that make sense only in DB catalogs. For us, backup admin, they are just like
unique savesets, backuped once.
If you ask to your DBAs to add a prefix part to rman channel names for sample,
you can then rename them and group them. Look at 7.2.3.3 in doc. May be a great
usage.
I saw you added -nsrinfo arg. Great. You can also speed up nru by tuning off
file list gathering for OS based savesets, focusing -for sample- on file servers
and db servers (for easier archive files tracking).
Cheers
Th
Kind regards - Bien cordialement - Vriendelijke groeten,
Thierry FAIDHERBE
Backup/Storage & System Management
LE FOREM
Département des Systèmes d'Information
Direction Infrastructure
Boulevard Tirou, 104 Tel: +32 (0)71/206730
B-6000 CHARLEROI Mobile: +32 (477)/995319
Fax: +32 (0)71/206199
BELGIUM Mail : Thierry.faidherbe<at>forem.be
"The future belongs to those who believe in the beauty of their dreams",
Eleanor Roosevelt
"Nowadays, people know the price of everything and the value of nothing", Oscar
Wilde
-----Message d'origine-----
De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] De
la part de Bowersock, Bryan
Envoyé : mardi 22 janvier 2013 16:12
À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
Objet : Re: [Networker] List alive ?
The list is still alive and I couldn't agree more with the previous comments
about the NRU 6.0. December 2012 is the latest and greatest version, correct?
I recently discovered it as well and am finally getting used to checking NRU
instead of the console first. FINALLY, INFORMATION I CAN USE THAT MAKES SENSE
(especially to management)! Kudos to the work that has been done with this
utility. I've already fixed some issues I didn't even know existed in our
environment thanks to it. I agree on the Facebook "like" issue...I'm not
really on Facebook very often and don't "like" things that are related to my
work.
It looks like you spent a lot of time with the manual which is a good thing.
One question I have is about running NSR_REPORTER on a daily basis. If the
first time you run it you set the query to "4 weeks ago" and the second time
you run it 24 hours later, you set the query to "1 day ago", does the utility
pick up right where it left off after the 4 weeks or does it get rid of the
initial data and only go back as far as one day? Does this make sense? I've
been afraid to change the query time as I do not want any of the historical
data I have gathered to get removed. Perhaps this is in your manual, but I was
unable to find a clear answer - maybe I'm just overlooking it. Bare with me as
I am still trying to understand some of the graphs/modules so I might not be
looking in the right section(s).
For example, should I be running the scheduled task like so every day? This
takes about 2 hours in our environment based on the log file.
NSR_REPORTER_6.0.exe -s emcnetworker1.uch.org -D MM/DD/YYYY -q "4 weeks
ago" -graph -t 17:30 -cfg -nodns -monitor -hdle 365 -nooldsession -nsrinfo
-nsrla -fulltree
Or is there a better way to run schedule this particular task? Maybe
change to -q "1 day ago" after the first run using -q "4 weeks ago"?
We only have a single datazone with a little less than 200 clients (Windows,
AIX, Netware, Linux), a storage node that hosts our IBM 3494 tape library, and
adv_file type devices from EMC Data Domain that are tied to the Networker
Server (which also hosts the NMC). Both the NW Server/NMC and the tape library
storage node are running Windows 2008. Networker version is 8.0.0.1. Have
you done any testing on NW 8.0.0.6 or the DA 8.x SP1 for NRU?
In any case, this is a great tool so please don't stop the great work you are
doing with it. Thanks again.
Bryan
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Michael Leone
Sent: Tuesday, January 22, 2013 9:27 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] List alive ?
> Having NetWorker Reporting Utility 6 joining facebook only resulted in
13
> likes.
> Any 5 year old boy has more friends ... ;-D
I use Facebook for personal use; I don't go and "like" pages and products
of "work" business. So even though I spent a good portion of my day doing
VMware related work, I don't go on FB and "like" EMC or VMware. Sorry. If
I remember, I will like your page. :-)
> I asked once myself if interest still even exists in it,
> packaging, testing and coding it for 6 OSes, for worldwide audience
> takes me lot of time ... and a for so few ardency ... or if I
> just continue for my friends.
>
> It disappointed me so deeply, cannot imagine.
I've used the Reporter for some time, it can be an incredibly resource. I
for one appreciate all the work you've done.
|
