Re: Odd server activity attached to no session or process, and deleting filespaces from very large nodes...
On 01/15/2013 05:56 PM, Alex Paschal wrote: Are those 40mil spread across several filespaces? I've seen situations on TSM-classic (i.e. pre-6) where doing smaller workloads, like deleting one filespace at a time, worked better than deleting the whole node. Would that be practical in this case? Thanks, I experimented after your suggestion: objects deleted wasn't particularly different doing the whole node vs. one FS at a time. I've addressed the prompt issue; no more thrashing on a quiesced instance. It'll be interesting to see if it happens again. At least I'll be sensitized; I don't really have a clear idea how long that has been getting in the way of normal operations. - Allen S. Rout
Odd server activity attached to no session or process, and deleting filespaces from very large nodes...
So I've been working on deleting a node with some 40M objects (80M, if you count copy pools). I kicked it off yesterday afternoon, and by this morning it had deleted a fine total of 128K objects. Not auspicious. The server instance was active (though not really busy), but it's essentially constantly active, so I didn't really pay much attention. But a crash in a different instance (ran out of log space, was trying to DB backup, but tapes were all occupied, etc.) made me want to quiesce not just the instance, but the whole system image. In an attempt to do that, I slew the filespace delete, and all other work on the server. Yet the thing was still occupying a whole CPU, and doing very substantial IO. I want to emphasize, no sessions except for my admin session doing the queries, and no processes. Anyone ever seen something like that? I restarted the server instance and the behavior hasn't yet repeated. - Allen S. Rout
Re: Odd server activity attached to no session or process, and deleting filespaces from very large nodes...
On 01/15/2013 12:46 PM, Prather, Wanda wrote: Is it V6, and could it be DB2 processes doing the I/O instead of the TSM server itself? No; 5.5. - Allen S. Rout
Re: Odd server activity attached to no session or process, and deleting filespaces from very large nodes...
Is it V6, and could it be DB2 processes doing the I/O instead of the TSM server itself? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen S. Rout Sent: Tuesday, January 15, 2013 11:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Odd server activity attached to no session or process, and deleting filespaces from very large nodes... So I've been working on deleting a node with some 40M objects (80M, if you count copy pools). I kicked it off yesterday afternoon, and by this morning it had deleted a fine total of 128K objects. Not auspicious. The server instance was active (though not really busy), but it's essentially constantly active, so I didn't really pay much attention. But a crash in a different instance (ran out of log space, was trying to DB backup, but tapes were all occupied, etc.) made me want to quiesce not just the instance, but the whole system image. In an attempt to do that, I slew the filespace delete, and all other work on the server. Yet the thing was still occupying a whole CPU, and doing very substantial IO. I want to emphasize, no sessions except for my admin session doing the queries, and no processes. Anyone ever seen something like that? I restarted the server instance and the behavior hasn't yet repeated. - Allen S. Rout
Re: Odd server activity attached to no session or process, and deleting filespaces from very large nodes...
Are those 40mil spread across several filespaces? I've seen situations on TSM-classic (i.e. pre-6) where doing smaller workloads, like deleting one filespace at a time, worked better than deleting the whole node. Would that be practical in this case? On 1/15/2013 10:04 AM, Allen S. Rout wrote: On 01/15/2013 12:46 PM, Prather, Wanda wrote: Is it V6, and could it be DB2 processes doing the I/O instead of the TSM server itself? No; 5.5. - Allen S. Rout
deleting filespaces / inactive files and primary storage size
Hello I have been analysing the size of my Primary Storage and Copy Storage, analysing the kind of backups I have been doing for different nodes and the kind of data being retained. Basically I have found at least 40TB of data in the Primary storage which really is not needed, and have approval to remove them. I have removed a lot of this redundant information successfully via two methods.. 1. delete filespaces within specific nodes 2. deleting versions of inactive files via a node's command line client However, after running these commands and confirming the processes are completed, when I do a Q auditocc pooltype=primary To compare the size of the primary store now to before, it hasn't dropped. I am wondering do the size reduction not occur til expiration runs fully? Richard html body font face=arial color=#808080 size=-2img alt=Santos Logo src=http://www.santos.com/library/logo.gif; brSantos Ltd A.B.N. 80 007 550 923br Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email and delete the email without making a copy./font font face=arial color=#008000 size=-2Please consider the environment before printing this email/font /body /html
Re: deleting filespaces / inactive files and primary storage size
On Nov 14, 2008, at 4:33 AM, Cheung, Richard wrote: I have removed a lot of this redundant information successfully via two methods.. 1. delete filespaces within specific nodes 2. deleting versions of inactive files via a node's command line client However, after running these commands and confirming the processes are completed, when I do a Q auditocc pooltype=primary To compare the size of the primary store now to before, it hasn't dropped. I am wondering do the size reduction not occur til expiration runs fully? Deleting filespaces immediately releases space, as posted this week. dsmc Delete BAckup marks files for expiration. Make sure you are running expiration regularly. And you probably didn't perform AUDit LICenses before executing Query AUDITOccupancy. Richard Sims
Strange problem deleting filespaces
Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56980 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05
Re: Strange problem deleting filespaces
Hi Richard! You didn't mention it, but I assume the restore was followed by an upgradedb? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Richard van Denzel [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 16:20 To: ADSM-L@VM.MARIST.EDU Subject: Strange problem deleting filespaces Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70
Re: Strange problem deleting filespaces
Richard, If I am understanding you correctly, you have performed the following Database backup to tape of a TSM server version 5.1.1.0 You have then tried to restore this database backup of a TSM server 5.1.1.0 to a TSM server version 5.2.6.3. This is not supported. You can only restore db backups back to a server of the same release that they came from. You have to upgrade the tsm server from 5.1.1.0 to 5.2.6.3 without doing a db restore. What you could do is the following; On your new system, install 5.1.1.0 and restore the db backup to this and then upgrade this new system from 5.1.1.0 to 5.2.6.3. You can then get a feel for how long the upgrade process will take and also do some testing on the new system to see if you have any issues. Apologies if I have not understood your email correctly and you are indeed doing an upgrade. Leigh -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: 15 November 2005 15:20 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Strange problem deleting filespaces Hi All, I've got a strange problem when I try do delete old filespaces. The scenario: I've made a backup of the old 5.1.1.0 database. On the new system I installed TSM 5.2.6.3 on the new system and restored the database there. So far so good. To start freshly on all clients we decided to delete all the old filespaces and than this: 11/10/05 13:48:55 ANR2017I Administrator ADMIN issued command: DELETE FILESPACE lima 1 t=any data=any namet=fsid wait=no (SESSION: 2669) 11/10/05 13:48:55 ANR0984I Process 63 for DELETE FILESPACE started in the BACKGROUND at 13:48:55. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0800I DELETE FILESPACE / (fsId=1) for node LIMA started as process 63. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0802I DELETE FILESPACE / (fsId=1) (backup/archive data) for node LIMA started. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR2183W imfsdel.c(1838): Transaction 0:56957 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:55 ANR1181E sstxn.c(372): Data storage transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56966 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0826I DELETE FILESPACE LIMA for node / encountered a transaction failure. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR0827I DELETE FILESPACE / (fsId=1) will be retried for node LIMA. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANRD sstxn.c(369): ThreadId19 SS commit prohibited - transaction failed. Callchain of previous message: 0x10016400 outDiagf - 0x102DBD08 ssPrepareTxn - 0x1008F8C0 CollectVotes - 0x1009064C tmEnd - 0x102B0C70 DeleteBackups - 0x102B1904 imFSDeletionThread - 0x10007B80 StartThread - 0xD004B57C _pthread_body - (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR1181E sstxn.c(372): Data storage transaction 0:56973 was aborted. (SESSION: 2669, PROCESS: 63) 11/10/05 13:48:56 ANR2183W imfsdel.c(1838): Transaction 0:56973 was aborted. (SESSION: 2669, PROCESS
Backing up MS Exchange / KVS + Deleting FileSpaces
Hi, This is my third post in as many days - thanks for all the help so far! I have just 2 more questions: 1. We are migrating from GroupWise 6 to MS Exchange soon. We have a user base of appx. 500 and will be implementing a KVS storage solution to handle mails archived-by-date. Does anyone have any tips/links/whitepapers/case studies on best practise in backing up Exchange, KVS or both with TSM (and possibly HSM)? What retention parameters are advisable? 2. I have just deleted filespaces for 12 nodes that are no longer operating on our network. The occupied size summed appx. 1.5Tb but the filespace deletion process seemed uncannily quick. The command I issued for each node's filespace was: DEL FILESP NODE_NAME * TYPE=ANY DATA=ANY Once issued I input 'Q PRO' to check what was happening and was shown that TSM was deleting objects. My question is: How and when will all of this space be reclaimed from both the onsite and offsite tapes as the whole purpose of deleting these filespaces was not only to purge a stack of data we no longer needed but, ultimately, to free up slots in our LTO library? Many thanks all. C. Adams IT Support Analyst WRC Holdings Limited This email and any files transmitted with it are confidential and intended solely for the individual(s) or entity(s) to whom it is addressed. Any views or opinions presented or expressed herein, are those of the author(s), and may not necessarily represent those of WWAV Rapp Collins Group or it's affiliates and representatives. No representation is given nor any liability accepted for the accuracy or completeness of any information contained in this email unless expressly stated to the contrary. Neither is any liability accepted for any damage or financial or personal loss howsoever caused as a result of using the information or data contained within this email. If you are not the intended recipient(s) and/or have received this email in error, you may not use, disseminate, store, forward, print or copy it, in any method or form, either digital or otherwise. You must delete it completely from your system(s) and notify the sender that you received it, so we can ensure it does not happen again. Registered Office: 1 Riverside, Manbre Road, London UK, W6 9WA. Registered in England No. 1581935
Re: Backing up MS Exchange / KVS + Deleting FileSpaces
Hi, i'am currently testing KVS VaultStore for Fileservers. My findings so far are - replacing the original file by a stubfile changes the reparse point of the file, so TSM is will cause a backup of this file by doing a recall of the file during a full-incremental backup, even the original file was backuped during former backups. - a solution for that is to do a incremental-by-date, using this method no recall and backup of already migrated files which were already backuped. but only doing incremental-by-date means to loose the expiration of deleted files, e.g. and even a file is renamed it will not be backed up cause this will not change the modified date. Mit freundlichen Grüßen / Best Regards Uwe Schreiber [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08.04.2004 17:55 Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Backing up MS Exchange / KVS + Deleting FileSpaces Hi, This is my third post in as many days - thanks for all the help so far! I have just 2 more questions: 1. We are migrating from GroupWise 6 to MS Exchange soon. We have a user base of appx. 500 and will be implementing a KVS storage solution to handle mails archived-by-date. Does anyone have any tips/links/whitepapers/case studies on best practise in backing up Exchange, KVS or both with TSM (and possibly HSM)? What retention parameters are advisable? 2. I have just deleted filespaces for 12 nodes that are no longer operating on our network. The occupied size summed appx. 1.5Tb but the filespace deletion process seemed uncannily quick. The command I issued for each node's filespace was: DEL FILESP NODE_NAME * TYPE=ANY DATA=ANY Once issued I input 'Q PRO' to check what was happening and was shown that TSM was deleting objects. My question is: How and when will all of this space be reclaimed from both the onsite and offsite tapes as the whole purpose of deleting these filespaces was not only to purge a stack of data we no longer needed but, ultimately, to free up slots in our LTO library? Many thanks all. C. Adams IT Support Analyst WRC Holdings Limited This email and any files transmitted with it are confidential and intended solely for the individual(s) or entity(s) to whom it is addressed. Any views or opinions presented or expressed herein, are those of the author(s), and may not necessarily represent those of WWAV Rapp Collins Group or it's affiliates and representatives. No representation is given nor any liability accepted for the accuracy or completeness of any information contained in this email unless expressly stated to the contrary. Neither is any liability accepted for any damage or financial or personal loss howsoever caused as a result of using the information or data contained within this email. If you are not the intended recipient(s) and/or have received this email in error, you may not use, disseminate, store, forward, print or copy it, in any method or form, either digital or otherwise. You must delete it completely from your system(s) and notify the sender that you received it, so we can ensure it does not happen again. Registered Office: 1 Riverside, Manbre Road, London UK, W6 9WA. Registered in England No. 1581935
Re: deleting filespaces
could be type ... type=unicode [EMAIL PROTECTED] 04/06/04 06:18AM Try using the filespace id instead. Regards, Karel -Oorspronkelijk bericht- Van: Moses Show [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 6 april 2004 12:21 Aan: [EMAIL PROTECTED] Onderwerp: deleting filespaces Am trying to delete a filespace on one of our TSM nodes using command delete filespace (nodename) (filespacename) type=any but it doesn't seem to work. The filespaces I am trying to delete are of the type \\XYZ\c$, where \\XYZ does not have the same name as the nodename (ie the filespaces are named after a different server) Can anybody help me get this sorted out please == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links contained herein, from your system. == The ST Paul Travelers E-mail System astpbcap103 made this annotation on 04/06/2004 05:17:06 AM. CONFIDENTIALITY NOTICE This message is confidential, intended only for the named recipient(s) and may contain information that is privileged, or exempt from disclosure under applicable law. If you are not the intended recipient(s), you are notified that the dissemination, distribution or copying of this message is strictly prohibited. If you receive this message in error, or are not the named recipient(s), please notify the sender by reply e-mail, delete this e-mail from your computer, and destroy any copies in any form immediately. Receipt by anyone other than the named recipient(s) is not a waiver of any attorney-client, work product, or other applicable privilege. This message and all contents may be reviewed by authorized parties of the Catholic Health System other than those named in the message header. The contents of this message do not bind the Catholic Health Systemto any contract, position, or course of action unless the sender is specifically authorized to enter into contracts on behal f of the Catholic Health System. The contents of this message do not necessarily constitute an official representation of the Catholic Health System.
deleting filespaces
Am trying to delete a filespace on one of our TSM nodes using command delete filespace (nodename) (filespacename) type=any but it doesn't seem to work. The filespaces I am trying to delete are of the type \\XYZ\c$, where \\XYZ does not have the same name as the nodename (ie the filespaces are named after a different server) Can anybody help me get this sorted out please == This communication, together with any attachments hereto or links contained herein, is for the sole use of the intended recipient(s) and may contain information that is confidential or legally protected. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, dissemination, distribution or use of this communication is STRICTLY PROHIBITED. If you have received this communication in error, please notify the sender immediately by return e-mail message and delete the original and all copies of the communication, along with any attachments hereto or links contained herein, from your system. == The ST Paul Travelers E-mail System astpbcap103 made this annotation on 04/06/2004 05:17:06 AM.
Deleting filespaces
I have mutiple nodes that backup oracle databases with RMAN using the TDP for oracle product. They all share the same rman catalog and backup to the same filespace name. Recently one of the nodes was discontinued and the database backups were not delete by rman before it was discontinued. FYI - We can't get this node back. It I delete the filespaces that are assoicated with this node will it only delete the filespaces that are assoicated with this node or will it try to delete all filespaces under the filespace name. The filespace name is the same on all nodes. TSMOB. Any help would be appricated. Troy L. Minter AIX Systems Administrator 479-441-5830 [EMAIL PROTECTED]
Trouble deleting filespaces
Trying to delete some unused filespaces from a windows nt client. Tried del filespace anonymouse \\cont_ed\apps Says no matching filespaces found. However, below find a cutting from a q filespace that says it is there. Need some help please. Node Name: ANONYMOUSE Filespace Name: \\cont_ed\apps FSID: 2 Platform: WinNT Filespace Type: NWCompat Is Filespace Unicode?: Yes Capacity (MB): 6,634.5 Pct Util: 64.9 Gary Lee Senior Operating Systems Analyst Ball State University phone 765-285-1310
Re: Trouble deleting filespaces
Look up the reference info for DELETE FILESPACE (HELP DEL FI will work from the Admin command line interface) and have a look at the NAMETYPE option. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Lee, Gary D. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 10/30/2003 09:17 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Trouble deleting filespaces Trying to delete some unused filespaces from a windows nt client. Tried del filespace anonymouse \\cont_ed\apps Says no matching filespaces found. However, below find a cutting from a q filespace that says it is there. Need some help please. Node Name: ANONYMOUSE Filespace Name: \\cont_ed\apps FSID: 2 Platform: WinNT Filespace Type: NWCompat Is Filespace Unicode?: Yes Capacity (MB): 6,634.5 Pct Util: 64.9 Gary Lee Senior Operating Systems Analyst Ball State University phone 765-285-1310
Re: Trouble deleting filespaces
Andy nailed it. Thank you very much. This is the perfect kind of help. Just point me to the correct manual section. I looked at it, but overlooked it.
Re: Trouble deleting filespaces
Glad that helped. Sure, I could have just said, use nametype=unicode (or nametype=fsid) But I'm a big believer in the latter part of give a man a fish, feed him for a day; teach him to fish, feed him for life. :-) Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Lee, Gary D. [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 10/30/2003 09:33 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Trouble deleting filespaces Andy nailed it. Thank you very much. This is the perfect kind of help. Just point me to the correct manual section. I looked at it, but overlooked it.
!!!Deleting Filespaces!!!
Hi, Does anyone no of a quick way for deleting file spaces. I have just recently upgraded our customer from the Notes connect agent to the new TDP for domino. The old filespaces for the connect agent are now no longer needed. They have about 1000 different filespaces and deleting them one by one will take ages. I can't start them all at once for fear of database deadlocks. Any ideas?? Cheers Scott **Internet Email Confidentiality Footer*** Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. Phoenix IT Group Limited is registered in England and Wales under company no. 3476115 Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS
Re: !!!Deleting Filespaces!!!
I had the same problem at one site. I issued a query filespace nodename filename, edited that file creating a macro delete filespace nodename filespacename wait=yes. Then start the macro: macro filename. Took a long time but I didn't have to babysit it and with wait=yes only one at a time ran. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (719) 260-5991 Email: [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Scott Thompson Sent: Tuesday, November 14, 2000 8:29 AM To: [EMAIL PROTECTED] Subject: !!!Deleting Filespaces!!! Hi, Does anyone no of a quick way for deleting file spaces. I have just recently upgraded our customer from the Notes connect agent to the new TDP for domino. The old filespaces for the connect agent are now no longer needed. They have about 1000 different filespaces and deleting them one by one will take ages. I can't start them all at once for fear of database deadlocks. Any ideas?? Cheers Scott **Internet Email Confidentiality Footer*** Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. Phoenix IT Group Limited is registered in England and Wales under company no. 3476115 Registered Office: Technology House, Hunsbury Hill Avenue, Northampton, NN4 8QS
