I whipped this up because I run into so many people who want to figure
it out on their own, but really are just lost in the slew of new
concepts.  Here is a basic list of things to do when setting up your tsm
server the first time.  Suggestions and corrections are welcome.

-Josh
---------------------------------------------------
---------------------------------------------------
Basic In-Order TSM Server Setup Checklist
Basic In-Order TSM Server Setup Checklist
-----------------------------------------
Physical Installation:
Physical Installation:
   Install physical devices
   Power on system
   Install o/s maintenance
   Install tsm server and drivers
   Define devices to the O/S
      349x, 357x, 358x and 359x use Atape/IBMTAPE/lmcpd
      all others use TSM drivers

Make a larger database and log:
   define dbvolume        (make space)
   define dbcopy          (mirror elsewhere)
   extend db              (tell tsm to use the new space)
   define logv            (make space)
   define logc            (mirror elsewhere)
   extend log             (tell tsm to use the new space)
   define spacetrigger    (auto-grow db and log)
   define dbbackuptrigger (only if SET LOGMODE ROLLFORWARD)

Ensure proper licensing:
   register license       (see the server/bin directory)

Storage setup inside TSM:
   define library          (top level of tape storage)
   define devclass         (points to a library)
   define drive            (points to a library)
   define stg              (points to a device class)
   define vol              (points to a devclass and storage pool)
   label libvol            (prepares a tape for TSM use)
   checkin libv            (makes tape show up in Q LIBVOL)

For Policy/Node Information:
   define domain           (top level of policy information)
   define policyset        (contained within a policy domain)
   define mgmtclass        (contained within policyset)
   define copygroup T=BACK (contained within a management class)
   define copygroup T=ARCH (contained within a management class)
   activate policy         (only one policyset active per domain)
   register node           (belongs to a policy domain)

Typical Storage Pool Hierarchy:
   Copygroup "destination" is disk pool
   Disk pool "NEXT" is tape pool
   An extra tape pool of type "COPYPOOL"

Other Important Things to Look Into:
   Administrator's Guide, Working With Network of TSM Servers
      Virtual Volumes
      Library Sharing
   Administrator's Guide, Chapter 1: Introduction
      Overview of storage hierarchy and TSM concepts
   Administrator's Guide, Protecting The Server
      Protection and recovery of the system
   Administrator's Guide, Disaster Recovery Manager
      Integrated, licensed tool for server protection
   DEFINE SCHED T=C
      client backup schedules
   DEFINE SCHED T=A
      server administrative schedules (don't overlap these)
         BACKUP STG (sync up copy pool)
         UPDATE STG RECLAIM=50 (reclaim free space from tapes)
         UPDATE STG RECLAIM=100 (turn off reclaimation)
         UPDATE STG HI=0 LO=0  (migrate the disk pool to tape)
         UPDATE STG HI=90 LO=70  (migrate only during overflow)
         BACKUP DB (TSM database is critical to server function)

In all procedures WATCH FOR ERRORS.

If you have questions, see http://www.tivoli.com for Documentation.
   TSM Administrator's Guide is procedural information
   TSM Administrator's Reference is command syntax
   TSM Messages Guide is decyphering for ANR/ANS messages

If you can't figure it out
   http://www.adsm.org - ADSM User's Group (searchable)
   http://www.tivoli.com - Online Knowledge Base
   IBM support: 800-237-5511 x 8

------------------------------------------------------------------------------
This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure.  If you have received it by mistake please 
let us know by reply and then delete it from your system; you should not copy 
the message or disclose its contents to anyone.
This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure.  If you have received it by mistake please 
let us know by reply and then delete it from your system; you should not copy 
the message or disclose its contents to anyone.