We definitely will be looking at flash for our next TSM server refresh, but
unfortunately that's still 2-3 years out. When we bought our last round of
servers, SSDs were still prohibitive for the size of database we have
(~1.5TB).

On Wed, Jan 27, 2016 at 04:34:15PM +0000, Alford, Ben wrote:
> If you never move ANYthing else to Flash, move the TSM DB there.   As someone 
> else mentioned, it is like a religious experience.  Our expirations went from 
> 3 hours to 10 minutes.
>
> Ben Alford?
> IT Manager, Office of Information Technology
> The University of Tennessee
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Skylar Thompson
> Sent: Wednesday, January 27, 2016 11:07 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] When can too many disk volumes be detrimental
>
> I would actually keep DB and logs separate, avoid putting the DB on RAID-5 
> due to its high write penalty. We have our DB on 15K RPM SAS disks in 3x 
> 4-disk RAID-10 sets. The logs we keep on RAID-1 collocated with the OS, since 
> it's pretty low load and all sequential I/O.
>
> On Wed, Jan 27, 2016 at 11:02:25AM -0500, Zoltan Forray wrote:
> > The box came with 6-6TB drives and 4-slots empty. We moved 6-600GB SAS
> > drives into the empty slots and created another RAID5 array of ~1.7TB
> > for additional storage. Sounds like maybe we should move the
> > DB/logs/archlogs to it?
>
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine