1) Before doing anything, check whether it will necessary to increase the verdeleted for this MC, so as to not inadvertently expire the client's data prematurely. (If verdeleted is 1 for these unique files, backing up the dummy file(s) will cause the "real" data to roll off immediately.) If this change would cause problems with retention of other clients' data, you can copy the domain that the client is in, then update the client to belong to the new domain. This effectively creates a "clean room" so that any changes made to retentions will not affect other machines' data.
2) The time involved for step 2 (execution of the script, not the writing) could be considerable, depending on number of files, server platform, connection speed, etc. If at all possible, run the script on the client machine. I once tried to do this for a Netware client running Groupwise, and wound up taking a different route entirely because the creation of the dummy files was agonizing slow over the network. Testing the script locally on my laptop worked fine.
3) It might be easier to get the file list for step one by running a query backup from the client rather than a Select from the server. Getting this type of information from the administrative client can be very time-consuming, particularly if your DB is large.
Ted
At 09:58 AM 3/30/2004 -0500, you wrote:
How about:
1) Pull a list of all those files from TSM with SELECT 2) write a script that creates an empty dummy file of the same name 3) backup (thus rebing) 3) delete
-----Original Message----- From: Salak Juraj [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 9:33 AM To: [EMAIL PROTECTED] Subject: AW: Rebinding backups of deleted files.
1) restore, 2) backup (thus rebind) 3) delete
See it positive - as a recovery test :-)
regards juraj
-----Urspr�ngliche Nachricht----- Von: Alan Davenport [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 30. M�rz 2004 16:07 An: [EMAIL PROTECTED] Betreff: Rebinding backups of deleted files.
Hello Group,
Just when you think you know how something works...
I recently discovered that a user backup directory was not following standard naming conventions and for this reason I was keeping 1 year's worth of backups rather than 45 days. Their application creates unique names for each backup then deletes old backups. I added and include option for their backup directory for the 45 day management class and ran a backup. The existing files in the directory rebound correctly to the 45 day class however the TSM backups of the deleted files are still bound to the default management class and will not go away for a year. This is causing me to retain many many gigabytes more data than necessary. Is there any way to get those files rebound to the 45 day class?
Thanks, Al
Alan Davenport Senior Storage Administrator Selective Insurance Co. of America [EMAIL PROTECTED] (973) 948-1306
