Fault information storage method and device, computer device and storage medium

CN117312022BActive Publication Date: 2026-10-23SHENZHEN JAGUAR MICROSYSTEMS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202210723811.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-06-24
Publication Date
2026-10-23
Estimated Expiration
2042-06-24

AI Technical Summary

Technical Problem

如果DPU异常或者DPU模拟的功能设备(例如虚拟网络设备和虚拟存储设备等)异常,会导致计算机设备的操作系统无法保留故障发生时的信息

Benefits of technology

[0023]第四方面,本申请提供了一种计算机可读存储介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现上述第一方面提供的方法的步骤。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117312022B_ABST
    Figure CN117312022B_ABST
Patent Text Reader

Abstract

The fault information storage method provided by the application selects a storage mode for storing fault information through the network and / or storage device of the host as a second storage rule from the first storage rule pre-configured when the host starts. Then, the fault information of the host is dumped in a log file when the host fails, and a storage mode for storing fault information through the network and / or storage device that can normally operate when the host fails and has a high priority is selected as a third storage rule from the second storage rule according to the network and / or storage device that can normally operate when the host fails, and the log file is stored according to the third storage rule. Therefore, the fault information storage method provided by the application has high adaptability, and can make the operating system of the host retain information at the time of failure for the host installed with a DPU or the host without the DPU.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer equipment, storage medium, and computer program product for storing fault information. Background Technology

[0002] Computer devices typically have an operating system (such as Linux) installed and are configured to store fault information when the operating system crashes, i.e., when the computer device malfunctions, to facilitate maintenance personnel in locating and analyzing the cause of the fault. However, current methods of storing fault information assume that the computer device's storage and network functions are in normal working order.

[0003] However, for computer devices equipped with a DPU (Data Processing Unit), since the DPU can provide storage and networking functions and take over these functions, to save costs, the computer's operating system can be installed on a storage device emulated by the DPU (i.e., a virtual storage device), and the network used by the operating system can use a network device emulated by the DPU (i.e., a virtual network device). If the DPU malfunctions or the functional devices emulated by the DPU (such as virtual network devices and virtual storage devices) malfunction, the computer's operating system will be unable to retain information from the time of the failure.

[0004] Therefore, current fault information storage methods have the drawback of low adaptability. For computer devices equipped with DPUs, the operating system of the computer device may not be able to retain information when the fault occurred. Summary of the Invention

[0005] This application can provide a highly adaptable fault information storage method, apparatus, computer device, computer-readable storage medium, and computer program product. For computer devices equipped with a DPU, it can also enable the computer device's operating system to retain information when a fault occurs.

[0006] In a first aspect, this application provides a method for storing fault information, the method comprising:

[0007] When the host starts up, it acquires the host's network and / or storage devices;

[0008] Retrieve the pre-configured first storage rule;

[0009] A second storage rule is selected from the first storage rule, wherein the second storage rule includes a storage method for storing the fault information through the host's network and / or storage devices;

[0010] When the host fails, the fault information of the host is dumped to the log file;

[0011] Obtain network and / or storage devices that can operate normally when the host fails;

[0012] A third storage rule is selected from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault;

[0013] The log file is stored according to the third storage rule.

[0014] Secondly, this application provides a fault information storage device, the device comprising:

[0015] The first acquisition module is used to acquire the host's network and / or storage devices when the host starts up;

[0016] The second acquisition module is used to acquire the pre-configured first storage rule;

[0017] A first selection module is used to select a second storage rule from the first storage rule, wherein the second storage rule includes a storage method for storing the fault information through the host's network and / or storage device;

[0018] A dump module is used to dump the fault information of the host to a log file when the host fails.

[0019] The third acquisition module is used to acquire network and / or storage devices that the host can operate normally in the event of a failure.

[0020] The second selection module is used to select a third storage rule from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault;

[0021] A storage module is used to store the log files in accordance with the third storage rule.

[0022] Thirdly, this application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method provided in the first aspect above.

[0023] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method provided in the first aspect above.

[0024] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method provided in the first aspect above.

[0025] The fault information storage method provided in this application, through the above steps, can select a storage method from a pre-configured list of all possible storage methods for fault information, choosing a network and / or storage device that supports the host's normal operation during a fault. This allows the host's operating system to retain information from the time of the fault, whether the host has a DPU or not. Therefore, the fault information storage method provided in this application has high adaptability. Attached Figure Description

[0026] Figure 1 A flowchart illustrating the fault information storage method provided in the first embodiment of this application;

