Hard disk array configuration method and device, storage medium and electronic equipment

Abstract

The invention discloses a configuration method and device of a hard disk array, a storage medium and electronic equipment, and relates to the technical field of storage systems.The configuration method comprises the steps that reference performance data of the hard disk array are obtained, and the reference performance data are used for indicating performance data of the hard disk array in a time period; the candidate decision condition meeting the reference performance data in the at least one candidate decision condition is determined as a target decision condition, the candidate decision condition is used for indicating the range of the performance data of the hard disk array, and the at least one candidate decision condition corresponds to candidate configuration of one hard disk array; determining a candidate configuration corresponding to the target decision condition as a target configuration; and under the condition that the current configuration of the hard disk array is inconsistent with the target configuration, configuring the hard disk array as the target configuration. The technical problem that an existing hard disk array configuration method is low in storage efficiency is solved, and the technical effect of improving the storage efficiency of a storage system is achieved.

Description

Technical Field

[0001] The present application relates to the field of storage systems, and in particular to a configuration method and device for a hard disk array, a storage medium, and an electronic device. Background Art

[0002] In the current era of rapid cloud computing and big data development, enterprise storage systems face unprecedented challenges and opportunities. With the explosive growth of data volumes, the demand for storage performance and reliability continues to increase, especially in scenarios with high concurrency, large data transfers, mixed workloads, and real-time data processing. In these scenarios, Redundant Array of Independent Disks (RAID) configurations can provide both performance and data redundancy.

[0003] However, RAID system configurations in related technologies are one-time settings, based on anticipated workloads and requirements. Once established, these configurations become the fundamental architecture for system operation and are difficult to change. These configurations cannot be flexibly adjusted to meet changing business needs. This rigid configuration limits the system's ability to respond to dynamic business demands and reduces overall storage efficiency. In other words, the disk array configuration methods used in related technologies suffer from low storage efficiency. Summary of the Invention

[0004] The present application provides a configuration method and device for a hard disk array, a storage medium, and an electronic device, to at least solve the problem of low storage efficiency in the configuration method for a hard disk array in the related art.

[0005] The present application provides a method for configuring a hard disk array, comprising: obtaining reference performance data of the hard disk array, wherein the reference performance data is used to indicate performance data of the hard disk array within a time period;

[0006] determining, among at least one candidate decision condition, a candidate decision condition that the reference performance data satisfies as a target decision condition, wherein the candidate decision condition is used to indicate a range of performance data of the hard disk array, and the at least one candidate decision condition each corresponds to a candidate configuration of the hard disk array;

[0007] Determine the candidate configuration corresponding to the target decision condition as the target configuration;

[0008] If the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration.

[0009] The present application also provides a configuration device for a hard disk array, comprising: a performance data acquisition module, configured to acquire reference performance data of the hard disk array, wherein the reference performance data is used to indicate performance data of the hard disk array within a time period;

[0010] a decision condition determination module, configured to determine, from among at least one candidate decision condition, a candidate decision condition that the reference performance data satisfies as a target decision condition, wherein the candidate decision condition is used to indicate a range of performance data of the hard disk array, and each of the at least one candidate decision condition corresponds to a candidate configuration of the hard disk array;

[0011] A target configuration determination module is used to determine the candidate configuration corresponding to the target decision condition as the target configuration;

[0012] The configuration module is used to configure the hard disk array to the target configuration when the current configuration of the hard disk array is inconsistent with the target configuration.

[0013] The present application also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any of the above-mentioned hard disk array configuration methods when executing the computer program.

[0014] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned methods for configuring a hard disk array are implemented.

[0015] The present application also provides a computer program product, including a computer program, which implements the steps of any of the above-mentioned hard disk array configuration methods when executed by a processor.

[0016] Through the present application, reference performance data of a hard disk array is obtained, wherein the reference performance data is used to indicate the performance data of the hard disk array within a time period; a candidate decision condition that the reference performance data satisfies is determined as a target decision condition, wherein the candidate decision condition is used to indicate the range of the hard disk array's performance data, and at least one candidate decision condition corresponds to a candidate configuration of the hard disk array; the candidate configuration corresponding to the target decision condition is determined as the target configuration; and when the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration. The performance data of the currently running hard disk array can be processed to obtain reference performance data, and the candidate decision conditions that the reference performance data satisfies are determined, thereby determining the candidate configuration corresponding to the candidate decision condition as the target configuration. The target configuration is the configuration to which the hard disk array is expected to be converted. Therefore, when the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration. In this way, the appropriate configuration for the hard disk array can be determined in real time and the configuration can be changed. Therefore, the technical problem of low storage efficiency in current hard disk array configuration methods can be solved, achieving the technical effect of improving the storage efficiency of the storage system. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0018] Figure 1 is a schematic diagram of a hardware environment for an optional method for configuring a hard disk array according to an embodiment of the present application;

[0019] Figure 2 is a flow chart of an optional method for configuring a hard disk array according to an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a first target configuration of an optional hard disk array according to an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of a first target configuration of another optional hard disk array according to an embodiment of the present application;

[0022] Figure 5 is a schematic diagram of a second target configuration of an optional hard disk array according to an embodiment of the present application;

[0023] Figure 6 is a schematic diagram of a second target configuration of another optional hard disk array according to an embodiment of the present application;

[0024] Figure 7 is a schematic diagram of an optional method for configuring a hard disk array according to an embodiment of the present application;

[0025] Figure 8 This is a structural block diagram of an optional hard disk array configuration device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0027] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0028] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0029] According to one aspect of an embodiment of the present application, a method for configuring a hard disk array is provided. As an optional implementation, the method for configuring a hard disk array can be applied to, but is not limited to, Figure 1 The configuration system of the hard disk array in the hardware environment shown in FIG. The configuration system of the hard disk array may include but is not limited to the terminal device 102, the network 110, and the hard disk array 112. The terminal device 102 runs a target client (such as Figure 1 (As shown, the target client is a client capable of configuring a disk array.) The terminal device 102 includes a display 108, a processor 106, and a memory 104. The display 108 can be used to display, for example, disk array performance data and also provide a human-computer interaction interface to receive user input on the interface and touch controls. The processor is configured to generate interaction instructions in response to these human-computer interaction operations and transmit them to the server. The memory is configured to store performance data.

[0030] Assumptions Figure 1 In the terminal device 102, a client for configuring a hard disk array is running. The specific process of this embodiment is as follows: In step S102, the terminal device 102 receives performance data from the hard disk array 112 via the network 110. The terminal device then executes steps S104-S108 to obtain reference performance data of the hard disk array, where the reference performance data indicates the performance data of the hard disk array within a time period; determines the candidate decision condition that the reference performance data meets as the target decision condition, where the candidate decision condition indicates the range of the performance data of the hard disk array, and at least one candidate decision condition corresponds to a candidate configuration of the hard disk array; determines the candidate configuration corresponding to the target decision condition as the target configuration; and if the current configuration of the hard disk array is inconsistent with the target configuration, configures the hard disk array to the target configuration. The terminal device 102 then executes step S110 to configure the hard disk array 112 according to the target configuration via the network 110.

[0031] Optionally, in this embodiment, the terminal device 102 may be a terminal device configured with a target client, and may include, but is not limited to, at least one of the following: a mobile phone (such as an Android phone or iOS phone), a laptop, a tablet computer, a PDA, a MID (Mobile Internet Device), a PAD, a desktop computer, a smart TV, etc. The network may include, but is not limited to, a wired network and a wireless network. The wired network includes a local area network, a metropolitan area network, and a wide area network, and the wireless network includes Bluetooth, Wi-Fi, and other networks that enable wireless communication. The network may also refer to the physical connection between the terminal device 102 and the disk array 112.

[0032] Optionally, the terminal device 102 may be a RAID controller. Although a hardware device, the RAID controller can be located inside or outside the disk array. It has core responsibilities such as executing instructions from the policy control layer, managing RAID level migration, stripe size adjustment, and monitoring disk health. The RAID controller physically implements intelligent policies.

[0033] Terminal device 102 can also be a software management system on a storage server. This software management system typically runs on the storage server rather than directly within the disk array. It is a key component of the policy control layer, responsible for data monitoring, pattern recognition, predictive modeling, and decision-making. By communicating with the RAID controller, the software management system indirectly controls storage operations within the array, enabling dynamic RAID configuration adjustments.

[0034] Terminal device 102 can also be a cloud storage service. Cloud storage services are not themselves part of the disk array, but they can be connected to the data center's storage system via the network, serving as additional storage resources. When local storage resources are limited or to address potential failures, the intelligent dynamic RAID system can automatically utilize the cloud storage service's resources to achieve temporary data migration or redundant storage.

[0035] It should be noted that the terminal device 102 can be displayed as the same product as the hard disk array 112. That is, the terminal device 102 can be located within the hard disk array as part of the hard disk array 112 to control a single hard disk array. The terminal device 102 can also be a separate external terminal responsible for configuring different hard disk arrays.

[0036] Optionally, the disk array (RAID) 112 is a method of combining multiple physical hard disks using specific data distribution and redundancy strategies to form a logically single storage device, thereby providing higher performance, larger storage capacity, and / or enhanced data reliability. It can be an array of disks or an array of hard disks.

[0037] The hard disk array 112 includes: physical hard disks, which can be traditional hard disk drives (HDDs) or solid-state drives (SSDs), which are connected to the RAID controller via data cables and share the data storage function.

[0038] The embodiment of the present application provides a method for configuring a hard disk array. Figure 2 is a flow chart of an optional method for configuring a hard disk array according to an embodiment of the present application; Figure 2 As shown, the configuration method of the hard disk array includes:

[0039] Step S202: Acquire reference performance data of the hard disk array, wherein the reference performance data is used to indicate performance data of the hard disk array within a time period;

[0040] It should be noted that a disk array is a collection of multiple hard drives that can provide faster read and write speeds, greater storage capacity, or data redundancy. A common form of this is a RAID array. Reference performance data is a collection of performance metrics exhibited by the disk array over a specific time period. This can include IOPS (input and output operations per second), throughput, latency, SMART data, and other key metrics for measuring disk or array performance. The time period is the window used to collect and analyze performance data. It can range from seconds, minutes, hours, or even longer, depending on the settings of the monitoring and management system.

[0041] In an optional implementation, the system periodically collects performance data from the hard disk array to reflect the array's operating status over a specific period of time. This data includes not only basic read and write performance metrics, but may also include disk health information, such as SMART data, as well as data access patterns and frequency. The collection of performance data is fundamental to subsequent analysis and prediction, providing information about the array's current state and past performance. This information is then used in decision-making algorithms to determine whether and how the RAID configuration should be adjusted.

[0042] It should be noted that the reference performance data can be the following data: IOPS (input / output operations per second): reflects the ability and strength of the hard disk array to handle read and write operations. Throughput: measures the total amount of data transmission per unit time, usually in MB / s or GB / s. Latency: the time required for a data request to complete the response, used to evaluate the speed of the hard disk array in processing I / O requests. SMART data: hard disk health indicators provided by Self-Monitoring, Analysis and Reporting Technology, including error rate, pre-read error, head flight time, etc., used to monitor potential failures of hard disks. Cache hit rate: reflects the effectiveness of the storage system cache. A higher cache hit rate means that more data requests can be obtained directly from the cache, reducing disk access and improving response speed.

[0043] In an optional embodiment, the reference performance data can be predicted data based on the performance data of the hard disk array. After obtaining the performance data of the hard disk array for each time period, the collected data can be classified and analyzed. For example, based on the real-time data within 15 minutes and the results of pattern recognition, historical data and prediction algorithms such as time series analysis, regression analysis, or machine learning prediction models (such as ARIMA and LSTM) can be used to predict the load trend and hard disk health status for the next 5 minutes. The prediction here can include two prediction methods:

[0044] Load trend prediction: Predicts the intensity and type of future I / O operations, helping the system prepare for possible high loads or pattern changes, such as increasing the stripe size to accommodate continuous reads and writes, or switching to a more redundant RAID configuration to cope with possible failures.

[0045] Hard drive health prediction: This function analyzes SMART data and other performance indicators to assess the health of hard drives and predict failure probability. For example, a gradual increase in the error rate of a hard drive, even if it is currently within the normal range, may indicate a risk of failure within the next few hours.

[0046] It's important to note that in intelligent storage systems, using historical and current data for analysis and decision-making is entirely feasible and doesn't necessarily require prediction. Predictive data is often used for forward-looking decision-making, such as predicting future load and failure risk to enable proactive responses. However, this doesn't mean prediction is the sole or necessary means of intelligent storage system management.

[0047] In an optional embodiment, the reference performance data can be historical data and current data, which can provide the past and present operating conditions of the storage system, including I / O patterns, performance indicators, data access frequency, disk health status, etc. Through monitoring and collection, this data can be analyzed without the need for prediction to optimize the current configuration and performance of the system.

[0048] By performing statistical analysis on historical data, you can identify the system's regular workload patterns, performance bottlenecks, and common failure points, thereby developing more effective storage strategies and fault recovery plans.

[0049] Real-time monitoring of the current status of the storage system, including IOPS, throughput, latency, disk error rate, etc., allows immediate response to sudden performance degradation or failure, and takes measures such as isolation, stripe size adjustment, and RAID level switching to optimize performance and ensure data security.

[0050] In some scenarios, a combination of forecasted, historical, and current data can provide a more comprehensive basis for decision-making. For example, forecasted data can be used to predict future load changes or failure risks, allowing the system to adjust configurations in a proactive manner. Historical and current data can be used to verify the accuracy of forecasts and to optimize based on system status in real time, ensuring real-time and accurate decision-making.

[0051] Step S204: Determine the candidate decision condition that the reference performance data satisfies from among the at least one candidate decision condition as the target decision condition, wherein the candidate decision condition is used to indicate a range of performance data of the hard disk array, and each of the at least one candidate decision condition corresponds to a candidate configuration of the hard disk array;

[0052] It's important to note that candidate decision conditions are a set of pre-defined possible decision conditions during system optimization or decision-making, based on current performance indicators and system status. These conditions specify the range within which data should be present to trigger corresponding actions. For example, when read and write latency falls below a certain threshold, the system may favor a more efficient RAID configuration; conversely, when latency falls below a certain threshold, a configuration that prioritizes data redundancy and security may be selected.

[0053] The target decision condition is the one that the system determines is most suitable for decision-making in the current state, among a set of candidate decision conditions. Once determined, the system will follow the guiding principles of this condition and make corresponding configuration adjustments.

[0054] Candidate configurations for a hard disk array can include RAID levels, stripe sizes, and redundancy mechanisms, which directly determine the performance, reliability, and storage efficiency of the array. The following is a detailed analysis of these factors:

[0055] RAID levels define how data is stored and redundancy is achieved within a hard drive array. Different RAID levels target different performance and reliability requirements, such as:

[0056] RAID0: Data striping without redundancy provides the highest read and write performance, but any single hard drive failure will result in data loss in the entire array.

[0057] RAID1: Mirroring, data is completely copied to two hard drives, providing data redundancy and ensuring high data reliability, but the storage capacity is only half of the total capacity of the hard drives in the array.

[0058] RAID 5: Striping with distributed parity requires at least three hard drives, provides data redundancy and high read and write performance, and can continue to operate even if a single hard drive fails.

[0059] RAID6: Similar to RAID5, but provides dual parity, which increases fault tolerance and can protect data when two hard drives fail at the same time.

[0060] RAID 10: A combination of RAID 1 and RAID 0, providing striping and mirroring, ensuring high read and write performance and data redundancy. It is suitable for scenarios requiring high performance and high reliability.

[0061] The stripe size refers to the unit size by which data blocks are distributed across the different hard drives in a RAID array. Choosing the stripe size has a direct impact on performance: Smaller stripe sizes (such as 8KB or 16KB) are beneficial for random read and write operations because they can more quickly read or write small data blocks from multiple hard drives, reducing seek time. Larger stripe sizes (such as 256KB or larger) are suitable for sequential reads and writes of large data blocks because they reduce data transfer latency during each I / O operation and improve data throughput.

[0062] Data redundancy involves storing additional data within a hard drive array to prevent data loss. Redundancy methods include: Parity: As used in RAID 5 and RAID 6, this method calculates parity blocks and distributes them across the array, ensuring that lost data can be reconstructed in the event of a hard drive failure. Mirroring: As used in RAID 1, data is completely replicated across two hard drives, providing data redundancy. This method allows for immediate failover to the mirrored drive in the event of a single drive failure, ensuring continuous data access.

[0063] In an alternative implementation, the system examines all candidate decision conditions to see which performance data ranges match the currently collected reference performance data. Those candidate decision conditions that successfully match are considered target decision conditions, i.e., the optimal decision solution that the system should use next.

[0064] Candidate decision conditions can cover a wide range of workloads and performance states that a disk array may face, with each condition corresponding to a possible optimization configuration or strategy. For example, if current read and write latency is low, the system may determine that it is a good time to upgrade the RAID level or adjust striping parameters to improve performance. Conversely, if the detected disk error rate increases, the system will tend to select a RAID configuration with increased redundancy protection, such as RAID 5 or RAID 6, to ensure data security and system stability.

[0065] This process embodies dynamic adaptation and optimization. Through real-time analysis and decision-making, the system can flexibly adjust storage configurations based on actual load and performance requirements, maximizing storage resource utilization while ensuring data reliability and business continuity. This mechanism is particularly suitable for scenarios where workloads or performance requirements frequently change, such as data centers, cloud computing environments, or high-performance computing clusters.

[0066] Step S206, determining the candidate configuration corresponding to the target decision condition as the target configuration;

[0067] As mentioned previously, target decision conditions refer to the specific criteria or circumstances that the system uses to make RAID configuration selections. These conditions may include factors such as real-time I / O patterns, load conditions, and failure rates. The target configuration can be the RAID configuration determined by the system to be optimal or most suitable for the current decision conditions among multiple candidate configurations after evaluation by the policy processing model and priority calculation.

[0068] In an optional embodiment, the system analyzes and compares all candidate configurations, and determines the optimal RAID configuration as the target configuration based on the current decision conditions, such as disk error rate, I / O optimization requirements, storage utilization or write latency, and the priority of these conditions. The system is able to quantitatively compare the potential benefits and costs of each candidate configuration. Ultimately, the system will determine the RAID configuration that best balances performance, security, and cost under the current decision conditions, and designate it as the target configuration. This configuration will then be applied to the virtualized storage layer to achieve intelligent adjustment and optimization of storage resources, thereby improving overall system performance and data redundancy, while reducing resource consumption and maintenance costs.

[0069] Step S208 : If the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration.

[0070] It's important to note that if the current disk array configuration fails to meet predicted performance requirements or business continuity requirements, the system will proactively adjust the configuration to the target configuration. This means that if monitoring and analysis reveal that the current disk array configuration fails to achieve the expected performance level or presents potential data security risks, the system will automatically or manually initiate a configuration change to ensure the storage system can adapt to the changing environment, provide optimal performance, and safeguard data security.

[0071] In an optional implementation, before starting any configuration changes, the details of the target configuration should be clearly defined, including but not limited to RAID level, stripe size, redundancy mechanism, etc. These parameters should be based on real-time analysis of I / O patterns, load conditions, disk health status, and business needs, that is, determining the target configuration.

[0072] After determining the target configuration, you can perform a RAID level migration, for example, from RAID 5 to RAID 6, or from RAID 0 to RAID 10. This typically involves redistributing data and rebuilding parity blocks. During the migration process, the system may limit data write operations to prevent data inconsistencies while ensuring sufficient free space to store the generated parity data.

[0073] If the stripe size needs to be adjusted, the system will reorganize the data blocks through a background task, ensuring that each data block is distributed across different hard drives according to the new stripe size. This may affect data read and write performance, so it should be scheduled appropriately and performed during low-load periods.

[0074] When adjusting redundancy mechanisms, such as adding redundant drives or changing parity policies, it's important to balance data integrity and storage efficiency. The system may need to: Ensure dual or triple writes during data migration to maintain redundancy and data consistency. Initialize and synchronize newly added drives or modified parity policies to ensure all data is correctly stored.

[0075] Example 1:

[0076] Assume that in step S202, through continuous performance data collection, the system detects that the write latency of the current hard disk array (RAID 5) has suddenly increased, exceeding the 100ms threshold. Based on the prediction model, this high latency is expected to persist for some time. Furthermore, the system identifies that the current I / O pattern is primarily continuous, large-scale data writes, with sequential writes accounting for over 80% of the total, and this trend is not expected to change within the next ten minutes.

[0077] In steps S204 through S206, the system performs an in-depth data analysis, including an assessment of disk health, consideration of service levels, and calculation of migration costs. Based on this information, the system determines that switching to a RAID 0 configuration and increasing the stripe size to 1MB will significantly improve write performance, and that the current disk health and business continuity requirements can withstand such a configuration change.

[0078] In step S208, the system confirms that the current configuration (RAID 5) is inconsistent with the target configuration (RAID 0 + 1MB stripe), and initiates the configuration migration process. The system gradually adjusts the disk array from RAID 5 to RAID 0, while also increasing the stripe size. During this process, the system monitors the performance impact on services to ensure that the migration operation does not cause data inconsistencies or service interruptions. For example, the system may limit the migration speed to ensure data continuity and consistency during peak service periods.

[0079] After the configuration migration is complete, the system continues to monitor the performance of the disk array under the new RAID configuration to ensure that the target configuration has indeed improved performance and resolved the initial issues. If, over the next few hours, the monitoring data shows a significant reduction in write latency and no data inconsistencies, the system has successfully optimized the disk array and achieved the expected performance improvement and stability enhancement goals. Conversely, if the monitoring results are unsatisfactory, the system may need to readjust its strategy or even roll back to the previous configuration to find a better solution.

[0080] Through the present application, reference performance data of a hard disk array is obtained, wherein the reference performance data is used to indicate the performance data of the hard disk array within a time period; a candidate decision condition that the reference performance data satisfies is determined as a target decision condition, wherein the candidate decision condition is used to indicate the range of the hard disk array's performance data, and at least one candidate decision condition corresponds to a candidate configuration of the hard disk array; the candidate configuration corresponding to the target decision condition is determined as the target configuration; and when the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration. The performance data of the currently running hard disk array can be processed to obtain reference performance data, and the candidate decision conditions that the reference performance data satisfies are determined, thereby determining the candidate configuration corresponding to the candidate decision condition as the target configuration. The target configuration is the configuration to which the hard disk array is expected to be converted. Therefore, when the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration. In this way, the appropriate configuration for the hard disk array can be determined in real time and the configuration can be changed. Therefore, the technical problem of low storage efficiency in current hard disk array configuration methods can be solved, achieving the technical effect of improving the storage efficiency of the storage system.

[0081] In an optional embodiment, the candidate decision condition that the reference performance data meets among at least one candidate decision condition is determined as the target decision condition, including: when the reference performance data indicates that the reliability index of the hard disk array does not meet the first index range, determining the target decision condition as the first candidate decision condition; when the reference performance data indicates that the efficiency index of the hard disk array does not meet the second index range, determining the target decision condition as the second candidate decision condition.

[0082] It's important to note that the first metric typically refers to a set of standards or thresholds for storage system reliability. This may include disk error rates, failure prediction indicators, and data redundancy levels to ensure data security and storage system stability. The second metric may be related to storage system efficiency, encompassing key metrics such as read and write speeds, I / O performance, and data throughput, aiming to optimize storage system efficiency and responsiveness.

[0083] In an optional implementation, the system will, based on the collected reference performance data, select a decision condition that meets the current performance characteristics from a pre-set set of multiple candidate strategies as the next execution strategy. When a reliability indicator is detected to be declining, such as a disk error rate exceeding a pre-set first indicator range, the system will select the first candidate decision condition focused on improving reliability as the target decision condition. Conversely, if efficiency indicators such as IOPS and throughput fall below a second indicator range, the system will tend to select the second candidate decision condition focused on improving efficiency.

[0084] The key to step S204 is determining target decision conditions based on reference performance data, thereby guiding adjustments to the system configuration. The system can check whether the disk array's reliability indicators are ideal, monitoring the array's health through signals such as SMART data and disk error rates. If indicators fall below a first set range, the system infers a potential risk of data loss or service interruption. Prioritize reliability enhancement measures, such as switching to a RAID 6 configuration or increasing disk redundancy, to ensure data security.

[0085] On the other hand, if the monitored efficiency indicators, such as IOPS, throughput, or latency, fail to meet the preset second indicator range, it indicates that the storage system's response speed or data processing capabilities may not meet business needs. The system will then shift to target decision conditions to improve efficiency. This may include adjusting the RAID configuration to increase read and write speeds, such as switching from RAID 5 to RAID 0, or adjusting the stripe size to optimize data access patterns, especially when the system identifies that the main data is read and written in large, sequential blocks.

[0086] Through the above-mentioned implementation mode of the present application, based on real-time performance data and preset policy conditions, the most appropriate target decision conditions are dynamically selected and configuration adjustments are made. The system can dynamically adjust the RAID configuration while maintaining data integrity and system stability to meet changing business needs and performance challenges, thereby ensuring that the storage system is both efficient and stable.

[0087] In an optional embodiment, when the reference performance data indicates that the reliability index of the hard disk array does not meet the first index range, determining the target decision condition as the first candidate decision condition includes at least one of the following:

[0088] 1) The error rate of the hard disk array is greater than the preset error rate, where the error rate indicates the ratio of the number of read and write errors to the total number of read and write errors in a unit of time.

