Steps to Dump the ADSM Server Database to Tape & Capture the Server's State
===========================================================================

Initiate a ADSM admin session.  As root on ar0084e0,
  dsmadmc -id=jasper -password=new4now

Use
  q sess
to insure there should be no active sessions.
  q proc
to insure there should be no active processes running.

  q stg
You'll see some stuff still in the BACKUPPOOL pool, and the High Mig Pct
and Low Mig Pct to be non-zero.

  - To see how much each tape is used,
        q v 000*

  - move rest of disk data to tape (make hi/low thresh on backuppool 0)
        update stg backuppool low=0
        update stg backuppool high=0
    This forces it all to be flushed off to tape.
    You may have to reissue these two commands to get *all* the data
    off of disk.

  - In order to give Southbury as clean of an ADSM server as possible,
    we'll purge the raw, logical volumes that comprise the backuppool.
    To see what volumes are defined to the backuppool, type
        q vol stg=backuppool
    You'll see things like /dev/rstg1-5.  We want to delete those volumes.
        delete vol /dev/rstg1
        delete vol /dev/rstg2
        delete vol /dev/rstg3
        delete vol /dev/rstg4
        delete vol /dev/rstg5
    ADSM won't let you delete these volumes 'till all the data is off them.

  - Update all non-scratch tape volumes to read-only, else you'll get funky
    errors in Southbury when the ADSM server loads a tape but it has the
    write-protect tabs set to R/O.
         update vol 00* acc=reado
    You can
         q v 00* f=d
    to see the read/only on all the tape volumes.

  - To show the status of all 15 tapes in the 7337 tape library.
         q libv
    The last one(s) should show Status=Scratch & null in the "Owner" and
    "Last Use" fields.  The first "Scratch" volume is the one you'll use
    in the <target> of this next command.

  - To backup the ADSM database
         backup db dev=tape type=full vol=<target> wait=yes
    By saying "wait=yes", you won't get the adsm> prompt back 'till this
    is done.  Otherwise, you can do a bunch of "q proc" commands to see
    if it's done yet or not.  This takes less than 10 minutes.

  - As an additional check that the above backup db command worked,
    (you can never be too careful, especially since you're dealing with
    a week's worth of work),
         q volh type=dbbackup
    You should see "Volume Type:" = BACKUPFULL
    for the "Volume Name:" 000014 <or whatever you had as <target> above>

  - To shut the ADSM server down,
         halt quiesce
    Do   ps -ef | grep dsmserv to insure it really shut down.

  - Save files to its own directory,
         cd /usr/tivoli/tsm/server
         mkdir nnbatchxxx-yyy, where nn = batch number
                                    xxx = Beginning tape label
                                    yyy = Ending tape label
     eg  mkdir 04batch000-014
     or  mkdir 05batch020-034
    Then
         cd    04batch000-014
         cp -p ../bin/dsmserv.devconv .
         cp -p ../bin/dsmserv.dsk .
         cp -p ../bin/dsmserv.opt .
         cp -p ../bin/volume.history .

  - Backup to adsmsrv1
         dsmc incr /usr/tivoli/tsm/server/nnbatchxxx-yyy/* -server=adsmsrv1

  - Copy all four files to Southbury.


To label a new batch of tapes:
       Load tapes in tape library.
       cd /usr/tivoli/tsm/server/bin
       vi vol.labels     and put each label in its own line
       ./dsmlabel -library=/dev/lb0 -drive=/dev/rmt0,116 -overwrite -search <vol.labels

Initialize source system for new backups:
    cd /usr/tivoli/tsm/server/bin     <--- Critical to be in this dir else cmds will fail.
    rm dsmserv.dsk
    rm log.dsm db.dsm
    dsmfmt -m -db  db.dsm 16 
    dsmfmt -m -log log.dsm 8
    dsmserv format 1 log.dsm 1 db.dsm
  - Bring up the ADSM server
      dsmserv
    You'll see that it doesn't know anything about anything, e.g.
      q occ
      q node
      q admin

    Register an admin id
      register admin gleddie new4now contact='707920 Gleddie, Darrel'
      grant auth gleddie cl=sy

    Define an ADSM DB volume using the raw logical volume, db1 that's already out there.
      def dbv /dev/rdb1
    You'll see with a 
      q dbv 
    command, that there's a small 
    /usr/tivoli/tsm/server/bin/db.dsm database volume out there that we don't
    need/want.  To delete it,
      del dbv /usr/tivoli/tsm/server/bin/db.dsm

    To mirror that DB volume we just created,
      def dbc /dev/rdb1 /dev/rdb1m

    With a q db command, you'll see the "Assigned Capacity" to be only 16MB,
    and the "Maximum Extension" to be 4,076.  To get ADSM to use the full 
    amount available,
      extend db 4076

    Do a similar thing with the ADSM log.
      define logv /dev/rlog1
      q logv
      del logv /usr/tivoli/tsm/server/bin/log.dsm
      extend log 100   (not the 4084 that's available, at least not now, 'cause
                        it'll take too long)

    To rename the server to this batch number, e.g. batch 5,
      set servername batch06

    To shut it down & start it in the background,
      halt quiesce
      cd /usr/tivoli/tsm/server/bin
      at now
        /usr/tivoli/tsm/server/bin/dsmserv quiet 1>/dev/null 2>&1

    Now reinitialize your ADSM admin session,
      cd /usr/tivoli/tsm/server/bin
      dsmadmc -id=gleddie -passw=new4now -itemcommit
      macro setup.macro
    Which defines all the other admins, nodes, the 7337 tape library
    (see q library to see the IBM7337 library), tape drive definitions,
    the 5 /dev/rstg1-5 volumes for the BACKUPPOOL storage pool, etc.
    Now we have good stuff,
      q admin
      q stg
      q v stg=backuppool  
    Now you can extend the log volume, which takes a few minutes
      extend log 1900

  - At this point, you can tell whoever to restart the Image-to-ADSM
    processes.  We don't have to wait for this next step of checking in
    all the scratch tapes, before you kick off the backups.  The reason
    is the backups will go to the 20 GB disk pool and it will be a few
    hours before ADSM kicks off a migrate-to-tape process.  If you
    wanted to, you could even take this opportunity to label the next
    batch of scratch tapes.

  - To checkin the new DLT tapes, make damn sure you've got the new batch of
    tapes loaded in the 7337 library, then
      checkin libv ibm7337 search=yes status=scr
    You can
      q pro
    and
      q libv
    to see this progress.  This takes about 20-30 minutes to finish.