Chris,

I would create a "stripped logical volume"  using as many disk as possible
(the more the better) in the Volume Group.  Also, do not create a
filesystem just leave the Logical Volume in the Volume Group.  This will
keep you from having to deal with the AIX JFS overhead.  When you define
your volumes to the disk storage pool point it to the (r)logical volume
name.  For instance if you create a logical volume in the volume group
named tsmstg1lv, then in TSM define you volume /dev/rstmstg1lv  to the disk
storage pool. This will give you some awesome throughput.

On the flip side when you do your migration to tape you will be doing
mostly sequential reads from the disk storage pools so the can keep the
tape drive(s)  running at max write speed.

Rich Brohl
ISM Support
Tie Line      547-9317
Direct  303-693-4969
Pager 888-524-9030


chris rees <rees_chris AT HOTMAIL DOT COM>@VM.MARIST.EDU> on 05/09/2002 08:46:02
AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:    "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:    ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:    comments on disk storage plan


Hi all,

Just wanted to sanity check my disk storage pool layout I'm planning.

AIX 4.3.3
Server H80
2 x D40 SSA drawers, two loops over two SSA 160 adapters
32 x 9Gb SSA disks
Max nodes backing up at any one time is approx 6

I don't want to mirror the volumes

32 x 9Gb logical volumes, each logical volume on one SSA disk. These lvs
will then translate into 32 disk storage pool volumes. This way if I have a
disk failure I only lose one disk pool volume.

Anyone got any ideas what kind of read/write performance I should expect to
see from this config?

Any other options considered.

Regards

Chris



_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.