ADSM-L

Possible expiry issues still with 3.1.2.16?

1999-04-15 00:48:25
Subject: Possible expiry issues still with 3.1.2.16?
From: Paul Fielding <paul.fielding AT HOME DOT COM>
Date: Wed, 14 Apr 1999 22:48:25 -0600
Being the cynical guy I am, I wanted to check to see if my expiry woes were
really gone after patching to 3.1.2.16.  After patching, we cleaned out 9 TB
of data, so things looked pretty good.

While digging through the 'backups' table, I found various files that still
had too many versions.  Thinking that these were probably files that hadn't
backed up since the upgrade, I went for details on the versions to check.

To my suprise, the files I checked had not only backed up recently (within
the last couple of days), but almost all the versions were recent (post
upgrade), as well.  To make it even more interesting, several of the
inactive versions had deactivation dates that were EARLIER than the
version's backup date.

Has anyone else encountered this, or have any insight as to how a file can
be deactivated before it's ever been backed up?

<sigh>.... a TB here, a TB there... who's counting.... :)

Paul
<Prev in Thread] Current Thread [Next in Thread>
  • Possible expiry issues still with 3.1.2.16?, Paul Fielding <=