We use cookies on this website. To find out more about cookies and how they are used on this website, see our Privacy Policy.
By clicking ‘Continue’, you hereby agree with our use of cookies.

{{vmH.selected.familySearch.replace("EonStor ", "")}} Maintenance Guide

{{vmH.selected.familySearch.replace("EonStor ", "")}} User Guide

Maintenance Guide

External Storage Management

KS / KS 5000U / KSi 5016U

IEC Container Storage Interface

Kubernetes ensures that applications can correctly access persistent storage through the Container Storage Interface (CSI). This enables the system to upgrade, update, and enhance its storage capabilities without having to update Kubernetes, maintaining a consistent, reliable platform.

IEC provides a set of storage classes. With IEC CSI you can do the following:

  • Create and use CSI-enabled persistent volumes
  • Protect CSI-enabled volumes using token authorization and encryption defined at the StorageClass or PVC level
  • Back up CSI-enabled volumes

StorageClass Parameters

The following configurable values and default values are available on the EonStor GS/GSx/KS product series.

ParameterDescriptionConfigurable valueDefault valueExample
compressIndicate if data compression is enabled.
  • KS: { true | false }
  • GS/GSx: { false, not support’ }
'false''false'
dedupeIndicate if data deduplication is enabled.
  • KS: { true | false }
  • GS/GSx:{ false, not support’ }
'false''false'
drivetypeThe drive type that consists of the volume.
  • KS: { any }
  • GS/GSx: { any | hdd | ssd }
'any''ssd'
groupaclGroup acl of a volume. The permission of different groups are divided by commas.Any valid format of group acl(empty string)' '
iscsiThe volume type as block-level or file-level.
When iscsi is set to false, the volume type is file-level.
When iscsi is set to true, the volume type is block-level.
  • KS/GSx: { false, not support’ }
  • GS: { true | false }
  • KS/GSx: 'false'
  • GS: 'true'
'false'
min_size  
  • KS: 1G
  • GS: 10G
  • GSx: 100G
 
permissionThe access permission to the volume (owner-group-other).Any expressions of Linux permission'rwxr-xr-x''rwxr-xr-x'
protectionThe level of data protection
  • KS/GSx: { any }
  • GS: { any | r6 | r5 | r1 }
'any''r5'
replicaThe number of data copy
  • KS: { 1 | 2 | 3 }
  • GS/GSx: { 1 | support }
  • KS: '2'
  • GS/GSx: '1'
'1'
snapshotIndicate if snapshot is enabled in the volume.
When snapshot is enabled, the space used by the snapshot will share the same space as the volume.
  • KS: { true | false }
  • GS/GSx: { false, not support’ }
'false''false'
storageipThe IP address of the storageA valid IP address or 'any''any''192.168.1.1'
useraclUser acl of a volume. The permission of different users are divided by commas.Any valid format of user acl(empty string)' '
poolIds 
  • KS/ GSx: { not support }
  • GS: Pool IDs
  • KS/GSx: 'not support'
  • GS: Pool IDs
 
xfsSnapshot 
  • KS: { true | false }
  • GS/GSx: { false, not support’ }
  • KS: 'true'
  • GS/GSx: 'false'
 

Volume Locality

Use data copies (replica) to ensure high availability and fault tolerance of data. In a containerized application environment, data persistence and availability are critical. The replica feature ensures that your applications can still access the data they need even if the node where the data resides fails.

  • Data replicas: When creating a PV through CSI, you can set the number of data replicas through configuring the parameter of StorageClass. You can have up to three replicas.
    Note:

    The greater the number of replicas, the more fault-tolerant the data is. More replicas will also occupy more storage space.

  • High availability: IEC automatically selects appropriate nodes for the replicas to reside so that replicas can be distributed across the nodes in the cluster. This prevents data from being unavailable due to the failure of one specific node.
  • Consistency: Each write operation is synchronized to all replicas to ensure that each replica is up to date.
  • Automatic repair: IEC detects the status of replicas. When a node is abnormal, resulting in the loss of replicas, it will automatically create new replicas on other healthy nodes to meet the number of replicas that has been configured.