The following is specified for Expess as volume information.
This information is for ETERNUS Disk storage system only.
Item | Description |
|---|---|
This is a volume name. | |
Apart from volume name, this is a name easy to understand "what operation is in progress on this volume". | |
This is an available size on volume. This can be specified in MB, GB, or TB as follows.
| |
This is a volume type.
| |
This is a source volume size of SDV, which can be specified only when a volume type is SDV. This can be specified in MB, GB, or TB as follows.
| |
This is the number of volumes to be created.
| |
Whether or not to encrypt a volume.
Default is "Disable". | |
RAID Level | This is a parameter to specify a RAID group in the list of "RAID group" of the screen. |
Note
In the case of creating two or more volumes at the same time, "_ x"(x is a digit) is given behind the specified volume name and the volume alias.
The larger the number of volumes to be created at the same time is, the smaller the maximum number of characters specifiable for the volume name and the volume alias are.
For 1 volume:
VOLUME-NAME (The maximum number of specifiable characters 16.)
For 2-10 volumes:
VOLUME-NAME_x (The maximum number of specifiable characters 14.)
For 11 or more volumes:
VOLUME-NAME_xx (The maximum number of specifiable characters 13.)
When using snapshot copy (SnapOPC+), it is recommended to specify at least one SDPV to each CM of an ETERNUS Disk storage system.
In addition, if any encrypted OPEN volume exists, an encrypted SDPV is required apart from a normal SDPV.
It is needed to encrypt copy destination volume, if copy source volume is encrypted when Advanced Copy is used,
If multiple volumes are created in RAID groups, it may not be able to create them up to maximum user capacity. To create volumes efficiently without waste of user capacity, set the volume size to multiples of base size (stripe size).
Base size for each RAID Level is as follows.
RAID Level (*1) | Base size(*2)(MB integer conversion) | |
|---|---|---|
RAID1 | 1D+1M | 1 (MB) |
RAID1+0 | 2D+2M | 1 (MB) |
3D+3M | 3 (MB) | |
4D+4M | 1 (MB) | |
5D+5M | 5 (MB) | |
6D+6M | 3 (MB) | |
7D+7M | 7 (MB) | |
8D+8M | 1 (MB) | |
9D+9M | 9 (MB) | |
10D+10M | 5 (MB) | |
11D+11M | 11 (MB) | |
12D+12M | 3 (MB) | |
13D+13M | 13(MB) | |
14D+14M | 7 (MB) | |
15D+15M | 15 (MB) | |
16D+16M | 1 (MB) | |
RAID5 | 2D+1P | 1 (MB) |
3D+1P | 3 (MB) | |
4D+1P | 1 (MB) | |
5D+1P | 5 (MB) | |
6D+1P | 3 (MB) | |
7D+1P | 7 (MB) | |
8D+1P | 1 (MB) | |
9D+1P | 9 (MB) | |
10D+1P | 5 (MB) | |
11D+1P | 11 (MB) | |
12D+1P | 3 (MB) | |
13D+1P | 13 (MB) | |
14D+1P | 7 (MB) | |
15D+1P | 15 (MB) | |
RAID5+0 | (2D+1P)*2 | 1 (MB) |
(3D+1P)*2 | 3 (MB) | |
(4D+1P)*2 | 1 (MB) | |
(5D+1P)*2 | 5 (MB) | |
(6D+1P)*2 | 3 (MB) | |
(7D+1P)*2 | 7 (MB) | |
(8D+1P)*2 | 1 (MB) | |
(9D+1P)*2 | 9 (MB) | |
(10D+1P)*2 | 5 (MB) | |
(11D+1P)*2 | 11 (MB) | |
(12D+1P)*2 | 3 (MB) | |
(13D+1P)*2 | 13 (MB) | |
(14D+1P)*2 | 7 (MB) | |
(15D+1P)*2 | 15 (MB) | |
RAID6 | 3D+2P | 3 (MB) |
4D+2P | 1 (MB) | |
5D+2P | 5 (MB) | |
6D+2P | 3 (MB) | |
7D+2P | 7 (MB) | |
8D+2P | 1 (MB) | |
9D+2P | 9 (MB) | |
10D+2P | 5 (MB) | |
11D+2P | 11 (MB) | |
12D+2P | 3 (MB) | |
13D+2P | 13 (MB) | |
14D+2P | 7 (MB) | |
*1 : D is Data,M is Mirror,P is Parity
*2 : Base size at volume creation
ETERNUS DX60/DX80/DX90 manage the size of volume as base size unit. Therefore, it may be remained unused area in RAID group if the size of volume is not multiple of the base size. Base size is not depending on disk drive capacity.
Following are the image of volume size in multiple of base size and not multiple of base size.
