I'm fairly sure I remember an IBM recommendation that suggested you should try to have broadly as many individual disk volumes defined in a stgpool as you will have concurrent client sessions writing to that stgpool.
David McClelland London On 3 May 2010, at 13:48, Howard Coles <[email protected]> wrote:
Smaller storage pool volumes and more of them. Then TSM only has to open and use what it needs at the time, and more processes can be run successfully at the same time. Of course this all depends on how much RAM and processor power you have as well. The Single LUN shouldn't be a problem as long as you have a good queue depth, but I would definitely break up the pool into multiple volumes. See Ya' Howard Coles Jr. John 3:16! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Mehdi Salehi Sent: Sunday, May 02, 2010 10:56 PM To: [email protected] Subject: Re: [ADSM-L] mediawait during backup to disk - One point is that you gain virtually nothing by 6 volume groups. You can put the six LUNs in a single VG, no performance difference I believe. - Have you tuned the queue_depth of the LUNs based on AMS documentation. Check it by "lsattr -El hdiskX" Here is my question from the group: Which one performs better? a- One big TSM volume on a 2TB LUN b- More than one TSM volumes on a 2TB LUN Thanks
