So, if I follow your message correctly and the point I have been trying to make... There is no easy (one button) method of reporting, which should be the basis of the software, the very basic core of any backup software, that I don't have.
To answer the other question posted by Mr. Joseph Dawes, How do I track failures?, I do it the long way. I start with the q events ex=yes as a first level then we start going through the activity logs starting with a search for ANE4959i reporting missed files. Next we go through individual error logs on the clients if necessary. -----Original Message----- From: Rushforth, Tim [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 1:05 PM To: [EMAIL PROTECTED] Subject: Re: Daily Backup Report And it depends on what you mean by a "successful" backup... We use Bill's method below to report on all events taht do not have a status of completed. (We only used to report on exceptions also ...) If you are worried about some files that were not processed then "completed" does not tell you what you want (for incrementals on 4.x clients and below). Here you will have to do additional queries to report on these failed objects. With archives and selective backups however, files in use will report as failed (can't confirm if other failed files will) (again 4.x and below) so that is covered here. Now, with 5.1, incrementals, archives, and selectives all report "completed" if files are not processed because of some error. But with incrementals you can now check the return code: 4 = files skipped (doesn't count files excluded by exclude statements). But with selectives and archives rc=4 could simply mean that your exclude statements are working so now you will have to do additional queries to report on failed objects here. We also do queries on file spaces as was mentioned that reports when the last backup completed. We've had at least one occasion where security was changed on an NT drive so that the "System Account" no longer had access (that is what the TSM scheduler was using). Here the backup status showes "completed" but the filespace in question did not get backed up and the file space query picked it up. Tim Rushforth City of Winnipeg -----Original Message----- From: Bill Boyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 9:40 AM To: [EMAIL PROTECTED] Subject: Re: Daily Backup Report Be very carefull with the EX=YES. There is a status of an event of '(?)' that doesn't show as an exception. This condition can occur when a backup schedule starts for a node, and then due to either the client crashing or a networking issue the connection is dropped and never re-established within the DURATION of the event. The status is '(?)'. There is an APAR open to have meaningful status's instead of the '(?)', but for now this doesn't show as an EXCEPTION. We got bit big-time at a client of our where they out-sourced the entire TSM operation to us. They were having failures, but they were not showing on our EX=YES report. They were not happy campers! I'm still having a hard time sitting! :-) We ended up writing some PERL code to parse the Q EV client events and reporting on anything that isn't COMPLETED. This behavior started somewhere in the 4.1.x patch levels. So, just be careful relying on the EX=YES to give you everything that failed. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Williams, Tim P {PBSG} Sent: Tuesday, April 16, 2002 10:01 AM To: [EMAIL PROTECTED] Subject: Re: Daily Backup Report we generally run a q event command ex=yes you can use begindate begintime parms, etc.... help q event fYI -----Original Message----- From: Orin Rehorst [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 8:48 AM To: [EMAIL PROTECTED] Subject: Daily Backup Report What are some good ways to get an automated daily report on which clients were or were no backed up successfully? TIA, Regards, Orin Orin Rehorst Port of Houston Authority (Largest U.S. port in foreign tonnage) e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Phone: (713)670-2443 Fax: (713)670-2457 TOPAS web site: <www.homestead.com/topas/topas.html <http://www.homestead.com/topas/topas.html> >
