User manual TYAN BROADCOM HT1000

[. . . ] User Manual BC4000 RAIDCoreTM BC4000 Series RAID Controllers BC4000-UM100-R 16215 Alton Parkway · P. O. Box 57013 · Irvine, CA 92619-7013 · Phone: 949-450-8700 · Fax: 949-450-8710 02/13/06 REVISION HISTORY Revision BC4000-UM100-R Date 02/13/06 Change Description Initial release; describes version 2. 1 of XelCoreTM software and the BC4000 Series of hardware controllers (which includes HT-1000 controllers). Broadcom Corporation P. O. Box 57013 16215 Alton Parkway Irvine, CA 92619-7013 © 2006 by Broadcom Corporation All rights reserved Printed in the U. S. A. Broadcom ®, the pulse logo, Connecting everything®, and the Connecting everything logo are among the trademarks of Broadcom Corporation and/or its affiliates in the United States, certain other countries and/or the EU. Any other trademarks or trade names mentioned are the property of their respective owners. [. . . ] To protect this data, you must first transform the array to a redundant array type (see "Transforming Arrays" on page 84). You can then assign spares. USING DISTRIBUTED SPARING RAIDCore's proprietary distributed sparing feature reserves space on each drive in an array. This space is used when the data from a failed drive is being regenerated during a restore task. Whereas other methods of sparing (such as dedicated spares) provide the same level of protection, distributed sparing provides better performance because all drives are active in an array and are not sitting idle, as is the case with dedicated spares. Another advantage of distributed spares is that because all drives are active, a drive cannot fail and go unnoticed, as is the case with dedicated or global spares. This is because with distributed sparing, each array has its own dedicated fail-over spaces. This averts the potential problem of having insufficient space to start a fail-over on the single disk that has been assigned as a spare. A distributed spare is assigned at the time an array is created or transformed. Distributed spares are valid only for RAID5 (four or more drives), RAID50 (four or more drives per RAID5 set), and RAID10 and RAID10n (six or more drives). This spare type is the most protective because space is allocated when the array is created. Like a dedicated spare, this spare type is assigned to a specific array. If you initially created an array without a distributed spare, you must transform the array to add a distributed spare. This is because a distributed spare can be assigned only when an array is being created or transformed. B ro ad c om C o rp or at ion Document BC4000-UM100-R Working with Spares Page 47 BC4000 Series RAID Controllers User Manual 02/13/06 Notes: · If there is insufficient unused space on the disks in an array, you cannot add a distributed spare without adding an additional disk and transforming to an array with distributed sparing enabled. The distributed spare option uses the equivalent storage of one of the disks in the array. For example: the total capacity of six drives is being used in a RAID5 array, and you have enabled distributed sparing. The capacity of one disk is lost to the RAID5 parity data, and the capacity of another disk is lost to the distributed sparing option. From RAIDConsole, see "Adding or Removing Distributed Spares" on page 97 to add or remove a distributed spare. From bcadm, see "Creating New Arrays: bcadm --create" on page 130. To add a distributed spare while creating an array: 1. In the Distributed Spare field, click Enabled. To add a distributed spare while transforming an array: 1. In the Distributed Spare field, click Enabled. To remove a distributed spare: 1. In the Distributed Spare field, click Disabled. B ro ad c om C o rp or at ion Page 48 Working with Spares Document BC4000-UM100-R User Manual 02/13/06 BC4000 Series RAID Controllers USING DEDICATED SPARING A dedicated spare is a disk that you assign as an alternate disk for a specific array. Should a disk fail in that array, the alternate disk is used to replace the failed disk and the array is rebuilt. [. . . ] The OS Name is set to "none" because the OS cannot see this array. . . . <ARRAY LIST> A Type OS Name Sys State Size Hide Id Task Task State % CA Scan Name -- ------- ---------- --- --------- ------- ---- ------------------ ------------ ------------- ----- -- ---- ------------------------------1 VOLUME 1 No NORMAL 1. 0GB NO 0x58746de30b9154bb NOT_ACTIVE . . . RW No . . . Command 14: Assign array 1 the label "old mirror. " bcadm -M -a 1 -n "Old Mirror" B ro a dc om Co rp o ra tio n Document BC4000-UM100-R Page 154 Example bcadm Usage with Output User Manual BC4000 Series RAID Controllers 02/13/06 Command 15: Assign array 3 the label ""new split. " bcadm -M -a 3 -n "New Split" Command 16: Query again the status of all arrays. bcadm -M -q -a "*" Command 16 output: Arrays 1 and 3 are now named. . . . <ARRAY LIST> A Type OS Name Sys State Size Hide Id Task Task State % CA Scan Name -- ------- ---------- --- --------- ------- ---- ------------------ ------------ ------------- ----- -- ---- ------------------------------1 VOLUME 1 No NORMAL 1. 0GB NO 0x58746de30b9154bb NOT_ACTIVE . . . RW No Old Mirror 2 RAID5 2 No NORMAL 1. 0GB NO 0x3e66719344426476 NOT_ACTIVE . . . RW No New Split Command 17: Unhide array 3. bcadm -M --unhide -a 3 Command 18 output: Array 3 is unhidden. array 3 un-hidden Command 18: Query the status of array 3. bcadm -M -q -a 3 B ro a dc om Co rp o ra tio n Example bcadm Usage with Output Page 155 Document BC4000-UM100-R BC4000 Series RAID Controllers 02/13/06 User Manual Command 18 output: Array 3 is now visible to the operating system, and the OS name has changed from "none" to "3. " . . . <ARRAY LIST> A Type OS Name Sys State Size Hide Id Task Task State % CA Scan Name -- ------- ---------- --- --------- ------- ---- ------------------ ------------ ------------- ----- -- ---- ------------------------------3 VOLUME 3 No NORMAL 1. 0GB NO 0x0b9b59b372c3a93a NOT_ACTIVE . . . [. . . ]