ANR3651W
The replication process is skipping a damaged file on volume volume name: Node node name, Type file type, File space filespace name, File name file name.

Explanation

During the replication process, a file is encountered that was previously found to be damaged. If this file is part of an aggregate, the entire aggregate was previously marked damaged, possibly because an integrity error was detected for some other file within the aggregate.

System action

The damaged file is not replicated.

User response

Perform the following actions:
  • Audit the volume with FIX=NO to verify that the file is damaged. If the file is undamaged, the audit process resets the file status. If the file is part of an aggregate and the entire aggregate is found to be undamaged, the audit process resets the aggregate status.
  • If the volume is in a primary storage pool and has a copy in the copy storage pool, attempt to restore the damaged file by issuing the RESTORE STGPOOL command.