[0089] 2) The error count of the hard disk array is greater than the preset error count, where the error count indicates the total number of operation errors that occurred in the hard disk array within a period of time;

[0090] 3) The number of hard disks in the hard disk array that send prompt messages exceeds the preset number of hard disks, where the prompt message indicates that a hard disk has failed;

[0091] It should be noted that the preset error rate can be a system-defined error rate threshold used to determine whether the hard disk array requires a higher redundancy RAID level (such as RAID 6). The preset error count can be the maximum error count allowed per unit time, used to trigger system adjustments to the hard disk array configuration. Prompt messages can be warning signals sent by the hard disks, typically displayed in SMART data, indicating that a hard disk may have begun to fail and require attention or preventive measures. The preset number of hard disks can be the system-set hard disk failure warning threshold. When this number is reached or exceeded, the system will determine that the reliability of the hard disk array is threatened.

[0092] In an optional implementation, the system continuously monitors the performance of the hard disk array. Specifically, if the reliability index detected in real time falls below a preset first index range, the system will shift its focus to strategies for increasing data redundancy and fault tolerance. This typically means switching from the current RAID configuration (e.g., RAID 5) to a more reliable RAID level (e.g., RAID 6), or implementing other measures to mitigate the risk of hard disk failure, to ensure the security of stored data and the continued operation of the system.

[0093] When the system detects a high error rate in the disk array, an error count exceeding safety limits, or excessive hard drives showing signs of failure, it automatically selects the first candidate decision criterion as the target decision criterion, prioritizing increased storage redundancy and security. This decision may trigger adjustments to the RAID configuration, such as switching from a low-redundancy RAID level to a high-redundancy RAID level, or initiating a replacement mechanism for a failed hard drive. Through real-time analysis and dynamic policy adjustments, the system finds the optimal balance between data security and storage efficiency, effectively addressing potential storage failures, reducing the risk of data loss, and ensuring business continuity and data integrity.

[0094] In an optional embodiment, when the reference performance data indicates that the efficiency index of the hard disk array does not meet the second index range, determining the target decision condition as the second candidate decision condition includes at least one of the following:

[0095] 1) The proportion of sequential read and write operations of the hard disk array is greater than a preset proportion, where sequential read and write indicates that the hard disk array reads or writes data continuously;

[0096] 2) The delay time of the hard disk array is greater than the preset delay time, where the delay time is used to indicate the time it takes for the hard disk array to complete a write operation.

