Hi David!
We are not there yet, but we will also use an ESS for the database volumes
in the very near future.
The way which TSM uses it's database (which isn't very intelligent by the
way) makes it very important to allocate as much volumes as possible. So
rather 20 small ones than two large volumes. Each client session or server
transaction locks a database volume, so if you want to minimize contention,
allocate as much volumes as possible.
>From experience I noticed that TSM performs better with 2 database volumes
on one physical disk than with one larger volume taking up the whole disk.
This seems rather strange (you want to prevent excessive head movements
between the two volumes on the same disk) but I have proven in practice that
the TSM database performs better!
So depending on your LUN size you can create one or more database volumes
per LUN.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: David E Ehresman [mailto:deehre01 AT LOUISVILLE DOT EDU]
Sent: Monday, May 02, 2005 17:50
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM db on ESS (shark) disk
Is there a definitive recommendation for the best way to lay out TSM DB
files on ESS disk? The ESS is raid 5; I have no control over placement. Is
it best to do one or two large db "volumes" or many smaller db "volumes".
My db is current 59 gig and I will be increasing it to about 100 gig.
David Ehresman
University of Louisville
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
its subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible for
any delay in receipt.
**********************************************************************
|
