>Correct. This machine has 8-internal 600GB 15K drives. The OS and DB are >on one pair of mirrored drives. The log and archlog share the rest of >the internal drives in a raid-10 (I think) array plus leaving extra space >to DB expansion (one server I plan to migrate to these new 6.2 servers has >a DB size of 190GB which comes to a minimum of ~600GB when converted from >5.5). The file devclass is SAN storage in a Claiiron box. There are >3-Qlogic HBA cards. 1-for disk and the other 2-for tape but only 1-in use >due to lack of switch-ports.
What is the performance of the mirrored drives during migration? 2 mirrored drives (i/o performance of one drive unless both can be used for reads) may not be enough iops for the updates needed during migration. In other words, you may be bottlenecked on the db drives. What kind of storage does the clariion have? Are there enought spindles to put the file pool on a different raidset than db/log? All our TSM instances run to Clariion or DMX (mostly clariion) where disk pools and db/logs use the same HBA's (2 of the). We get excellent performance. If possible, I would put the db/log on the clariion - It will be faster than the internal drives. You get right back cache, and some read caching. In fact, I'm to the place where I don't care where the db/log/pools are in the clariion - we just wide spread everything across all raidsets and get excellent performance. Also, what is the utilization of the log drives? Are they sitting idle most of the time? If so, then those are wasted iops. You could use more for the db and less for the logs. Logs are mostly sequential and don't need much iops, which are much better used for the db (random access). Rick ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
