Murray,
        I think the DRMDBBACKUPEXPIREDAYS parameter is only relevant if you're
using the DRM feature.  To expire DB backups, you'll need to issue the
DELETE VOLHIST command... if you wanted to keep 7 days worth of DB
backups...

DELETE VOLHIST TODATE=TODAY-7 TYPE=DBBACKUP

Unfortunately, ADSM doesn't let you issue admin commands in a macro that
will wait on each other.. this is supposed to be fixed in Version 3 with
a parameter that will tell ADSM to wait for the prior command to finish
before processing the next command.  Until then you'll either need to
write a script to check for when the database backup finishes or, if you
know how long your DB backup runs, set up a second admin schedule that
will backup your volhist and devconfig files.

Tim Pittson
tpittson AT himail.hcc DOT com




>From:  Nicholas, Murray, Haltek/AU[SMTP:MurrayNi AT HALTEK.COM DOT AU]
>Sent:  Monday, July 14, 1997 2:12 AM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Scheduling database backups
>
>I have a little problem with my DR backups (on Windows NT).  After backing
>up all the system data I want to create a database backup then backup my
>volhistory and devconfig.
>This should be a relatively automatic process requiring an operator to
>specify the name of the next database backup tape and mount the
>corresponding 3.5inch floppy disk.  I had hoped to run a macro like this:
>        backup db type=full devclass=dltclass volume=%1 scratch=no
>        commit
>        backup devconfig f=a:\devconfg.out
>        commit
>        backup volhistory f=a:\volhist.out
>
>The problem is that the backup db command starts a background process to
>run the database backup at some future time and, even with commit
>statements in the macro, the backup devconfig and backup volhistory
>commands are well and truly finished before the backup db has even asked
>for a tape mount.  Is there a mechanism to monitor (as opposed to simply
>querying) a process?
>The other problem with the plan is that I am not sure how to make the
>database backup tapes writable once they are returned from offsite storage.
> I have reset the DRMDBBACKUPEXPIREDAYS down to 7 now but ADSM still gives
>me messages:
>        ANR1490W Volume %1 already in use - skipped.
>        ANR4583E Database backup terminated - output media full and scratch
>media
>could not be mounted.
>
>I am not running the DRM component.
>
>Murray Nicholas
>System Specialist
>HALTEK PTY LTD
>