To be honest:

I did not have the time to read all the stuff in the ADSM
manuals when I had to take this over from a colleague who
left. In today's world, I guess that many of us lack the
time to read thoroughly through the manuals. And, to be
honest, some questions here on the list seem to be at a
very low level. Since we're here to help each another, I
would like to point out some more items where to look at:

   Device Class definitions as already stated:
   Have a look at the command 'DEFINE DEVCLASS'
   Used to define a media type for sequential access
   media - of which tape is one possible.
   Then a Storage Pool definition using this device
   class is required. Have a look at the command 'DEFINE
   STGPOOL'. More than one STGPOOL may use the same
   DEVCLASS - for example the Storage Pools named (lets say)
   'ARCHTAPE' and 'BACKTAPE' may be based on DEVCLASS
   named '3490CART' (You needn't use these names at Your
   site, it's just to give the kid a name).
   The reference manual (well, at least the VM manuals for
   V2.1) does not point from the command DEFINE DEVCLASS to
   the command DEFINE STGPOOL which makes things not much
   easier - although the admin guide and the admin reference
   provide a lot of information.
   The Disk Storage Pool(s) You have defined point(s) to the
   Next Storage Pool(s) You have defined and a migration
   threshold of less than 100% is defined.
   It may be desirable to have the size of the used disk
   pools holding a good amount or more than 100% of the
   average daily load and create administrative schedules
   to start migration from disk to tape after the backups
   and/or archives of the clients have finished.
   Otherwise a good performance degradation is to be expected
   (since the ADSM Database needs to be updated for both,
   incoming data and relocation of already stored data,
   plus the additional I/O on Your storage disks and tapes).

Well, these three points are just the absolute basics and
I am far away from suggesting that this is all You need. But
these points should bring You on track.

In general, either a failrly good amount of time or a course
is strongly recommended to administrate an ADSM server. I was
keen enough to start with almost nothing than a little spare
time and some interest in this area - and I'm still far away
from being an ADSM expert: Although the product provides many
goodies, it is not a 'plug and play' product; but the more
knowledge You have, the more the product can do for You and
Your company. And maybe, one day, You will find someone to
need the help You then can give.

Best regards

Andreas Peikert, Systems Programmer
   aMaDEUS Data Processing GmbH
   P.O. Box,   D-85424 Erding,   Germany
   Fon: +49 (0)8122 43-5805
   Fax: +49 (0)8122 43-3260
   email: apeikert AT amadeus DOT net