You wouldn't normally use a dumbdb command, but rather a backup db command
from a running ADSM server.  The database backup is used during a restore
using the dsmserv restoredb command.  The backup contains all information
about the ADSM environment including policy domains, stg pools, etc., as
well as all information about where client data is kept.

Normally, a database backup is a scheduled operation occurring everyday
after the heaviest database processing occurs.

We recommend the following steps for backup end of day processing:

After all the clients have backed up their data to the server...

1. backup stg diskpool copypool -- make a copy of client data for offsite
storage in your copy pool
2. backup stg tapepool copypool -- in case some data migrated during the
client backups.
3. update stg diskpool highmig=0 lowmig=0 -- this migrates the data from
diskpool to your tapepool
3a. update stg diskpool highmig=90 lowmig=70 -- reset the migration
thresholds
4. backup db type=full devclass=devclassname scratch=yes -- this backs up
the database
5. remove the database backup and copy storage pool volumes to the offsite

Some folks also do file expiration processing before the database backup,
or perhaps immediately after it.

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