The normal way to do this is to migrate the disk pools to tape on a daily
basis, after the client backups have completed.  To do this, create an
admin schedule: update stg diskpool highmig=0 lowmig=0.

Actually, as a daily task order, use the following:

1. backup stg diskpool copypool (this is for the off-site stuff)
2. backup stg tapepool copypool (in case some data migrated during the
client backups.  Oftentimes this command will not move any data which is
normal)
3. Migrate diskpool to tapepool.  This is done by dropping the thresholds
on the diskpool to 0.
4. backup the ADSM database
5. backup the volumehistory and device configuration files.  You want to
have these off-site too as your life will be easier in the event of
 disaster.
6. checkout the tapes used during the backup stg and backup db operations
above.
7. Get these tapes the heck out of the computer room.

Ideally, the first five things are synchronized with one starting
immediately after the previous completes.  You can use scripts to do this,
or purchase a tool.  Those interested in a tool should contact me off-line.

Hope this clarifies and helps.  Everybody doing "good" ADSM day-to-day
management is performing these tasks.  If you are not, you run the risk of
not having a recoverable server environment and this is not good.  Remember
our motto:  Backup in leisure, restore in panic!

Thanks,

Kelly Lipp
Storage Solutions Specialists, Inc.
lipp AT storsol DOT com
www.storsol.com
(719) 531-5926