When processing the named device class, it was discovered that it was not configured properly. A device class can be referenced by storage pools of type RECLAMATIONTYPE=THRESHOLD or RECLAMATIONTYPE=SNAPLOCK. For storage pools of type RECLAMATIONTYPE=SNAPLOCK, all directories specified in the device class must be on NetApp SnapLock WORM Volumes.
If the Tivoli® Storage Manager server is starting, the server continues; however, attempts made to read from or write to that storage pool will fail until the storage pools referencing the device class and the device class are properly configured.
Check the activity log for ANR8502, ANR8383E, and ANR8388E messages. If these messages have been issued, follow the instructions in the User Response section of those messages to resolve the issues.
If the problem is not resolved, use the QUERY DEVCLASS command with the FORMAT=DETAILED option to obtain the specified directories for the device class. Verify that each directory is available to the Tivoli Storage Manager server, e.g., on-line, in read-write mode, configured properly, etc.
If the problem is not resolved, for a device class used by RECLAMATIONTYPE=SNAPLOCK storage pools, check that each directory is a NetApp SnapLock WORM Volume. If not, use the UPDATE DEVCLASS command to update the device class directory structure appropriately.
If the problem is not resolved, use the QUERY STGPOOL command with the FORMAT=DETAILED option to determine which storage pools are pointing to the device class. Verify that storage pools of either type RECLAMATIONTYPE=THRESHOLD or RECLAMATIONTYPE=SNAPLOCK are using the device class. If storage pools of both types are using the device class, modify the storage pool definitions such that only one type of storage pool uses the device class. If you wish to have storage pools of both reclamation types pointing to the same directory structure, you may create two device classes with the same directory structure, and have storage pools of one reclamation type use one device class while storage pools of the other reclamation type uses the other device class.
If you have made updates to the storage pools and device classes and the problem is not resolved, you may need to restart the Tivoli Storage Manager server.