More specifically:

Set up a number of admin command schedules to accomplish this starting at
sufficient intervals to allow process completion.  That's the hard part.

Time    Scheduled operation
----------------------------------------------------------------------------
--------------------------
--------------------------
06:00   backup stg diskpool copypool maxprocess=n
06:00   backup stg diskpool copypool maxprocess=n
08:00   backup stg tapepool copypool maxprocess=n/2
09:00   update stg diskpool highmig=0 lowmig=0 migproc=n
11:00   update stg diskpool highmig=90 lowmig=70
11:30   backup db type=full devclass=yourdevclass

Where n is the number of drives you have.  You may want to set this to one,
the default, to only create a single copypool tape per day rather than
multiple tapes.  Notice that setting the migration thresholds back to 90 and
70 will not stop the migration.

The schedule times will be variable based on your environment.  If you note
how long your migrations are running now you should be able to set this up
fairly accurately.

Now, if you really want to get sexy you can write a script to do all of
this.  Your script will watch for completion of each step and then start the
next step.  In the case of backup stg it's easy: you can attach a wait=yes.
For migration it's harder.  You need to check if a migration process is
still running.  I believe there is a script in the example scripts that does
this for you.

Perhaps someone will mention STORServer Manager too.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: lipp AT storsol DOT com or lipp AT storserver DOT com
www.storsol.com
www.storserver.com