Cannot delete an MSDP disk pool
If you cannot delete a disk pool that you believe contains no valid backup images, the following information may help you troubleshoot the problem.
Under some circumstances, the fragments that compose an expired backup image may remain on disk even though the images have expired. For example, if the storage server crashes, normal clean-up processes may not run. In those circumstances, you cannot delete a disk pool because image fragment records still exist. The error message may be similar to the following:
DSM has found that one or more volumes in the disk pool diskpoolname has image fragments.
To delete the disk pool, you must first delete the image fragments. The nbdelete command deletes expired image fragments from disk volumes.
To delete the fragments of expired images
- Run the following command on the master server:
UNIX: /usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -force
Windows: install_path\NetBackup\bin\admincmd\nbdelete -allvolumes -force
The -allvolumes option deletes expired image fragments from all volumes that contain them.
The -force option removes the database entries of the image fragments even if fragment deletion fails.
Incomplete storage lifecycle policy duplication jobs may prevent disk pool deletion. You can determine if incomplete jobs exist and then cancel them.
To cancel storage lifecycle policy duplication jobs
- Determine if incomplete SLP duplication jobs exist by running the following command on the master server:
UNIX: /usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -image_incomplete
Windows: install_path\NetBackup\bin\admincmd\nbstlutil stlilist -image_incomplete
- Cancel the incomplete jobs by running the following command for each backup ID returned by the previous command (xxxxx represents the backup ID):
UNIX: /usr/openv/netbackup/bin/admincmd/nbstlutil cancel -backupid xxxxx
Windows: install_path\NetBackup\bin\admincmd\nbstlutil cancel -backupid xxxxx