Resolving RELABEL operation errors

Edit online

If you run a RELABEL operation when all drives are busy, the target volume cannot be relabeled because it cannot obtain a drive. Busy drives are drives that are in use for regular operations such as backup, restore, migration, and reclamation.

When a RELABEL error occurs, the following example information is produced:
ANR0984I Process 25 for RELABEL started in the BACKGROUND at 22:10:36.
ANR8799I RELABEL: Operation for library IBMVTL started as process 25.
ANR1341I Scratch volume 007403 has been deleted from storage pool VTLPOOL.
ANR8847E No LTO-type drives are currently available in library IBMVTL.
ANR8801I LABEL LIBVOLUME process 25 for library IBMVTL completed; 0 volume(s)
labeled, 0 volume(s) checked-in.
ANR0985I Process 25 for RELABEL running in the BACKGROUND completed with
completion state SUCCESS at 22:10:36.
To resolve a RELABEL error, complete the following steps:
  1. Ensure that one drive is kept available for the RELABEL operation and relabel a target volume.
  2. Update the device classes that point to the library. Update the device classes with a MOUNTLIMIT parameter value that is less than the total number of drives available.

    If a RELABEL operation cannot obtain a drive or fails to relabel a volume, IBM Storage Protect tries to relabel the volume during each future RELABEL operation.

If the RELABEL operation fails, issue the LABEL LIBVOLUME command for all volumes that are checked out of IBM Storage Protect but that are not relabeled. Include the following parameters with the LABEL LIBVOLUME command:
SEARCH=YES LABELSOURCE=BARCODE OVERWRITE=YES CHECKIN=SCRATCH