[0097] It should be noted that the preset ratio is used to determine whether the current sequential read and write operations are dominant. If the current ratio of sequential read and write operations is higher than this ratio, it may indicate that the storage system should adjust its configuration to better support such operations. Latency refers to the time required from the issuance of a data access request to the response of the request, including but not limited to the time for data retrieval, processing, and return to the requester. High latency may indicate that the storage system has a performance bottleneck when handling the current workload. The preset latency is a standard or threshold set by the system to determine whether the current latency is within an acceptable range. If the actual latency exceeds the preset value, the system may need to take measures to improve storage efficiency or reduce latency, such as adjusting the RAID configuration.

[0098] In an optional embodiment, if an efficiency indicator of the storage system, such as the latency of I / O operations or the performance of sequential read and write operations, is lower than an expected standard or threshold, the system needs to take measures to improve efficiency.

[0099] When the system observes that sequential read and write operations account for the majority of total operations, if this ratio exceeds a preset threshold, the system will tend to optimize the configuration to support sequential data access. For example, this may include adjusting to a RAID 0 configuration or increasing the stripe size, as these configurations generally improve the efficiency of sequential read and write operations.

[0100] If the average time to complete a write operation exceeds the latency threshold set by the system, the system will also consider the efficiency indicator to be substandard. In this case, the system may need to be reconfigured to reduce latency, such as switching to a more efficient but potentially less redundant RAID configuration, or reducing the burden on storage nodes by optimizing data distribution strategies.

[0101] Through the above-mentioned implementation methods of the present application, the storage strategy can be flexibly adjusted according to real-time efficiency indicators, reliability indicators and preset thresholds to adapt to different business scenarios and performance requirements, ensuring the smoothness of services and optimization of user experience.

[0102] In an optional embodiment, after determining that the target decision condition is the first candidate decision condition, the method includes: configuring the hard disk array to a first target configuration, wherein the first target configuration is a configuration corresponding to the first candidate decision condition;

[0103] After configuring the disk array as the first target configuration, include one of the following:

[0104] 1) Send the target data to the first hard disk in the hard disk array and create a mirror image of the target data on the second hard disk in the hard disk array;

[0105] 2) Sending the target data to the third hard disk in the hard disk array, and sending verification information of the target data to the third hard disk.

[0106] It should be noted that the target data may be a specific data set that needs to be stored or processed in the RAID array, and is the main object of system management and optimization.

[0107] In a RAID configuration, mirroring refers to a completely replicated copy of data between two or more disks. Mirroring is the foundation of RAID 1 (mirrored arrays), providing data redundancy, fast failure recovery, and read acceleration. Parity information is used as a checksum or metadata for data integrity and consistency. In RAID configurations, particularly RAID 5 and RAID 6, parity information is used to detect or correct data errors and ensure data accuracy.

[0108] In an optional implementation, if the new configuration is a mirrored pair, such as RAID 1, the system will ensure that data is written to both hard drives simultaneously to ensure data consistency and redundancy. If the configuration involves parity, such as RAID 5 or RAID 6, the system will calculate and store parity information based on the location of the data blocks and the parity policy to prevent data corruption or loss and enable rapid data recovery when needed.

[0109] When the system identifies that the hard disk array faces serious reliability challenges, it converts the hard disk array to the first target configuration, which may include switching to RAID1 (mirrored array) or RAID6 (striped array with double parity) to adapt to the current high-risk environment. After the configuration conversion, the system begins to implement specific redundancy and protection strategies. In the case of a mirrored array (such as RAID1), the system will ensure that the data is written synchronously to at least two copies, namely the first hard disk and the second hard disk, so that even if one of the hard disks fails, the data on the other hard disk is still available and the business is not affected. For RAID configurations that use parity (such as RAID5 or RAID6), the system will store data verification information on a separate hard disk (the third hard disk), so that even if one or more hard disks in the array fail, the system can recover the lost data through the verification information, avoiding data loss or business interruption.

[0110] Figure 3 is a schematic diagram of a first target configuration of an optional hard disk array according to an embodiment of the present application; Figure 3 The architecture shown in the figure writes the data to two or more disks (such as Figure 3 The first and second hard disks shown in the figure) each contain a complete copy of the data.

[0111] This architecture provides data redundancy. If one disk fails, data can be read from another disk, enabling instant data recovery. However, disk space utilization is low because data is completely replicated, requiring twice or more storage space than the original data. It is suitable for applications with extremely high data security requirements and frequent read operations, such as financial trading systems and critical data backup.

[0112] Figure 4 FIG. 1 is a schematic diagram of a first target configuration of another optional hard disk array according to an embodiment of the present application; FIG. Figure 4 As shown, the target data (data 1 to data 15) can be stored in five third hard drives, each of which can store corresponding data and verification information. For example, data 1 to data 3 can be sub-data of a data block, and verification information 1 and verification information 2 can be two pieces of verification information generated based on data 1 to data 3.

[0113] This architecture uses two sets of parity information to allow data recovery even if two disks fail simultaneously. This provides higher data redundancy and fault tolerance, allowing data to be recovered even if two disks fail simultaneously. However, disk space utilization is further reduced. This architecture is suitable for applications with extremely high data security requirements, such as disaster recovery systems and high-availability server clusters.

[0114] In an optional embodiment, after determining that the target decision condition is the second candidate decision condition, the method includes: configuring the hard disk array to a second target configuration, wherein the second target configuration is a configuration corresponding to the second candidate decision condition;

[0115] After configuring the disk array as the secondary target configuration, include one of the following:

[0116] 1) Split the target data into multiple sub-data according to the preset stripes, and send the multiple sub-data one by one to the multiple hard disks included in the hard disk array;

[0117] 2) Dividing the target data into multiple sub-data according to preset stripes; sending the multiple sub-data one by one to the fifth hard disk included in the hard disk array, and mirroring the sub-data on the sixth hard disk in the hard disk array.

[0118] It should be noted that a pre-defined stripe size determines how data is divided and distributed across the disks in the disk array. Larger pre-defined stripes are suitable for continuous reading and writing of large blocks of data, while smaller stripes are suitable for high-frequency random access. Sub-data is the smaller data units formed by dividing data into pre-defined stripes. These sub-data are distributed and stored on different disks in the disk array.

[0119] After determining the second candidate decision condition as the target decision condition, the system adjusts the disk array configuration to match the second target configuration of this decision to optimize storage efficiency or respond to performance challenges. Once the configuration is adjusted, the system will reorganize the data storage method based on the new configuration parameters, such as stripe size, to ensure that data can be read and written more efficiently.

[0120] In an optional embodiment, upon identifying that an efficiency metric (e.g., read / write speed, I / O latency) falls below a preset second metric range, the target decision condition is determined to be the second candidate decision condition. This typically indicates that the system needs to take measures to improve storage efficiency, such as switching to a RAID 0 configuration to leverage parallel read / write operations and reduce data access latency. After determining the second target configuration, the system will perform configuration changes, including adjusting stripe size and altering data distribution rules, to accommodate the new RAID level.

[0121] After the configuration is adjusted, the system needs to reorganize data storage to ensure that data can be effectively divided and distributed across the disks in the array according to the preset stripe size. This step is crucial for maximizing read and write performance, as proper data distribution reduces single bottlenecks and fully utilizes the read and write capabilities of all disks. If the system selects a RAID 0 configuration, this typically means that data will be divided into multiple sub-data blocks, which will then be sent in parallel to multiple disks in the array for fast data read and write speeds.

[0122] Figure 5 is a schematic diagram of a second target configuration of an optional hard disk array according to an embodiment of the present application; Figure 5 As shown in , this architecture can use data block technology, where data is divided into blocks of the same size and written to at least two disks at the same time. Figure 5 As shown, the target data can be divided into data 1 to data 6 and stored on the hard disk one by one.

[0123] This architecture offers the fastest read and write speeds because data is distributed across multiple disks, allowing read and write operations to proceed in parallel. However, failure of any single disk can cause the entire RAID array to fail, resulting in a high risk of data loss. It is suitable for applications that require high performance but less data security, such as temporary data processing and caching.

[0124] Figure 6 FIG. 1 is a schematic diagram of a second target configuration of another optional hard disk array according to an embodiment of the present application; FIG. Figure 6 As shown, the architecture combines mirroring technology and striping technology. The target data (data 1 to data 6) are stored in the fifth hard disk respectively, and the mirror file is stored in the corresponding sixth hard disk.

[0125] This architecture provides high-performance read and write operations and data redundancy, as mirroring provides data protection and striping speeds up data access. However, disk space utilization is low because mirroring requires additional storage space. It is suitable for applications requiring both high performance and redundancy, such as high-end servers, database storage, and virtualization platforms.

[0126] Through the above-described implementation of this application, storage configurations can be dynamically adjusted based on actual performance requirements and business scenarios to achieve both efficient and secure data storage and access. This capability is particularly important in environments that require processing large numbers of concurrent read and write operations, high-frequency data access, or where there is a risk of potential hardware failure. It can significantly improve the overall performance and reliability of the storage system and enhance the system's disaster resilience.

[0127] Example 2:

[0128] The candidate decision conditions may be pre-set, and the corresponding candidate configurations may also be pre-determined. Specifically, the relationship between the decision conditions and the configurations may be as follows:

[0129] 1. The target decision condition is: when the hard disk error frequency exceeds 5 times per minute, or the number of errors in I / O (input / output) operations exceeds 30 times per second.

[0130] The target configuration is for the system to automatically initiate a RAID 6 migration to increase redundancy and fault tolerance. To prevent business disruptions during the data migration, the system speed is limited to 500MB / s to ensure a smooth migration.

