This is an old revision of the document!
TSM> select volume_name,write_errors,read_errors,access,STGPOOL_NAME from volumes where error_state<>'No' and ( WRITE_ERRORS>0 or READ_ERRORS>0 )
TSM> update vol <volume_name> access=destroy
TSM> checkout libvol <library_name> <volume_name>
TSM> restore vol <volume_name> preview=yes
TSM> restore vol <volume_name>
TSM> delete vol <volume_name> discard=yes
On source server do the following:
If the setting for recovering damaged files is OFF, turn it on by issuing the SET REPLRECOVERDAMAGED command and specifying ON:
set replrecoverdamaged on copy to clipboard
If the REPLRECOVERDAMAGED system parameter is set to OFF, and you change the setting to ON, an automatic scan of the Tivoli Storage Manager system is started. You must wait for the process to be completed successfully before you can initiate the recovery of damaged files by using the REPLICATE NODE command. Recover damaged files by running the REPLICATE NODE command and specifying a value for the RECOVERDAMAGED parameter. Take one of the following actions:
To run the full node replication process and recover damaged files, specify the name of the node or node group, and the RECOVERDAMAGED parameter with a value of YES. For example, to run the full node replication process and recover damaged files for client nodes in the PAYROLL group, issue the following command:
replicate node payroll recoverdamaged=yes copy to clipboard
To run the node replication process only to recover damaged files, specify the name of the node or node group, and the RECOVERDAMAGED parameter with a value of ONLY. For example, to recover damaged files for client nodes in the PAYROLL group without running the full node replication process, issue the following command:
replicate node payroll recoverdamaged=only
TSM> delete vol <volume_name> discard=yes TSM> checkout libvol <library_name> <volume_name> remove=bulk
TSM> backup stgpool <primary_stgpool> <secondary_stgpool>