Re: TSM Disk Pool Management

2003-02-21 Thread John Underdown
Manuel,

The remote copypool ended up being NetWare 6, i can serve up a 8TB volume to TSM with 
Novell Storage Services (NSS). NetWare's Common Internet FileSystem (CIFS) allows TSM 
access without loading a NetWare client on the TSM server. 

i chose this approach because copypools can only access sequential media, so NAS was 
my only option. It also appears copypools can only have a single device which limited 
me to one NAS volume per copypool. Windows volumes have a limit of 2TB which was too 
small for my backuppool, short of having to break it up into multiple 2TB  backuppools 
and copypools, i decide to use NetWare to get around this, we are also a NetWare shop 
so this was a no brainier.

Everything seems to working fine so far but it's still new. I also have another 7TB of 
ATA disk arrays on order that should get here in a couple of weeks, the price is now 
down to ~$3,000/TB. 

Let me know how this solution sound to you and also let me know what you decide to go 
with.

Thanks,

john



 [EMAIL PROTECTED] 02/20/03 09:03AM 
John,
I read your message on adsm.org Mailing List.
I wonder if you implemented the remote copy pool.
We are considering a similar solution, and we are talking to DataCore and
FalconStor.
Thanks,
Manuel J. Sanchez

Assurant Group
(305) 252-7035 x32153
[EMAIL PROTECTED]



-
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of this 
communication is strictly prohibited. If you received this in error, please
reply immediately and delete the material from all computers. Email sent 
through the Internet is not secure. Do not use email to send us confidential
information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and 
confidential information.



Re: TSM Disk Pool Management

2003-01-31 Thread John Underdown
Hi Wanda,

We still use tape for the copypool, but this is now not a viable DR solutions due to 
the time factor to restore from tape. We are presently evaluating ISCSI and NAS 
solutions for a disk copypool at a remote site, using 1Gb Ethernet (we have dark fibre 
to our DR site). The two ISCSI products we have evaluated so far are Ipstor from 
Falconstor and SANsympthony from DataCore, both are great products. The NAS solutions 
we are presently looking at is NetWare 6's NSS (with CIFS since our TSM Server is 
W2K), it's looking really good since is can server up a 8TB volume and the copypool 
can use a device type of FILE. Novell's solution is also the most affordable (free 
since we are a big NetWare shop). Our Audit department has already given us the OK to 
go to disk for the copypool as long as it's offsite. I'll backup the db to the offsite 
storage also, so in theory if we lose our TSM server, i can build a new one restore 
the DB from the remote site and start doing restores immediately from the copypool, if 
the backupool is gone TSM automatically pulls files from the copypool. I hope to have 
this all in place in the next couple months (if not sooner) using ATA drive 
enclosures, right now i can get 3.2 TB for $10,000. i have $25,000 in the budget, so 
if i go with the NetWare NAS i should easily make it.

Let me know how this all sounds to you or if you have any further questions.

john
Synovus

 Prather, Wanda [EMAIL PROTECTED] 01/30/03 05:11PM 
Hi John,

We have also starting looking at an all disk backuppool for the future.
I am curious how you handle:

1) backups of your DB
2) disaster recovery planning/offsite backups

Thanks!
Wanda Prather
Johns Hopkins Applied Physics Lab


-Original Message-
From: John Underdown [mailto:[EMAIL PROTECTED]] 
Sent: Friday, January 10, 2003 8:50 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Disk Pool Management


Mark,

We been using a all disk backuppool for a number of years now. It's grown to
4TB, we just keep adding disk expansion to the server as we need more
storage (We are now looking at the new ATA Raid Expansion Cabinets 3TB for
$10,000).  We backup 377 servers (80 to 100 GB total) nightly and growing.
The TSM database is 15GB sitting on raid 10 with 15K rpm drives (very fast)
, i also defrag the DB monthly. This is a dream setup and works very well,
restores run in the blink of a eye. I run the TSM server  by myself as a
part-time duty. The only problem you'll have is figuring out what to do with
all your free time.

The is a common topic on the list, search the achives at www.adsm.org. Let
me know if you have any questions.


John
Synovus
Synovus Makes FORTUNE '100 Best Companies To Work For' in America For Sixth
Straight Year.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Hokanson, Mark
Sent: Thursday, January 09, 2003 7:15 AM
To: [EMAIL PROTECTED]
Subject: TSM Disk Pool Management


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



-
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of this 
communication is strictly prohibited. If you received this in error, please
reply immediately and delete the material from all computers. Email sent 
through the Internet is not secure. Do not use email to send us confidential
information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and 
confidential information.



-
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of this 
communication is strictly prohibited. If you received this in error, please
reply immediately and delete the material from all computers. Email sent 
through the Internet is not secure. Do not use email to send us confidential
information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and 
confidential information.



Re: TSM Disk Pool Management

2003-01-10 Thread John Underdown
Mark,

We been using a all disk backuppool for a number of years now. It's grown to 4TB, we 
just keep adding disk expansion to the server as we need more storage (We are now 
looking at the new ATA Raid Expansion Cabinets 3TB for $10,000).  We backup 377 
servers (80 to 100 GB total) nightly and growing. The TSM database is 15GB sitting on 
raid 10 with 15K rpm drives (very fast) , i also defrag the DB monthly. This is a 
dream setup and works very well, restores run in the blink of a eye. I run the TSM 
server  by myself as a part-time duty. The only problem you'll have is figuring out 
what to do with all your free time.

The is a common topic on the list, search the achives at www.adsm.org. Let me know if 
you have any questions.


