Nope.  This server has only 2-PD/PS/MC.  It is on the other side of our
firewall, used to backup selective hospital systems.  Nothing has changed
since we built a new V6.2 server and export/imported everything from the
old server, back in January/February of this year.

On Tue, Nov 13, 2012 at 2:40 AM, Karel Bos <tsm.wad AT gmail DOT com> wrote:

> Hi,
>
> Was there any change in management classes (class the file was bound 2 was
> deleted after file became inactive)?
>
> Grace delay comes to mind.
>
> Kind regards,
> karel
>
> ----- Oorspronkelijk bericht -----
> Van: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
> Verzonden: maandag 12 november 2012 15:13
> Aan: ADSM-L AT VM.MARIST DOT EDU
> Onderwerp: Re: [ADSM-L] Inactive/deleted file backup not expiring
>
> Zoltan,
> Maybe I missed something, but is the it still present on the file system?
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Zoltan Forray
> Sent: Monday, November 12, 2012 9:04 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Inactive/deleted file backup not expiring
>
> Unfortunately, the info from the user is a screenshot of the inactive file
> (X) and dates I posted.
>
> As for the MC backup copygroup values:
>
> VERE = 5
> RETE = 30
> VERD = 1
> RETO = 180
>
>
> On Mon, Nov 12, 2012 at 5:49 AM, Chavdar Cholev <chavdar.cholev AT gmail DOT 
> com
> >wrote:
>
> > can you post backup copy group settings and small list of file which
> > are not expiring
> >
> > On Sat, Nov 10, 2012 at 1:16 AM, Nick Laflamme <nick AT laflamme DOT us> 
> > wrote:
> > > This is probably a silly question, but are you sure expiration is
> > running for the node in question? With Version 6, expiration can now
> > be granular, and its results are reported in a granular manner. You
> > can run expiration on just this node, if only to see if anything weird
> > happens as a consequence.
> > >
> > > Just a thought,
> > > Nick
> > >
> > > On Nov 9, 2012, at 3:11 PM, Zoltan Forray <zforray AT VCU DOT EDU> wrote:
> > >
> > >> I recently had someone point out that when they were looking
> > >> through
> > files
> > >> backed up for their node (billing time!), they found a backup that
> > >> is INACTIVE and has been since 02/23/2012.  The file is an ordinary
> > >> TAR
> > file -
> > >> 3.2GB in size.
> > >>
> > >> The reason this is an issue is the Management Class for that
> > >> node/PD is
> > set
> > >> for *180-days* for RETO?
> > >>
> > >> So, why would an expired/deleted backup not roll-off?
> > >>
> > >> Yes, EXPIRE INVENTORY runs automatic/daily (checked the logs for
> > >> the
> > past
> > >> 2-months to confirm).
> > >>
> > >> Server is Linux 6.2.3.0  (I have looked at the 6.2.4 updates and
> > >> didn't
> > see
> > >> anything that should effect/address this).
> > >>
> > >> --
> > >> *Zoltan Forray*
> > >> T
>
>
> [Het originele bericht is niet volledig opgenomen]




--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html