Cris,

1.) Your scheduled backup taking 5 to 15 minutes to "start"
    seems to be a schedule definition situation.
    We haven't seen any problems with this yet.
    When you schedule the COMMAND type schedule, the ADSM Scheduler
    receives the scheduled "command" and executes it.
    I haven't seen this "delay" from the testing we did here.
    With "Polling" schedules, the client asks the server what
    time it should run, then waits until that time, then
    executes the "Objects" field for the COMMAND type schedule.
    Are you using "Polling Schedules"?  Are the clocks set
    correctly on your machines?
    Can you provide more information on what you mean by
    5 to 15 minutes to "start"?

2.) The ADSM Server fields you mentioned below are not updated
    after an Exchange Backup.  We are looking at making use of them
    in the future.  The "Last Backup" pieces make a lot of sense
    but we are not sure about Capacity and %Util yet.

Del Hoobler
ADSM Agent Development
hoobler AT us.ibm DOT com

>> We are currently testing the new Exchage client and have
>> found several perplexing issues:
>>
>> Vitals: ADSM v3 for NT,  Exchange Agent v1
>>
>>
>> 1)  It takes upwards of 5 to 15 minutes for the scheduled backup to
>> start. This seems very slow and
>>  a bit disconcerting since it's the only client and the backup is very
>> small, about 10MB.
>>
>> 2) The filespace records do not show any information for:
>>         Capacity(MB)
>>         %Util
>>         Last Backup Start
>>         Days Since Last Backup Started
>>         Last Backup Completed
>>         Days Since Last Backup Completed
>>
>> Any thoughts?
>>
>> ________________________
>> Cris Robinson
>> Senior Technical Analyst
>> Desktop Services Technical Support
>> Liberty Mutual Insurance
>> 603.431.8400.54837
>> cris.robinson AT libertymutual DOT com