Steve...

Well, not necessarily.  If DBBACKUPEXPIREDAYS is set to N (say 5) and DRM is 
being
used to move drmedia, then db backup vols get deleted from the volume history 
when
they are three days old and off-site.  The drmedia gets moved from vault to
vaultretrieve on its way to being returned onsite for re-use.  However, if you 
run a
'del volh t=dbb todate=-M', (M=3, say, and M<N) then the N-M (2) oldest db 
backup
drmedia that are off-site in vault status disappear.  Since you are using drm 
to get
them back on-site and drm no longer knows about them, they will remain off-site
forever, or at least until you do a (yearly or quarterly) audit of your off-site
volumes (reconciling with ADSM's notion of what is off-site, i.e. vault status
drmedia).  Then you will find two tape offsite that are not being used by ADSM 
and
you can re-use them.  Of course, if you record manually which volumes are going 
to
be deleted by the del volhist command then you could also manually have them
returned on-site.

I would normally do a 'del volh t=all todate=-30' to keep the volhist a 
reasonable
size and there is no problem with this conflicting with a dbbackupexpiredays 
less
than 30 (and who sets it higher than 7?).  You could also do a 'del volh t=dbb
todate=-10' without worries, but in principle it should be doing nothing.

Cheers...
Bruce

steveh AT WESLEY.COM DOT AU wrote:

> Bruce,
>
> Are you saying that we shouldn't run del volhist t=dbb if we are using DRM?
>
> Steve.
>

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