Eric,

If your users don't want any protection  against accidental deletion, why
not just change the verdeleted and retonly parameters to the lowest values
allowed?  This is a policy question.  Either they want protection from
their own mistakes and will pay for it, or they don't.

Perhaps you could do a one time cleanup by making a new domain with 'quick
purge' values in the copy groups.  Update the nodes to use the new domain
and run exp inv.  Then update them back to their normal domains, with the
policies set to something they are willing to pay for.

You are right about the deficiencies in *SM regarding the administrators
inability to force the cleanup of a set of trash files which no one wants.


--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <0002219511.AA951179158 AT ccmail.adp.wisc DOT edu>, on 02/22/00
In <0002219511.AA951179158 AT ccmail.adp.wisc DOT edu>, on 02/22/00
   at 12:07 PM, Eric LEWIS <eric.lewis AT CCMAIL.ADP.WISC DOT EDU> said:

>     Hi: has anyone coded a SQL statement that will produce a list of
>file
>     names (with directory paths) that are the deleted files for a
>     particular node?

>     SELECT filespace_name, HL_name, LL_name FROM backups
>     WHERE
>          node_name = '....'  and
>          for each set of records with matching filenames there is no
>                record with status = 'A'
>     (and eliminate duplicate file records from output)

>     The reason I need this list is to help client customers clean up
>their
>     backup occupancy.  I have many who deleted files to save on backup
>     bills only to discover the last version of the deleted file hangs
>     around for awhile.

>     More troubling, once a file is deleted I cannot find a way to rebind
>     the inactive version at the server.  I'd like to optionaly be able
>to
>     rebind deleted files on a node to a management class with NO
>VERSIONS
>     RETAINED so the last version will go bye bye.

>     I would use this list to generate one byte files to be added to the
>     appropriate directories.

>     Then run a backup with include statements for the same files to put
>     them into the NO VERSIONS RETAINED mgt class.

>     Then run a batch job to delete the files again.

>     then run a backup to get rid of all the deleted file versions at the
>     backup server.

>     Or is there a better way?

>     Thanks.

>     Eric Lewis UW-Madison
>     eric.lewis AT doit.wisc DOT edu