Dwight, The last completed incremental is what controls the update, per each filespace; hence, if you exclude.fs (or use DOMAIN to exclude), then the date in the filespaces table should reflect that -- it's also what is shown from the ba-client "q fi", or admin.client "q fi f=d".
So... you probably want to generate some tier-1 & tier-2 warning lists; tier-1 to show how many fs backups are older than a week, how many are older than a month --- then, send msg to owner to notify of planned purge from backup storage (assume you have an SLA for doing this)... this could be semi-automated, so at least some review (and notification) occurs before the delete action is performed. Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cook, Dwight E Sent: Friday, May 31, 2002 6:53 AM To: [EMAIL PROTECTED] Subject: node filespace cleanup, any ideas ? ? ? As filespaces come and go on a client, does anyone know of a solid way to clean them up ? ? ? Since directories are "backed up" even when they are "excluded" would the "Last Backup Start Date/Time:" reflect the last time the file system was mounted ? ? ? here is an example of why I would like to clean up things... We have an SAP disaster recovery box that has also been and will continue to be used for misc other things... So this has had QA TS BX PF etc... instances on it and filesystems have come and gone over the last year because they are generally of the form /oracle/XXX/sapdata# where XXX is some instance like PF1 and # is a sequence number Well, I did a select node_name,sum(capacity) as "filespace capacity MB",sum(capacity*pct_util/100) as "filespace occupied MB" from adsm.filespaces group by node_name and I really don't think this box has 17 exabytes of filespaces on it ;-) Filespace MB Occupied MB 17,592,369,800,454 17,592,367,574,528 memory refresh: terabyte is 1024 gigabytes petabyte is 1024 terabytes exabyte is 1024 petabytes zettabyte is 1024 exabytes yottabyte is 1024 zettabytes Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109
