I have been in the process of upgrading my clients from V2.1.06 to V3.1.01.
I have had the following occurrances after upgrading.  Has anyone else
noticed the differences?  I am running all clients on NT.  I used the same
exact dsm.opt file.  I am backing up to V3 servers on AIX and MVS.

1.) In my dsmsched.log there is no more detailed information.  It basically
looks just like my dsmerror.log with added information when the scheduler
starts and finishes.

Before:
05/12/1998 18:01:05 Normal File--> 53,792 E:\DATA\DISCUSS4.NTF  Sent

After:
no detail at all.


2.) Changing retries doesn't seem to work.  I have changing retries set to
1 as part of my management class.  So I don't understand how upgrading
client version affects that.  All I get are a bunch of messages stating
that file changed during backup, and skips to the next file.

Before:
05/09/1998 18:02:57 Normal File--> 262,144 E:\DATA\Certlog.nsf  Sent
05/09/1998 18:03:22 Retry # 1  Normal File--> 262,144 E:\DATA\Certlog.nsf
Sent

After:
05/12/1998 17:36:50 ANS1228E Sending of object 'E:\notesdb\web41.ntf'
failed
05/12/1998 17:36:50 ANS1840E File 'E:\notesdb\web41.ntf' changed during
processing.  File skipped.

This results in having several failures more than I had with the Version 2
client.

3.) Version 2 client took a hold of (or locked) a file while it was backing
it up.  Version 3 doesn't seem to do that.  Is this the case?  If not, is
that why my files are changing and creating backup failures as mentioned
above in issue 2.) ?

Thanks