Configuring the HSM Interface

A HSM is common abreviation for a hierarchical configuration manager. What this is in practice is a software frount end that presents a file system layer in front of the tape drives and a robotic media changer.

HSM's are used to store large amounts of data, and in 2005 HSM system can be expected to store a Peta Byte more can be expected from HSM larger services.

Configuring D-Cache for the HSM Interface

This section is yet to be replicated so may contain bugs!

In the ssh admin interface or alternatively in the setup file enter the following lines. The first 4 lines setup a stroage grouping, while the last two commands specify the location of PNFS which is host name specific and also the location of your mass storage migration script.

queue define class osm lhcb:tape -pending=0 -total=0 -expire=0
queue define class osm dteam:tape -pending=0 -total=0 -expire=0
queue define class osm atlas:tape -pending=0 -total=0 -expire=0
queue define class osm cms:tape -pending=0 -total=0 -expire=0

hsm set osm -pnfs=/pnfs/gridpp.rl.ac.uk/
hsm set osm -command=/root/pnfs2ads2.sh

and remove lfs=precious from the pool's line in "/opt/d-cache/config/`hostname -s`.poollist"