Dot Hill Systems RAIDCore, User Manual

Page: 18 / 134

16 Chapter 2 Getting Started
Features of RAIDCore
The features of RAIDCore described in this user manual apply to all license levels and supported operating
systems. See
Supported Operating Systems on page 15.
The following table describes these features. Also see Table 4 on page 21 for a summary of features that are
available with each license level of RAIDCore: RAIDCore Basic, RAIDCore Plus, and RAIDCore VST.
Table 3 Features of RAIDCore
RAIDCore Feature Description
Arrays (general information) RAIDCore allows:
• Creating arrays of different RAID levels using the same
disks.
NOTE:
RAID 5 is supported by RAIDCore Plus and
RAIDCore VST. RAID 1n, 10n, and 50 are supported by
RAIDCore VST.
• Creating different RAID level arrays on the same disk, to
adapt each array to the I/O that it processes.
• Creating an array from a mix of different-type disks. For
example, a RAID 10 array can be created from a group of
disks that contain two SATA II HDDs, a SAS HDD, and a
SATA SSD.
• Migrating an existing array to another RAID level, if the type
of array being used is not the optimal type for the application.
This function depends on the array capacity and redundancy
level.
A array refers to data storage created by RAIDCore from one or
more disks. Although an array can be created from several disks, it
is seen by the operating system as a single disk.
Array copying The Copy option is used to create a new array that contains an exact
copy of the data on a source array. It combines the Create Array and
Copy Array functions into a single command.
NOTE:
This feature is available only with RAIDCore
VST. See Copy Arrays (supported only by RAIDCore VST)
on page 80.
Array hiding An array can be hidden from the operating system so that neither
the software nor users can see or access it. This is a key element in
creating secure data backups.
Array recovery If an array is accidentally deleted, it can be recovered by creating a
new array with the same properties as the deleted array. This can
occur only if disk Write Access operations are not in-progress.