Users Guide

prepares the virtual disk to maintain redundant data and improves write performance. For example, after
the background initialization of a RAID 5 virtual disk completes, the parity information has been initialized.
After the background initialization of a RAID 1 virtual disk completes, the physical disks are mirrored.
The background initialization process helps the controller identify and correct problems that may occur
with the redundant data at a later time. In this regard, the background initialization process is similar to a
check consistency. The background initialization should be allowed to run to completion. If cancelled,
the background initialization automatically restarts within 0 to 5 minutes. Some processes such as read
and write operations are possible while the background initialization is running. Other processes, such as
creating a virtual disk, cannot be run concurrently with a background initialization. These processes cause
the background initialization to cancel.
The background initialization rate, configurable between 0% and 100%, represents the percentage of the
system resources dedicated to running the background initialization task. At 0%, the background
initialization has the lowest priority for the controller, takes the most time to complete, and is the setting
with the least impact to system performance. A background initialization rate of 0% does not mean that
the background initialization is stopped or paused. At 100%, the background initialization is the highest
priority for the controller. The background initialization time is minimized and is the setting with the most
impact to system performance.
Check consistency
The Check Consistency task verifies the accuracy of the redundant (parity) information. This task only
applies to redundant virtual disks. When necessary, the Check Consistency task rebuilds the redundant
data. If the virtual disk is in a Failed Redundancy state, running a check consistency may be able to return
the virtual disk to a Ready state.
The check consistency rate, configurable between 0% and 100%, represents the percentage of the
system resources dedicated to running the check consistency task. At 0%, the check consistency has the
lowest priority for the controller, takes the most time to complete, and is the setting with the least impact
to system performance. A check consistency rate of 0% does not mean that the check consistency is
stopped or paused. At 100%, the check consistency is the highest priority for the controller. The check
consistency time is minimized and is the setting with the most impact to system performance.
Create or change security keys
When configuring the controller properties, you can create or change the security keys. The controller
uses the encryption key to lock or unlock access to SED. You can create only one encryption key for
each encryption-capable controller. The security key is managed using the Local Key Management (LKM)
feature. LKM is used to generate the key ID and the password or key required to secure the virtual disk. If
you are using LKM, you must create the encryption key by providing the Security Key Identifier and the
Passphrase.
This task is not supported on PERC hardware controllers running in HBA mode.
If you create the security key in Add to Pending Operation mode and a job is not created, and then if you
delete the security key, the create security key pending operation is cleared.
Configuring controller properties using web interface
1. In the iDRAC web interface, go to Overview → Storage → Controllers → Setup.
238