[0131] 2. The target decision condition is: when the system recognizes that sequential read and write operations (such as continuous file reads) account for more than 80% of the total I / O operations within 300 consecutive seconds.

[0132] The target configuration is to switch the hard disk array to RAID 0 level and increase the stripe size to 1MB to maximize the performance of sequential data access and improve read and write speeds.

[0133] 3. The target decision condition is: when the system detects that the storage space utilization rate is continuously lower than 40% and this state lasts for more than 1 hour.

[0134] The target configuration is: the system will start the consolidation of RAID arrays, reduce the number of RAID groups, and perform defragmentation to improve the efficiency of storage space utilization and clean up useless or scattered data.

[0135] It's important to note that RAID group consolidation involves combining multiple existing RAID groups into a single, larger group to improve storage efficiency and resource utilization. When multiple RAID groups are configured independently, but storage space is underutilized, consolidation can reduce unused space and improve overall storage utilization. Multiple RAID groups can increase management complexity, especially during data backup, recovery, and troubleshooting. Consolidating RAID groups can simplify storage architecture and reduce operational costs.

[0136] In an optional implementation, consolidating RAID groups can involve analyzing the load, data distribution, and health of each existing RAID group. Based on business needs and projected load adjustments, a new consolidation plan is designed. Data migration is performed to redistribute data from various RAID groups to the new, larger RAID group, which typically requires additional storage space and processing time. The RAID controller or software RAID manager configuration is updated to ensure data distribution according to the new structure. The consolidation process is monitored to ensure data consistency and to promptly address any data anomalies or performance fluctuations.

[0137] It's important to note that hard drive defragmentation is a maintenance operation designed to optimize data storage layout, reduce seek times during reads and writes, and thus improve performance. In a hard drive array, due to the wide distribution of data, random write operations can lead to data fragmentation, meaning that data blocks are stored in different locations on the hard drive rather than being stored contiguously. Excessive fragmentation reduces read and write efficiency because each I / O operation may require access to multiple discrete locations, increasing seek time and I / O latency.

[0138] 4. The target decision condition is: When the delay time of writing data to the hard disk array exceeds 100 milliseconds, it usually indicates that the system faces complex I / O operations or bottlenecks.

[0139] The target configuration is: the system enables a strategy to coordinate RAID0 and RAID1, that is, on the one hand, RAID0 is used to improve the read and write speed, and on the other hand, RAID1 is used to provide data redundancy and fast recovery to meet the performance challenges in mixed read and write mode.

[0140] Example 3:

[0141] The candidate decision conditions can be a description of a scenario. For example, by referring to performance data, it is possible to determine the preset scenario in which the disk array is in, for example:

[0142] 1. Sudden random writing scenario;

[0143] Target configuration: Because random write operations require high disk read and write dispersion, choose a RAID 10 configuration with a smaller stripe size to ensure that data can be quickly and evenly distributed across multiple disks, thereby improving random write speed and efficiency.

[0144] 2. Long-term sequential reading scenario;

[0145] Target configuration: In scenarios where a large number of continuous read operations need to be processed over a long period of time, the system switches to RAID 0 and increases the stripe size. This facilitates high-speed reading of continuous data, reduces disk seek time, and improves read performance.

[0146] 3. Bandwidth usage is 30%;

[0147] Target configuration: When the storage system's bandwidth utilization is monitored to be low (30%) and concurrent write operations are present, the system considers reducing the number of RAID groups to improve data processing efficiency and bandwidth utilization, and attempts to adjust the write mode from concurrent to sequential to reduce disk seek operations and optimize write performance.

[0148] 4.Multi-disk warning scenario;

[0149] Target Configuration: When the system receives warning signals from multiple hard drives indicating potential drive failure, it immediately switches to a RAID 6 configuration and initiates a rebuild of the array to ensure data security and system availability. RAID 6 provides a higher level of data redundancy, preventing data loss even if two hard drives fail simultaneously. This provides enhanced protection in multi-drive warning scenarios.

[0150] In an optional embodiment, configuring the hard disk array to a target configuration includes: calculating a target priority of the target configuration based on a current configuration of the hard disk array; determining a target configuration time according to the target priority; and configuring the hard disk array to the target configuration within the target configuration time when the current configuration of the hard disk array is inconsistent with the target configuration.

[0151] It should be noted that the target priority can be the result of a quantitative assessment of the importance and urgency of the configuration change based on various factors. These factors may include data redundancy requirements, current I / O operation types, business continuity requirements, and estimated resource consumption. The target configuration time can be the time window within which the system plans to complete the transition from the current disk array configuration to the target configuration. The length of this time window must be carefully planned to ensure that the configuration change has minimal business impact while achieving the new configuration as quickly as possible to improve performance or enhance data protection.

[0152] In an optional implementation, the system first analyzes the current state of the disk array, including the current RAID level, stripe size, read / write load patterns, and so on. Based on this information and business requirements, it then calculates a priority ranking for the target configuration. This step ensures the rationality of the configuration change and avoids unnecessary adjustments or wasted resources. Based on the priority calculation, a decision is made on when to execute the configuration change. This can be immediate in an emergency or scheduled during off-peak hours to minimize the impact on ongoing services.

[0153] In an optional embodiment, the target configuration determined according to the target priority can be determined by preset weights. If the target priority is greater than the first weight (such as 0.9), the urgency of the hard disk array configuration can be considered "fatal", with high performance impact and high reliability impact. If the target priority is greater than the second weight (such as 0.7) and less than or equal to the first weight, the urgency of the hard disk array configuration can be considered "serious", with medium performance impact and high reliability impact. If the target priority is greater than the third weight (such as 0.4) and less than or equal to the second weight, the urgency of the hard disk array configuration can be considered "general", with low performance impact and medium reliability impact. If the target priority is greater than the fourth weight (such as 0.2) and less than or equal to the third weight, the urgency of the hard disk array configuration can be considered "prompt", with low performance impact and low reliability impact. If the target priority is less than or equal to the fourth weight, the configuration task can be temporarily not executed.

[0154] Regarding urgency: Fatal indicates that the event has a very serious impact on performance and reliability, requiring immediate action to prevent data loss or system crashes. Severe indicates that the event has a lesser impact on performance, but still a significant impact on reliability. Action should be taken within 15 minutes to prevent potentially serious consequences. Fair indicates that the event has a lower impact on both performance and reliability, but for the sake of long-term system health, it should be addressed within 1 hour. Advisory indicates that the event has a minor impact and serves primarily as a reminder. It can be addressed within 24 hours based on system resource availability.

[0155] Determining the level of urgency allows for a corresponding timeframe, and target configuration times can be pre-set. For example, when the urgency reaches "Critical," the system should immediately initiate recovery measures whenever a problem is detected, typically within seconds to minutes. For "Critical" level events, due to the potential for significant data integrity threats, the system should initiate appropriate action within 15 minutes to mitigate risk. Tasks marked "Normal," while not significantly impacting current operations, should be addressed within an hour as preventative maintenance to maintain long-term system stability. For "Information" level events, these typically represent minor changes in system status or low-priority resource demands. They can be scheduled for handling within 24 hours without impacting higher-priority tasks, providing sufficient flexibility within the system. The above configuration times (immediate, 15 minutes, 1 hour, 24 hours) can be pre-set based on needs, allowing for differentiation between tasks of varying severity.

[0156] In an optional embodiment, the first through fourth weights can be determined based on performance data, including but not limited to key indicators such as disk error rate, data access frequency, service level, and migration cost. This historical data can be used to construct an adaptive curve that automatically adjusts based on actual operating conditions to determine the current target priority thresholds (first, second, third, and fourth weights).

[0157] In an optional implementation, the system continuously monitors the performance and health of the hard disk array, collecting real-time data on various indicators, such as disk error rates, the type and frequency of I / O operations, storage utilization, and business demand levels. This data is regularly aggregated to form a historical data set. Based on the historical data set, the system uses data analysis methods (such as time series analysis and regression analysis) to identify data trends and patterns. For example, using the ARIMA model, the system can predict the changing trend of disk error rates over a period of time, which helps to prevent possible hardware failures in advance. Similarly, models can be built for data access frequency and other performance indicators to predict their dynamic changes.

[0158] In an optional embodiment, calculating the target priority of the target configuration based on the current configuration of the hard disk array includes: determining a first parameter according to the current configuration of the hard disk array, wherein the first parameter is used to indicate the level of error in the current configuration; determining the importance of data currently processed by the hard disk array as a second parameter; predicting the bandwidth occupancy rate used by configuring the target configuration, and determining the negative of the bandwidth occupancy rate as a third parameter; and obtaining the target priority by weightedly summing the first parameter, the second parameter, the third parameter, and the data access frequency of the hard disk array.

[0159] It should be noted that the first parameter indicates the severity of possible problems or errors in the current configuration. This parameter directly reflects the health level and potential risks of the current system state and is an important basis for evaluating the necessity of configuration adjustments. The second parameter can represent the importance of the data, measuring the criticality of the data stored in the hard disk array to the business or system operation. When determining configuration priority, high-importance data will prompt the system to be more inclined to take measures to protect the integrity and availability of the data. The third parameter can represent the predicted bandwidth usage of the configuration, usually expressed as a negative number to reflect the positive value of bandwidth savings in the weighted sum. The assessment of bandwidth usage helps the system avoid making configuration changes that may increase the burden when resources are tight.

[0160] For example, target priority = α * first parameter (range can be 0-1) + β * data access frequency + γ * second parameter (such as 1-5 levels) - δ * migration cost (bandwidth usage);

