filespaces not deleted
Hello TSM'ers With the danger that some of you might think I am not the sharpest tool in the shed, there is one thing about filespaces I do not understand. Why are there filespaces which will not expire?? If I rename a node and existing files go under a new directory structure I would have expected that TSM looks at the old filespaces as deleted and applies the normal retention periods as specified in the Mgmtclasses for a deleted file. Is there somebody out there who would be able to give me short explanation why this is not happening and how I can identify all my dead filespaces out there. I am pretty sure I do have tons of them out there. Thanks Andrea Mac Murray
Re: filespaces not deleted
When a file system just ~up goes away~ TSM has no way of knowing WHY ??? might have died due to the media on which it resides died might have gone away because someone just unmounted it might have gone away because someone deleted it (for whatever reason) So TSM freezes that entire filesystem until it comes back and resumes normal incremental processing OR you purge it from an admin session... Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Macmurray, Andrea (CAG-CC) [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:05 AM To: [EMAIL PROTECTED] Subject: filespaces not deleted Hello TSM'ers With the danger that some of you might think I am not the sharpest tool in the shed, there is one thing about filespaces I do not understand. Why are there filespaces which will not expire?? If I rename a node and existing files go under a new directory structure I would have expected that TSM looks at the old filespaces as deleted and applies the normal retention periods as specified in the Mgmtclasses for a deleted file. Is there somebody out there who would be able to give me short explanation why this is not happening and how I can identify all my dead filespaces out there. I am pretty sure I do have tons of them out there. Thanks Andrea Mac Murray
Re: filespaces not deleted
If you want to delete those, then use delete filespace. AS you have renamed these nodes, there is most likely NO ACTIVITY happening for these filespaces, therefore they are frozen so to speak. If you were running a backup schedule for these nodes, some of the data would be expired. After deleting the filespaces, you can ten remove node for the old nodes. (You don't have to do expire inventory for the filespaces that you delete, the delete deletes the data immediately.) David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 12/13/02 11:04AM Hello TSM'ers With the danger that some of you might think I am not the sharpest tool in the shed, there is one thing about filespaces I do not understand. Why are there filespaces which will not expire?? If I rename a node and existing files go under a new directory structure I would have expected that TSM looks at the old filespaces as deleted and applies the normal retention periods as specified in the Mgmtclasses for a deleted file. Is there somebody out there who would be able to give me short explanation why this is not happening and how I can identify all my dead filespaces out there. I am pretty sure I do have tons of them out there. Thanks Andrea Mac Murray MMS health-first.org made the following annotations on 12/13/2002 11:18:45 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: filespaces not deleted
-Why are there filespaces which will not expire?? If I rename a node and -existing files go under a new directory structure I would have expected -that TSM looks at the old filespaces as deleted and applies the normal -retention periods as specified in the Mgmtclasses for a deleted file. But TSM does not work like that. TSM never expires active file backups. Active files are files that still exist on the client and TSM checks as part of the backup process if the file that existed last backup time, still exists. Because you have changed the node name TSM no longer gets the chance to do this comparison, so the files will stay active forever, and the last backup will never expire. There has been past discussion about ways of deleting these unwanted files. Have a look in ADSM.ORG, but why not just delete the old filsspaces after you have successful backups on the new node and it has been a period of time equal to your retention of retain only version ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
