The only way to see status=Started jobs is if you perform a query while they 
are under way: if you really wanted that, a cron job capture would take care of 
it.  Running a query after all scheduled backups have finished will report 
final status of Completed (or Missed or Failed), which is probably what you get 
at 09:00.  And, of course, the Events table does not contain information for 
backups which are independently performed on the client.

Such event information is superficial, of course...  The client administrator 
should be reviewing backup logs (and the dsmerror.log!) for anomalies which may 
be delaying backups (e.g., retries) or be causing individual files or whole 
file systems to not get backed up (as in a Domain omission or forgotten, old 
Exclude).

    Richard Sims   http://people.bu.edu/rbs

On Jun 29, 2010, at 1:28 PM, Moyer, Joni M wrote:

> Hi Richard,
> 
> Is there any other way to do a report that would list missed, failed, in 
> progress and started backups then on a daily basis running it from the prior 
> day at 6PM until the current time the script is run at 9AM?  I currently run 
> q event at 9AM which catches the missed & failed backups, but nothing that 
> currently accounts for anything that is in progress or has been started.
> 
> Any suggestions/ideas are appreciated!  This one has me stumped!