User Capacity (Logical Capacity)............................................................................................................................22
Hot Spares.............................................................................................................................................................28
Data Protection............................................................................................................................. 31
Data Block Guard ..................................................................................................................................................31
Disk Drive Patrol....................................................................................................................................................33
Fast Recovery ........................................................................................................................................................36
Extreme Cache Pool ..............................................................................................................................................56
Optimization of Volume Configurations ........................................................................................ 57
Data Encryption ............................................................................................................................ 66
Encryption with Self Encrypting Drive (SED)..........................................................................................................67
Firmware Data Encryption.....................................................................................................................................68
Key Management Server Linkage..........................................................................................................................69
User Access Management ............................................................................................................. 72
User Authentication ..............................................................................................................................................74
Power Consumption Visualization .........................................................................................................................80
Device Time Synchronization.................................................................................................................................87
Power Control ............................................................................................................................... 88
Power Synchronized Unit.......................................................................................................................................88
Remote Power Operation (Wake On LAN) .............................................................................................................89
Stable Operation via Load Control............................................................................................... 122
Quality of Service (QoS).......................................................................................................................................122
Server Linkage Functions ............................................................................................................ 132
Oracle VM Linkage ..............................................................................................................................................132
Microsoft Linkage................................................................................................................................................141
LAN Connection .......................................................................................................................... 153
LAN for Operation Management (MNT Port) .......................................................................................................153
LAN for Remote Support (RMT Port)....................................................................................................................155
LAN Control (Master CM/Slave CM)......................................................................................................................158
Network Communication Protocols .....................................................................................................................160
Power Supply Connection............................................................................................................ 162
Input Power Supply Lines ....................................................................................................................................162
Target Volumes of Each Function ........................................................................................................................212
Combinations of Functions That Are Available for Simultaneous Executions............................... 214
Combinations of Functions That Are Available for Simultaneous Executions.......................................................214
Number of Processes That Can Be Executed Simultaneously...............................................................................216
Capacity That Can Be Processed Simultaneously .................................................................................................216
Figure 8 Example of a RAID Group .........................................................................................................................25
Figure 10 Hot Spares................................................................................................................................................28
Figure 11 Hot Spare Selection Criteria......................................................................................................................30
Figure 12 Data Block Guard......................................................................................................................................31
Figure 13 Disk Drive Patrol.......................................................................................................................................33
Figure 14 Redundant Copy Function ........................................................................................................................34
Figure 16 Fast Recovery ...........................................................................................................................................36
Figure 39 Data Encryption with Self Encrypting Drives (SED) ...................................................................................67
Figure 40 Firmware Data Encryption........................................................................................................................68
Figure 41 Key Management Server Linkage.............................................................................................................70
Figure 47 Device Time Synchronization....................................................................................................................87
Figure 48 Power Synchronized Unit..........................................................................................................................88
Figure 49
Wake On LAN ...........................................................................................................................................89
Figure 50 Example of Advanced Copy ......................................................................................................................90
Figure 53 EC or REC Reverse .....................................................................................................................................96
Figure 54 Targets for the Multi-Copy Function .........................................................................................................97
Figure 84 Microsoft Linkage...................................................................................................................................141
Figure 86 Single Path Connection (When a SAN Connection Is Used — Direct Connection) .....................................146
Figure 87 Single Path Connection (When a SAN Connection Is Used — Switch Connection) ....................................146
Figure 88 Multipath Connection (When a SAN Connection Is Used — Basic Connection Configuration)...................147
Figure 89 Multipath Connection (When a SAN Connection Is Used — Switch Connection).......................................147
Figure 90 Multipath Connection (When a SAN Connection Is Used — for Enhanced Performance)..........................148
Figure 91 Example of Non-Supported Connection Configuration (When Multiple Types of Remote Interfaces Are In-
stalled in the Same ETERNUS DX/AF)......................................................................................................149
Figure 92 Example of Supported Connection Configuration (When Multiple Types of Remote Interfaces Are Installed
in the Same ETERNUS DX/AF) .................................................................................................................149
Figure 93 An FC Connection for a Remote Copy between ETERNUS DX/AF Storage Systems (When Redundant Paths
Are Used) ...............................................................................................................................................150
Figure 94 An FC Connection for a Remote Copy between ETERNUS DX/AF Storage Systems (When Lines Are Used).....
Figure 96 Connection Example without a Dedicated Remote Support Port ............................................................154
Figure 97 Connection Example When the IP Address of the Slave CM Is Set (and a Dedicated Remote Support Port Is
Not Used)...............................................................................................................................................154
Figure 98 Overview of the AIS Connect Function ....................................................................................................155
Table 4 Formula for Calculating User Capacity for Each RAID Level .......................................................................22
Table 5 User Capacity per Drive.............................................................................................................................23
Table 6 RAID Group Types and Usage....................................................................................................................24
Table 7 Recommended Number of Drives per RAID Group ....................................................................................25
Table 8 Volumes That Can Be Created...................................................................................................................27
Table 9 Hot Spare Installation Conditions.............................................................................................................29
Table 10 Hot Spare Selection Criteria (Condition 1) ................................................................................................30
Table 11 Hot Spare Selection Criteria (Condition 2) ................................................................................................30
Table 12 TPP Maximum Number and Capacity........................................................................................................43
Table 13 Chunk Size According to the Configured TPP Capacity...............................................................................44
Table 14 Levels and Configurations for a RAID Group That Can Be Registered in a TPP...........................................44
Table 17 Chunk Size and Data Transfer Unit ..........................................................................................................49
Table 18 The Maximum Number and the Maximum Capacity of FTSPs...................................................................51
Table 19 Levels and Configurations for a RAID Group That Can Be Registered in a FTSP .........................................52
Table 22 Optimization of Volume Configurations....................................................................................................57
Table 23 Functional Comparison between the SED Authentication Key (Common Key) and Key Management Server
Table 24 Available Functions for Default Roles .......................................................................................................73
Table 25 Client Public Key (SSH Authentication).....................................................................................................74
Table 30 Control Software (Advanced Copy) ...........................................................................................................90
Table 31 Characteristics of SnapOPC/SnapOPC+ Operations with Each Type of Copy Destination Logical Volume .......
Table 32 REC Data Transfer Mode ...........................................................................................................................93
Table 33 Available Cascade Copy Combinations (When a Cascade Copy Performs Session 1 Followed by Session 2) ..
Table 34 Available Cascade Copy Combinations (When a Cascade Copy Performs Session 2 Followed by Session 1) ..
Table 35 Available Stripe Depth............................................................................................................................104
Table 36 Guideline for the Number of Drives and User Capacities (When 1.92TB SSDs Are Installed) ...................106
Table 37 Guideline for the Number of Drives and User Capacities (When 1.2TB SAS Disks Are Installed)..............109
Table 38 Deduplication/Compression Function Specifications...............................................................................114
Table 39 Method for Enabling the Deduplication/Compression Function..............................................................115
Table 40 Volumes That Are to Be Created depending on the Selection of "Deduplication" and "Compression"......116
Table 41 Deduplication/Compression Setting for TPPs Where the Target Volumes Can Be Created .......................116
Table 42 Target Deduplication/Compression Volumes of Each Function ...............................................................119
Table 43 Storage Cluster Function Specifications ..................................................................................................126
SAN Functions ..........................................................................................................................................15
Table 45 Maximum VVOL Capacity........................................................................................................................137
Table 46 VVOL Management Information Specifications ......................................................................................137
Table 47 Volume Types That Can Be Used with Veeam Storage Integration..........................................................140
Table 49 Connectable Models and Available Remote Interfaces ...........................................................................152
Table 50 LAN Port Availability...............................................................................................................................160
Table 58 Number of Installable Drives..................................................................................................................184
Table 59 Hot Swap and Hot Expansion Availability for Components.....................................................................208
Table 60 List of Supported Protocols.....................................................................................................................210
Table 61 Combinations of Functions That Can Be Executed Simultaneously (1/2) ................................................214
Table 62 Combinations of Functions That Can Be Executed Simultaneously (2/2) ................................................214
Fujitsu would like to thank you for purchasing the FUJITSU Storage ETERNUS DX500 S4/DX600 S4, ETERNUS
DX500 S3/DX600 S3 (hereinafter collectively referred to as ETERNUS DX).
The ETERNUS DX is designed to be connected to Fujitsu servers (
and other servers) or non-Fujitsu servers.
This manual provides the system design information for the ETERNUS DX storage systems.
This manual is intended for use of the ETERNUS DX in regions other than Japan.
This manual applies to the latest controller firmware version.
Refer to the following manuals of your model as necessary:
"Overview"
"Site Planning Guide"
"Product List"
"Configuration Guide (Basic)"
"ETERNUS Web GUI User's Guide"
"ETERNUS CLI User's Guide"
"Configuration Guide -Server Connection-"
Document Conventions
■
Third-Party Product Names
Oracle Solaris may be referred to as "Solaris", "Solaris Operating System", or "Solaris OS".
•
•
Microsoft® Windows Server® may be referred to as "Windows Server".
■
Notice Symbols
The following notice symbols are used in this manual:
Indicates information that you need to observe when using the ETERNUS storage system.
Make sure to read the information.
Indicates information and suggestions that supplement the descriptions included in this
manual.
To avoid damaging the ETERNUS storage system, pay attention to the
following points when cleaning the ETERNUS storage system:
Warning layout ribbon
Example warning
- Make sure to disconnect the power when cleaning.
- Be car
eful that no liquid seeps into the ETERNUS storage system
when using cleaners, etc.
- Do not use alcohol or other solvents to clean the ETERNUS storage system.
CAUTION
Do
Preface
Warning Signs
Warning signs are shown throughout this manual in order to prevent injury to the user and/or material damage.
These signs are composed of a symbol and a message describing the recommended level of caution. The following explains the symbol, its level of caution, and its meaning as used in this manual.
The following symbols are used to indicate the type of warnings or cautions being described.
This symbol indicates the possibility of serious or fatal injury if the ETERNUS DX is not used
properly.
This symbol indicates the possibility of minor or moderate personal injury, as well as damage to the
ETERNUS DX and/or to other users and their property, if the ETERNUS DX is not
used properly.
This symbol indicates IMPORTANT information for the user to note when using the ETERNUS
DX.
The triangle emphasizes the urgency of the WARNING and CAUTION contents. Inside the
triangle and above it are details concerning the symbol (e.g. Electrical Shock).
The barred "Do Not..." circle warns against certain actions. The action which must be
avoided is both illustrated inside the barred circle and written above it (e.g. No Disassembly).
The black "Must Do..." circle indicates actions that must be taken. The required action is
both illustrated inside the black disk and written above it (e.g. Unplug).
How Warnings are Presented in This Manual
A message is written beside the symbol indicating the caution level. This message is marked with a vertical ribbon in the left margin, to distinguish this warning from ordinary descriptions.
The ETERNUS DX provides various functions to ensure data integrity, enhance security, reduce cost, and optimize
the overall performance of the system.
The ETERNUS DX integrates block data (SAN area) and file data (NAS area) in a single device and also provides
advanced functions according to each connection.
These functions enable to respond to problems from various situations.
The ETERNUS DX has functions such as the SAN function (supports block data access), the NAS function (supports
file data access), and basic functions that can be used without needing to recognize the SAN or the NAS connection.
For more details about the basic functions, refer to "2. Basic Functions
functions that are used for a SAN connection, refer to "3. SAN Functions" (page 112).
Table 1 Basic Functions
OverviewFunction
Data protection
Functions that ensure data integrity to improve data reliability.
It is possible to detect and fix drive failures early.
Functions that prevent unintentional storage access.
Stable operation
For stable operation of server connections, the appropriate response action and the processing priority can be specified for
each server.
If an error occurs in the storage system during operations, the
connected storage system is switched automatically and operations can continue.
Data relocation
A function that migrates data between ETERNUS storage systems.
Non-disruptive data relocation
A function that migrates data between ETERNUS storage systems without stopping the business server.
Information linkage (function linkage with servers)
Functions that cooperate with a server to improve performance
in a virtualized environment. Beneficial effects such as centralized management of the entire storage system and a reduction
of the load on servers can be realized.
Parity for data A to D: P A, B, C, D
Parity for data E to H: P E, F, G, H
Parity for data I to L: P I, J, K, L
Parity for data M to P: P M, N, O, P
2. Basic Functions
RAID Functions
● RAID1+0 (Striping of Pairs of Drives for Mirroring)
RAID1+0 combines the high I/O performance of RAID0 (striping) with the reliability of RAID1 (mirroring).
Figure 3 RAID1+0 Concept
● RAID5 (Striping with Distributed Parity)
Data is divided into blocks and allocated across multiple drives together with parity information created from
the data in order to ensure the redundancy of the data.
● RAID5+0 (Double Striping with Distributed Parity)
Multiple RAID5 volumes are RAID0 striped. For large capacity configurations, RAID5+0 provides better performance, better reliability, and shorter rebuilding times than RAID5.
Parity for data A to D: P1 A, B, C, D and P2 A, B, C, D
Parity for data E to H: P1 E, F, G, H and P2 E, F, G, H
Parity for data I to L: P1 I, J, K, L and P2 I, J, K, L
Parity for data M to P: P1 M, N, O, P and P2 M, N, O, P
2. Basic Functions
RAID Functions
● RAID6 (Striping with Double Distributed Parity)
Allocating two different parities on different drives (double parity) makes it possible to recover from up to two
drive failures.
Parity for data A, B, C: P1 A, B, C and P2 A, B, C
Parity for data D, E, F: P1 D, E, F and P2 D, E, F
Parity for data G, H, I: P1 G, H, I and P2 G, H, I
Parity for data J, K, L: P1 J, K, L and P2 J, K, L
Parity for data M, N, O: P1 M, N, O and P2 M, N, O
Parity for data P, Q, R: P1 P, Q, R and P2 P, Q, R
Parity for data S, T, U: P1 S, T, U and P2 S, T, U
Parity for data V, W, X: P1 V, W, X and P2 V, W, X
:
Fast recovery Hot Spare: FHS
2. Basic Functions
RAID Functions
● RAID6-FR (Provides the High Speed Rebuild Function, and Striping with Double Distributed Parity)
Distributing multiple data groups and reserved space equivalent to hot spares to the configuration drives makes
it possible to recover from up to two drive failures. RAID6-FR requires less build time than RAID6.
Figure 7 RAID6-FR Concept
■
Reliability, Performance, Capacity for Each RAID Level
Table 3 shows the comparison result of reliability, performance, capacity for each RAID level.
Table 3 RAID Level Comparison
RAID levelReliabilityPerformance (*1)Capacity
RAID0
RAID1
RAID1+0
RAID5
RAID5+0
RAID6◎
RAID6-FR◎
´
◎◎
¡¡
¡
¡¡¡
¡¡¡
◎△
¡¡
¡¡
◎: Very good ¡: Good △: Reasonable ´: Poor
*1: Performance may differ according to the number of drives and the processing method from the host.
Select the appropriate RAID level according to the usage.
Recommended RAID levels are RAID1, RAID1+0, RAID5, RAID5+0, RAID6, and RAID6-FR.
•
When importance is placed upon read and write performance, a RAID1+0 configuration is recommended.
•
For read only file servers and backup servers, RAID5, RAID5+0, RAID6, or RAID6-FR can also be used for higher
•
efficiency. However, if the drive fails, note that data restoration from parities and rebuilding process may result in a loss in performance.
For SSDs, a RAID5 configuration or a fault tolerant enhanced RAID6 configuration is recommended because
•
SSDs operate much faster than other types of drive. For large capacity SSDs, using a RAID6-FR configuration,
which provides excellent performance for the rebuild process, is recommended.
Using a RAID6 or RAID6-FR configuration is recommended when Nearline SAS disks that have 6TB or more are
•
used. For details on the RAID levels that can be configured with Nearline SAS disks that have 6TB or more,
refer to "
Supported RAID" (page 16).
User Capacity (Logical Capacity)
User Capacity for Each RAID Level
The user capacity depends on the capacity of drives that configure a RAID group and the RAID level.
Table 4 shows the formula for calculating the user capacity for each RAID level.
Table 4 Formula for Calculating User Capacity for Each RAID Level
RAID levelFormula for user capacity computation
RAID0
RAID1
RAID1+0
RAID5
RAID5+0
RAID6
RAID6-FR
*1: "N" is the number of RAID6 configuration sets. For example, if a RAID6 group is configured with "(3D+2P)
´2+1HS", N is "2".
Drive capacity ´ Number of drives
Drive capacity ´ Number of drives ¸ 2
Drive capacity ´ Number of drives ¸ 2
Drive capacity ´ (Number of drives - 1)
Drive capacity ´ (Number of drives - 2)
Drive capacity ´ (Number of drives - 2)
Drive capacity ´ (Number of drives - (2 ´ N) - Number of hot spares) (*1)
The supported drives vary between the ETERNUS DX500 S4/DX600 S4 and the ETERNUS DX500 S3/DX600 S3. For
details about drives, refer to "Overview" of the currently used storage systems.
Table 5 User Capacity per Drive
Product name (*1)User capacity
400GB SSD374,528MB
800GB SSD750,080MB
960GB SSD914,432MB
1.6TB SSD1,501,440MB
1.92TB SSD1,830,144MB
3.84TB SSD3,661,568MB
7.68TB SSD7,324,416MB
15.36TB SSD14,650,112MB
30.72TB SSD29,301,504MB
300GB SAS disk279,040MB
600GB SAS disk559,104MB
900GB SAS disk839,168MB
1.2TB SAS disk1,119,232MB
1.8TB SAS disk1,679,360MB
2.4TB SAS disk2,239,744MB
1TB Nearline SAS disk937,728MB
2TB Nearline SAS disk1,866,240MB
3TB Nearline SAS disk2,799,872MB
4TB Nearline SAS disk3,733,504MB
6TB Nearline SAS disk (*2)5,601,024MB
8TB Nearline SAS disk (*2)7,468,288MB
10TB Nearline SAS disk (*2)9,341,696MB
12TB Nearline SAS disk (*2)11,210,496MB
14TB Nearline SAS disk (*2)13,079,296MB
*1: The capacity of the product names for the drives is based on the assumption that 1MB = 1,0002 bytes,
while the user capacity for each drive is based on the assumption that 1MB = 1,0242 bytes. Furthermore,
OS file management overhead will reduce the actual usable capacity.
The user capacity is constant regardless of the drive size (2.5"/3.5"), the SSD type (Value SSD and MLC SSD),
or the encryption support (SED).
*2: For details on the RAID levels that can be configured with Nearline SAS disks that have 6TB or more, refer
This section explains RAID groups.
A RAID group is a group of drives. It is a unit that configures RAID. Multiple RAID groups with the same RAID
level or multiple RAID groups with different RAID levels can be set together in the
group is created, RAID levels can be changed and drives can be added.
Table 6 RAID Group Types and Usage
ETERNUS DX. After a RAID
TypeUsage
RAID groupAreas to store normal data. Volumes (Standard, WSV,
SDV, SDPV) for work and Advanced Copy can be created
in a RAID group.
REC Disk BufferAreas that are dedicated for the REC Consistency mode to
temporarily back up copy data.
Thin Provisioning
Pool (TPP) (*5)
Flexible Tier Sub
Pool (FTSP) (*6)
RAID groups that are used for Thin Provisioning in which
the areas are managed as a Thin Provisioning Pool (TPP).
Thin Provisioning Volumes (TPVs) can be created in a
TPP.
RAID groups that are used for the Flexible Tier function in
which the areas are managed as a Flexible Tier Sub Pool
(FTSP). Larger pools (Flexible Tier Pools: FTRPs) are comprised by layers of FTSPs. Flexible Tier Volumes (FTVs) can
be created in an FTSP.
*1: This value is for a 15.36TB SSD RAID6-FR ([13D+2P]´2+1HS) configuration in the
S3.
For details on the number of configuration drives for each RAID level and recommended configurations,
refer to Table 7.
*2: This value is for a 30.72TB SSD RAID6-FR ([13D+2P]´2+1HS) configuration in the
ETERNUS DX500 S4/DX600
S4.
For details on the number of configuration drives for each RAID level and recommended configurations,
refer to Table 7.
*3: This value is for a 15.36TB SSD RAID1+0 (4D+4M) configuration in the ETERNUS DX500 S3/DX600 S3.
*4: This value is for a 30.72TB SSD RAID1+0 (4D+4M) configuration in the ETERNUS DX500 S4/DX600 S4.
*5: For details on the number of configuration drives for each RAID level and recommended configurations,
refer to Table 14.
*6: For details on the number of configuration drives for each RAID level and recommended configurations,
refer to Table 19.
*7: Total of the Thin Provisioning Pool capacity and the FTSP capacity.
The same size drives (2.5", 3.5") and the same kind of drives (SAS disks, Nearline SAS disks, SSDs, or SEDs) must
be used to configure a RAID group.
Figure 8 Example of a RAID Group
SAS disks and Nearline SAS disks can be installed together in the same group. Note that SAS disks and Near-
•
line SAS disks cannot be installed with SSDs or SEDs.
Use drives that have the same size, capacity, rotational speed (for disks), Advanced Format support, inter-
•
face speed (for SSDs), and drive enclosure transfer speed (for SSDs) to configure RAID groups.
-
-
-
-
-
For details on the RAID levels that can be configured with Nearline SAS disks that have 6TB or more, refer to
•
"Supported RAID
If a RAID group is configured with drives that have different capacities, all the drives in the RAID group are
recognized as having the same capacity as the drive with the smallest capacity in the RAID group and the
rest of the capacity in the drives that have a larger capacity cannot be used.
If a RAID group is configured with drives that have different rotational speeds, the performance of all of
the drives in the RAID group is reduced to that of the drive with the lowest rotational speed.
If a RAID group is configured with SSDs that have different interface speeds, the performance of all of the
SSDs in the RAID group is reduced to that of the SSD with the lowest interface speed.
3.5" SAS disks are handled as being the same size type as the drives for high-density drive enclosures. For
example, 3.5" Nearline SAS disks and Nearline SAS disks for high-density drive enclosures can exist together in the same RAID group.
When a RAID group is configured with SSDs in both the high-density drive enclosure (6Gbit/s), and the
3.5" type drive enclosure or the high-density drive enclosure (12Gbit/s), because the interface speed of
the high-density drive enclosure (6Gbit/s) is 6Gbit/s, all of the SSDs in the RAID group operate at 6Gbit/s.
" (page 16).
Table 7 shows the recommended number of drives that configure a RAID group.
Table 7 Recommended Number of Drives per RAID Group
RAID level
RAID122(1D+1M)
RAID1+04 to 324(2D+2M), 6(3D+3M), 8(4D+4M), 10(5D+5M)
RAID53 to 163(2D+1P), 4(3D+1P), 5(4D+1P), 6(5D+1P)
RAID5+06 to 32
RAID65 to 165(3D+2P), 6(4D+2P), 7(5D+2P)
RAID6-FR11 to 31
Number of configuration drives
Recommended number of drives (*1)
3(2D+1P) ´ 2,
17 ((6D+2P) ´2+1HS)
4(3D+1P) ´ 2, 5(4D+1P) ´ 2, 6(5D+1P) ´ 2
*1: D = Data, M = Mirror, P = Parity, HS = Hot Spare
Sequential access performance hardly varies with the number of drives for the RAID group.
•
Random access performance tends to be proportional to the number of drives for the RAID group.
•
Use of higher capacity drives will increase the time required for the drive rebuild process to complete.
•
For RAID5, RAID5+0, and RAID6, ensure that a single RAID group is not being configured with too many
•
drives.
If the number of drives increases, the time to perform data restoration from parities and Rebuild/Copyback
when a drive fails also increases.
For details on the recommended number of drives, refer to Table 7.
The RAID level that can be registered in REC Disk Buffers is RAID1+0. The drive configurations that can be
•
registered in REC Disk Buffers is 2D+2M or 4D+4M.
For details on the Thin Provisioning function and the RAID configurations that can be registered in Thin Pro-
visioning Pools, refer to "Storage Capacity Virtualization" (page 43
For details on the Flexible Tier functions and the RAID configurations that can be registered in Flexible Tier
Pools, refer to "Automated Storage Tiering" (page 49).
).
Volume
An assigned CM is allocated to each RAID group. For details, refer to "
Assigned CMs" (page 105).
For the installation locations of the drives that configure the RAID group, refer to "Recommended RAID Group
Configuration" (page 200).
This section explains volumes.
Logical drive areas in RAID groups are called volumes.
A volume is the basic RAID unit that can be recognized by the server.
Figure 9 Volume Concept
A volume may be up to 128TB. However, the maximum capacity of volume varies depending on the OS of the
server.
The maximum number of volumes that can be created in the
ETERNUS DX is 16,384. Volumes can be created
until the combined total for each volume type reaches the maximum number of volumes.
A volume can be expanded or moved if required. Multiple volumes can be concatenated and treated as a single
volume. For availability of expansion, displacement, and concatenation for each volume, refer to "Target Vol-
The types of volumes that are listed in the table below can be created in the ETERNUS DX.
Table 8 Volumes That Can Be Created
TypeUsageMaximum capacity
Standard (Open)A standard volume is used for normal usage, such as file sys-
Snap Data Volume (SDV)This area is used as the copy destination for SnapOPC/
Snap Data Pool Volume (SDPV)This volume is used to configure the Snap Data Pool (SDP)
Thin Provisioning Volume (TPV)This virtual volume is created in a Thin Provisioning Pool area. 128TB
Flexible Tier Volume (FTV)This volume is a target volume for layering. Data is automati-
Virtual Volumes (VVOLs)A VVOL is a VMware vSphere dedicated capacity virtualization
Deduplication/Compression VolumeThis volume is a virtual volume that is recognized by the serv-
Wide Striping Volume (WSV)This volume is created by concatenating distributed areas in
ODX Buffer volumeAn ODX Buffer volume is a dedicated volume that is required
tems and databases. The server recognizes it as a single logical unit.
"Standard" is displayed as the type for this volume in ETERNUS
Web GUI/ETERNUS CLI and "Open" is displayed in ETERNUS SF
software.
SnapOPC+. There is a SDV for each copy destination.
area. The SDP capacity equals the total capacity of the SDPVs.
A volume is supplied from a SDP when the amount of updates
exceeds the capacity of the copy destination SDV.
cally redistributed in small block units according to the access
frequency. An FTV belongs to a Flexible Tier Pool.
volume. Operations can be simplified by associating VVOLs
with virtual disks.
Its volume type is FTV.
er when the Deduplication/Compression function is used. It
can be created by enabling the Deduplication/Compression
setting for a volume that is to be created. The data is seen by
the server as being non-deduplicated and uncompressed.
The volume type is TPV.
from 2 to 64 RAID groups. Processing speed is fast because
data access is distributed.
to use the Offloaded Data Transfer (ODX) function of Windows
Server 2012 or later. It is used to save the source data when
data is updated while a copy is being processed.
It can be created one per ETERNUS DX.
Its volume type is Standard, TPV, or FTV.
*1: When multiple volumes are concatenated using the LUN Concatenation function, the maximum capacity is
also
128TB.
*2: The capacity differs depending on the copy source volume capacity.
After a volume is created, formatting automatically starts. A server can access the volume while it is being for-
matted. Wait for the format to complete if high performance access is required for the volume.
parameter.
For details about the stripe sizes for each RAID level and the stripe depth parameter values, refer to "ETER-
NUS Web GUI User's Guide".
Note that the available user capacity can be fully utilized if an exact multiple of the stripe size is set for the
volume size. If an exact multiple of the stripe size is not set for the volume size, the capacity is not fully
utilized and some areas remain unused.
When a Thin Provisioning Pool (TPP) is created, a control volume is created for each RAID group that config-
•
ures the relevant TPP. Therefore, the maximum number of volumes that can be created in the ETERNUS DX
decreases by the number of RAID groups that configure a TPP.
When the Flexible Tier function is enabled, 64 work volumes are created. The maximum number of volumes
•
that can be created in the ETERNUS DX decreases by the number of work volumes that are created.
When a Flexible Tier Sub Pool (FTSP) is created, a control volume is created for each RAID group that config-
•
ures the relevant FTSP. Therefore, the maximum number of volumes that can be created in the ETERNUS DX
decreases by the number of RAID groups that configure an FTSP.
When using the VVOL function, a single volume for the VVOL management information is created the mo-
•
ment a VVOL is created. The maximum number of volumes that can be created in the ETERNUS DX decreases by the number of volumes for the VVOL management information that are created.
Hot Spares
, volumes have different stripe sizes that depend on the RAID level and the stripe depth
Hot spares are used as spare drives for when drives in a RAID group fail, or when drives are in error status.
Figure 10 Hot Spares
When the RAID level is RAID6-FR, data in a failed drive can be restored to a reserved space in a RAID group
even when a drive error occurs because a RAID6-FR RAID group retains a reserved space for a whole drive in
the RAID group. If the reserved area is in use and an error occurs in another drive (2nd) in the RAID group,
then the hot spare is used as a spare.
■
Types of Hot Spares
The following two types of hot spare are available:
Global Hot Spare
•
This is available for any RAID group. When multiple hot spares are installed, the most appropriate drive is automatically selected and incorporated into a RAID group.
This is only available to the specified RAID group (one RAID group).
The Dedicated Hot Spare cannot be registered in a RAID group that is registered in TPPs, FTRPs, or REC Disk
Buffers.
Assign "Dedicated Hot Spares" to RAID groups that contain important data, in order to preferentially improve
their access to hot spares.
■
Number of Installable Hot Spares
The number of required hot spares is determined by the total number of drives.
The following table shows the recommended number of hot spares for each drive type.
Table 9 Hot Spare Installation Conditions
Model
ETERNUS DX500 S4/DX500 S31246——
ETERNUS DX600 S4/DX600 S3124689
■
Types of Drives
If a combination of SAS disks, Nearline SAS disks, SSDs, and SEDs is installed in the ETERNUS DX, each different
type of drive requires a corresponding hot spare.
2.5" and 3.5" drive types are available. The drive type for high-density drive enclosures is 3.5".
There are two types of rotational speeds for SAS disks; 10,000rpm and 15,000rpm. If a drive error occurs and a
hot spare is configured in a RAID group with different rotational speed drives, the performance of all the drives
in the RAID group is determined by the drive with the slowest rotational speed. When using SAS disks with different rotational speeds, prepare hot spares that correspond to the different rotational speed drives if required.
Even if a RAID group is configured with SAS disks that have different interface speeds, performance is not affected.
There are two types of interface speeds for SSDs; 6Gbit/s and 12Gbit/s. If a drive error occurs and a hot spare is
configured in a RAID group with different interface speed SSDs, the performance of all the SSDs in the RAID
group is determined by the SSDs with the slowest interface speed. Preparing SSDs with the same interface speed
as the hot spare is recommended.
The capacity of each hot spare must be equal to the largest capacity of the same-type drives.
Total number of drives
Up to 120Up to 240Up to 480Up to 720Up to 960Up to 1056
■
Selection Criteria
When multiple Global Hot Spares are installed, among the drives that match the selection criteria in the order of
priority for Condition 1, drives that match the selection criteria in the order of priority for Condition 2 are automatically selected as a hot spare to replace the failed drive.
If different drive types or capacities are mixed, the recommended action is to install a hot spare for each different drive type or capacity on each path.
Table 10 Hot Spare Selection Criteria (Condition 1)
Selection order
1A drive enclosure that is located in the same path as the failed drive
2A drive enclosure that is not located in the same path as the failed drive
Selection criteria
● Condition 2
Table 11 Hot Spare Selection Criteria (Condition 2)
Selection order
1A hot spare with the same type, same capacity, and same rotational speed (for disks) or same interface speed
2A hot spare with the same type, and same rotational speed (for disks) or same interface speed (for SSDs) as the
3A hot spare with the same type and same capacity as the failed drive but with a different rotational speed (for
4A hot spare with the same type as the failed drive but with a larger capacity and a different rotational speed (for
*1: If multiple drives are applicable, priority is given to the drives in ascending order of the enclosure number
and the drive slot number.
*2: When there are multiple hot spares with a larger capacity than the failed drive, the hot spare with the
smallest capacity among them is used first.
The figure below shows an example of a drive search order when a drive failure occurs.
First, drives are selected in the order of priority (1 to 4) for Condition 2 among the drives in the drive enclosures
that are located in the same path as the failed drive. If there are no applicable drives in the same path, drives
that match Condition 2 are selected in the order of priority (1 to 4) among the drives that match priority order 2
of Condition 1.
Figure 11 Hot Spare Selection Criteria
Selection criteria
(for SSDs) as the failed drive (*1)
failed drive but with a larger capacity (*1) (*2)
disks) or a different interface speed (for SSDs) (*1)
disks) or a different interface speed (for SSDs) (*1) (*2)
Search order (order of priority described in Table 10)