Joshua , TSM 4.2.1 Server . Ur help in this regard is highly appreciated. Client Ver 4.2.2.
I am facing a very odd problem with TSM. The TSM Server is running on a AIX operating system. The O/S Level on the Operating System is 4.3.3. The client windows 2000 was upgraded from 4.1 to 4.2.1 on the tsm side and as 4.2.2 does have Unicode filespace , the old filespace had to be renamed on the TSM Server , now once I renamed it , I am backing up all the other filespace but the only thing which TSM Server comes without backing up is the system object filespace. It gives this error on the client side:Since the Filespace for System Object could not be renamed i removed it and not i am not getting this System Object backed up, all other filespaces of this client is backing up. The TSM data base says J1P303(nodename) is WinNT 5.00, TSM client Version 4, Release 2, Level 2.0, and J1P304(nodename) is WinNT 5.00, TSM client Version 4, Release 1, Level 2.0. ANS1228E: 01/07/2003 01:58:55 fsCheckAdd: unable to update filespace on server. There is nothing else being backed up during this schedule for this node. Joshua Bassi <[EMAIL PROTECTED]> wrote:Yes, if you manually move it from one volume to another it will defrag. But that is a manual process. If you setup a reclamation threshold on a FILE disk pool, reclamation occurs automatically. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant -ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Salak Juraj Sent: Thursday, January 09, 2003 11:53 AM To: [EMAIL PROTECTED] Subject: Re: TSM Disk Pool Management would occasional move data (from disk to disk) not resolve this fragmentation issue? regards juraj Salak > -----Original Message----- > From: Joshua Bassi [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 09, 2003 8:17 PM > To: [EMAIL PROTECTED] > Subject: Re: TSM Disk Pool Management > > > Unfortunately disk pools with a device class of DISK get fragmented > and will incur a higher overhead penalty the longer they exist > (without data > moving off to tape). I had a customer try this configuration and it > ended up blowing up in their face. > > > -- > Joshua S. Bassi > IBM Certified - AIX 4/5L, SAN, Shark > Tivoli Certified Consultant -ADSM/TSM > eServer Systems Expert -pSeries HACMP > > AIX, HACMP, Storage, TSM Consultant > Cell (831) 595-3962 > [EMAIL PROTECTED] > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf > Of Andy Carlson > Sent: Thursday, January 09, 2003 11:09 AM > To: [EMAIL PROTECTED] > Subject: Re: TSM Disk Pool Management > > > We have given this a little bit of thought also. You would not need > to use type=file - just enlarge your current disk pool. Expire will > age the files out of there. The only thing to watch, is for it to be > getting full, and more disk needs to be added. > > > Andy Carlson |\ _,,,---,,_ > Senior Technical Specialist ZZZzz /,`.-'`' -. ;-;;,_ > BJC Health Care |,4- ) )-,_. > ,\ ( `'-' > St. Louis, Missouri '---''(_/--' `-'\_) > Cat Pics: http://andyc.dyndns.org/animal.html > > > On Thu, 9 Jan 2003, Hokanson, Mark wrote: > > > We are considering creating an extremely large TSM disk storage pool > > (IE: 1-10TB). The goal being to eliminate going to tape. Does anyone > > have any really BIG disk pools? Are there tools available > for managing > > > large TSM disk pools over time. (IE: Reclamation, Aging > Data, etc) The > > > documentation from Tivoli suggests that we need to set it up as a > > device type=FILE. What are the drawbacks using this approach? Is > > performance dramatically impacted? etc... > > > > Thanks in advance, > > > > Mark Hokanson > > Thomson Legal & Regulatory > > > --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
