Folks,

I am backing up a WIN2K (build 2195) client running TSM 3.7.2 to a
WIN2K server running TSM 3.7.3. For the past two scheduled backups,
the WIN2K client machine has received a Dr. Watson (access violation)
during the expiration of a large number (>33K) of files, causing the
scheduler to stop, and the backup session to abruptly end. There are no
significant errors logged in the server's activity log, and nothing in the
client's dsmsched.log to indicate a problem.

There was no noticeable activity occurring on the server side other than
this backup (no inventory expirations, no stg pool migrations, etc.). I
later ran this backup manually from the command line without any trouble.
I am not overly concerned with the scheduler stopping since I have it set
to restart after a failure.

Anyone else noticed failures of this type with this particular client?
Unfortunately, I don't see a v3.7.3 client yet available.

Not sure if this is a bug, or an indicator of some other problem.

Thanks for any insight.

--Ruth
  Cornell Theory Center
  Cornell Theory Center