Either A or B will work, but on an MD3000 you'll have to add the additional disks to the diskgroup in the GUI 1 disk at a time.
Option A will take hours to days, depending on the disk sizes, disk spindle speeds and production IO. After growing the diskgroup you can either extend the virtual disk(s) or create new virtual disks. The option to grow a virtual disk is command line only (smcli (part of the storage manager software install)).
Option B will be available nearly immediately (but the virtual disk will be scrubbing, so it'll not be full performance potential till it's done), but you will need to move some of your data to the second disk (do not use dynamic disk to merge the 2 disks into a single drive letter if you're using Windows).
Performance wise a raid 5 is best off limited to 6 or 7 drives. With 7200 rpm drives, once you get to 6 or 7 drives and cannot afford to make a separate/2nd raid 5, I'd recommend raid 6 instead of raid 5.
Dev Mgr
4 Operator
•
9.3K Posts
0
April 7th, 2014 09:00
Either A or B will work, but on an MD3000 you'll have to add the additional disks to the diskgroup in the GUI 1 disk at a time.
Option A will take hours to days, depending on the disk sizes, disk spindle speeds and production IO. After growing the diskgroup you can either extend the virtual disk(s) or create new virtual disks. The option to grow a virtual disk is command line only (smcli (part of the storage manager software install)).
Option B will be available nearly immediately (but the virtual disk will be scrubbing, so it'll not be full performance potential till it's done), but you will need to move some of your data to the second disk (do not use dynamic disk to merge the 2 disks into a single drive letter if you're using Windows).
Performance wise a raid 5 is best off limited to 6 or 7 drives. With 7200 rpm drives, once you get to 6 or 7 drives and cannot afford to make a separate/2nd raid 5, I'd recommend raid 6 instead of raid 5.