[0161] Based on the current configuration of the disk array, the system determines the order and importance of configuration adjustments by calculating the target configuration's target priority. This process involves determining three key parameters: the current configuration's error level, the criticality of the data being processed, and the predicted bandwidth utilization of the configuration. Ultimately, by weighting these parameters along with data access frequency, the system derives the target priority, a metric that helps the system intelligently select and execute the optimal configuration adjustment strategy.

[0162] In an optional implementation, the first parameter may indicate the fault risk level of the current configuration. For a certain configuration, its fault risk level may also be determined, and the correspondence between the fault risk level and the configuration may be stored by setting a corresponding table or the like.

[0163] In an optional embodiment, the second parameter (service level) can indicate the importance of the business for which the data currently processed by the disk array is relevant. The second parameter can be graded based on the importance of the business within the project. Critical businesses, such as online trading systems, customer relationship management systems (CRM), and data warehouses, are typically assigned higher service levels due to their direct connection to customer service quality and decision support. The level can also be determined based on the performance requirements of the business, such as required IOPS, bandwidth, latency, and throughput. For example, real-time data analysis and video streaming services require low latency and high bandwidth and should be assigned a higher service level than simple data storage or backup.

[0164] In an optional implementation, you can communicate with the business department to understand the basic requirements of each business, including performance, reliability, cost, and legal compliance. Convert these requirements into specific quantitative indicators, such as required IOPS, throughput, latency, redundancy level, and failure recovery time. Based on the collected information, classify the business and set a level. For example, you can define the business level as 1-5, where 5 is the highest priority and 1 is the lowest priority. The level setting should take into account the direct economic benefits, long-term value, potential risks, and legal compliance requirements of the business.

[0165] Example 4:

[0166] Consider a financial trading system running in a RAID 5 configuration. However, recent performance monitoring indicates that the disk error rate has been gradually increasing, reaching 0.05%, exceeding the preset error rate threshold of 0.02%. This indicates that the stability and reliability of the current configuration have declined. The high first parameter indicates that the existing RAID configuration has a high risk of failure.

[0167] At the same time, considering that the transaction data stored in the system is extremely critical to business operations, the importance of the data is determined as the second parameter, and this parameter is also set to a higher value, which means that the system should give priority to protecting the integrity and availability of this data when making decisions.

[0168] The system predicts that if the configuration is migrated from RAID 5 to RAID 6 to improve data redundancy, the expected bandwidth utilization will be 65%. Therefore, the negative value of the predicted bandwidth utilization is weighted as the third parameter, which reflects the positive contribution of bandwidth savings to the configuration priority calculation.

[0169] By taking a weighted sum of the first, second, and third parameters, along with the data access frequency (assuming a high average of 100,000 I / O operations per day), the system concludes that the target priority is high, meaning that the RAID configuration should be adjusted to RAID 6 first. The system then switches the disk array from RAID 5 to RAID 6 and, through dynamic striping and data migration strategies, minimizes the impact on existing services while significantly enhancing data redundancy and reliability.

[0170] Through the above-mentioned implementation methods of the present application, efficient and accurate management of storage tasks can be achieved, ensuring that the system can give priority to responding to the most important needs when processing events of various natures.

[0171] When a disk failure or other event that could immediately impact data integrity and system stability is detected, the system marks it as critical. This means the system immediately executes pre-defined responses, such as data migration, fault isolation, or redundancy reconstruction, to ensure data security and business continuity. This immediate response mechanism significantly reduces the risk of data loss and accelerates recovery time.

[0172] For events marked as "critical," such as a sharp drop in performance or deterioration in disk health, the system requires action within 15 minutes. This ensures that in the event of a major performance bottleneck or impending failure, timely resource scheduling, such as switching RAID levels, adjusting stripe sizes, or initiating backup policies, can be performed, quickly alleviating performance issues and reducing the risk of system downtime or data recovery delays.

[0173] For tasks marked "Normal," such as storage utilization optimization, stripe resizing, or disk health monitoring, the system executes them within an hour. These tasks typically have minimal impact on current business operations but are critical to long-term system efficiency and data security. By executing these tasks within a reasonable timeframe, you can continuously optimize storage configurations and maintain optimal system performance without disrupting business operations.

[0174] "Reminder"-level tasks, such as scheduled maintenance, performance tuning, or data consolidation, can be completed within 24 hours. These tasks contribute to long-term system maintenance and performance optimization but do not require immediate execution. Giving these tasks a relatively generous time window allows the system to automatically execute them during low-load periods, avoiding disruption to real-time operations while ensuring the continuity and effectiveness of system maintenance.

[0175] This mechanism enables dynamic optimization of storage resources and fault prevention while maintaining business continuity and high performance. This efficient resource scheduling and task priority management significantly improves the overall efficiency of the storage system, reduces manual intervention by operations personnel, lowers operating costs, and enhances data reliability and security.

[0176] In an optional embodiment, configuring the hard disk array as the target configuration includes: obtaining current performance data of the hard disk array and isolating the target configuration if the current performance data satisfies a prompt condition;

[0177] When the current performance data meets the prompt conditions, isolate the target configuration, including at least one of the following:

[0178] 1) If the configuration progress deviation is greater than the first deviation for a period that meets the preset period, isolate the target configuration;

[0179] 2) If the number of verification failures of the hard disk array exceeds the preset number, the target configuration is isolated;

[0180] 3) Isolate the target configuration if the latency of the hard disk array is greater than the preset latency;

[0181] 4) When the bandwidth utilization of the hard disk array does not meet the preset range, isolate the target configuration.

[0182] It should be noted that alert conditions can be a set of predefined performance thresholds. When the actual performance data of the disk array reaches or exceeds these thresholds, the system will trigger specific alerts or actions. These conditions are the basis for the system to determine whether to take emergency measures, such as isolating the target configuration, to protect data or restore performance.

[0183] In an optional implementation, the system first obtains real-time performance data, such as disk error rates, read / write speeds, latency, and the number of checksum errors. It then compares this data with pre-set alert criteria. If the current performance data reaches or exceeds the alert criteria, indicating a potential performance risk or failure, the system will take measures to isolate the target configuration to prevent further impact on the business.

[0184] In an optional implementation, a configuration progress deviation (migration progress deviation) of less than 5% is considered normal, indicating that data migration from one RAID level to another is proceeding as expected without significant delays. If the migration progress deviation exceeds 10% (the first deviation) for three consecutive monitoring periods (preset periods), this may indicate resource contention, hardware performance degradation, or software-level issues, requiring immediate inspection and adjustment to avoid data migration failure or unnecessary business impact.

[0185] In an optional embodiment, a verification failure rate below 0.001% indicates that the RAID group's data verification mechanism is operating properly, effectively ensuring data consistency and integrity. If a single verification task fails more than three times, this typically indicates a potential problem with the storage media, such as bad sectors on the disk or a RAID controller failure. In this case, the system should automatically initiate troubleshooting and data recovery processes to prevent further spread of data corruption and ensure data security.

[0186] In an optional implementation, the impact of service latency should be less than 20% of the baseline, which is the average latency of the system under normal conditions. This means that the system should be able to maintain a relatively stable performance level, even during resource adjustments or optimizations. If service latency increases by more than 50%, this may be due to performance bottlenecks caused by data migration, RAID reconstruction, or disk health issues. In this case, immediate measures should be taken, such as pausing data migration, adjusting stripe size, or increasing redundancy, to reduce latency and avoid a significant degradation in service experience.

[0187] In an optional implementation, the ideal bandwidth utilization range is 70%-90%. A bandwidth utilization rate that is too high or too low is detrimental to the stable operation of the system and the efficient use of resources. If the bandwidth utilization rate is consistently above 95%, it indicates that the system may be overloaded and data transmission or processing capacity has reached its limit, which may affect storage performance and other services that rely on storage resources. Conversely, if the utilization rate is below 50%, there may be resource waste, indicating that storage capacity is not fully utilized. In both cases, the policy control layer should dynamically adjust the striping strategy, RAID level, or load distribution to achieve better resource balance and utilization efficiency.

[0188] Through the above-mentioned implementation of the present application, through a sophisticated monitoring and early warning mechanism, combined with intelligent dynamic strategies, automatic optimization and adjustment are carried out, ensuring that when making RAID configuration adjustments, performance anomalies can be responded to immediately, avoiding negative impacts on business. In the event of an anomaly, the target configuration is quickly isolated, avoiding configuration changes under unstable conditions, ensuring data security, system performance stability, and maximizing resource utilization, thereby providing powerful storage support and service guarantees for various business scenarios.

[0189] In an optional implementation, during the target configuration process of the hard disk array, 5% of the bandwidth can be reserved as a dedicated emergency channel to deal with emergencies such as large-scale data migration, sudden read and write peaks, or data recovery operations. This reserved bandwidth ensures that in an emergency, the system has sufficient resources to quickly respond and handle problems without reducing data processing speed or increasing latency due to resource constraints. When the system detects that the business delay has increased by more than 30% compared to normal, it will automatically terminate the ongoing RAID configuration migration. This is done to avoid possible unstable factors in the configuration change process that further deteriorate business performance, while giving system and operation and maintenance personnel time to diagnose and resolve the problem.

[0190] In an optional implementation manner, after the hard disk array is configured using the target configuration, if a problem occurs, a rollback operation can be performed on the hard disk array.

