Use Restore Volume to treat a single volume, and skip the superfluous
steps.

The volume persists per a situation which the Activity Log should
explain...perhaps a missing copy storage pool source or error on a
copypool tape.

  Richard Sims

On Jun 5, 2006, at 9:53 AM, Lawrence Clark wrote:

We had multiple write errors on a cartridge and did our normal
procedure:
- checkout the vol
- update access to destroyed
- do a restore stgpool

normally the volume is gone from the tsn db. however, this time the
volume has persisted.
anyone had this situation before.
i think this is the 1st time we've gone through this procedure since
upgrading to tsm 5.3(3).