Well that just bites!

I just spoke with IBM support and the v3.1.2.0 version for AIX had a bug
with the expire inventory as well.  We had to upgrade. Now this pops up.  So
what choice do we have in the matter.

Let your library grow until they find a fix, or go back to a version that
has other bugs in it?

IBM --- THIS DOES NOT MAKE ME HAPPY.  Especially when I bill my users on a
consumption basis and the software can't keep track of what should be
deleted and what not.

I hope that APAR IX85298 has top priority!!!!!!

Anthony Jones
ADSM Administration
Koch Industries, Inc.
316-828-2432

> -----Original Message-----
> From: Paul Zarnowski [SMTP:vkm AT CORNELLC.CIT.CORNELL DOT EDU]
> Sent: Thursday, January 14, 1999 10:03 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: verexist & verdelete information ignored on 3.1.2.1
>
> Gareth,
>
> Thank you for posting this e-mail.  I did some checking, and it looks like
> we also have the same problem.  We are running 3.1.2.1 on AIX.  This
> explains why our database growth has accelerated since upgrading to
> 3.1.2.1.
>
> I'd advise others on 3.1.2.1 to check this out too.
>
> ..Paul
> --
> At 12:43 PM 1/14/99 -0000, you wrote:
> >We have recently noticed that after upgrading to 3.1.2.1 on AIX and NT
> >platforms, more versions of changed files are kept than the parameters in
> >the ACTIVE copygroups stipulate.
> >
> >For example:
> >
> >If policies are set so that:
> >
> >3 copies are kept if the data exists
> >1 copy is kept if the data is deleted
> >
> >If a file then changes and is backed up 5 times, 5 copies are kept! Even
> if
> >the data is then deleted from the client and another backup is performed.
> We
> >have also run expire inventory with no change.
> >
> >Has anyone else out there found this?
> >
> >The time based expiration for these versions still seems to work ok.
> >