[0191] Specifically, when performance degradation or data consistency issues caused by abnormal conditions or configuration changes are detected, the system automatically or manually restores to the previous known healthy or stable state. When the system automatically or manually attempts to change the RAID level, striping strategy, or data distribution pattern, if the change operation causes a significant performance degradation or system instability, the rollback mechanism will be quickly activated to restore to the state before the change to ensure that the business is not affected. During the process of migrating data from one RAID group to another, if data loss, verification failure, or abnormal migration progress is detected, the system will immediately stop the migration and perform data recovery or roll back to the configuration state before the migration to ensure data security. If a hard disk or RAID controller failure is detected during dynamic health monitoring, and the system attempts to replace or rebuild data, if there is a problem with the new hardware or the reconstruction process, the rollback mechanism will ensure that a spare hard disk or data backup is used to restore the system to the state before the failure until the problem is completely resolved.

[0192] In an optional implementation, if a problem is encountered during the migration process, such as a data consistency verification failure or an exacerbated disk failure, the system can immediately activate a dual-write verification mechanism. This means that all data write operations are recorded to both the original and new RAID configurations until the data is confirmed to be fully synchronized and consistent. If the new configuration is found to be unsuitable or to have caused additional problems, the system can seamlessly roll back to the original RAID configuration without any data loss.

[0193] In an optional implementation, if the system switches to a RAID 0 configuration with a 1MB stripe due to a high percentage of sequential IO operations, but performance subsequently does not improve or degrades (for example, due to an unexpected increase in random IO), the system will automatically monitor performance changes and automatically roll back to the previous RAID configuration within a specified time window (e.g., 24 hours) based on the monitoring results. This mechanism relies on continuous performance monitoring, and if performance deviates from the normal range, the system will automatically initiate a rollback process, ensuring data consistency and integrity during the rollback process.

[0194] In an optional implementation, when storage utilization remains low, the system initiates RAID group consolidation and defragmentation to optimize storage space usage. However, if business demand suddenly surges during this process, such as after a RAID group consolidation or defragmentation, causing a sudden increase in storage pressure, the system will retain the original configuration settings for at least 24 hours. This means that even if capacity reclamation policies are executed, the system will provide a buffer period to ensure that it can quickly roll back to the original RAID configuration if necessary to cope with the sudden increase in storage space demand.

[0195] In an optional implementation, the system enables the coordinated use of RAID0 and RAID1 based on the detected write latency to meet the performance challenges of mixed read and write modes. However, if the load pattern changes again later, such as switching to pure read mode, the system's built-in dynamic load balancing algorithm will adjust the usage ratio of the RAID configuration based on the latest load status. The system automatically detects changes in the load pattern and reconfigures the RAID level when necessary to adapt to the new workload and ensure optimal performance. This mechanism ensures that the system can maintain the most efficient operation even under extreme load changes.

[0196] Figure 7 is a schematic diagram of an optional hard disk array configuration method according to an embodiment of the present application; Figure 7 As shown, the configuration method of the hard disk array can be applied to Figure 7 The environment in the system may include: policy control layer, virtualized storage layer and physical layer devices. Specifically:

[0197] The policy control layer is responsible for driving the intelligent decision-making and response mechanisms of the entire system. This layer has two key components: a data monitoring, identification, and prediction model, and a dynamic policy engine.

[0198] The data monitoring, identification, and prediction model collects and analyzes real-time performance data from the hard disk array, such as IOPS, throughput, response time, SMART data (disk health indicators), and cache hit rates. Using pattern recognition technology, the model can distinguish between different I / O types (sequential or random) and data block sizes, providing detailed data support for subsequent decision-making. Based on collected historical data, the prediction module employs machine learning or statistical forecasting methods to predict future load trends and drive health, generating adaptive curves and dynamic thresholds. This provides a forward-looking perspective for real-time decision-making at the policy control layer.

[0199] The dynamic policy engine dynamically generates and executes storage policies based on the output of a data monitoring and prediction model, as well as a comprehensive assessment of three dimensions (primary, secondary, and tertiary parameters): failure risk level, service level, and migration cost. Failure risk assessment helps identify potential failure points in the disk array, while service level adjusts the storage configuration based on current business priorities and needs. Migration cost considers the impact of configuration changes on system performance and resources. By making decisions based on these three dimensions, the dynamic policy engine intelligently selects the most appropriate RAID level, stripe size, and redundancy mechanism (target configuration), ensuring optimal storage efficiency and data security while meeting business needs.

[0200] The virtualized storage layer acts as a bridge between the policy control layer and the physical device layer. Its primary responsibility is to execute the policy control layer's decisions, enabling seamless RAID level migration, distributed object storage management, and dynamic striping policies. When the policy control layer decides to switch RAID configurations, the virtualized storage layer is responsible for the actual data reconstruction and migration process, ensuring a smooth transition from one RAID level to another while minimizing service impact. This module allows data to be distributed across multiple physical disks, supporting large datasets and high-concurrency read and write requirements. It enhances the overall performance and scalability of the storage system through data sharding and parallel processing. The dynamic striping engine is responsible for dynamically adjusting the stripe size based on the current workload and access patterns to optimize read and write efficiency. For example, in scenarios with high concurrent read and write activity, the striping engine may select a smaller stripe size to speed data locating; while in scenarios with high sequential read and write activity, it may increase the stripe size to reduce seek time and improve throughput.

[0201] The physical layer, including RAID / SAS controllers and connected hard disk devices, is the hardware foundation for implementing intelligent dynamic RAID strategies. At this level, dynamic health monitoring and early warning systems are key.

[0202] The dynamic health monitoring engine monitors the health of the RAID controller and hard drives in real time, including key indicators such as controller voltage stability, hard drive bad sector rate, temperature fluctuations, and disk rotation speed. Dynamic health monitoring not only monitors the current status but also predicts future health trends through data analysis, providing a more comprehensive basis for decision-making at the policy control layer. The physical layer monitoring system, consisting of a dynamic health monitoring engine and an early warning system, detects controller voltage fluctuations, increases in hard drive bad sector rates, and other indicators in real time, ensuring optimal hardware operation. The early warning system can predict device failures 48 hours in advance, providing system administrators with ample time to perform preventative maintenance or adjust resource allocation, thereby avoiding data loss and business interruption.

[0203] In an optional implementation, deep learning and multi-dimensional sensor technology can be introduced to not only monitor and predict the health status of hard drives and I / O behavior in real time, but also proactively identify potential system-level failures such as power fluctuations and temperature anomalies, further optimizing resource management and fault response strategies.

[0204] An environmental perception layer is added above the physical device layer, integrating temperature sensors, humidity sensors, smoke detectors, vibration sensors, and power status monitoring modules. These sensors not only monitor the health of hard drives and RAID controllers, but also detect the computer room environment and power supply status, providing a more comprehensive view of system health. Leveraging historical performance data, environmental monitoring data, and system event logs, deep neural network models such as convolutional neural networks (CNNs) and long short-term memory networks (LSTMs) are trained to accurately predict the impact of hard drive failures, power instability, and other environmental factors on the storage system. This model is capable of identifying complex correlations and patterns, achieving prediction accuracy superior to traditional statistical models.

[0205] When the deep learning model predicts a possible failure, the system automatically triggers self-healing mechanisms. In addition to existing RAID level adjustment, dynamic striping, and data migration strategies, new self-healing strategies include automatic power supply voltage regulation, environmental condition control (such as activating the cooling system), and isolation and replacement of faulty hardware units.

[0206] The system can also learn storage resource requirements for different time periods and business types by collecting business operating patterns. This enables the intelligent dynamic RAID system to adjust configurations more precisely. For example, before the predicted peak period of video on demand, the relevant storage pool can be switched to RAID 0 to improve read and write speeds; when the data backup period is expected, it can automatically switch to RAID 1 to enhance data security.

[0207] Example 5:

[0208] Imagine a large company's data center predicting that power grid fluctuations caused by nearby construction could impact storage system stability. Based on this prediction, the system automatically activates the UPS's voltage stabilization function and reduces bandwidth usage during RAID configuration migration to reduce power consumption and potential latency. Simultaneously, the environmental sensing layer detects a slight temperature rise in the computer room and activates the cooling system to prevent storage hardware performance degradation or failure due to excessive temperatures.

[0209] The intelligent operations platform received an early warning indicating a large-scale data backup operation expected within the next 48 hours, which could put pressure on storage bandwidth and drive wear. By learning from user behavior and business patterns, the system preemptively migrated some non-critical data to cloud storage, freeing up local storage resources to prepare for the upcoming peak workload. When storage resources within the data center reached the warning threshold, the intelligent system automatically pulled resources from the cloud to provide additional storage space, ensuring unimpeded business continuity.

[0210] Through the integration of deep learning, environmental perception, and an intelligent operation and maintenance platform, this solution not only improves the robustness and responsiveness of the storage system, but also enhances its resistance to environmental factors, providing a solid foundation for the efficient operation of data centers.

[0211] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0212] The embodiment of the present application also provides a configuration device for a hard disk array. Figure 8 This is a structural block diagram of an optional hard disk array configuration device according to an embodiment of the present application, such as Figure 8 As shown, the device includes:

[0213] The performance data acquisition module 802 is used to acquire reference performance data of the hard disk array, wherein the reference performance data is used to indicate the performance data of the hard disk array within a time period;

[0214] A decision condition determination module 804 is configured to determine, from among at least one candidate decision condition, a candidate decision condition that the reference performance data satisfies as a target decision condition, wherein the candidate decision condition indicates a range of performance data of the hard disk array, and each of the at least one candidate decision condition corresponds to a candidate configuration of the hard disk array;

