Dianne,

I've run across a similar situation using 2.1 on a AIX.  I've been told
to check which SMSUPx patch I'm running.  If you are using SMSUP5, go
back to SMSUP4 on your Netware 4 servers.  From what I have been told,
the newer TSAxxx.NLMs have a problem with NDS objects. I haven't had a
chance to down my servers to see if this valid or not.

>----------
>From:  Dianne Sharp[SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent:  Wednesday, September 18, 1996 5:02 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Backup Integrity checking
>
>HELP .......... PLEASE
>
>We are about to start the rollout of ADSM to all our Netware 3.x,
>Netware 4.x and HP-UX servers using MVS V1 as the server.
>
>When looking at the scheduled events, it seems that a status of
>Completed should indicate a successful backup.   In actual fact, I have
>found that this status still shows even if the backup fails on certain
>files.  Perhaps they are in use and are skipped (which we deem as
>acceptable) but I have also seen a backup showing Completed and the log
>contains the following error messages :
>
>ANS4089E File not found during Backup, Archive or Migrate processing.
>ANS4301E Server detected system error
>
>Both were preceded by ANS4228E Sending of object 'xxx' failed
>
>The message manual doesn't tell me any more than the actual messages do
>- just see your System Administrator - which is me.
>
>These messages were all relating to NDS objects on a Netware 4.x
>server.
> I'm not sure if it's ever happened with normal files.
>Does anyone know if this is specific to NDS objects?
>
>How can I find out which files have had errors, apart from having to
>check the error log on every single client every day?   I'm worried
>that
>if a file keeps getting missed that we will never have a backup of it.
>