Maximum data protection, but slower performance.
|
Maximum performance for the unit, but less data protection.
|
||
FUA (Force Unit Access)
|
Honor FUA (If no BBU is present)
Ignore FUA (If BBU is present)
|
Honor FUA (If no BBU is present)
Ignore FUA (If BBU is present)
|
|
Disabled, if no BBU present. (Enabled, if BBU is present.)
|
Disabled (If BBU is present, this essentially disables the BBU for this unit.)
|
||
Disable Cache on Degrade
|
|
FUA (Force Unit Access). The FUA bit is a way that the RAID controller or a program (such as a database program) can ensure that data is actually written to the disk drive media, and is not stored in cache. When a write command has the FUA bit set, then the disk drive will only issue “command complete” to the controller once the data is written to media. When performance is considered more important than protection, it may be desirable to ignore the FUA bit.
|
|
Write Journaling. Write journaling tracks the writing of data to disk and preserves a copy of data that has not yet been written to the disk media. Following a power failure or in the event of accidental drive removal and reinsertion, the firmware can recover the unit without data loss. All pending writes sitting in the controller cache are replayed after power is restored or the drive is reinserted and are flushed from the controller to the drive.
|
|
Write cache disabled on degrade. In the event that a unit degrades, the use of write cache can be disabled until the unit is rebuilt. Once the unit is rebuilt, the write cache will automatically be re-enabled.
|
1
|
Choose Management >> Controller Settings from the menu bar in 3DM2.
|
2
|
In the Unit Policies section of the Controller Settings page, select the profile you want to use from the drop-down list in the StorSave column.
|
LSI Corporation |
Copyright LSI 2004-2010
To contact Support, go to http://www.lsi.com/channel/ContactUs