Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error Reports 1

Status
Not open for further replies.

bdunk

MIS
May 8, 2001
1
US
Is there any way I can use mminfo (or a similar command or a script) to display info about ONLY the save sets or clients that were unsucessful. I have lots of clients and it is very tiersome to look through all of the Savegroup completion reports to determine which backups failed.
 
There are a couple of ways to do it..

For example,

mminfo -q "pool=backup,savetime > 1 day ago" -v -ot | grep cE should show you failed save sets. If you grep for "ci" you would see incomplete save sets.

Be careful though. Just because a save set completed successfully doesn't always mean there are no errors.. If someone installs MSSQL or Oracle on a system without telling you, the logs are pretty much the only way you would see locked or changed files during the backup. There may also be I/O errors to deal with.

I use an automated script to go thorough each client every morning and report to a log file that is then mailed. I'm also working on a web based reporting system that I'm testing now.. Basically, unless you want to use something like Legato GEMS, everything is still pretty manual.

Good Luck!
 
I have been having similar problems (finding success/failure metrics), but I also have been seeking a solution for across-the-board report generation. I have to say, GEMS Reporter is bad. But BOM (Backup Operations Manager) from seems to be a one-stop shop for Networker server management, report generation, and real-time display of bandwidth/IO/tape drive usage/etc. I am currently setting up BOM after a disasterous interaction with Reporter, and I have to say that in the first 5 minutes I was more impressed with BOM than I was with hours spent with GEMS Reporter.
Otherwise, I agree with ag100 that most everything you want to do with Networker is manual, whether GUI or CLI.
--Ted
NOTE: I have used perl to create a "tailing" program that runs as a daemon, reads the last line of /nsr/logs/messages (or daemon.log or savegrp or whatever), and acts dependant on the pattern match (Failed, Succeeded, volid, other). It was initially intended as a "eject full tapes before the drive is needed" script, but it could be used for many 'instant' messages concerning events. If interested in the bare bones "tailing" daemon program, feel free to contact me at tgr_ii@hotmail.com and I'll get you a copy.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top