Timothy This is one of my pet hates about TSM.
A scheduled backup which is actually in progress - ie actively transferring data between client and server - shows a status of 'Started'. A scheduled backup which started but encountered an error, dropped the session or whatever shows a status of 'In Progress'. Am I the only one who thinks this is the wrong way round? An 'In Progress' status indicates that the server is in a state to carry on the backup if the client is able to recover and re-establish the session. If this happens, the status will change to Restarted then Completed. One example is if the server OS restarts. Otherwise, In Progress is as far as it ever gets. I also don't like the fact that 'In Progress' events don't show up with QUERY EVENT * * EXCEPTIONSONLY=YES because they most definitely are exceptions. I don't like the fact that if you want to do a SQL query on the Events table for these rows instead, you have to remember to search for 'In Progres', not 'In Progress'. For example: select node_name, status from events where scheduled_start='2004-06-30 18:30:00' and (status='In Progres' or status='Missed' or status='Failed') NODE_NAME STATUS ------------------ ---------- OUSE In Progres And I don't like the fact that the Technology Preview release of Operational Reporting only selects Future, Started, Completed, Pending, Failed or Missed schedules, so they don't get picked up here either, but I don't know if this got changed in the release version. Rant over. Neil Schofield Yorkshire Water Services Ltd. Download walks around Yorkshire Water's reservoirs at http://www.yorkshirewater.com/yourenjoyment/main_walk.html The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
