Exchange Event 703, Online Maintenance - Runtime seconds seems too long
I recently put together a script to collect Event 703 information for analysis of online maintenance. After looking at the data, the run time in seconds is longer than the duration from the "Started on" attribute of the job to the TimeGenerated attribute. All information taken from the ReplacementStrings collection of the Event object, as displayed in the "Message" attribute. Does this value perhaps represent cumulative time spent by multiple threads? Scratching my head...
June 29th, 2012 11:23am

Hi Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. Terence Yu TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2012 10:32pm

Hi CBS3, Yes it is cummulative and it is value for all the invocations it made. To help you understand better, Online Defragmentation has completed a full pass on database %database file name%, freeing %number of pages freed% pages. This pass started on %OLD start date% and ran for a total of %total number of seconds actively running OLD against database% seconds, requiring %number of invocations% invocations over %number of days% days. Since the database was created it has been fully defragmented %total OLD completions% times over %number of days since database was created% days. Does this help? Thank you Santhosh
August 16th, 2012 6:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics