Author: Niklas Lundstrom <niklas.lundstrom AT FORENINGSSPARBANKEN DOT SE>
Date: Wed, 17 Nov 2004 13:07:32 +0100
Yes, I tried it, but with no success. It's only the System Object filespace that's impossible to delete. I renamed it to something else but it's still the same problem. /Niklas --Ursprungligt meddela
Author: Bill Dourado <bill.dourado AT ALSTEC DOT COM>
Date: Wed, 17 Nov 2004 11:04:20 +0000
Have you tried the via Storage Manager Server Web GUI ? Bill Niklas Lundstrom <niklas.lundstrom AT FORENINGSSPARBANKEN DOT SE> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> 17/11/2
Author: Niklas Lundstrom <niklas.lundstrom AT FORENINGSSPARBANKEN DOT SE>
Date: Wed, 17 Nov 2004 11:52:01 +0100
Hello I have exported a node from one TSM server to another but I never used the exported node and decided to remove it But trying to remove node SPNT350 TSM tells me: Inventory reference still exist
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Mon, 28 Oct 2002 11:13:52 -0500
Another alternative: I have run into this before, but never when using the admin web GUI. It seems to pass along the FSID information that is required to get the job done. (I am TSM 4.2.1.15...) Try,
Author: Bas van Kampen <b.vankampen AT INTERCONNECT DOT NL>
Date: Mon, 27 Jul 2015 08:02:51 +0000
Robert, I had the same problem. I made a service request for this. I can be fixed with a "repair occupancy" command. http://www-01.ibm.com/support/docview.wss?uid=swg21579500 Before running this comm
Author: Krzysztof Przygoda <przygod AT GMAIL DOT COM>
Date: Sat, 25 Jul 2015 16:05:10 +0200
Hi Robert Instead of renaming filespaces maybe the better option would be just to rename the node to old_node and create the new one with the same name. Then just grant access for the new node for al
Author: Robert Ouzen <rouzen AT UNIV.HAIFA.AC DOT IL>
Date: Sat, 25 Jul 2015 09:56:06 +0000
HI Krzysztof It's why I am doing now , running on those volumes an audit vol fix=yes. When finishing will re-run a move nodedata Bu if this will no help I am stuck !. Thinking to rename the F.S to _O
Author: Krzysztof Przygoda <przygod AT GMAIL DOT COM>
Date: Sat, 25 Jul 2015 11:48:51 +0200
Hi Robert Did you try to repair data/volumes in that old storage pool (even with audit vol fix=yes if you don't care about that data ) ? After fixing try to run move nodedata agian. ps. I guess you w
Author: Robert Ouzen <rouzen AT UNIV.HAIFA.AC DOT IL>
Date: Sat, 25 Jul 2015 07:34:04 +0000
Hi to all I made today a MOVE NODEDATA of a client WWW from storage DD_EDUCATION to storage V3700_1 The process did not finish successfully , some volumes with read errors. Now I got with command Q O
Author: David Bronder <david-bronder AT UIOWA DOT EDU>
Date: Mon, 2 Apr 2007 20:30:54 -0500
The problem I saw here was this: ANR2900W The character string '11' was truncated during assignment. Changing the cast and select a bit could yield output that could in turn be run to automatically d
Hi Steven, Your suggestion is to use nametype FSID to delete the specify filespace. Would you please tell me the placing of '1' behind OMRON, is this the way to say FSID =1 ? delete filespace OMRON 1
Author: William Boyer <bjdboyer AT COMCAST DOT NET>
Date: Fri, 20 Jan 2006 10:09:14 -0500
The filespace name has to be the NUMBER, not the NAME when you speicfy NAMETYPE=FSID. Do a Q FI DOCAPPS to get the corresponding number for the DOA filespace and use that in its place in the GEN BACK
Author: PAC Brion Arnaud <Arnaud.Brion AT PANALPINA DOT COM>
Date: Fri, 20 Jan 2006 15:48:58 +0100
Timothy, Try to use exactly the same syntax as the one used by the GUI : GENERATE BACKUPSET DOCAPPS "weekly docapp" 5 DEVCLASS=3592CLASS NAMETYPE=FSID DESCRIPTION="weekly docapparch" RETENTION=1 WAIT
Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
Date: Thu, 13 Oct 2005 09:31:10 +0200
Hi Etienne! That's right, but in your case, I would be interested in why the delete fails and thus upgrade my TSM server first. Maybe you can solve the failure yourself afterwards, but in any case, y
Author: Etienne Brodeur <ebrodeur AT SERTI DOT COM>
Date: Wed, 12 Oct 2005 13:36:18 -0400
Hi Eric, Indeed it does... but it says the fix is that instead of ending in sucess, the delete filespace will end in error with the appropriate error message: "... The intent of this APAR is to chang
Author: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
Date: Wed, 12 Oct 2005 11:38:08 +0200
Hi Etienne! The apar states: ** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be * * fixed in levels 5.1.10 and 5.2.4. Note * * that this is subject
Author: Etienne Brodeur <ebrodeur AT SERTI DOT COM>
Date: Tue, 11 Oct 2005 14:12:29 -0400
Hello All, I have a probleme with deleting a Windows filespace for a particular node I want to remove. When I run DELETE FILESPACE on it it finishes without errors, but the filespace itself is not de
Author: "Robert L. Rippy" <robert_rippy AT KINDREDHEALTHCARE DOT COM>
Date: Mon, 30 Dec 2002 14:22:50 -0500
If the volumes that have damaged file are volumes marked OFFSITE, just delete those volumes because when your backup storage pool runs again, it will make new copies. But if the volume damaged is an
Author: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Date: Mon, 30 Dec 2002 14:02:36 -0500
Thanks for the help. I did and this is what I get: 12/30/2002 13:23:24 ANR1255W Files on volume 041108 cannot be restored access mode is "unavailable" or "offsite". 12/30/2002 13:23:25 ANR1255W Files
Author: Fred Johanson <fred AT MIDWAY.UCHICAGO DOT EDU>
Date: Mon, 30 Dec 2002 12:37:46 -0600
Among other things, you should audit the onsite volume, if known, or the storagepool; move the good files off the offending volumes; and restore or delete the files that can't be copied by reclamatio