Hello,

You say existing DB volume.  Was that volume previously used for a DB backup?
Does ADSM still remember that (q volhist t=dbb, search for that volume)?  If so,
ADSM will not re-use that volume.  Every DB backup must be on an un-used tape
i.e. you can't stack multiple backups on one tape, even incremental DB backups).

To re-use old tapes, delete them from the volume history:
del volh t=dbb todate=<date> totime=<time>
where data and time are after the date/time of the DB backup you want to
delete.  Note that you will delete all DB backups older than that date.  Note
that all this really does is tell ADSM to forget about the backup, in both its
database (so it will now use the tape as a new empty tape) and in the volume
history file (so that, unless you recorded the volume serial number elsewhere,
you won't know that the tape was a DB backup); the tape still has the backup on
it.

Note also that you don't want to mix 'dev vol t=dbb' with dbbackupexpiredays
parameter in the DRM module since you can cause ADSM to lose track of empty
tapes.


Cheers...
Bruce

"Ahn, Hyun" wrote:

> My ADSM server is ADSM V3.1.2.1 on Solaris 2.6.
>
> Whenever I backup database using "backup db" with the following parameters:
>
>     backup db devclass=<dev class name> vol=<vol name> search=yes
>
> existing DB volume(DLT7000 tape with 35G capacity) is not used even though
> there are free space on the tape, instead New volume is allocated to library
> and being
> used.  (Same for incremental and full backup)
> The number of incremental backup is set to 32.
>
> Any comments on this problem?
>
> Thanks,
>
> Hyun

--
Bruce Elrick, Ph.D.
Bruce Elrick, Ph.D.
mailto:belrick AT home DOT com
http://members.home.net/belrick/