Administrator Guide

RAID 6-6 (4 data segments, 2 parity segments for each stripe)
RAID 6-10 (8 data segments, 2 parity segments for each stripe.)
Redundancy Requirements
Drive size is used to determine the redundancy level to apply to a tier of drives. If any drive in a tier surpasses a threshold size, a specic
redundancy level can be applied to the tier containing that drive. If a redundancy level is required, the Storage Center operating system sets
the level and it cannot be changed.
Table 1. HDD Redundancy Recommendations and Requirements
Disk Size Level of Redundancy Recommended or Enforced
Up to 3 TB Dual redundant is the recommended level
NOTE: Non-redundant storage is not an option for
SCv2000 Series Storage Centers.
3 TB and higher Dual redundant is required and enforced
Table 2. SSD Redundancy Recommendations and Requirements
Disk Size Level of Redundancy Recommended or Enforced
Up to 18 TB Dual redundant is the recommended level
NOTE: Non-redundant storage is not an option for
SCv2000 Series Storage Centers.
18 TB and higher Dual redundant is required and enforced
Data Progression
Storage Center uses Data Progression to move data within a virtualized storage environment. Data Progression moves data between tiers
and drive types, as well as among multiple RAID levels within the same tier, for a constant balance of performance and cost.
How Data Progression Works
Once every 24 hours, Storage Center assesses disk use and moves data to disk space that is more ecient for the data usage. By default,
Data Progression runs each day at 7 PM system time, but the timing of the run can be changed in the Storage Center settings. Data
Progression behavior is determined by the storage prole applied to each volume. Data progression runs until it completes or reaches the
maximum run time.
NOTE
: With SCv2000 series controllers, Data Progression moves data between RAID 10 and RAID 5/6 and restripes RAID, but
does not move data between storage tiers.
Data Progression and Snapshots
Storage Center also uses Data Progression to move snapshots. When a snapshot is created, either as scheduled or manually, the data is
frozen and moved to the tier specied by the storage prole to hold snapshots.
Snapshots can occur as a scheduled event according to the snapshot prole, manually by creating a snapshot, or on demand by Storage
Center to move data o of Tier 1 in a ash-optimized storage type.
Storage Center Overview
49