Analyzing the ANR2317W error message

The ANR2317W error message is issued when a process determines that there is a damaged file.

ANR2317W Audit Volume found damaged file on volume volumeName: Node nodeName,
Type fileType, File space fileSpaceName, fsId fileSpaceID,
File name fileName is number version of totalVersions versions.

1. Issue the QUERY VOLUME volumeName F=D command.
2. Issue the following SQL select statement from an administrative client to this server: select* from VOLHISTORY where VOLUME_NAME='volume_name' AND TYPE='STGNEW.
   The results of the QUERY VOLUME command indicate when this volume was last written. The information from the SELECT operation reports when this volume was added to the storage pool. Often, AUDIT VOLUME might report files as damaged because at the time that the data was written, the hardware was malfunctioning and did not write the data correctly, even though it reported to the IBM Storage Protect server that the operation was successful. As a result of this device malfunction, many files on many different volumes might be affected. Perform the following steps to resolve this issue:
   1. Evaluate the system error logs or other information about this drive to determine if it still reports an error. If errors are still reported, they must first be resolved. To resolve a hardware issue, work with the hardware vendor to correct the problem.
   2. If this storage pool is a copy of a storage pool volume, simply delete this volume using the DELETE VOLUME volumeName DISCARDDATA=YES command. The next time a storage pool backup is run for the primary storage pool or storage pools where this damaged data resides, it will be backed up again to this copy storage pool and no further action is necessary.
      • If this storage pool is a primary storage pool volume and the data was written directly to this volume when the client stored the data, then it is likely that there are no undamaged copies of the data on the server. If possible, back up the files again from the client.
      • If this storage pool is a primary storage pool volume but the data was put on this volume by MIGRATION, MOVE DATA, or MOVE NODEDATA commands, there might be an undamaged copy of the file on the server. If the primary storage pool that contained this file was backed up to a copy storage pool prior to the MIGRATION, MOVE DATA, or MOVE NODEDATA commands, then an undamaged file might exist. If an undamaged file exists, issue the UPDATE VOLUME volumeName ACCESS=DESTROYED command and then issue the RESTORE VOLUME volumeName command to recover the damaged files for this volume from the copy storage pool.