I have a client running Sun Solaris 5.8 with client version 5.1.5 TSM server is AIX 4.3.3 running TSM 5.1.6.5 Below is the include/exclude list from the dsm.sys include * shared_dynamic_60 include /a
Author: "Amini, Mehdi" <Mehdi.Amini AT VALUEOPTIONS DOT COM>
Date: Wed, 13 Nov 2002 12:59:22 -0500
What I have found since my previous email is this. If I run my SQLFULL.CMD from the Client....The information is updated...But if the server schedule calls up the command this information is not upda
Mehdi, I suggest calling support since it should be working. It works when I back up my SQL 2000 server using TDP for SQL 2.2.1 to a TSDM 5.1.0 TSM server. BEFORE == Node Name: HOOBIE_SQL Filespace N
Author: Dale Jolliff <dale.jolliff.b AT BAYER DOT COM>
Date: Thu, 14 Mar 2002 11:12:57 -0500
Ah, that's it.... This worked. DELETE FILESPACE WINNODE 4 NAMETYPE=FSID Thanks to everyone! "William F. Colwell" To: ADSM-L AT VM.MARIST DOT EDU <bcolwell@DRAPER. cc: COM> Subject: Re: Delete filespa
Author: Martin Janosik <martin.janosik AT CZ.IBM DOT COM>
Date: Mon, 25 Jan 2016 14:02:28 +0100
Hi Yann, it seems the proposed functionality can be already achieved via command DECOMMISSION VM while specifying FSID. Here is a real-word test: Server Version 7, Release 1, Level 3.0 @AIX tsm: TSM_
Author: David Longo [mailto:David.Longo AT HEALTH-FIRST DOT ORG]
Date: Sun, 04 Oct 2015 17:10:42 -0500
If you are trying to delete an entire filespace, then I have a suggestion. With apologies to Andy Raibeck, sometimes "The Web Admin is your friend." On the Web Admin select from the left side "Object
Author: "Minns, Farren - Chichester" <fminns AT WILEY DOT COM>
Date: Mon, 16 May 2011 10:41:49 +0100
Thanks Grigori I was missing a space { NULL\System State }, so the below command worked. Thanks for your advice though. I'll try that next time :-/ Regards Farren delete filespace CHI-AS-SCCMEUR 'CHI
Author: Grigori Solonovitch <Grigori.Solonovitch AT AHLIUNITED DOT COM>
Date: Mon, 16 May 2011 12:26:21 +0300
Try namet=fsid and use filespace ID instead of name. FSID can be taken from "q fi <node> f=d". You will avoid a lot of problems with cpecial characters in filespace name. Grigori G. Solonovitch Hi al
Author: "Huebschman, George J." <gjhuebschman AT LEGGMASON DOT COM>
Date: Wed, 5 Jan 2011 10:14:25 -0500
Charles, "... or a user with admin auth on the TSM server," That is the case. We have an account for TSM to run backups. The TSM Admins have the same admin authority as that account. Richard, I had d
Author: "Loon, EJ van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
Date: Thu, 20 Aug 2009 11:00:55 +0200
Hi Margaret! Thanks for your reply! We use TSMManager which uses NAMET=FSID by default for deleting filespaces... Kindest regards, Eric van Loon KLM Royal Dutch Airlines Did you try deleting by FSID?
Author: "Clark, Margaret" <MClark AT SDDPC DOT ORG>
Date: Mon, 13 Apr 2009 14:33:17 -0700
If there's nothing in the filespace that you need to keep, you can try this: delete filespace WHQ_FILESERV_1 2 nametype=FSID I've also been unable to delete filespaces using the filespace name, or in
Author: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
Date: Thu, 24 Jul 2008 13:35:20 -0400
Shawn thanks, We will begin testing the Point-in-Time method first to see how that works out. We may try Multiple Node backup sets for the individual file spaces also. ( we are only doing backup sets
Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
Date: Thu, 24 Jul 2008 11:37:02 -0400
"Which uses fewer tapes Point-in-Time backupsets or Multiple Nodes backupsets? " I don't think one has anything to do with the other. For example, we are performing multiple-node, point-in-time backu
Author: Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Date: Fri, 13 Jul 2007 10:01:23 -0400
a q node would show those clients that have not accessed the system in some time. You can run write a daily script that performs your select statement, and creates a report and a macro for deleting a
Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>
Date: Fri, 13 Jul 2007 09:47:29 -0400
You can run write a daily script that performs your select statement, and creates a report and a macro for deleting all the offending file systems. Then, if all looks good for deletion, just run the
Author: Stuart Lamble <adsm AT CAROUSEL.ITS.MONASH.EDU DOT AU>
Date: Fri, 13 Jul 2007 16:34:35 +1000
Hi all. Whilst investigating something else, we discovered a number of nodes that have old filespaces still stored within TSM - eg: Node Name: (node name) Filespace Name: /data Hexadecimal Filespace
Author: "Gill, Geoffrey L." <GEOFFREY.L.GILL AT SAIC DOT COM>
Date: Tue, 9 Jan 2007 16:10:31 -0800
Sorry for responding so late on this. Below are the message specifics I got yesterday when trying the move data. What I did notice was that I lost a disk, which crashed TSM again, and it looks to me
Author: Steven Harris <steve AT STEVENHARRIS DOT INFO>
Date: Wed, 13 Dec 2006 10:21:19 +1000
Hi Avy, While the filespace name is \\Eomron\e$, not \\mro1\e$ as you have specified, I have had trouble in the past with this and the fix is to use the FSID to identify which filespace to delete. In
Author: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
Date: Fri, 20 Jan 2006 09:24:41 -0500
Hello, I am still trying to set up a Admin Schedule to generate a backup set. I need to one have a backup set for one filespace/volume for a client. The other day I was able to generate a backup set