A server setup question
Posted in 2000
Topics: Performance & Tuning
Hello, everyone, I am in the process of migrating a database server to a new UNIX box, and I'd like some opinions on the best way to lay out the disk. The specifics of the new hardware/software are: * Sun E3500 with 4 CPU's * A5200 StorEdge array with 8-18 GB disks (100MB per second fiber channel) * Veritas Volume Manager The database is used for a data warehouse-type application, with no more than 2 dozen or so simultaneous connections. Currently the database stores about 21GBs, and I expect it to grow at least another 8 or 10 GB. The database itself is rather straightforward, with 6 really large tables and around 20 small tables. Specifically, I'd like opinions on how to best set up the disks for both performance and fault tolerance. Thank you in advance for your advice.
Vickey Crouch wrote: > > Hello, everyone, > > I am in the process of migrating a database server to a new UNIX box, > and I'd like some opinions on the best way to lay out the disk. The > specifics of the new hardware/software are: > > * Sun E3500 with 4 CPU's > * A5200 StorEdge array with 8-18 GB disks (100MB per second fiber > channel) > * Veritas Volume Manager > > The database is used for a data warehouse-type application, with no > more than 2 dozen or so simultaneous connections. Currently the > database stores about 21GBs, and I expect it to grow at least another 8 > or 10 GB. The database itself is rather straightforward, with 6 really > large tables and around 20 small tables. Specifically, I'd like > opinions on how to best set up the disks for both performance and fault > tolerance. Set up a three pair RAID10 array and mirror RAID1) the remaining pair. Place your rootdbs, logical logs, and physical log dbspaces (three separate ones on separate VM partitions, not using offsets, so you can easily move them later if you get more disks) on the singleton RAID1 pair. Create 27 2GB partitions on the RAID10 array and use them to create multiple dbspaces, one for small static tables, one for small dynamic tables and several to fragment the larger tables over. Remember to use symbolic links for all chunk paths so you can move them later if needed. Use the balance of the mirrored pair for any quiet filesystems you will need including 3 small temp filesystems for use by PSORT_DBTEMP. Art S. Kagel