Are you sure that file is set to the default management class for the node? Maybe there was an errant include statement back when the file was initially backed up that bound it to a different management class.
-- Skylar Thompson ([email protected]) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine On 11/ 9/12 01:11 PM, Zoltan Forray 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 [email protected] - 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
