Filter
Top Products
ANR1166E Move Data for offsite volume cannot copy damaged file in storage pool storage
pool name: Node node name, Type file type, File space filespace name, File name
file name.
Explanation: A move data process for an offsite volume cannot locate an
undamaged copy of the specified file in any storage pool accessible by the server. If
this file is part of an aggregate, the process could not locate an undamaged copy of
the aggregate to which the file belongs.
System Action: The file will skipped and will not be moved from the offsite
volume.
User Response: The indicated storage pool is a primary pool that contains a
damaged copy of the file. The only usable copy of the file may now only reside on
the offsite volume that was involved in the move data process. If you bring this
volume back onsite, you can recreate the file in the primary pool by using the
RESTORE STGPOOL command. After the restore, you can reissue the MOVE
DATA command.
ANR1167E Space reclamation for offsite volume(s) cannot copy damaged file in storage
pool storage pool name: Node node name, Type file type, File space filespace
name, File name file name.
Explanation: A reclamation process of offsite volumes cannot locate an
undamaged copy of the specified file in any storage pool accessible by the server. If
this file is part of an aggregate, the process could not locate an undamaged copy of
the aggregate to which the file belongs.
System Action: The file is skipped and will not be moved from the offsite volume.
User Response: The indicated storage pool is a primary pool that contains a
damaged copy of the file. The only usable copy of the file may now only reside on
an offsite volume that was involved in the reclamation process, but was not totally
reclaimed. If you bring this volume back onsite, you can recreate the file in the
primary pool by using the RESTORE STGPOOL command.
ANR1168W Migration skipping damaged file on volume volume name: Node node name,
Type file type, File space filespace name, File name file name.
Explanation: During migration, 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 will not be moved.
User Response: Audit the indicated volume with FIX=NO to verify that the file is
damaged. The audit will reset the file status if the file is found to be undamaged
189
Tivoli Storage Manager Messages
3. Common and Platform
Specfic Messages