Do you buffer your backups to a diskpool ?  If so perform your copy
     storage pool before you migrate to tape, then all the required data
     will still be on disk.

     Our MVS ADSM servers run to 3490 tapes but our AIX ADSM servers run
     with 3590's.  Some of these 3590's will have 100,000+ files on them...
     talk about potential for long waits by multiple processes wanting the
     same tape.

     All I can say about the copy storage pool is it runs an incremental
     against the primary storage pool, so if you buffer fresh backups into
     disk pools the only tapes mounted in a copy storage pool operation
     should be output tapes. (provided you ensure the copy runs daily, that
     you run the copy before performing a migration of the disk pool to a
     tape pool, and that your disk pool didn't fill and  start auto
     migrating sometime during your normal backup window...)

     later,
           Dwight



______________________________ Reply Separator _________________________________
Subject: Multiple backup processes waiting for the same input tape.
Author:  lverelle (lverelle AT JANBE.JNJ DOT COM) at unix,mime
Date:    6/3/98 3:03 AM


     Hello list,

     We daily run a backup of the primary storagepools in order to bring
     the copy storagepools offsite.
     As we are using only 3490 (2.4 GB) cartridges, this is a time
     consuming process (we have to backup +/- 50 GB).

     In order to speed up processing, we run multiple backup processes of
     the same storagepool by using the maxprocess=2 parameter.

     This indeed speeds up things, but it can still be improved as we
     noticed that the processes often are waiting for the same input tape.

     Is this normal?  How is the backup being organized ?  By input
     cartridge? By node ?  By Filespace?

     Best regards,  Luc.

     Luc Verellen
     Janssen Pharmaceutica
     Beerse / Belgium
     lverelle AT janbe.jnj DOT com