When you see the "expiring" message, it does NOT necessarily mean that ADSM
is deleting anything from it's data base.

It just means ADSM has recognized that
1) This file was on the client the previous time the backup ran, but
2) Is not on the client now.

This causes several things to happen.
1) The last backup for the file is marked "inactive" instead of "active"


2) ADSM starts managing the backups for the file based on the "VERDELETED"
and "RETONLY" parameters in your backup copy groups.  These parameters allow
policies to be set for deleted files that are different from active files.

For example, if you have VERDELETED=0, it would cause the backups for this
file to be expired the next time inventory expiration is run.

If you have VERDELETED=1 RETONLY=30, then the last backup for this file will
be expired 30 days from the time you see the "expiring" message.

Hope this helps.

***************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
***************************************************************






> -----Original Message-----
> From: Joel Fuhrman [SMTP:joelf AT CAC.WASHINGTON DOT EDU]
> Sent: Wednesday, March 03, 1999 12:48 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: File Expiration
>
> The expired file remains in the ADSM database until an 'expire inventroy'
> command is run.  The expiration interval (EXPInterval) is set in
> the dsmserv.opt file.  I have set mine to 0 and use an administrative
> schedule to issue the command.  That way I control the start time.
>
> On Wed, 3 Mar 1999, Cohn, Grant wrote:
>
> > Greetings all
> >
> > Can anyone tell me what is actually happening to a file when it is
> expired?
> > Is it being marked as inactive or is it actually being deleted from the
> ADSM
> > database?
> >
> > I see the following in the dsmsched.log file :
> >
> > 03/02/1999 21:25:39 Expiring-->                  0
> > I:\Common\Utilops\fsa11.tmp  Sent
> > 03/02/1999 21:25:39 Expiring-->                  0
> > I:\Common\Utilops\fsa7.tmp  Sent
> > 03/02/1999 21:25:39 Expiring-->                  0
> > I:\Common\Utilops\fsa8.tmp  Sent
> >
> >
> > We are running ADSM NT Client V2.1
> > and ADSM Server 2.1.5.15
> >
> > Many thanks
> >
> >
> > Grant Cohn
> >
> > Shell & BP South African Petroleum Refineries
> > Durban, South Africa.
> > Tel     :   (+27)  (0)31 - 480 1610
> > Cell    :   (+27)  (0)83 254 4012
> > e-mail :   grant .cohn AT sapref DOT com
> >