Is there a way to keep the inactive version expiring?? If a client calls me and wants to hold data for a node, if I just stop backups, then eventually expiration will get the inactive copies and that is not what we want. And if you change mgmt class for the node, the inactive copies won't be affected.
Anybody got any ideas?? Regards, Matt -----Original Message----- From: Andrew Raibeck [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 1:51 PM To: [EMAIL PROTECTED] Subject: Re: filespace no longer backed up because mount or drive is gone You are correct. Inactive versions will expire per management class criteria. The active versions will stay around forever (*). The reason for this is as you stated: TSM errs on the side of caution since it has no knowledge of the status of the file system. (*) ... at least until another incremental backup is performed for that file system, a client node with BACKDELETE=YES deletes the backups, or a TSM administrator deletes the file space) Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "Ford, Phillip" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/24/2003 12:29 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: filespace no longer backed up because mount or drive is gone Others can correct me if I am wrong. Extra versions (inactive) are still controlled by the management class. The final active versions are kept forever. TSM does not know if they were deleted or the filespace went bad for some reason. Thus one has to hand delete them from TSM if they are not needed. The only thing I am not 100% sure of is the inactive versions. -- Phillip Ford Senior Software Specialist Corporate Computer Center Schering-Plough Corp. (901) 320-4462 (901) 320-4856 FAX [EMAIL PROTECTED] -----Original Message----- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: Friday, January 24, 2003 1:17 PM To: [EMAIL PROTECTED] Subject: filespace no longer backed up because mount or drive is gone Can anyone tell me what the affect is if a filespace no longer exists? Lets say either a drive D on a Windows server or /cost1 is no longer on a unix client. The filespace is no longer on the new client with the same name so it hasn't been touched in say 180 days. What is really there? Does the management class settings have any affect on it? Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 ********************************************************************* This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