[0215] A target configuration determination module 806 is configured to determine a candidate configuration corresponding to a target decision condition as a target configuration;

[0216] The configuration module 808 is configured to configure the hard disk array to the target configuration when the current configuration of the hard disk array is inconsistent with the target configuration.

[0217] Optionally, the decision condition determination module 804 is further configured to: determine the target decision condition as the first candidate decision condition when the reference performance data indicates that the reliability index of the hard disk array does not satisfy a first index range; and determine the target decision condition as the second candidate decision condition when the reference performance data indicates that the efficiency index of the hard disk array does not satisfy a second index range.

[0218] Optionally, the decision condition determination module 804 is further configured to: the error rate of the hard disk array is greater than a preset error rate, wherein the error rate indicates the ratio of the number of read and write errors of the hard disk array in a unit time to the total number of read and write errors; the error number of the hard disk array is greater than a preset error number, wherein the error number indicates the total number of operation errors occurring in the hard disk array within a period of time; the number of hard disks in the hard disk array that send prompt information is greater than a preset number of hard disks, wherein the prompt information indicates that a hard disk has failed; the proportion of sequential read and write operations of the hard disk array is greater than a preset proportion, wherein sequential read and write indicates that the hard disk array continuously reads or writes data; and the delay time of the hard disk array is greater than a preset delay time, wherein the delay time indicates the time it takes for the hard disk array to complete a write operation.

[0219] Optionally, the decision condition determination module 804 is further configured to: configure the hard disk array to a first target configuration, wherein the first target configuration is a configuration corresponding to the first candidate decision condition; send the target data to the first hard disk in the hard disk array, and establish a mirror of the target data on the second hard disk in the hard disk array; send the target data to the third hard disk in the hard disk array, and send verification information of the target data to the third hard disk.

[0220] Optionally, the above-mentioned decision condition determination module 804 is also used to: configure the hard disk array to a second target configuration, wherein the second target configuration is a configuration corresponding to the second candidate decision condition; divide the target data into multiple sub-data according to a preset stripe, and send the multiple sub-data one by one to the multiple hard disks included in the hard disk array; divide the target data into multiple sub-data according to a preset stripe; send the multiple sub-data one by one to the fifth hard disk included in the hard disk array, and establish a mirror of the sub-data on the sixth hard disk in the hard disk array.

[0221] Optionally, the configuration module 808 is further configured to: calculate a target priority of a target configuration based on a current configuration of the hard disk array; determine a target configuration time according to the target priority; and configure the hard disk array to the target configuration within the target configuration time when the current configuration of the hard disk array is inconsistent with the target configuration.

[0222] Optionally, the configuration module 808 is further configured to: determine a first parameter based on the current configuration of the hard disk array, wherein the first parameter is used to indicate the level of error in the current configuration; determine the importance of data currently processed by the hard disk array as a second parameter; predict the bandwidth occupancy rate used by the target configuration, and determine the negative of the bandwidth occupancy rate as a third parameter; and obtain a target priority by weighted summing the first parameter, the second parameter, the third parameter, and the data access frequency of the hard disk array.

[0223] Optionally, the configuration module 808 is further configured to: obtain current performance data of the hard disk array, and isolate the target configuration if the current performance data satisfies a prompt condition; isolate the target configuration if the configuration progress deviation is greater than the first deviation for a period that satisfies a preset period; isolate the target configuration if the number of verification failures of the hard disk array is greater than a preset number; isolate the target configuration if the delay of the hard disk array is greater than a preset delay; and isolate the target configuration if the bandwidth utilization of the hard disk array does not meet a preset range.

[0224] For descriptions of features in the embodiment corresponding to the hard disk array configuration device, reference can be made to the relevant descriptions of the embodiment corresponding to the hard disk array configuration method, which will not be described in detail here.

[0225] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps of any of the above-mentioned hard disk array configuration method embodiments.

[0226] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps of any of the above-mentioned hard disk array configuration method embodiments when run.

[0227] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0228] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the computer program implements the steps of any of the above-mentioned hard disk array configuration method embodiments.

[0229] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above-mentioned hard disk array configuration method embodiments are implemented.

[0230] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0231] The above describes in detail the configuration method and device for a hard disk array, storage medium, and electronic device provided by this application. This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above embodiments is only intended to help understand the method and core concept of this application. It should be noted that for ordinary technicians in this technical field, various improvements and modifications can be made to this application without departing from the principles of this application, and such improvements and modifications also fall within the scope of protection of the claims of this application.

Claims

1. A method for configuring a hard disk array, characterized in that: include: Acquire reference performance data of the hard disk array, wherein the reference performance data is used to indicate performance data of the hard disk array within a time period; Determining the candidate decision condition satisfied by the reference performance data among at least one candidate decision condition as a target decision condition, wherein the candidate decision condition is used to indicate a range of performance data of the hard disk array, and each of the at least one candidate decision condition corresponds to a candidate configuration of the hard disk array; Determining the candidate configuration corresponding to the target decision condition as the target configuration; When the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration.

2. The method according to claim 1, characterized in that The step of determining the candidate decision condition that the reference performance data satisfies in at least one candidate decision condition as the target decision condition includes: When the reference performance data indicates that the reliability index of the hard disk array does not meet a first index range, determining the target decision condition as a first candidate decision condition; When the reference performance data indicates that the efficiency index of the hard disk array does not meet a second index range, the target decision condition is determined to be a second candidate decision condition.

3. The method according to claim 2, characterized in that When the reference performance data indicates that the reliability index of the hard disk array does not meet the first index range, determining the target decision condition as the first candidate decision condition includes at least one of the following: The error rate of the hard disk array is greater than a preset error rate, wherein the error rate is used to indicate the ratio of the number of read and write errors to the total number of read and write errors of the hard disk array in a unit time; The error number of the hard disk array is greater than a preset error number, wherein the error number is used to indicate the total number of operation errors occurring in the hard disk array within a period of time; The number of hard disks in the hard disk array that send prompt information is greater than a preset number of hard disks, wherein the prompt information is used to indicate that a hard disk has failed; When the reference performance data indicates that the efficiency index of the hard disk array does not meet the second index range, determining the target decision condition as the second candidate decision condition includes at least one of the following: A proportion of sequential read and write operations of the hard disk array is greater than a preset proportion, wherein the sequential read and write indicates that the hard disk array reads or writes data continuously; The delay time of the hard disk array is greater than a preset delay time, wherein the delay time is used to indicate the time it takes for the hard disk array to complete a write operation.

4. The method according to claim 3, characterized in that After determining that the target decision condition is the first candidate decision condition, the method further includes: Configuring the hard disk array to a first target configuration, wherein the first target configuration is a configuration corresponding to the first candidate decision condition; After configuring the hard disk array to the first target configuration, the method further includes one of the following steps: Sending target data to a first hard disk in the hard disk array, and creating a mirror image of the target data on a second hard disk in the hard disk array; The target data is sent to a third hard disk in the hard disk array, and verification information of the target data is sent to the third hard disk.

5. The method according to claim 3, characterized in that After determining that the target decision condition is the second candidate decision condition, the method further includes: Configuring the hard disk array to a second target configuration, wherein the second target configuration is a configuration corresponding to the second candidate decision condition; After configuring the hard disk array to the second target configuration, the method further includes one of the following: Splitting the target data into a plurality of sub-data according to preset stripes, and sending the plurality of sub-data one by one to a plurality of hard disks included in the hard disk array; The target data is divided into a plurality of sub-data according to a preset stripe; the plurality of sub-data are sent one by one to the fifth hard disk included in the hard disk array, and a mirror image of the sub-data is established on the sixth hard disk in the hard disk array.

6. The method according to any one of claims 1 to 5, characterized in that Configuring the hard disk array to the target configuration includes: Calculating a target priority of the target configuration based on a current configuration of the hard disk array; determining a target configuration time according to the target priority; When the current configuration of the hard disk array is inconsistent with the target configuration, the hard disk array is configured to the target configuration within the target configuration time.

7. The method according to claim 6, characterized in that The calculating the target priority of the target configuration based on the current configuration of the hard disk array includes: Determine a first parameter according to a current configuration of the hard disk array, wherein the first parameter is used to indicate a level of error in the current configuration; determining the importance of data currently processed by the hard disk array as a second parameter; Predicting a bandwidth occupancy rate used by the target configuration, and determining a negative of the bandwidth occupancy rate as a third parameter; The target priority is obtained by weightedly summing the first parameter, the second parameter, the third parameter, and the data access frequency of the hard disk array.

8. The method according to any one of claims 1 to 5, characterized in that Configuring the hard disk array to the target configuration includes: Acquiring current performance data of the hard disk array, and isolating the target configuration if the current performance data meets a prompt condition; When the current performance data satisfies the prompt condition, isolating the target configuration includes at least one of the following: When the configuration progress deviation is greater than the first deviation for a period that satisfies a preset period, isolating the target configuration; If the number of verification failures of the hard disk array is greater than a preset number, isolating the target configuration; When the delay of the hard disk array is greater than a preset delay, isolating the target configuration; When the bandwidth utilization of the hard disk array does not meet a preset range, the target configuration is isolated.

9. An electronic device, characterized in that: include: memory for storing computer programs; A processor, configured to implement the steps of the hard disk array configuration method according to any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the method for configuring a hard disk array according to any one of claims 1 to 8 are implemented.

Images