Actually the process is to just mark the primary volume as destroyed, then
perform a "restore volume"
TSM uses the contents of the destroyed volume in order to rebuild it.
Now, with the old tape ~deleted~ from TSM, it doesn't know what was on it in
order to rebuild it !
Sorry...
Here is some info on volume recovery... (from my 10 year archive stuff)
Periodic audits of the volumes within these pools should be performed to
ensure data integrety.
THSES AUDITS SHOULD BE PERFORMED WITH FIX=NO TO ENSURE NO DATA LOSS!
If a volume is found to have errors perform one of the following to refresh
the damaged data.
A) If the damaged volume is a primary data storage pool volume, 10YRARCH
volume.
        1) DO NOT run a "move data", "delete volume (discard=yes)", or
"audit volume (fix=yes)"
                against the damaged volume because these will remove
references to the data
                needing to be repaired!
        2) Ensure no other tape activity is running on the box, such as
migrations or
                reclamations, that might tie up required resources.
        3) Issue the following command from within an administrative command
line session:
                RESTORE VOLUME volser COPYSTGPOOL=10YRARCHCP
                this will start a background process to restore the damaged
volume.
        4) CHECK THE RESULTS OF THE "RESTORE VOLUME" !
                The restoration may be incomplete for one or more of the
following reasons:
                   * Files were either never backed up or the backup copies
are marked as
                     damaged. Use the QUERY CONTENT command to get more
information on the
                     remaining files on the volume.
                   * A copy storage pool was specified on the RESTORE
command, but files
                     were backed up to a different copy storage pool. Use
the PREVIEW
                     parameter when you issue the RESTORE command again to
determine if this
                     is the problem.
                   * Volumes in the copy storage pool needed to perform the
restore
                     operation are offsite or unavailable. Check the
activity log for
                     messages that occurred during restore processing.
                   * Backup file copies in copy storage pools were moved or
deleted by other
                     TSM processes during a restore.
                Correct problems when possible and rerun the "RESTORE
VOLUME" command.
        5) The "RESTORE VOLUME" command changes the access mode of the
specified volumes
                to DESTROYED. When all files on a volume are restored to
other locations,
                the destroyed volume is empty, and TSM deletes it from the
database.
                If the volume is not fully recovered perform a "QUERY
CONTENT" on the destroyed
                volume to determine the physically lost files and inform
their owner(s).

Dwight