Use this command to delete a storage pool volume and, optionally, the files stored in the volume.
If you are deleting several volumes, delete the volumes one at a time. Deleting more than one volume at a time can adversely affect server performance.
Storage pool volumes cannot be deleted if they are in use. For example, a volume cannot be deleted if a user is restoring or retrieving a file residing in the volume, if the server is writing information to the volume, or if a reclamation process is using the volume.
If you issue the DELETE VOLUME command, volume information is deleted from the Tivoli® Storage Manager database. However, the physical files that are allocated with DEFINE VOLUME command are not removed from the file space.
If this command is applied to a WORM (write once, read many) volume, the volume returns to scratch if it has space remaining in which data can be written. (Note that data on WORM volumes, including deleted and expired data, cannot be overwritten. Therefore, data can only be written in space that does not contain current, deleted, or expired data.) If a WORM volume does not have any space available in which data can be written, it remains private. To remove the volume from the library, you must use the CHECKOUT LIBVOLUME command.
The DELETE VOLUME command automatically updates the server library inventory for sequential volumes if the volume is returned to scratch status when the volume becomes empty. To determine whether a volume will be returned to scratch status, issue the QUERY VOLUME command and look at the output. If the value for the attribute "Scratch Volume?" is "Yes," then the server library inventory is automatically updated.
If the value is "No," you can issue the UPDATE LIBVOLUME command to specify the status as scratch. It is recommended that you issue the UPDATE LIBVOLUME command after issuing the DELETE VOLUME command.
Attempting to use the DELETE VOLUME command to delete WORM FILE volumes in a storage pool with RECLAMATIONTYPE=SNAPLOCK fails with an error message. Deletion of empty WORM FILE volumes is performed only by the reclamation process.
If you issue the DELETE VOLUME command for a volume in a storage pool that has a SHRED parameter value greater than 0, the volume is placed in the pending state until shredding is run. Shredding is necessary to complete the deletion, even if the volume is empty.
If you issue the DELETE VOLUME command for a volume in a storage pool that is set up for data deduplication, the Tivoli Storage Manager destroys any object that is referencing data on that volume.
To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to which the volume is defined.
.-DISCARDdata--=--No------. >>-DELete Volume--volume_name--+-------------------------+------> '-DISCARDdata--=--+-No--+-' '-Yes-' .-Wait--=--No------. >--+------------------+---------------------------------------->< '-Wait--=--+-No--+-' '-Yes-'
If the volume being deleted is a primary storage pool volume, the server checks whether any copy storage pool has copies of files that are being deleted. When files stored in a primary storage pool volume are deleted, any copies of these files in copy storage pools are also deleted.
When you delete a disk volume in a primary storage pool, the command also deletes any files that are cached copies (copies of files that have been migrated to the next storage pool). Deleting cached copies of files does not delete the files that have already been migrated or backed up to copy storage pools. Only the cached copies of the files are affected.
If the volume being deleted is a copy storage pool volume, only files on the copy pool volume are deleted. The primary storage pool files are not affected.
Do not use the DELETE VOLUME command with DISCARDDATA=YES if a restore process (RESTORE STGPOOL or RESTORE VOLUME) is running. The DELETE VOLUME command could cause the restore to be incomplete.
If you cancel the DELETE VOLUME operation during processing or if a system failure occurs, some files might remain on the volume. You can delete the same volume again to have the server delete the remaining files and then the volume.
The server displays messages that are created from the background process either in the activity log or the server console, depending on where messages are logged.
delete volume stgvol.1
Command | Description |
---|---|
CANCEL PROCESS | Cancels a background server process. |
DEFINE VOLUME | Assigns a volume to be used for storage within a specified storage pool. |
MOVE DATA | Moves data from a specified storage pool volume to another storage pool volume. |
MOVE DRMEDIA | Moves DRM media on-site and off-site. |
QUERY CONTENT | Displays information about files in a storage pool volume. |
QUERY DRMEDIA | Displays information about disaster recovery volumes. |
QUERY PROCESS | Displays information about background processes. |
QUERY VOLUME | Displays information about storage pool volumes. |
UPDATE VOLUME | Updates the attributes of storage pool volumes. |