The user confirmed that it DOES NOT exists on disk. Long since deleted. However, he just commented that he really can't confirm when it was deleted, so lets just go with "DOH - could have been deleted within the past 180-days......" TSM is W-A-D (unless proved otherwise)....
Sorry for annoying folks with a stupid question........ On Mon, Nov 12, 2012 at 9:13 AM, Rick Adamson <rickadam...@winn-dixie.com>wrote: > 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@VM.MARIST.EDU] On Behalf Of > Zoltan Forray > Sent: Monday, November 12, 2012 9:04 AM > To: ADSM-L@VM.MARIST.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.cho...@gmail.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 <n...@laflamme.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 <zfor...@vcu.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* > > >> TSM Software & Hardware Administrator Virginia Commonwealth > > >> University UCC/Office of Technology Services zfor...@vcu.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 > > > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.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 > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.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
