Todd,
I just had this problem with a bunch of oracle archive files that had been
placed into the wrong directory and so had picked up the default retention
(retonly 365) instead of the oracle one (retonly 35). Your suggested approach
will work fine for active files, which will be rebound, but inactive files will
not be.
As you have suggested, set up your includes to give these files a short
retention period.
Then, generate your list of inactive files. In my case it was easy as the
files had ascending sequence numbers. If your case isn't that simple you could
use either the ba client q backup command or alternatively use the admin client
to select appropriately from the contents table and post-process the output.
Both approaches have issues, but are do-able.
Take this list and process it through your favourite scripting language.
In batches of say 100 files,
create a new zero length file with the name of the file you want deleted from
tsm. Under unix I'd use touch, under windows I'm not sure.
back up the directory
delete the batch
Repeat until all files processed.
back up the directory one last time
Set your include/excludes to whatever your long term requirement is for this.
This should fix the problem.
Regards
Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia
>>> Todd_Lundstedt AT VIA-CHRISTI DOT ORG 24/04/2002 6:32:23 >>>
I have a bunch of files that have been backed up in one directory on this
node that we no longer need to keep. These files all have unique names,
but share the extension of .prt. There is a very large number of inactive
versions (simply because these are temporary files that get deleted each
day). I would like to find a way to expire the files in this folder.
Is there a command to do this? or do I have to change the management class
for this file to a dummy management class/backup copy group (say, "nohold"
set to 1, 0, 0, 0)?
If I have to change the management class, what are the steps I need to do
to accomplish this? Is it simply...
Create new management class/backup copy group (call it nohold)?
modify the options file for this node to have an "include <path>\*.prt
nohold"
and then run an incremental
Is that basically it?
**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.
Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited. It may be subject to a statutory duty of
confidentiality if it relates to health service matters.
If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail. You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************
|
