Hi,

we run TSM 5.2.x on SUSE Linux SLES8 an SUSE 9.2 - the deamon likes to die,
it is common. Our hardware admins solved this problem with an automated
restart of dsmcad.

Regards, Dierk




|---------+--------------------------->
|         |           John Monahan    |
|         |           <JMonahan@COMPUR|
|         |           ES.COM>         |
|         |           Gesendet von:   |
|         |           "ADSM: Dist Stor|
|         |           Manager"        |
|         |           <[email protected]|
|         |           T.EDU>          |
|         |                           |
|         |                           |
|         |           04.01.2006 18:50|
|         |           Bitte antworten |
|         |           an "ADSM: Dist  |
|         |           Stor Manager"   |
|         |                           |
|---------+--------------------------->
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                                                     |
  |        An:      ADSM-L AT VM.MARIST DOT EDU                                 
                                                                            |
  |        Kopie:                                                               
                                                                     |
  |        Thema:   Re: [ADSM-L] Missed backups                                 
                                                                     |
  
>--------------------------------------------------------------------------------------------------------------------------------------------------|




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.

The only time I notice missed backups nowadays is when the backup session
abends somehow leaving the status in a hung state and the scheduler service
still started.  Normally, SOP is to go and restart the CAD on all clients
whose backup status is reporting as failed or started (and the backup is no
longer running) and that helps a lot as well.


______________________________
John Monahan
Senior Consultant Enterprise Solutions
Computech Resources, Inc.
Office: 952-833-0930 ext 109
Cell: 952-221-6938
http://www.computechresources.com




             "Meadows, Andrew"
             <AMeadows AT BMI DOT COM
             >                                                          To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Missed backups


             01/04/2006 10:18
             AM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






I have a general question here.

I have about 150 clients.
Client info:

Windows 2003 server
Windows 2000 server
Red Hat Linux 3 AS
AIX 5.1

All running tsm client version 5 or later sending data to a tsm server
on AIX running version 5.3

On a nightly basis I have at least 6 or 7 of these servers that miss
their backups due to the service stopping. Is this common. Do other
people experience these misses or is it something I need to look into on
these servers. For the most part they are not the same server and I have
the schedules spread from 7pm to 12 pm hourly.

Just wanting to get a general guage of if there is something that I need
to look into that I am doing wrong or if this is a normal and acceptable
level of misses per night.

Thanks,
Andrew
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************