One thing you might want to consider:  given the number of files that TSM
is processing (as shown in the dsmsched.log excerpt you sent) it's
conceivable that the backup is taxing the amount of available memory on the
Netware box.  You could try backing up with the MEMORYEFficientbackup
option set to yes.

If that does not provide any relief, or if the backups are already running
with that option, you should probably get in touch with IBM support and
asking for assistance.  They may have you do some tracing that would
provide a more detailed picture of what is occurring.At this point, I would
recommend getting in touch with IBM support and asking for
assistance.  They may have you do some tracing that would provide a more
detailed picture of what is occurring.

-Ted

At 10:16 AM 7/9/2004, you wrote:

Ted,

We put in the verbose option in our novell tsm client's
dsm.opt file, but it only showed the following.

07/09/2004 04:01:30 ANS1898I ***** Processed   361,500 files *****
07/09/2004 04:01:35 ANS1898I ***** Processed   362,000 files *****
07/09/2004 04:01:39 ANS1898I ***** Processed   362,500 files *****
07/09/2004 04:01:43 ANS1898I ***** Processed   363,000 files *****
07/09/2004 04:01:47 ANS1898I ***** Processed   363,500 files *****
07/09/2004 04:01:50 ANS1898I ***** Processed   364,000 files *****

It didn't show the file that it was backing up when the Server crash occurred.

TSM novell client 5.2
Netware OS 6.5 SP2


Ted Byrne wrote:

> At 03:49 PM 7/8/2004, you wrote:
> >I looked in the dsmsched.log there is nothing in there. (see below)
>
> If you run your scheduled backups with the -verbose option, it will record
> the files being backed up.  Based on the dsmsched.log file contents you
> posted, it looks like the option in effect for the scheduled backups is
-quiet.
>
> -Ted