Paul,

Somewhere between the read and the write of my last response to you the
brain evidently went to sleep.  When I said:


> If the file is restored incorrectly, and the user does not become aware of
>the bad file, it is likely that this bad file will now be backed up again
>by ADSM during the next incremental backup.  Some days later, the remaining
?inactive backups of this file will expire.  These remaining inactive backups
>would be the only valid copies of this file at this point, and they will
>be expired.
>
>Q2: Will this second backup be considered a "good backup" or a "bad backup"
>    by the analysis tool that you are going to provide to us to determine if
>    we have been affected by the compression problem?
>
>===> This second backup will be considered a "bad backup" by the
>     tool.  Howwver if the file has changed between the two
>     backups it be ok unless it again happens to land in the
>     problem size range.


I had forgotten we were talking about backing up a bad restored file.  I was
working on a second backup of the original file after a period of time.

I should have said that the second backup ( backup of a previously restored
"bad backup"file ) would probably NOT be considered a "bad backup"
because the chances of it again falling into the correct size range would be
very small.

Sorry about the incorrect information.

Regards,
Jacquie Reith