>>From Steven Schraer:
>>It looks like for storage pools are recommend for raid 0 
>>(mirroring), raid
>>0+1 (mirroring & stripping) or raid 5 (distributed parity).  
>>These are 0+safe
>>methods to protect the storage pool.  Do you know of any 
>>companies that use just raid 1 (stripping) on their storage 
>>pools?  Is there an issue of tsm loosing a storage pool and 
>>the database having issues due to the lost storage pool data?

From: William Rosette [mailto:Bill_Rosette AT PAPAJOHNS DOT COM] 
> Does any TSM gurus have any suggestions for our AIX admin

[donning my advocacy armor]
I still don't see any reason to create redundancy for the disk storage
pool. Unless you're not using a tape library, there's no reason for it.
The disk pool should get flushed to a more stable medium, and that flush
should take place fairly soon after the client backups to disk finish.
Why waste gobs of disk on something that's going to flushed clear every
day?

As far the db and log are concerned, just create volume copies with TSM
and make sure the copies are on disks that are on separate disks.

That's really all there is to it.

--
Mark Stapleton (stapleton AT berbee DOT com)