The backup set generation process encountered a file that was previously found to be damaged. The process encountered the file during a sequential scan of all files on the storage pool volume; the indicated file may or may not have been a candidate for inclusion in the backup set.
If this file is part of an aggregate, it may have been previously marked as damaged because an integrity error was detected in some other file within the same aggregate. AUDIT VOLUME can determine if this is the case, and if so, will reset the damaged state for the file.
The damaged file is not added to the backupset.
Audit the indicated volume with FIX=NO to determine if the file is actually damaged. The audit will reset the file's damaged state if the file is not damaged. (If the file is part of an aggregate, and none of the files within the aggregate are damaged, the audit will also reset the entire aggregate's damaged state.)
If the file remains in the damaged state after the audit completes, attempt to restore the damaged file by using the RESTORE STGPOOL command. Note, however, that this is only an option if the damaged file is in a primary storage pool that had been previously backed up to a copy storage pool.
If the audit resets the file's damaged state, or the damaged file was successfully restored using RESTORE STGPOOL, and it is important for this file be included in the backup set, then rerun the GENERATE BACKUPSET command to generate a new backup set containing the file.