Users Guide
l Loadbalance
l Auto replace member on predictive failure
l Re dundant path view
To locate this task in Storage Management, do one of the following:
1. Select Storage in the Storage tree.
2. On the Storage Dashboard page, select Change Controller Properties... from the Available Tasks drop down menu.
3. Click Execute.
Or:
1. Expand the Storage tree object to display the controller objects.
2. Select a controller object.
3. Select the Information/Configuration subtab.
4. Select Change Controller Properties... from the Controller Tasks drop down menu.
5. Click Execute.
Related Information:
l "Set Rebuild Rate"
l "Set Background Initialization Rate"
l "Set Check Consistency Rate"
l "Set Reconstruct Rate"
l "Abort check consistency on error"
l "Revertible Hot Spare"
l "Loadbalance"
l "Redundant Path Configuration"
Manage Preserved Cache
The Managed Preserved Cache feature provides you the option to ignore or restore the controller cache data.
In the write-back policy, data is written to the cache before being written to the physical disk. If the virtual disk goes offline or is deleted for any reason, the
data in the cache is lost.
Data in the cache may also be lost in case of unintended cable or power failure. In the event of such a failure, Storage Management preserves the data
written on the preserved or dirty cache until you recover the virtual disk or clear the cache.
This feature is available only on SAS controllers with firmware version 6.1 and later.
The status of the controller is affected by the preserved cache. The controller status is displayed as degraded if the controller has preserved cache.
Manage Preserved Cache
NOTE: You can set these properties through the command line interface also. See "omconfig Controller Commands" for more information.
CAUTION: You may not be able to use Storage Management to manage the preserved cache in some cases. As an example, consider you have a
RAID 1 level with two disks—D1 and D2. If you now remove D2, the virtual disk is degraded and the data in the controller cache is written to D1.
At this point, D1 has the latest data. Now, if you re-insert D2 and pull out D1, the virtual disk will still be degraded and will not have the latest
data.