Table 5. Read policies
Feature
Description
Read Ahead
Allows the controller to read sequentially ahead of requested data
and to store the additional data in cache memory, anticipating that
the data is required soon. This speeds up reads for sequential data,
but there is slight improvement when accessing random data.
No Read Ahead
Disables the
Read Ahead
capability.
Adaptive Read Ahead
Adaptive read ahead is no longer supported. Selecting adaptive read
ahead is equivalent to selecting
Read Ahead
option.
Virtual disk migration
The PERC 10 series supports migration of virtual disks from one controller to another without taking the target controller offline. The
controller can import RAID virtual disks in optimal, degraded, or partially degraded states. You cannot import a virtual disk that is offline.
Disk migration pointers:
•
Supports migration of virtual disks from PERC H330, H730, H730P, and H830 to PERC 10 series
•
Supports migration of volumes created within PERC 10 series
•
Does not support migration from PERC 10 series to H330, H730, H730P, H830, H310, H710, H710P, H810
•
Does not support migration from H310, H710, H710P, and H810 to PERC10 series
NOTE:
The source controller must be offline prior to performing the disk migration.
NOTE:
Importing non-RAID drives and uneven span RAID 10 virtual disks from PERC 9 to PERC 10 are not supported.
NOTE:
Disks cannot be migrated to older generations of the PERC cards.
NOTE:
Importing secured virtual disks is supported as long as the appropriate Local Key Management (LKM) is supplied or
configured.
When a controller detects a configured physical disk, it flags the physical disk as foreign, and generates an alert indicating that a foreign
disk was detected.
CAUTION:
Do not attempt disk migration during RLM or online capacity expansion (OCE). This causes loss of the virtual disk.
Virtual disk initialization
PERC 10 series supports two types of virtual disk initialization:
•
Full Initialization
•
Fast Initialization
CAUTION:
Initializing virtual disks erases files and file systems while keeping the virtual disk configuration intact.
Full initialization
Performing a full initialization on a virtual disk overwrites all blocks and destroys any data that previously existed on the virtual disk. Full
initialization of a virtual disk eliminates the need for the virtual disk to undergo a Background initialization (BGI). Full initialization can be
performed after the virtual disk is created.
Features
21
