|
Well,
first of all, you can't add 8 gig drives to a RAID set composed of 4 gig drives
because all drives in a RAID set must be composed of drives of the same size and
type. You can create a new RAID set with the new arms but they cannot be
part of the existing set composed of 4 gig drives. Presumably, your
existing IOP will support two RAID sets.
Someone else will post the details but, in general, you can indicate that
drives 9 and 10 in the existing RAID set are being withdrawn and that you want
the data that they current contain to be spread over drives 1 through 8 in the
RAID set. STRSST then work with disk.
Be
advised, if you have any periods of very heavy disk insert, update, or delete
and if there is only one disk IOP for all your RAID disk then you run the risk
of overloading the disk IOP that is supporting you RAID sets with RAID
computations. If your database is journaled, there is a "doubling" effect
- the effect of each insert/update/delete causes a write to the database and
another write to the journal. Since the database and journals are in RAID
sets, each write (journal and database) causes two reads and two writes -
the reads overlap and the writes overlap. All of this IO can be very hard
on your disk subsystem.
Using
the normal defaults, your current system has 48 gb with 40 usable and 36.8 gb of
data and programs and so forth. When you are done, you will have a total
of 108 gb with 87.42 gb of usable space therefore your projected disk space
utilization will be 42 percent. You should rebalance that data across all
the disk arms. If DSKBAL isn't available, you will need to unload then
reload in order to balance the storage. If you don't rebalance, you will
see very heavy utilization of the new (empty) drives when objects are
created.
Richard Jackson
|
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.