•Verify that a Core Server and Migration Purge Server have been configured for each s torage
subsystem.
•Verify that each storage subsystem is accessible by using lsjunctions and ensuring that there is at
least one junction to the Root fileset of each subsystem. (The root fi leset for a given subsystem
can be found in the specific configuration for the subsystem’s Core Server)
Servers
•Verify that all required HPSS servers are configured and running.
•Verify that all servers are configured with the intended level of logging, whether using their
server specific policies or the default policy. Also, verify that all Core Server and Mover log
policies have the DEBUG flag turned on to aid in the diagnostics of any future problems.
Devices and Drives
•Verify that all devices/drives are configured and each is assigned to an appropriate PVR/Mover.
•For tape devices, verify that the “Locate Support” option is enabled if supported.
•For tape devices, verify that the “NO-DELAY” option is enabled if supported by the device.
•For disk devices, verify that the “Bytes on Device” and “Starting Offset” values are correct.
•Verify that all configured drives are unlocked.
Storage Classes
•Verify that all storage classes are defined and each has sufficient free storage space.
•Verify that each storage class that will be migrated and purged is configured with the appropr iate
migration and purge policy.
•Verify that no storage class at the lowest level in a hierarchy is configured with a migration or
purge policy.
•To support repack and recover of tape volumes, verify that the stripe width of each tape stora ge
class is less than half of the number of available drives of the appropriate dri ve type.
Storage Hierarchies
•Verify that all storage hierarchies are defined.
Classes of Service (COS)
•Verify that all classes of service are defined.
•Verify that each COS is associated with the appropriate storage hierarchy.
•Verify that the COS is configured to use the characteristics of the hierar chy and the underlying
storage classes. In addition, verify that the classes of service have the correct Minimu m File Size
and Maximum File Size values. If these sizes overlap, the file placement may be indeterminate
when the user creates a file using the size hints. For classes of services which are not to be used as
part of standard file placement, set their Force Selection flag to ON so that they will only be
HPSS Management Guide November 2009
Release 7.3 (Revision 1.0) 18