the client determines if a scheduled backup is successful or fails

now on a changing file you might see a "failed" message in your sched.log
but look closer and you'll probably also see where a retry caught it (it
will try an additional "changingretries" number of times to back up the
file) that is if you have static set for the copy group serialization... if
you have dynamic you should just see it take the changed file (ouch)

so when you are saying "files failed to back up" are you refering to the
summary statistics at the end of the sched.log after a scheduled event ? ? ?

Dwight

> ----------
> From:         Susan Wright[SMTP:S.Wright AT LABSAFETY DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, March 21, 2000 11:12 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Failed status on backups
>
> What tells ADSM if the backups have failed or completed successfully. Is
> it
> an error message that comes up or is it by the number of files that failed
> to backup?? What?? We have backups that say successful but when we look
> there were a few files that failed to backup because they were being
> acessed.
>
> Please let me know
>
> TIA
>
> Susan Wright
> Lab Safety Supply
> Janesville, WI 53546
> s.wright AT labsafety DOT com
>
> AIX 4.3.2
> ADSM 3.1.2.1
>