Querying data MIGRATE progress using OceanStor 9000 V100R001C01


OceanStor 9000 V100R001C01 currently does not have any effective method for querying data MIGRATE progress, but allows you to estimate the progress using the following operations:
a. Running the df –h command on the standby node to query and compare the used disk capacity with the total capacity to be migrated.
b. Calculating and comparing the number of migrated files with the total number of files to be migrated based on the IOPS and used MIGRATE time on the WebUI.

Other related questions:
Method used to recover data on OceanStor 9000 V100R001C01
Based on failed objects and data recovery triggering conditions, OceanStor 9000 V100R001C01 recovers data using two methods: ensuring zero data loss on the original disk or node and writing the data in a failed disk or node to other normal disks or nodes through calculations.

Principles of quick data recovery using OceanStor 9000 V100R001C01
Based on the load balancing policy and data protection levels, OceanStor 9000 divides storage resources into multiple logical groups, and each disk may belong to multiple logical groups. A logical group is an independent unit for data protection and recovery. A data protection level is assigned to each logical group (for example, 4+2). If a disk failure triggers data recovery, all logical groups to which the failed disk belongs will take part in data recovery concurrently. Therefore, the recovery speed is faster than that of a traditional RAID group. If a node failure triggers data recovery, logical groups to which all disks of the failed node belong will take part in data recovery concurrently. The maximum recovery speed is 1 TB/hour.

Manually starting data recovery using OceanStor 9000 V100R001C01
OceanStor 9000 V100R001C01 creates policies for automatic data recovery based on the following procedures: 1. Log in to OceanStor DeviceManager. 2. Choose Settings > Cluster Settings > Protection Policy > Automatic Data Reconstruction. 3. In the function pane, click Create. 4. In the Create Data Reconstruction Policy dialog box, select Execution Period and Impact, and click OK. - Execution Period defines the time segment during which the data recovery task is executed on the specified day every week. The periods specified in data recovery policies cannot overlap. - Impact indicates the level of the impact of data recovery tasks on system performance during the time segment specified by Execution Period. The level includes High, Medium, Low, Stop, and Full Speed. In the Succeeded dialog box, click OK. The page for configuring the data recovery policy is displayed.

Introduction to OceanStor 9000 V100R001C01 data balancing
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.

Cabinets used by OceanStor 9000 V100R001C01
The FR42611 and FR42612L cabinets are recommended for OceanStor 9000 V100R001C01.

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