[0027] Figure 2 This is a schematic diagram of a fault information storage device provided in the second embodiment of this application;

[0028] Figure 3 A schematic diagram of the modules of a computer device provided in the third embodiment of this application. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0030] The fault information storage method provided in this application can be applied to hosts in data centers (e.g., computer rooms) that are configured with DPUs (Data Processing Units) or hosts that are not configured with DPUs.

[0031] The host can be implemented using a standalone server or a server cluster consisting of multiple servers. The host can be equipped with smart network interface cards (NICs). For example, smart NICs based on FPGAs (Field Programmable Gate Arrays) or SoCs (System on Chips) can be used. Smart NICs may include digital processing units (DPUs). DPUs can simulate virtual network devices and virtual storage devices.

[0032] The host includes an operating system. The host's operating system can be installed in a virtual storage device emulated by the DPU. If the DPU malfunctions or the functional devices emulated by the DPU (such as virtual network devices and / or virtual storage devices) malfunction, the host's operating system may crash, meaning the host malfunctions and the operating system cannot retain information from the time of the failure.

[0033] The fault information storage method provided in this application selects a storage method that stores fault information via the host's network and / or storage devices from a pre-configured first storage rule as a second storage rule when the host starts up. Then, when the host fails, the fault information is dumped into a log file. Furthermore, based on the network and / or storage devices that the host can operate normally during a fault, a storage method with higher priority that stores fault information via a network and / or storage device that the host can operate normally during a fault is selected from the second storage rule as a third storage rule, and the log file is stored according to the third storage rule. In other words, the fault information storage method provided in this application can store fault information by selecting a storage method that supports the host's normal operation via a network and / or storage device from a pre-configured list of all possible storage methods. This allows the host's operating system to retain information at the time of the fault, whether the host has a DPU or not. Therefore, the fault information storage method provided in this application has high adaptability.

[0034] To illustrate the fault information storage method provided in this application in detail, the following description is provided in conjunction with the accompanying drawings and embodiments.

[0035] Please see Figure 1 , Figure 1 This is a flowchart illustrating the fault information storage method provided in the first embodiment of this application. The fault information storage method provided in the first embodiment of this application may include the following steps:

[0036] Step S101: When the host starts up, obtain the host's network and / or storage devices.

[0037] Specifically, when the host is powered on and the operating system begins to run normally, the host can be controlled to obtain the host's network and / or storage devices, i.e., network devices and / or storage devices, through the operating system's system tools (such as the lspci command).

[0038] Step S103: Obtain the pre-configured first storage rule.

[0039] Specifically, operations and maintenance (O&M) personnel can configure the primary storage rules on the data center's O&M platform through configuration files or online interaction. The O&M platform can be a software program running on a standalone server or a server cluster composed of multiple servers, used by O&M personnel to maintain hosts in the data center. The primary storage rules include various storage methods for storing fault information, each with different priorities. When a host starts up, it can be controlled to retrieve the pre-configured primary storage rules from the O&M platform.

[0040] In a modified embodiment of the first embodiment, the first storage rule can be configured to include multiple storage methods for storing the fault information through different networks and / or storage devices, each of which has a different priority.

[0041] In a data center, hosts responsible for different service types may include different network and / or storage devices, or they may include the same network and / or storage devices. These network and / or storage devices can be any one of the following devices, or a combination of any number of the following devices: the host's local network device, the host's local storage device, a BMC (Baseboard Manager Controller) device, a virtual network device simulated by the DPU, a virtual storage device simulated by the DPU, etc. It should be noted that the BMC device mentioned in this application refers to the storage of the BMC device.

[0042] Accordingly, the storage methods can include at least the following: Storage Method 1: Fault information is stored using the host's local network device combined with cloud storage; Storage Method 2: Fault information is stored using a virtual network device simulated by the DPU combined with cloud storage; Storage Method 3: Fault information is stored using the host's local storage device; Storage Method 4: Fault information is stored using a virtual storage device simulated by the DPU; Storage Method 5: Fault information is stored using the host's BMC device. The priority of Storage Method 1 is 1; the priority of Storage Method 2 is 2; the priority of Storage Method 3 is 3; the priority of Storage Method 4 is 4; and the priority of Storage Method 5 is 5. It should be noted that the priority of each storage method can be set according to its reliability.