John
Synovus
Synovus Makes FORTUNE '100 Best Companies To Work For' in America For Sixth Straight 
Year.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Hokanson, Mark
Sent: Thursday, January 09, 2003 7:15 AM
To: [EMAIL PROTECTED]
Subject: TSM Disk Pool Management


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



-
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of this 
communication is strictly prohibited. If you received this in error, please
reply immediately and delete the material from all computers. Email sent 
through the Internet is not secure. Do not use email to send us confidential
information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and 
confidential information.



Re: TSM Disk Pool Management

2003-01-10 Thread John Underdown
Mark,

Yep. Retention is 30 days. Device type is Disk, don't use File because you have to 
manage the volumes like tape and that takes extra work. i've never had a problem with 
fragmentation, i suppose it's possible if you make your disk volumes very small, my 
disk volumes are 200Gb each and my backuppool Pct Util has run in the high 90's with 
no problems. 

Has far as keeping my storage small is where i really have to get creative. First, all 
clients compress data (don't turn on compress always because already compressed 
files will grow), that way files are stored compressed on the disk pools. Second and 
most important use global excludes so you don't backup any thing you don't need. One 
of the biggest saving was not backing up indexes for Groupwise Databases, all 
groupwise admin's know if they restore a DB they have to reindex, the indexes take up 
much more space than the DB's themselves. i also exclude temp files and 
subdirectories, recycle directories, and salvage directories on NetWare Servers. If it 
wasn't for my creative use of excludes my storage requirements for backups would be 
much greater. You need to do a lot of work with users, administrators, and dba's to 
get backups down to the bare minium. 

Let me know if you have any other questions.

John
Synovus

 Hokanson, Mark [EMAIL PROTECTED] 01/10/03 10:22AM 

John,

So all of your backup data is on the disk and none ever goes to tape? What is your 
retention? Are you device type file? How do you handle storage pool fragmentation? 
With 377 servers at 100gB nightly it seems you would fill your 4TB with about 40 day 
retention, correct?

Thanks a lot for your help,

Mark


 -Original Message-
From: John Underdown [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 10, 2003 7:50 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: TSM Disk Pool Management


Mark,

We been using a all disk backuppool for a number of years now. It's grown to 4TB, we 
just keep adding disk expansion to the server as we need more storage (We are now 
looking at the new ATA Raid Expansion Cabinets 3TB for $10,000).  We backup 377 
servers (80 to 100 GB total) nightly and growing. The TSM database is 15GB sitting on 
raid 10 with 15K rpm drives (very fast) , i also defrag the DB monthly. This is a 
dream setup and works very well, restores run in the blink of a eye. I run the TSM 
server  by myself as a part-time duty. The only problem you'll have is figuring out 
what to do with all your free time.

The is a common topic on the list, search the achives at www.adsm.org. Let me know if 
you have any questions.


John
Synovus
Synovus Makes FORTUNE '100 Best Companies To Work For' in America For Sixth Straight 
Year.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
Hokanson, Mark
Sent: Thursday, January 09, 2003 7:15 AM
To: [EMAIL PROTECTED]
Subject: TSM Disk Pool Management


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





NOTICE: This communication is intended only for the person or entity to whom it is 
addressed and may contain confidential, proprietary, and/or privileged material. 
Unless you are the intended addressee, any review, reliance, dissemination, 
distribution, copying or use whatsoever of this communication is strictly prohibited. 
If you received this in error, please reply immediately and delete the material from 
all computers. Email sent through the Internet is not secure. Do not use email to send 
us confidential information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and confidential 
information.



-
NOTICE: This communication is intended only for the person or entity to
whom it is addressed and may contain confidential, proprietary, and/or
privileged material. Unless you are the intended addressee, any review,
reliance, dissemination, distribution, copying or use whatsoever of this 
communication is strictly prohibited. If you received this in error, please
reply immediately and delete the material from all computers. Email sent 
through the Internet is not secure. Do not use email to send us confidential
information such as credit card numbers, PIN numbers, passwords, 
Social Security Numbers, Account numbers, or other important and 
confidential information.



TSM Disk Pool Management

2003-01-09 Thread Hokanson, Mark
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



Re: TSM Disk Pool Management

2003-01-09 Thread Joshua Bassi
I have a customer with 9 TSM servers and around 20TB of disk pool
storage.  We use a device class of DISK because data does not stay on
disk, instead it moves off to tape daily.

If you plan to use this large diskpool to permanently store your backup
data, then you should definitely use a devclass of FILE.  Why?  Because
FILE is sequential and the DISK device class is random.  Over time a
DISK storage pool will fragment as expiration occurs and TSM doesn't
automatically do a reorg on it like it can with a sequential FILE disk
pool.


--
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
Hokanson, Mark
Sent: Thursday, January 09, 2003 7:15 AM
To: [EMAIL PROTECTED]
Subject: TSM Disk Pool Management


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



Re: TSM Disk Pool Management

2003-01-09 Thread Andy Carlson
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




Re: TSM Disk Pool Management

2003-01-09 Thread Joshua Bassi
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




Re: TSM Disk Pool Management

2003-01-09 Thread Salak Juraj
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
 




Re: TSM Disk Pool Management

2003-01-09 Thread Joshua Bassi
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
 




Re: TSM Disk Pool Management

2003-01-09 Thread Lawrence Clark
Storage pools can be type random ( disk). We still need to migrate to
cartridge but we have about 13 16GB disk areas set up and allocated to
various storage pools as the primary pools which migrate to tape.
There's no reason, with sufficient space, that you could not hold your
backups on disk, but if you lose the disk you lose the backups.

 [EMAIL PROTECTED] 01/09/03 02:52PM 
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
 




Re: TSM Disk Pool Management

2003-01-09 Thread Sunil Nair
 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