Introduction to OceanStor 9000 V100R001C01 data balancing

3

OceanStor 9000 data balancing refers to the balancing of data capacity on storage nodes. After a disk or node is added, you can migrate it to make data evenly distributed on all storage nodes.
OceanStor 9000 provides two modes of data balancing:
- Manual balancing: After a data balancing task is manually started, the system checks whether data in each node pool is balanced in the system. If data is unbalanced, the system starts a data balancing task.
- Automatic balancing: After a disk or node is added, the system waits 30 minutes and then starts a data balancing task. If the waiting time is shorter than 30 minutes and more disks or nodes are added, the system waits another 30 minutes before starting a data balancing task.

Other related questions:
Configuring OceanStor 9000 V100R001C01 data balancing policies
OceanStor 9000 V100R001C01 data balancing polices are configured as follows: 1. Log in to OceanStor DeviceManager. 2. Choose Settings > Cluster Settings > Protection Policy > Data Balancing Policy. 3. Set Balancing Mode. 4. Set Balancing Policy. 5. Click Save. In the Execution Result dialog box, click Close after viewing the Succeed result. 6. (Optional) Click Task Management on the lower right of OceanStor DeviceManager to query the progress and other basic information of the data balancing task.

OceanStor 9000 V100R001C01 data balancing policy levels
OceanStor 9000 data balancing policy levels are based on the impact of data balancing on normal services. These priority levels comprise the following: High: Data balancing causes system performance to deteriorate by no more than 50%. Medium: Data balancing causes system performance to deteriorate by no more than 30%. Low: Data balancing causes system performance to deteriorate by no more than 10% (by default). When a data recovery task and a data balancing task are both initiated, the former is performed prior to the latter.

Manually enabling or disabling OceanStor 9000 V100R001C01 data balancing
The procedure for manually enabling or disabling OceanStor 9000 V100R001C01 data balancing is as follows: 1. Log in to OceanStor DeviceManager. 2. Choose Settings > Cluster Settings > Protection Policy > Data Balancing Policy. 3. Check whether Data Balancing Mode is set to Manual. If yes, go to step 5. If not, go to step 4. 4. Select Manual for Data Balancing Mode and click Save. In the Execution Result dialog box, click Close after viewing the Succeed result. Then, you can select Start or Stop for Manual. 5. Select Start or Stop as needed. Carefully read the warning information in the Warning dialog box. Ensure all operations are correct, and then select I have read and understand the consequences associated with performing this operation. Click OK.

Introduction to OceanStor 9000 V100R001C01 software architecture
The software architecture of OceanStor 9000 V100R001C01 is as follows: The software architecture is fully symmetric with WushanFS run on all storage nodes. Metadata is evenly distributed to eliminate performance bottlenecks. OceanStor 9000 supports the seamless flexible expansion of 3 to 288 storage nodes and enables file system capacity to be expanded up to 40 PB. OceanStor 9000 provides NFS, CIFS, and FTP services, enabling clients running different operating systems to share files. Two types of client authentication modes are supported, local authentication and domain server authentication based on Active Domain (AD), Lightweight Directory Access Protocol (LDAP), and Network Information Service (NIS). Administrators can securely access DeviceManager and OceanStor SystemReporter (an optional report tool) to manage system resources and monitor system status and performance through HTTPS.

Introduction to the high watermark of OceanStor 9000 V100R001C01
In OceanStor 9000 V100R001C01, the default high watermark is that the used space occupies 85% of the total storage space of a node pool. When the used space of a node pool reaches the high watermark, the system reports a capacity insufficiency alarm, and refuses data to be written to the node pool. By default, the alarm clearance threshold is 5% lower than the high watermark. That is, when the percentage of used space is lower than 80%, the capacity insufficiency alarm is cleared. The alarm threshold and clearance threshold of the high watermark can be manually changed.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top