[0043] The fault information storage method provided in the first embodiment of this application enumerates the types of networks and / or storage devices that all hosts in a data center may include, and then pre-configures a first storage rule that includes all possible storage methods for storing fault information. For any host in the data center, whether it has a DPU or not, the host's operating system can retain information from when a fault occurred. Therefore, the fault information storage method provided in this embodiment has high adaptability.

[0044] Step S105: Select a second storage rule from the first storage rule, wherein the second storage rule includes a storage method for storing the fault information through the host's network and / or storage device.

[0045] Specifically, the fault information storage method provided in the first embodiment of this application can control the host to select a suitable storage method for storing fault information through the host's own network and / or storage device from the first storage rules as the second storage rule based on the host's own network and / or storage device.

[0046] For example, if the host's network and / or storage devices include virtual network devices, virtual storage devices, and BMC devices, then the host can be controlled to select a second storage rule from the first storage rule based on the virtual network devices, virtual storage devices, and BMC devices. The second storage rule includes: Storage method 5: The host's BMC device stores fault information (priority 5); Storage method 2: The virtual network device simulated by the DPU is combined with the cloud storage device to store fault information (priority 2); Storage method 4: The virtual storage device simulated by the DPU stores fault information (priority 4).

[0047] Step S107: When the host fails, the fault information of the host is dumped into the log file.

[0048] Specifically, when the host's operating system crashes, i.e., when the host fails, the host can be controlled to use the operating system's kdump tool to dump the fault information (e.g., data running in memory at the time of the fault) into a log file. In the fault information storage method provided in the first embodiment of this application, dumping the data running in memory into a log file when the host fails is beneficial for protecting the on-site data that caused the host failure.

[0049] Step S109: Obtain the network and / or storage devices that the host can operate normally in the event of a failure.

[0050] Specifically, when the host fails, the host can be controlled to detect whether the network device is functioning normally via the operating system's ping command, and the host can be controlled to detect whether the storage device is functioning normally via the operating system's touch command. In the first embodiment, for example, if the host detects that the virtual network device is not functioning normally via the operating system's ping command, and the host detects that both the virtual storage device and the BMC device are functioning normally via the operating system's touch command, then it can be determined that the network and / or storage devices that can function normally when the host fails include the virtual storage device and the BMC device. It should be noted that the network and / or storage devices that can function normally mean that the drivers loaded on the network and / or storage devices are in a normal operating state.

[0051] Step S1011: Select a third storage rule from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault.

[0052] Specifically, after obtaining the network and / or storage devices that the host can operate normally in the event of a failure, a third storage rule can be formed from the second storage rule. The third storage rule includes a storage method that stores the failure information through the network and / or storage devices that the host can operate normally in the event of a failure and has a high priority.

[0053] For example, if the host's virtual storage device and BMC device can operate normally when the host fails, and the second storage rule includes: Storage method 5: The host's BMC device stores fault information (priority 5); Storage method 2: The virtual network device simulated by the DPU, combined with cloud storage device, stores fault information (priority 2); Storage method 4: The virtual storage device simulated by the DPU stores fault information (priority 4), then a third storage rule can be selected from the second storage rule, where the third storage rule includes: Storage method 4: The virtual storage device simulated by the DPU stores fault information (priority 4).

[0054] Step S1013: Store the log file according to the third storage rule.

[0055] Specifically, after determining the third storage rule, the host can be controlled to store log files according to the third storage rule. In a modified embodiment of the first embodiment, the log files storing fault information can also be sent to the operation and maintenance platform in an agreed format for analysis by operation and maintenance personnel.

[0056] The fault information storage method provided in this application, through the above steps, can select a storage method from a pre-configured list of all possible storage methods for fault information, choosing a network and / or storage device that supports the host's normal operation during a fault. This allows the host's operating system to retain information from the time of the fault, whether the host has a DPU or not. Therefore, the fault information storage method provided in this application has high adaptability.

[0057] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.

[0058] Correspondingly, the second embodiment of this application also provides a fault information storage device. The implementation scheme of this fault information storage device is similar to the implementation scheme of the fault information storage method provided in the first embodiment. Therefore, for a detailed description of the fault information storage device provided in the second embodiment of this application, please refer to the detailed description of the fault information storage method provided in the first embodiment.

[0059] Please see Figure 2 , Figure 2 This is a fault information storage device provided in the second embodiment of this application. The fault information storage device may include: a first acquisition module 201, a second acquisition module 203, a first selection module 205, a dump module 207, a third acquisition module 209, a second selection module 2011, and a storage module 2013. Wherein:

[0060] The first acquisition module 201 is used to acquire the host's network and / or storage devices when the host starts up.

[0061] Specifically, when the host is powered on and the operating system starts to run normally, the first acquisition module 201 can control the host to acquire the host's network and / or storage devices, i.e., network devices and / or storage devices, through the operating system's system tools (e.g., lspci).

[0062] The second acquisition module 203 is used to acquire the pre-configured first storage rule.

[0063] Specifically, operations and maintenance personnel can configure the first storage rule on the data center's operations and maintenance platform through configuration files or online interaction. The operations and maintenance platform can be a software program running on a standalone server or a server cluster composed of multiple servers, used by operations and maintenance personnel to maintain hosts in the data center. The first storage rule includes various storage methods for storing fault information, each with different priorities. When a host starts up, the second acquisition module 203 can control the host to retrieve the pre-configured first storage rule from the operations and maintenance platform.

[0064] In a modified embodiment of the second embodiment, the first storage rule can be configured to include multiple storage methods for storing the fault information through different networks and / or storage devices, each of which has a different priority.

[0065] In a data center, hosts responsible for different service types may include different network and / or storage devices, or they may include the same network and / or storage devices. These network and / or storage devices can be any one of the following devices, or a combination of any number of the following devices: the host's local network device, the host's local storage device, a BMC (Baseboard Manager Controller) device, a virtual network device simulated by the DPU, a virtual storage device simulated by the DPU, etc. It should be noted that the BMC device mentioned in this application refers to the storage of the BMC device.

[0066] Accordingly, the storage methods can include at least the following: Storage Method 1: Fault information is stored using the host's local network device combined with cloud storage; Storage Method 2: Fault information is stored using a virtual network device simulated by the DPU combined with cloud storage; Storage Method 3: Fault information is stored using the host's local storage device; Storage Method 4: Fault information is stored using a virtual storage device simulated by the DPU; Storage Method 5: Fault information is stored using the host's BMC device. The priority of Storage Method 1 is 1; the priority of Storage Method 2 is 2; the priority of Storage Method 3 is 3; the priority of Storage Method 4 is 4; and the priority of Storage Method 5 is 5. It should be noted that the priority of each storage method can be set according to its stability.

[0067] The fault information storage device provided in the second embodiment of this application enumerates the types of networks and / or storage devices that all hosts in a data center may include, and then accordingly obtains a first storage rule pre-configured with all possible storage methods for storing fault information through the second acquisition module. For any host in the data center, whether it has a DPU or not, the host's operating system can retain information at the time of the fault. Therefore, the fault information storage device provided in this embodiment has high adaptability.

[0068] The first selection module 205 is used to select a second storage rule from the first storage rule, wherein the second storage rule includes a storage method for storing the fault information through the host's network and / or storage device.

[0069] Specifically, the fault information storage device provided in the second embodiment of this application can control the host to select a suitable storage method for storing fault information through the host's own network and / or storage device as the second storage rule based on the host's own network and / or storage device from the first storage rule through the first selection module 205.

[0070] The dump module 207 is used to dump the fault information of the host into a log file when the host fails.

[0071] Specifically, when the host's operating system crashes, i.e., when the host fails, the dump module 207 can control the host to dump the fault information (e.g., data running in memory) to a log file using the operating system's kdump tool. In the fault information storage device provided in the second embodiment of this application, the dump module dumps the data running in memory to a log file when the host fails, which helps protect the on-site data that caused the host failure.

[0072] The third acquisition module 209 is used to acquire the network and / or storage devices that the host can operate normally in the event of a failure.

[0073] Specifically, when the host fails, the third acquisition module 209 can control the host to detect whether the network device is running normally through the ping command of the operating system, and control the host to detect whether the storage device is running normally through the touch command of the operating system.

[0074] The second selection module 2011 is used to select a third storage rule from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault.

[0075] Specifically, after obtaining the network and / or storage devices that the host can operate normally in the event of a failure, the second selection module 2011 can control the host to form a third storage rule from the second storage rule. The third storage rule includes a storage method that stores the fault information through the network and / or storage devices that the host can operate normally in the event of a failure and has a high priority.

[0076] Storage module 2013 is used to store the log file in accordance with the third storage rule.

[0077] Specifically, after determining the third storage rule, the storage module 2013 can control the host to store log files according to the third storage rule. In a modified embodiment of the second embodiment, the fault information storage device may further include a sending module. The sending module is used to control the host to send the log files storing fault information to the operation and maintenance platform in an agreed format for analysis by operation and maintenance personnel.

