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.
