We have >1% miss rate on Win2k and higher running 5.2.2.10 agent or
higher.  We use the CAD to manage the scheduler.  Many failures have
been traced to the scheduler hanging on agents lower than 5.2.2.10 (not
saying this one is perfect) so we have standardized on this version for
now.  5.2.4.0 looks promising...

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Wednesday, January 04, 2006 1:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Missed backups

On Jan 4, 2006, at 12:50 PM, John Monahan wrote:

> I've noticed a dramatic increase in reliability/stability in
> letting the
> client acceptor daemon (CAD) control the scheduler.  In many cases you
> don't have to restart services every time you make a options file
> change
> with this method either. ...

Use of CAD is a great idea for avoiding client memory issues, and
general overhead during the great period of each day when there is no
scheduled TSM activity.  Be sure that your MANAGEDServices client
option is set to have CAD only manage the Scheduler: you would not
want your Security department to one day run port scans and be
shocked to find a considerable number of Web servers running on
internal systems where they would never expect such to be...and
particularly where those Web servers are running as the all-powerful
"root" rather than safe "nobody".  Remember that CAD can also host
the Web Client, and does so by default.  (Deploy the Web Client
judiciously.)

    Richard Sims


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.