[0078] The fault information storage device provided in this application, through the aforementioned functional modules, can select a storage method from a pre-configured list of all possible storage methods for fault information, choosing a network and / or storage device that supports the host's normal operation during a fault. This allows the host's operating system to retain information from the time of the fault, whether the host has a DPU or not. Therefore, the fault information storage device provided in this application has high adaptability.

[0079] Each functional module in the aforementioned fault information storage device can be implemented entirely or partially through software, hardware, or a combination thereof. These functional modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each functional module.

[0080] Accordingly, the third embodiment of this application also provides a computer device, the internal structure of which can be illustrated as follows: Figure 3 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data such as fault information. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a fault information storage method.

[0081] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0082] Accordingly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the above-described fault information storage method.

[0083] Accordingly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described fault information storage method.

[0084] Accordingly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described fault information storage method.

[0085] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The processors involved in the embodiments provided in this application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited thereto.

[0086] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0087] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for storing fault information, characterized in that, The method includes: When the host starts up, it acquires the host's network and / or storage devices, which include any one of the following devices, or any combination of the following devices: local network devices and / or storage devices, storage of the host's BMC device, and acquires virtual network devices and virtual storage devices simulated by the DPU, wherein the host is configured with the DPU; Obtain a pre-configured first storage rule, wherein the first storage rule includes: Storage method 1: storage method of storing fault information using the host's local network device in conjunction with cloud storage device; Storage method 2: storage method of storing fault information using a virtual network device simulated by the DPU in conjunction with cloud storage device; Storage method 3: storage method of storing fault information using the host's local storage device; Storage method 4: storage method of storing fault information using a virtual storage device simulated by the DPU; Storage method 5: storage method of storing fault information using the host's BMC device; wherein each of the storage methods has a different priority. A second storage rule is selected from the first storage rule, wherein the second storage rule includes a storage method suitable for storing the fault information through the host's own network and / or storage devices; When the host fails, the fault information of the host is dumped to the log file; Obtain network and / or storage devices that can operate normally when the host fails; A third storage rule is selected from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault; The log file is stored according to the third storage rule.

2. The method according to claim 1, characterized in that, The first storage rule is configured to include multiple storage methods for storing the fault information through different networks and / or storage devices, each of which has a different priority.

3. The method according to claim 1 or 2, characterized in that, The first storage rule is configured on the operation and maintenance platform.

4. The method according to claim 1, characterized in that, The fault information includes data that was running in memory when the host failed.

5. A fault information storage device, characterized in that, The device includes: The first acquisition module is used to acquire the network and / or storage devices of the host when the host starts up. The network and / or storage devices include any one of the following devices, or any combination of the following devices: local network devices and / or storage devices, storage of the host's BMC device, and acquire virtual network devices and virtual storage devices simulated by the DPU, wherein the host is configured with the DPU. The second acquisition module is used to acquire pre-configured first storage rules, wherein the first storage rules include: Storage method 1: storage method of storing fault information by combining the host's local network device with cloud storage device; Storage method 2: storage method of storing fault information by combining the virtual network device simulated by the DPU with cloud storage device; Storage method 3: storage method of storing fault information by the host's local storage device; Storage method 4: storage method of storing fault information by the virtual storage device simulated by the DPU; Storage method 5: storage method of storing fault information by the host's BMC device; wherein each of the storage methods has a different priority. A first selection module is used to select a second storage rule from the first storage rule, wherein the second storage rule includes a storage method suitable for storing the fault information through the host's own network and / or storage device; A dump module is used to dump the fault information of the host to a log file when the host fails. The third acquisition module is used to acquire network and / or storage devices that the host can operate normally in the event of a failure. The second selection module is used to select a third storage rule from the second storage rule, wherein the third storage rule includes a storage method with high priority that stores the fault information through a network and / or storage device that the host can operate normally in the event of a fault; A storage module is used to store the log files in accordance with the third storage rule.

6. The apparatus according to claim 5, characterized in that, The first storage rule is configured to include multiple storage methods for storing the fault information through different networks and / or storage devices, each of which has a different priority.

7. The apparatus according to claim 5 or 6, characterized in that, The first storage rule is configured on the operation and maintenance platform.

8. The apparatus according to claim 5, characterized in that, The fault information includes data that was running in memory when the host failed.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 4.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 4.

Citation Information

Patent Citations

  • Data storage method and device of distributed storage system

    CN102571845A