Verify that the disk is ready to decommission prior to removing the configuration from the environment.
- Backup policies are no longer using the Disk Storage Unit, including Storage Unit Groups and Storage Lifecycle Policies.
- Disk Storage Unit still exists within the environment, but is empty or has images that can be expired. Do not remove the disk storage unit until the entire process is complete.
- Inspection of the disk storage unit path ("ls -l" or "dir") shows the same information as what is currently contained in the catalog or Images On Media report.
- For disk pools, make sure that all volumes within the pool have been checked in the reports and catalog to ensure they are empty or to identify images ready to expire
First, to check for any incomplete SLP backup, duplications, or imports - which have yet to be written to the soon to be deleted disk pool:
This output will highlight the Storage Lifecycle Policy with incomplete images. If zero images are returned from the above command you may proceed with the step 'Finding the Images on Disk' below, Use the command below to show the SLP configurations to determine which storage unit is using the disk pool that needs to be removed from the configuration.
To cancel images from completing their SLP duplications (only if the customer specifies the image copies are not needed), and if the SLP has an destination/operation step configured to use the diskpool:
./netbackup/bin/admincmd/nbstlutil cancel -lifecycle <lifecycle_name>
./netbackup/bin/admincmd/bpimmedia -stype <Storage Server Type> -dp <disk pool name>
./netbackup/bin/admincmd/bpexpdate -backupid client_1234567890 -copy 1 -d 0
./netbackup/bin/admincmd/bpexpdate -stype %servertype% -dp %diskpoolname%
./netbackup/bin/admincmd/bpimage -cleanup -allclients
If nbdelete is failing due to images not found on the disk (status code 83), you can follow with the below command:
./netbackup/bin/admincmd/nbdelete -allvolumes -force
Be sure when runnning nbdelete with the -force option that all disks and media servers that are valid are up and running. If nbdelete is unable to contact the media server, or if the media server was contacted but the disk path was not available, the -force option will proceed with removing images in a "to be deleted" state from the EMM tables. After the images are removed from the EMM tables, there will be no further attempts to remove the images from disk. If a disk or media server was temporarily offline while this command was run, it could leave orphaned images on the disk.
It is possible for the catalog record to be deleted before the nbdelete command has cleared the EMM Images, ImageFragment and ImageCopy tables in the database. Re-check the reports (Disk Reports > Images On Disk) to ensure they now return no data for that Disk Pool. Failure to successfully decommission a disk storage unit can lead to Image Cleanup errors.
bpstudel -label <storage_unit_name>
If applicable, remove the disk pool(s).*
nbdevconfig -deletedp -dp <disk-pool-name> -stype <server-type>
If applicable, remove credentials for the Storage Server from the media server(s). *
* For OpenStorageTechnology disk types (OST)
- for Advanced Disk (AdvancedDisk) there are no credentials, so the tpconfig step below is not needed, but you must remove the storage server, storage units, and diskpool.
(From the media server)
./volmgr/bin/tpconfig -delete -storage_server -stype <server-type> -sts_user_id <user id>
*If -sts_user_id is not immediately known, check "tpconfig -dsh" for this value for the correct Storage Server. Note, this step must be performed prior to the media server being decommissioned.
nbdevconfig -deletests -storage_server <storage-server-name> -stype <server-type>