Networker

Re: [Networker] check running savegroups from command line

2006-12-18 14:36:56
Subject: Re: [Networker] check running savegroups from command line
From: Bob Flynn <Bob.Flynn AT S3GROUP DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 18 Dec 2006 19:26:42 -0000
Send along the sec rules. I am using linux.

-Bob


-----Original Message-----
From: Daniel Rich [mailto:drich AT pdi DOT com] 
Sent: 18 December 2006 17:45
To: EMC NetWorker discussion; Bob Flynn
Subject: Re: [Networker] check running savegroups from command line

Bob Flynn wrote:
> How do I get a list of currently running savegroups ? I want to to the
> following every 24 hours.
>   

You don't say what OS you are on, so I'll give you a couple of options.

On *nix, you can just run "ps -efww | grep savegrp" (or "ps -auxww |
grep savegrp" depending on which *nix you are running).  If you don't
see any savegrp processes, there aren't any running.

The "correct" way to do it is to look at the output of nsradmin, but
it's a little tough to script against.
    > nsradmin
    NetWorker administration program.
    Use the "help" command for help, "visual" for full-screen mode.
    nsradmin> show name
    nsradmin> print type: nsr group; status: running
                        name: Savegroup1;
                        name: Savegroup2;
                        name: Savegroup3;
                        name: Savegroup4;

> 2.    Verify for each completed savegroup
>
> The clients and savegroups that succeeded.
>
> The clients and savegroups that failed
>   

That's trickier.  You may just want to send your savegroup completion
reports somewhere where you can process them off-line, or look at
something like Bocada's backup report software.  The information is
nsradmin (run nsradmin and run the command "print name: groupname" where
groupname is the name of any of your completed savegroups). but it is
*really* hard to parse.

> The purpose of this is an automated email to allow a quick review of
> operations, rather than scan group savegroup output. For point 2, I
> guess I can use some of
> http://www.stoffel.org/john/sources/nss/nss-3.2.pl
>   

Well, if you are on Linux, I have some rules that do this using SEC
(Simple Event Corelator).  It watches the logs and sends me an e-mail
whenever there are any errors in the savegroup output.  It isn't always
perfect, but it allows me to catch most things that go wrong.

-- 
Dan Rich <drich AT pdi DOT com>
          PDI Dreamworks |  "Step up to red alert!"  "Are you sure, sir?
           (650)562-9018 |   It means changing the bulb in the sign..."


The information contained in this e-mail and in any attachments is confidential 
and is designated solely for the attention of the intended recipient(s). If you 
are not an intended recipient, you must not use, disclose, copy, distribute or 
retain this e-mail or any part thereof. If you have received this e-mail in 
error, please notify the sender by return e-mail and delete all copies of this 
e-mail from your computer system(s).
Please direct any additional queries to: communications AT s3group DOT com.
Thank You.

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