Re: [Networker] Networker 7.4

There is a new RAP resource in the client (nsrexecd):

nsrdmin -p nsrexec
nsradmin> p type : NSR log ; name : daemon.raw
nsradmin> update runtime rendered log : /nsr/logs/daemon.rendered

This, plus stop & restart of NetWorker daemons, should get
a runtime-rendered version of the log.  There's an extra
message ID column shoved on the front, but it should be worth
looking at for purposes of this thread.


Siobhan Ellis
IDATA Integrity
Sydney

On 20/7/07 12:27 PM, "Peter Viertel" <Peter.Viertel AT MACQUARIE DOT COM> wrote:

> nsr_render_log has a lot of options thankfully - there's more info, such as
> category and severity, and the format is well defined now in the man page.
> 
> The per-line view is therefore only a small tweak, but the real issue is
> whether we will still see unformatted lines in daemon.log any more that are
> the result of some binaries writing random debug messages to STDERR - another
> issue to investigate is when we run a script or a binary as a notification and
> we take advantage of it's STDOUT and STDERR pointing at daemon log, how will
> these work now?
> 
> Of course - the developers want us to use syslog - but historically there have
> always been more messages in daemon.log than almost anywhere else - anyway,
> the upshot is that every line of code will need to be checked.
> 
> 
> 
> Here's the startup messages from daemon.raw...  Just as-is first...
> 
> 42506 1183558982 2 0 0 1 11520 0 isd93 nsrd 9 %s %s: %s 3 0 6 server 0 6
> notice 49 14 7324 7 started
> 10100 1183559066 2 0 0 1 11539 0 isd93 nsrmmdbd 27 media db is checking btrees
> 0
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 28 @(#) Product:
> NetWorker
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 32 @(#) Release:
> 7.4.Build.187
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 22 @(#) Build number: 187
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 43 @(#) Build date:   Fri Jun
> 8 18:09:58 2007
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 28 @(#) Build arch.:
> solaris7w
> 0 1183559075 2 0 0 1 11520 0 isd93 nsrd 2 %s 1 0 53 @(#) Build info:
> DBG=0,OPT=-O2 -fno-strict-aliasing
> 9870 1183559082 2 0 0 1 11539 0 isd93 nsrmmdbd 45 media db is consistency
> checking the database 0
> 9867 1183559082 2 0 0 1 11539 0 isd93 nsrmmdbd 44 Creating new client id
> mapping for client:%s 1 12 5 isd93
> 10106 1183559087 2 0 0 1 11539 0 isd93 nsrmmdbd 29 media db is open for
> business 0
> 9513 1183559088 2 0 0 1 11541 0 isd93 nsrindexd 42 Running nsrck to check
> client file indices 0
> 42506 1183559091 2 0 0 1 11520 0 isd93 nsrd 9 %s %s: %s 3 0 5 index 0 6 notice
> 49 44 9352 24 checking index for '%s'  1 0 5 isd93
> 9404 1183559091 2 0 0 1 11544 0 isd93 nsrck 26 %s is missing; re-creating 1 23
> 25 /zfs/nsr/index/isd93/.nsr
> 
> 
> 
> 
> Then, using C locale, and a timezone of Australia/NSW and piping through the
> render pipe with args to add a header, and to 'ofuscate', and to strip some of
> the crud, the closest I can get is 'nsr_render_log -lzaceptyhm daemon.raw':
> 
> TimeStamp ProgramName RenderedMessage
> 
> 07/05/07 00:23:02  nsrd server notice: started
> 07/05/07 00:24:26  nsrmmdbd media db is checking btrees
> 07/05/07 00:24:35  nsrd @(#) Product:      NetWorker
> 07/05/07 00:24:35  nsrd @(#) Release:      7.4.Build.187
> 07/05/07 00:24:35  nsrd @(#) Build number: 187
> 07/05/07 00:24:35  nsrd @(#) Build date:   Fri Jun  8 18:09:58 2007
> 07/05/07 00:24:35  nsrd @(#) Build arch.:  solaris7w
> 07/05/07 00:24:35  nsrd @(#) Build info:   DBG=0,OPT=-O2 -fno-strict-aliasing
> 07/05/07 00:24:42  nsrmmdbd media db is consistency checking the database
> 07/05/07 00:24:42  nsrmmdbd Creating new client id mapping for client:host1
> 07/05/07 00:24:47  nsrmmdbd media db is open for business
> 07/05/07 00:24:48  nsrindexd Running nsrck to check client file indices
> 07/05/07 00:24:51  nsrd index notice: checking index for 'isd93'
> 07/05/07 00:24:51  nsrck /zfs/nsr/index/isd93/.nsr is missing; re-creating
> 
> 
> Comparing this to startup on my 7.3.2 server, theres still some differences...
> The : after the daemon name,
> 
> 06/03/07 15:53:57 nsrd: server notice: started
> 06/03/07 15:53:59 nsrmmdbd: media db is checking btrees
> 06/03/07 15:53:59 nsrmmdbd: media db is consistency checking the database
> 06/03/07 15:54:02 nsrmmdbd: media db is open for business
> 06/03/07 15:54:03 nsrmmgd: Starting nsrmmgd.
> 06/03/07 15:54:07 nsrd: @(#) Product:      NetWorker
> 06/03/07 15:54:07 nsrd: @(#) Release:      nw_7_3_2_jumbo.Build.386
> 06/03/07 15:54:07 nsrd: @(#) Build number: 386
> 06/03/07 15:54:07 nsrd: @(#) Build date:   Sat Feb 17 12:22:26 2007
> 06/03/07 15:54:07 nsrd: @(#) Build arch.:  solaris7w
> 06/03/07 15:54:07 nsrd: @(#) Build info:   DBG=0,OPT=-O2 -fno-strict-aliasing
> 06/03/07 15:54:07 nsrindexd: Running nsrck to check client file indices
> 
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Kyle Oliver
> Sent: Friday, 20 July 2007 8:19 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Networker 7.4 - any experiences
> 
> Just curious, are you still able to run the logs through the nsr_render_logs
> filter and get anything that looks like what you used to get from the logs?
> This will determine if log scraping should be dumped or just tweaked.
> 
> Maybe it is time that we on this list try to ratchet up the pressure on EMC to
> give the keys to the jobs database, so we can just query that.  That would be
> better than log scraping anyway....
> 
> -Kyle
> 
> 
> ----- Original Message ----
> From: Peter Viertel <Peter.Viertel AT MACQUARIE DOT COM>
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Sent: Thursday, July 19, 2007 4:29:14 AM
> Subject: Re: [Networker] Networker 7.4 - any experiences
> 
> As far as I can tell 7.4 is a branch off one of the 7.3.2 Jumbo Builds but I
> am not sure which  - it adds internationalisation to the NMC gui and to the
> logs, and there is a new clinet upgrade mechanism.
> 
> From the perspective of NMC it has several improvements:
> * The JRE required is 1.5 instead of 1.4
> * usability tweaks - tape operations displayed on the library window etc...
> 
> The Client upgrade functionality seems like it will be useful, but you have to
> have at least 7.4 clients beofre this can be used, so it will be a while
> before the benefits can be seen.
> 
> The internationalisation seems to have been implemented reasonably well - it
> provides french, german, and chinese language packs so far.
> 
> However!!!!   The /nsr/logs/daemon.log is gone!    The code for alerting has
> been completely overhauled in all binaries and modules and the default is now
> to write to /nsr/logs/daemon.raw. It is intended that to read the raw log you
> pipe it through the new nsr_render_logs filter that localises the error
> messages. The result is that all custom scripts that watch networker log files
> will be broken.
> 
> 
> I think from my perspective - I will upgrade my NMC server first - I'm hoping
> they have fixed some bugs in it... It's not too hard to back out of if it does
> screw up, and our windows client people will be pleased they can finally dump
> the 1.4 JRE from their builds....
> 
> But there's no way I'm going near it on an actual backup server - not until
> version 7.4.7 (as Davina has said, that will really fly).
> 
> The current latest sorta-stable version is 7.3.2 Build 499 - EMC are about to
> release 7.3.3 which will have more fixes in it that 7.4...    So I'm waiting
> to test 7.3.3
> 
> 
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Ronny Egner
> Sent: Thursday, 19 July 2007 5:46 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] Networker 7.4 - any experiences
> 
> Hi list,
> 
> i would like to ask for you experiences with Networker 7.4.
> Currently we are running 7.2.2 but a few customer of us run
> 7.3.2 Update 1 - so far without any major issues...
> --
> Mit freundlichen Grüßen
> 
> Ronny Egner
> Diplom-Ingenieur (BA)
> Systeme & Service
> Oracle DBA
> 
> Telefon: +49 381 2524-422
> Telefax: +49 381 2524-399
> 
> 
> mailto:ronny.egner AT siv DOT de
> http://www.siv.de
> 
> 
> ******************************************************************************
> *********
> Aus Rechtsgründen ist die in dieser E-Mail gegebene Information nicht
> rechtsverbindlich. Eine rechtsverbindliche Bestätigung reichen wir Ihnen auf
> Anforderung in schriftlicher Form nach. Diese Nachricht ist ausschließlich für
> den bezeichneten Adressaten oder dessen Vertreter bestimmt.
> 
> The information contained in this email is not legally binding. At your
> request, we will provide you with a legally binding confirmation in written
> form. 
> This
> message is intended solely for the addressee, entity to which the email is
> addressed or the authorised agent.
> ******************************************************************************
> *********
> 
> 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
> 
> NOTICE
> This e-mail and any attachments are confidential and may contain copyright
> material of Macquarie Bank or third parties. If you are not the intended
> recipient of this email you should not read, print, re-transmit, store or act
> in reliance on this e-mail or any attachments, and should destroy all copies
> of them. Macquarie Bank does not guarantee the integrity of any emails or any
> attached files. The views or opinions expressed are the author's own and may
> not reflect the views or opinions of Macquarie Bank.
> 
> 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
> 
> 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
> 


Siobhán

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