Networker

[Networker] Script to look for backup failures.....7.6x & 8.0

2013-02-04 11:18:44
Subject: [Networker] Script to look for backup failures.....7.6x & 8.0
From: japgar <networker-forum AT BACKUPCENTRAL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 4 Feb 2013 08:18:00 -0800
A couple of things.... 

1) Another option would be EMC's Data Protection Advisor which could be used 
for Networker and other backup products.  However, this is costly and requires 
infrastructure to install.  But, it would give you a single tool to monitor 
failures (and possibly create problem tickets).

2) I created a series of perl scripts that are used to create a Networker Logs 
website.  It centrally locates the logs on a single server and provides among 
other things a way to identify failed savesets and clients on a Networker 
server.  If you didn't want to bother with the creation of the actual website, 
you could just run the perl program (via the savegroup notification feature 
whenever a savegroup completes) on each of your Networker servers.  From there 
you could do one of two things, add code to the perl program to kick off your 
problem ticket creation for clients identified as "Failed"or... create a second 
script that would go through the files that get created by my script on your 
Networker server to identify failed clients and/or savegroups with unsuccessful 
savesets.   I've offered these scripts and instructions a number of times on 
this list.... A few have been successful in actually installing it......  You 
must be willing to modify perl scripts to add file loc!
 ations.  The only Networker modification is to add a Savegroup Notification 
that will execute the perl program.  The perl program will parse each line of 
the savegroup log and create some fileson your Networker server.
If you want a copy of the scripts... send me an email: jim.apgar13 AT gmail DOT 
com

Jim



Thanks for the info. My other use of this is to include in the script to
automatically cut a problem ticket for said failed backup.

My other issue is that I still have to upgrade 19 other masters that span
multiple O/S flavors, multiple masters, and multiple hardware platforms. So
I'm trying to setup this process to be its own "island" on each master so
that it isn't dependent on some other server or service outside the master
server it is running on.

Networker is just ONE of the backup products I help support. I help
support over 100 backup master servers. So this would be very helpful to
automatically open a trouble ticket when a backup fails. [Wink]

+----------------------------------------------------------------------
|This was sent by jim.apgar13 AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------