The following operations can be performed for LUN concatenated volumes:
Deleting a volume
Creating an affinity group
Changing the configuration of an affinity group (adding/deleting a volume)
Storage Cruiser can manage the ETERNUS DX100 S4/DX200 S4 that have the following component:
SAS-CA board that responds to a 12 Gbps port transfer speed
Storage Cruiser can use the following function that is added in the ETERNUS DX200 S3, DX500 S3/DX600 S3, and the ETERNUS All-Flash Arrays:
Separate configuration of data deduplication and compression for Thin Provisioning Pools and separate display
Configuration of data deduplication and compression when a Thin Provisioning Pool is created
This function can be also used with the ETERNUS DX200 S4.
Expanding the maximum pool capacity of Thin Provisioning pools and Tier pools that are added to the ETERNUS DX S3 series and the ETERNUS All-Flash Arrays is supported. The following information is displayed on Web Console:
Capacity of Thin Provisioning pools and Tier pools (exceeding 2 PB)
Capacities exceeding 2 PB can be displayed starting from version 16.5.
Chunk size
The chunk size is a capacity per block in Thin Provisioning Volumes or Flexible Tier Volumes.
This function can be also used with the ETERNUS DX S4 series.
Point
To use the above functions for storage devices other than the ETERNUS DX S4 series, the firmware version of the target storage device must be V10L70 or later.
For the ETERNUS DX S4 series, DX S3 series, and the ETERNUS All-Flash Arrays, Thin Provisioning Pools that disks are selected automatically can be created.
Point
To use the above functions for storage devices other than the ETERNUS DX S4 series, the firmware version of the target storage device must be V10L70 or later.
See
Refer to the following section in the Storage Cruiser Operation Guide for details:
Chapter "Operation" > "Resource Management" > "Thin Provisioning Management"
The total value of the evaluatable capacity in the same time zone is expanded to 48 PB (6 PB in version 16.4) for Tier pools in the ETERNUS DX S3 series (excluding DX60 S3) and the ETERNUS AF series.
The ETERNUS DX S4 series (excluding DX60 S4) has also been expanded to 48 PB.
Point
To use the above functions for storage devices other than the ETERNUS DX S4 series, the firmware version of the target storage device must be V10L70 or later.
The total value of the evaluatable used capacity in a Tier pool varies by the chunk size that is set for each Tier pool. Refer to "Upper Limit of Automated Storage Tiering" in the Installation and Setup Guide for details.
For Automated Storage Tiering in the ETERNUS DX S3 series (excluding DX60 S3) and the ETERNUS AF series, increasing the data amount that can be processed for a one-time relocation reduces the time required for a relocation.
This function is also applied when using the ETERNUS DX S4 series (excluding DX60 S4).
See
Refer to "Tiering Policies" in the Storage Cruiser Operation Guide for Optimization Function for details.
The following operations can be performed in a Storage Cluster environment:
Setting and displaying the total capacity of TFOVs per storage device
Expanding the maximum number of TFO groups that can be created from 2 to 32
Creating TFO groups in the same direction
Point
To use the above functions for storage devices other than the ETERNUS DX S4 series, the firmware version of the target storage device must be V10L70 or later.
See
Refer to "Storage Cluster Function" in the Storage Cruiser Operation Guide for details.
The following operations can be performed from Web Console:
Expanding the volume capacity
Adding an expanded volume to a TFO group
Releasing and recovering a TFO pair in the maintenance procedure
In version 16.4 or earlier, the above operations required commands to be executed from ETERNUS CLI. However, because they can be performed from Web Console with version 16.5 or later, the operability of the storage operation using the Storage Cluster function is improved.
See
Refer to "Storage Cluster Function" in the Storage Cruiser Operation Guide for details.
Automatic Failover function during a RAID close
In a Storage Cluster environment, if the RAID close of the storage device occurs during operation with a TFO status is "Active", Automatic Failover is performed if the Failover mode is "Auto".
Automatic Failover function triggered by CA port linkdown
In a Storage Cluster environment, in TFO groups that satisfy all the following requirements, if all the CA ports belonging to the Primary TFO Group are linked down because of CA port failure or connection failure during operation with a TFO status of the Primary TFO Group is "Active", Automatic Failover is performed.
For TFO groups, the Automatic Failover function is set to be used if CA port linkdown occurs.
The Failover mode is set to "Auto".
The Failback mode is set to "Manual".
In version 16.4 or earlier, even if the Failover mode was "Auto", performing a Manual Failover was required. Because Automatic Failover is performed for version 16.5 or later, the maintenance procedure is reduced when compared with version 16.4 or earlier.
Point
To use the above functions for storage devices other than the ETERNUS DX S4 series, the firmware version of the target storage device must be V10L70 or later.
See
Refer to "RAID Close" of the chapter "Storage Cluster Function" in the Storage Cruiser Operation Guide for the maintenance procedure for the RAID close.
Refer to "Configuring TFO Group" in "Installation" of the chapter "Storage Cluster Function" in the Storage Cruiser Operation Guide for the configuration procedure of the Automatic Failover function triggered by CA port linkdown.
Refer to "CA Port Linkdown" of the chapter "Storage Cluster Function" in the Storage Cruiser Operation Guide for the maintenance procedure for the CA port linkdown.
