You can delete empty storage pool volumes or volumes that
contain data from primary storage pools, copy storage pools, or active-data
pools. You can also delete the client files that those volumes contain.
About this task
If files that are not cached are deleted from a primary
storage pool volume, any copies of these files in copy storage pools
and active-data pools are deleted.
Files in a copy storage pool
or an active-data pool are never deleted unless the following conditions
apply:
- Data retention is off, or the files have met their retention criterion.
- The volume that contains the copy file is deleted by using the DISCARDDATA=YES option.
- A read error is detected by using the AUDIT VOLUME command
with the FIX=YES option for a copy storage pool volume
or an active-data pool volume.
- The primary file is deleted due to policy-based file expiration
or file space deletion, or because the primary storage pool volume
is deleted.
You cannot delete a CENTERA volume if the data in the
volume was stored by using a server with retention protection enabled
and if the data is not expired.
Restrictions: - To delete many volumes, delete the volumes one at a time. If you
concurrently delete many volumes, server performance can be affected.
- When you issue the AUDIT VOLUME command, only
the storage pool volume is audited. When you issue the AUDIT
LIBVOLUME command, the entire physical tape volume is audited.
For example, assume that the storage pool volume and the tape volume
both contain a damaged file which is named X that is on volume Y.
If the X file is deleted from the storage pool, and you issue the AUDIT
VOLUME command on volume Y, the command would not detect
the damaged data. However, if you issue the AUDIT LIBVOLUME command,
it detects the damaged data on volume Y.
| Task |
Required Privilege Class |
|---|
| Delete volumes from any storage pool |
System or unrestricted storage |
| Delete volumes from storage pools
over which the volumes have authority |
Restricted storage |