What I ended up doing was something very similar to Steve's suggestion. However, since they were db2 logs that were backed up, their path didn't really exist. I ended up going to another machine, creating a stanza in the dsm.sys for the node I wanted to mess with. I created directories mirroring the path that db2 used (/dbname/dbnode), and touched the files in there. Of course, I had to use virtualmountpoint, but in your case, since Windows uses filespace names like \\compname\d$, I think you should be able to rename that filespace to the new machine/drive you're doing this on and then back up each file individually. If you just back up the directory, you'll have to copy all those active files over or they'll inactivate. So, to make a cryptic paragraph easier to understand:
ServerA - server data normally lives on ServerAnode - nodename that ServerA uses ServerB - server that you'll use to recreate the path in consideration of the queueing. 1. Create a stanza for ServerAnode in the dsm.sys on ServerB. Be sure to use the correct includes/excludes. 2. Recreate the path to the files on ServerB. 3. Create all those zero length files you want to rebind. 4. On the tsm server, "rename filespace \\ServerA\x$ \\ServerB\y$" where y$ is the drive where you recreate the path. This because when you back up those files, it wants to use the UNC of the current drive. 5. Back up each file individually to rebind it. This is necessary because otherwise it'll inactivate all those other active files. If inactivating all those files until the next backup is OK with you, that'll save a bit of work. 6. In TSM, rename the \\ServerB\y$ filesystem back to \\ServerA\x$. Voila, your files have been rebound and everybody is still wondering which pea the cup is under. Good luck, Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Todd Lundstedt [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 7:57 AM To: [EMAIL PROTECTED] Subject: Re: Expiring specific files Wow! Steve, that sounds like.. um.. fun?! I follow along with what you are trying to do, but I am not sure what this would do to the application, since that application watches this directory (as, I am guessing, a sort of queue). I would hesitate to create any file on my own in this directory, even more so, a file that has already been created by the application in this directory. I will certainly keep this workaround in mind for future issues, though. Just to clarify.. is there no way to expire a single file version, active or inactive? |--------+--------------------------------> | | Steve Harris | | | <[EMAIL PROTECTED]| | | LD.GOV.AU> | | | Sent by: "ADSM: Dist | | | Stor Manager" | | | <[EMAIL PROTECTED]>| | | | | | | | | 04/23/02 06:59 PM | | | Please respond to | | | "ADSM: Dist Stor | | | Manager" | | | | |--------+--------------------------------> >--------------------------------------------------------------------------- -------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Expiring specific files | >--------------------------------------------------------------------------- -------------------------------------| 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 >>> [EMAIL PROTECTED] 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. **********************************************************************
