I have two DEC Alpha systems running v2r1m2 of the adsm client.  Each
has now had a situation (different times for each machine) where the
adsm client is still in memory (running in the background as a unix
daemon like it's supposed to), but they've stopped doing their
backups.  Fortunately our adsm server sends an email summary about
adsm activity once a week and so I can see when backups haven't been
done.  Each time this has happened it's been an entire week where no
backups have happened.  Each time this has happened I've rebooted the
Alpha workstation and everything is hunky-dory again.

Here is the contents of my dsm.sys file:

servername              cmsa
commmethod              TCPip
tcpport                 1600
tcpserveraddress        backup.berkeley.edu
nodename                tuna2.berkeley.edu
schedmode               polling
queryschedperiod        6
passwordaccess          generate
schedlogname            /usr/local/adsm/sched.log
schedlogretention       14
* errorlogretention     14
inclexcl                /usr/local/adsm/backup.excl


Here is my dsm.opt file:

servername      cmsa
quiet


The last entry in the sched.log file looks fine:

Executing scheduled command now.
06/15/1996 23:56:44 Total number of objects inspected:   29,333
06/15/1996 23:56:44 Total number of objects backed up:       25
06/15/1996 23:56:44 Total number of objects updated:          0
06/15/1996 23:56:44 Total number of objects rebound:          0
06/15/1996 23:56:44 Total number of objects deleted:          8
06/15/1996 23:56:44 Total number of objects failed:           0
06/15/1996 23:56:44 Total number of bytes transferred:     25.9 MB
06/15/1996 23:56:44 Data transfer time:                  216.21 sec
06/15/1996 23:56:44 Data transfer rate:                  123.04 KB/sec
06/15/1996 23:56:44 Average file size:                  1,064.1 KB
06/15/1996 23:56:44 Elapsed processing time:            0:08:57
06/15/1996 23:56:44 Scheduled event 'DAILY_2300' completed successfully.
06/15/1996 23:56:44 Sending results for scheduled event 'DAILY_2300'.
06/15/1996 23:56:45 Results sent to server for scheduled event 'DAILY_2300'.

06/15/1996 23:56:45 ANS4483I Schedule log pruning started.
06/15/1996 23:56:46 Schedule Log Prune: 958 lines processed.  60 lines pruned.
06/15/1996 23:56:46 ANS4484I Schedule log pruning finished successfully.
06/15/1996 23:56:46 Querying server for next scheduled event.
06/15/1996 23:56:46 Next operation scheduled:
06/15/1996 23:56:46 ------------------------------------------------------------
06/15/1996 23:56:46 Schedule Name:         DAILY_2300
06/15/1996 23:56:46 Action:                Incremental
06/15/1996 23:56:46 Objects:
06/15/1996 23:56:46 Options:
06/15/1996 23:56:46 Server Window Start:   23:00:00  on 06/16/1996
06/15/1996 23:56:46 ------------------------------------------------------------
06/15/1996 23:56:46 Schedule will be refreshed in 6 hours.