I would say it is a problem. If the backup can't get to some of the data
then it is an error.

Kai

> Date:    Tue, 19 Mar 2002 16:04:04 -0500
> From:    "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
> Subject: Re: Backup StgPool Issue Discovered
>
> The question I have:  Does anyone consider this a problem or are you OK
with
> it working like this?
>
> I found out today it appears that a BACKUP STGpool command will just skip
> tapes that are in an UNAVAILABLE, DESTROYED, or DAMAGED status and put out
a
> little warning message and give you a SUCCESS.  DESTROYED is not a problem
> because I took the overt action to say it was destroyed, but skipping
> UNAVAILABLE or DAMAGED is not good.  I would bet there are hundreds of
> customers not aware of this.   The exposure is your copypool (disaster
> recovery set) may not include all of the data and not a valid restore
point.
> Unfortunately, a tape can get in the UNAVAILABLE status just because the
> tape library had a problem dismounting the tape.
>