Data updating method and apparatus, and distributed system

Abstract

The application provides a data updating method and device and a distributed system. The method comprises the following steps: in response to a replacement operation of a first security control board card corresponding to a target node in the distributed system, a configuration recovery interface including a configuration recovery control is displayed; in response to a trigger operation on the configuration recovery control, a configuration file of a first baseboard management controller integrated on the first security control board card is acquired; the configuration file is transmitted to a second baseboard management controller integrated on a second security control board card; the second security control board card is a board card used after the first security control board card is replaced.

Description

Technical Field

[0001] This application relates to electronic information technology, and more particularly to a data updating method, apparatus and distributed system. Background Technology

[0002] Distributed systems can rely on multi-node clusters to achieve collaborative operation. The Baseboard Management Controller (BMC), as the core management module of the nodes in the distributed system, is integrated onto the Secure Control Module (SCM) board. The BMC stores critical configurations (such as network, accounts, certificates, and platform policies). If the SCM board fails or is replaced, the locally stored configuration data is usually lost, leading to operational risks such as difficulty in configuration recovery and failure of remote node control. Summary of the Invention

[0003] In view of this, embodiments of this application provide at least one data update method, apparatus, and distributed system.

[0004] The technical solution of this application embodiment is implemented as follows: In a first aspect, embodiments of this application provide a data update method, which is applied to the system management module of a distributed system, and the method includes: In response to the replacement operation of the first security control board corresponding to the target node in the distributed system, a configuration recovery interface including configuration recovery controls is displayed. In response to a trigger operation on the configuration recovery control, the configuration file of the first baseboard management controller integrated on the first security control board is obtained; The configuration file is transmitted to the second baseboard management controller integrated on the second security control board; the second security control board is the board that is put into use after replacing the first security control board.

[0005] Secondly, embodiments of this application provide a data update method applied to a second baseboard management controller integrated on a second security control board. The data update method includes: Obtain the configuration file of the first baseboard management controller, which is integrated on the first security control board, corresponding to the target node in the distributed system; Update configuration parameters based on configuration file; The configuration file is a file obtained by the system management module of the distributed system in response to the trigger operation of the configuration recovery control and transmitted to the second baseboard management controller; the configuration recovery control belongs to the configuration recovery interface; the configuration recovery interface is triggered and displayed in response to the replacement operation of the first security control board.

[0006] Thirdly, embodiments of this application provide a data updating apparatus, the apparatus comprising: The display unit is used to respond to the replacement operation of the first security control board corresponding to the target node in the distributed system and display the configuration recovery interface including the configuration recovery control. The first acquisition unit is used to acquire the configuration file of the first baseboard management controller integrated on the first security control board in response to a trigger operation on the configuration recovery control. The transmission unit is used to transmit configuration files to the second baseboard management controller integrated on the second security control board; the second security control board is the board that is put into use after replacing the first security control board.

[0007] Fourthly, embodiments of this application provide a distributed system, which includes a system management module and multiple nodes; wherein the system management module is used for: In response to the replacement operation of the first security control board corresponding to the target node among multiple nodes, a configuration recovery interface including configuration recovery controls is displayed; In response to a trigger operation on the configuration recovery control, the configuration file of the first baseboard management controller integrated on the first security control board is obtained; The configuration file is transmitted to the second baseboard management controller integrated on the second security control board; the second security control board is the board that is put into use after replacing the first security control board.

[0008] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this application. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0010] Figure 1 A schematic diagram of the implementation process of a data update method provided in this application embodiment. Figure 1 ; Figure 2 A schematic diagram of the configuration recovery interface provided in an embodiment of this application; Figure 3 A schematic diagram of the composition structure of a distributed system provided in this application embodiment. Figure 1 ; Figure 4 A schematic diagram of the implementation process of a data update method provided in this application embodiment. Figure 2 ; Figure 5 A schematic diagram of the composition structure of a data update device provided in this application embodiment. Figure 1 ; Figure 6 A schematic diagram of the composition structure of a data update device provided in this application embodiment. Figure 2 ; Figure 7 A schematic diagram of the composition structure of a distributed system provided in this application embodiment. Figure 2 ; Figure 8 This is a schematic diagram of a hardware entity of the data update device provided in an embodiment of this application. Detailed Implementation

[0011] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0012] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0013] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0014] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0015] To address the technical problems in related technologies, embodiments of this application provide a data update method that can be applied to the System Management Module (SMM) of a distributed system. The technical solution of this application will be described in detail below with reference to embodiments, such as... Figure 1 As shown, this data update method can be implemented through steps S101 to S103: Step S101: In response to the replacement operation of the first security control board corresponding to the target node in the distributed system, a configuration recovery interface including configuration recovery controls is displayed.

[0016] Here, the target node refers to the node in a distributed system whose security control board needs to be replaced. For example, this security control board could be an SCM board.

[0017] In this embodiment, the system management module communicates with the security control boards of each node in real time. When the first security control board corresponding to the target node is replaced, the communication between the system management module and the first security control board is interrupted. At this time, the system management module determines that the first security control board corresponding to the target node has been replaced.

[0018] In this embodiment, the electronic device containing the system management module includes a display component. After determining that the first security control board corresponding to the target node has been replaced, the system management module displays a configuration recovery interface through the display component. This configuration recovery interface includes a configuration recovery control, which, when triggered, retrieves the configuration file of the first baseboard management controller integrated on the first security control board that has been successfully backed up.

[0019] Step S102: In response to a trigger operation on the configuration recovery control, obtain the configuration file of the first baseboard management controller integrated on the first security control board.

[0020] In this embodiment, a first baseboard management controller (BMC) is integrated on the first security control board, and the first baseboard management controller stores a configuration file. The configuration file includes configuration parameters, which, exemplarily, may include at least one of the following: network parameters, account parameters, certificates, and platform policies.

[0021] Understandably, the baseboard management controller corresponding to each node will periodically back up its stored configuration file to the system management module. For example, the baseboard management controller can back up its configuration file every 24 hours. The system management module can store the configuration files sent by each baseboard management controller in its memory. That is, before the first security control board is replaced, the system management module has already stored the configuration file of the first baseboard management controller, and therefore can retrieve the configuration file of the first baseboard management controller from its own memory when the user triggers the configuration recovery control. The memory of the system management module can be persistent memory. For example, this persistent memory can include at least one of the following: Read Only Memory (ROM), Ferromagnetic Random Access Memory (FRAM), or other non-volatile storage media.

[0022] For example, such as Figure 2 As shown, the configuration recovery interface 20 includes a password setting control 201, a backup process control 202, and a download backup file control 203 (i.e., a configuration recovery control). After receiving a replacement operation from the download backup file control 203, the configuration file of the first baseboard management controller integrated on the first security control board can be obtained.

[0023] Step S103: Transmit the configuration file to the second baseboard management controller integrated on the second security control board; the second security control board is the board put into use after replacing the first security control board.

[0024] In this embodiment, after the first security control board of the target node is replaced with the second security control board, the second baseboard management controller integrated on the second security control board and the system management module establish a communication connection. At this time, the system management module can transmit a configuration file to the second baseboard management controller. After the second baseboard management controller obtains the configuration file transmitted by the system management module, it can update its own configuration parameters based on the configuration file.

[0025] In some embodiments, after obtaining the configuration file of the first baseboard management controller, the configuration file can be encrypted, and then the encrypted configuration file can be transmitted to the second baseboard management controller. For example, as shown... Figure 2 As shown, the configuration recovery interface 20 also includes encrypting the entire file control 204 and encrypting only the sensitive data control 205. In response to the selection operation of encrypting the entire file control 204 or encrypting only the sensitive data control 205, the encryption object is determined, and then the determined encryption object is encrypted.

[0026] In this embodiment, after the system management module detects a replacement operation on the first security control board corresponding to the target node in the distributed system, it displays a configuration recovery interface containing configuration recovery controls. When the system management module detects a trigger operation on the configuration recovery controls, it can obtain the configuration file of the first baseboard management controller integrated on the first security control board and transmit the configuration file to the second baseboard management controller integrated on the replaced second security control board. This allows for rapid configuration migration and restoration, resolving the configuration loss problem caused by security control board replacement and effectively reducing the operational risks of the distributed cluster.

[0027] In some embodiments, step S102 can also be implemented by steps S201 and S202: Step S201: In response to the triggered operation of the configuration recovery control, determine the incremental information of the configuration file and obtain the first backup file; the first backup file is the complete configuration file of the first backup.

[0028] It is understandable that the periodic backup of the configuration files stored by the baseboard management controllers corresponding to each node to the system management module refers to backing up the current incremental information to the system management module. This current incremental information is determined by comparing the current complete configuration file of the baseboard management controller with the initial backup file. For example, the configuration changes between the current complete configuration file and the initial backup file are defined as the current incremental information. In other words, the system management module stores incremental information that has changed relative to the initial backup file.

[0029] In some embodiments, the current incremental information can also be determined by comparing the current complete configuration file of the baseboard management controller with the previous complete configuration file. For example, the configuration changes between the current complete configuration file and the previous complete configuration file are determined as the current incremental information. That is, the system management module stores incremental information that has changed relative to the previous complete configuration file.

[0030] In this embodiment of the application, different incremental information corresponds to different backup dates. Therefore, the incremental information corresponding to the target backup date can be determined by obtaining the target backup date input by the user.

[0031] Step S202: Based on the incremental information and the initial backup file, determine the configuration file of the first baseboard management controller.

[0032] In this embodiment, the initial backup file can be modified based on incremental information to obtain the configuration file of the first baseboard management controller.

[0033] In this embodiment, in response to a trigger operation on the configuration recovery control, incremental information of the configuration file is determined, and the first backup file is obtained; the first backup file is the complete configuration file from the first backup. Then, based on the incremental information and the first backup file, the configuration file of the first baseboard management controller is determined. In this way, when the baseboard management controller of each node is backed up, it can only back up the configuration changes that differ from the first backup file. When configuration recovery is needed, the complete configuration file from the previous backup can be obtained through the incremental information and the first backup file, thereby simplifying the backup operation of each node, reducing the storage resources occupied by backup data, and ensuring accurate and efficient execution of the configuration recovery process.

[0034] In some embodiments, the step S201 above, "determining incremental information of the configuration file in response to a trigger operation on the configuration recovery control," can be implemented through steps S301 and S302: Step S301: In response to the triggered operation of the configuration recovery control, a file selection interface is displayed; the file selection interface includes multiple selection controls; different selection controls correspond to the backup time of different incremental information.

[0035] In this embodiment of the application, when the user triggers the configuration recovery control, the system management module can display a file selection interface through the display component. The file selection interface includes multiple selection controls, each of which corresponds to a backup time. This backup time represents the time when the first baseboard management controller of the target node backs up incremental information to the system management module. In other words, each backup time corresponds to an incremental information, so different selection controls correspond to the backup time of different incremental information.

[0036] It is understandable that when the first security control board of the target node is replaced by the second security control board, the user may not need to back up the current configuration file of the first baseboard management controller of the first security control board to the second security control board. Therefore, by displaying multiple selection controls, the user can be provided with the function of restoring incremental information and corresponding complete configuration files at any backup time point, so as to meet the differentiated configuration recovery needs.

[0037] Step S302: In response to a trigger operation on a target selection control among multiple selection controls, incremental information of the configuration file is obtained based on the target backup time corresponding to the target selection control.

[0038] In this embodiment of the application, after displaying multiple selection controls, the user can trigger a target selection control among the multiple selection controls. At this time, the system management module can obtain the incremental information backed up by the first baseboard management controller of the target node to the system management module at the target backup time based on the target backup time corresponding to the target selection control.

[0039] In this embodiment, in response to a trigger operation on the configuration recovery control, a file selection interface is displayed. The file selection interface includes multiple selection controls; different selection controls correspond to backup times for different incremental information. In response to a trigger operation on the target selection control among the multiple selection controls, incremental information of the configuration file is obtained based on the target backup time corresponding to the target selection control. This provides multiple historical incremental information selection entry points, allowing users to select incremental information corresponding to the target backup time as needed, thus meeting the recovery needs of different historical version configurations.

[0040] In some embodiments, step S302 can be implemented by steps S401 to S403: Step S401: In response to a trigger operation on a target selection control among multiple selection controls, determine the target backup time corresponding to the target selection control.

[0041] In this embodiment of the application, each of the multiple selection controls corresponds to a backup time. Therefore, when a trigger operation is received for the target selection control among the multiple selection controls, the target backup time corresponding to the target selection control can be determined.

[0042] Step S402: Determine the target incremental information corresponding to the target backup time, and at least one other incremental information corresponding to all other backup times before the target backup time.

[0043] Step S403: The target incremental information and at least one other incremental information are determined as the incremental information of the configuration file.

[0044] In this embodiment, target incremental information is obtained based on the target backup time. Then, all other backup times prior to the target backup time are determined based on the target backup time. Corresponding additional incremental information is obtained for each of these additional backup times. Finally, the target incremental information and at least one other additional incremental information are used as the incremental information for the configuration file.

[0045] It is understood that the current incremental information (i.e., target incremental information and other incremental information) in this embodiment is determined by comparing the current complete configuration file of the baseboard management controller with the previous complete configuration file. Therefore, obtaining only the target incremental information and the first backup file is insufficient to obtain the complete configuration file of the first baseboard management controller at the target backup time. Therefore, it is also necessary to obtain at least one other incremental information corresponding to all other backup times prior to the target backup time. The target incremental information and at least one other incremental information together constitute the complete configuration file of the first baseboard management controller at the target backup time, which is equivalent to the configuration change content of the first backup file. Based on this configuration change content and the first backup file, the complete configuration file of the first baseboard management controller at the target backup time is determined.

[0046] In this embodiment, in response to a trigger operation on a target selection control among multiple selection controls, the target backup time corresponding to the target selection control is determined; the target incremental information corresponding to the target backup time is determined, as well as at least one other incremental information corresponding to all other backup times prior to the target backup time; the target incremental information and at least one other incremental information are determined as the incremental information of the configuration file. Thus, by obtaining the target incremental information and all other preceding incremental information, the complete incremental information of the configuration file is obtained, which can comprehensively cover the configuration changes at each stage, providing data support for restoring the complete configuration file of the baseboard management controller at the target backup time in conjunction with the initial backup file.

[0047] In some embodiments, the above method can also be implemented through steps S501 and S502: In step S501, in response to a trigger operation on the configuration recovery control, a firmware recovery interface including the firmware recovery control is displayed.

[0048] In this embodiment, the electronic device housing the system management module includes a display component. After determining that the first security control board corresponding to the target node has been replaced, the system management module displays a firmware recovery interface through the display component. This firmware recovery interface includes a firmware recovery control, which, when triggered, sends firmware update information to the second baseboard management controller.

[0049] It is understandable that when the SCM board is replaced, the configuration file and firmware stored in the BMC of the SCM board will be lost. Therefore, when the configuration recovery control is triggered to obtain the configuration file of the first baseboard management controller integrated on the first security control board, the firmware recovery interface can be displayed simultaneously to prompt the user to restore the configuration file at the same time.

[0050] In step S502, in response to the trigger operation of the firmware recovery control, firmware update information is sent to the second baseboard management controller.

[0051] The firmware update information is used to instruct the second baseboard management controller to update the firmware through the baseboard management controller integrated on other security control boards; the other security control boards are the boards corresponding to other nodes in the distributed system other than the target node.

[0052] In this embodiment, after the second security control board is installed and put into use, the system management module sends firmware update information to the second baseboard management controller integrated on the second security control board. Upon receiving the firmware update information, the second baseboard management controller can retrieve firmware from baseboard management controllers integrated on other security control boards to update its own firmware. Exemplarily, this firmware may be the firmware of the Unified Extensible Firmware Interface (UEFI) and / or the ExpansionCompute Controller (XCC).

[0053] It is understandable that a distributed system includes multiple nodes, each with an SCM board. Therefore, the BMC integrated on the SCM board of each node can back up their own firmware. When any SCM board is replaced, it can obtain its own firmware through the BMC of other SCM boards that have not been replaced, so that there will be no firmware loss after the SCM board is replaced.

[0054] In this embodiment, in response to a trigger operation on the configuration recovery control, a firmware recovery interface including the firmware recovery control is displayed; in response to a trigger operation on the firmware recovery control, firmware update information is sent to the second baseboard management controller; wherein, the firmware update information is used to instruct the second baseboard management controller to update the firmware through a baseboard management controller integrated on other security control boards; other security control boards are boards corresponding to nodes other than the target node in the distributed system. In this way, the firmware update is completed collaboratively using the baseboard management controllers of other nodes in the distributed system, fully utilizing existing hardware resources of the cluster, simplifying the firmware update process, and improving the efficiency of firmware recovery by the second baseboard management controller.

[0055] This application embodiment also provides a data update method, which is applied to a second baseboard management controller integrated on a second security control board. This data update method can be implemented through steps S601 and S602: Step S601: Obtain the configuration file of the first baseboard management controller, which is integrated on the first security control board, corresponding to the target node in the distributed system.

[0056] The configuration file is a file obtained by the system management module of the distributed system in response to the trigger operation of the configuration recovery control and transmitted to the second baseboard management controller; the configuration recovery control belongs to the configuration recovery interface; the configuration recovery interface is triggered and displayed in response to the replacement operation of the first security control board.

[0057] In this embodiment, when the first security control board corresponding to the target node in the distributed system is replaced, the system management module displays a configuration recovery interface including a configuration recovery control. When the configuration recovery control is triggered, the system management module retrieves the configuration file of the first baseboard management controller integrated on the first security control board from its own memory. Then, when the first security control board is replaced with a second security control board and the second security control board is put into use, the system management module transmits the configuration file to the second baseboard management controller integrated on the second security control board. The second baseboard management controller can receive the configuration file of the first baseboard management controller transmitted by the system management module.

[0058] Step S602: Update configuration parameters based on the configuration file.

[0059] In this embodiment of the application, the configuration file includes multiple configuration parameters, and the second baseboard management controller can update its own original configuration parameters based on the configuration parameters in the configuration file.

[0060] In this embodiment, the second baseboard management controller obtains the configuration file of the first baseboard management controller integrated on the first security control board corresponding to the target node in the distributed system, and updates the configuration parameters based on the configuration file. In this way, the second baseboard management controller can update its own original configuration parameters through the configuration file of the first baseboard management controller transmitted by the system management module, enabling rapid configuration migration and restoration. This solves the configuration loss problem caused by security control board replacement and effectively reduces the operational risks of the distributed cluster.

[0061] In some embodiments, the above method can also be implemented through steps S701 to S704: Step S701: Receive firmware update information sent by the system management module.

[0062] In this embodiment, after the configuration recovery control is triggered, the system management module displays the firmware recovery interface through its own display component. When the firmware recovery control in the firmware recovery interface is triggered, the system management module sends firmware update information to the second baseboard management controller. The firmware update information is used to instruct the second baseboard management controller to update the firmware through the baseboard management controller integrated on other security control boards.

[0063] In step S702, in response to firmware update information, a firmware acquisition request is sent to the baseboard management controller integrated on other security control boards.

[0064] In this embodiment of the application, after the second baseboard management controller receives the firmware update information sent by the system management module, it can send a firmware acquisition request to the baseboard management controller integrated on other security control boards based on the firmware update information, so as to obtain the firmware package data of the first baseboard management controller of the first security control board before replacement from the baseboard management controller on other security control boards.

[0065] In some embodiments, after the second security control board is replaced and put into use, the system management module can send the identification information of the first baseboard management controller to the second baseboard management controller integrated on the second security control board. The second baseboard management controller can then send a firmware retrieval request carrying the identification information of the first baseboard management controller to the baseboard management controllers on other security control boards. In this way, the baseboard management controllers on other security control boards can retrieve the firmware package data of the first baseboard management controller from their own memory using the identification information of the first baseboard management controller.

[0066] Step S703: Receive firmware package data sent by the baseboard management controller integrated on other security control boards.

[0067] In this embodiment of the application, the baseboard management controller integrated on other security control boards can obtain the firmware package data of the baseboard management controller backed up on other security control boards based on the identification information of the first baseboard management controller after receiving a firmware acquisition request carrying the identification information of the first baseboard management controller.

[0068] It is understandable that the memory of the baseboard management controller on other security control boards stores the correspondence between the identification information of different baseboard management controllers and the firmware package data backed up by different baseboard management controllers. The baseboard management controller on other security control boards can obtain the firmware package data of the first baseboard management controller through the identification information of the first baseboard management controller and multiple correspondences.

[0069] Step S704: Update the firmware based on the firmware package data.

[0070] In this embodiment of the application, after receiving firmware package data sent by the baseboard management controller on other security control boards, the second security control board updates its own initial firmware by receiving the firmware package data.

[0071] In this embodiment, the second baseboard management controller of the replaced second security control board can obtain the firmware package data of the first baseboard management controller of the previous first security control board by communicating with the baseboard management controllers of other security control boards. This utilizes the interconnected nature of multiple nodes in a distributed system to complete the interactive transmission of firmware package data within each node, achieving cluster sharing of firmware resources. This ensures that the firmware used by the second baseboard management controller is consistent with the firmware of the previous security control board, resolving the firmware loss problem caused by security control board replacement and effectively reducing the operational risks of the distributed cluster.

[0072] In some embodiments, the above method can also be implemented through steps S801 and S802: Step S801: In response to the file backup command sent by the system management module, send the first backup file to the system management module; the first backup file is the complete configuration file for the first backup.

[0073] In this embodiment of the application, when the second security control board is replaced and put into use for the first time, the system management module sends a file backup instruction to the second baseboard management controller of the second security control board. After receiving the file backup instruction, the system management module sends the first backup file to the system management module.

[0074] Step S802: If the initial backup file changes, determine the incremental information of the initial backup file and send the incremental information to the system management module.

[0075] In this embodiment of the application, when the first backup file changes, the first backup file becomes the first complete configuration file. At this time, it is necessary to determine the configuration change content between the first complete configuration file and the first backup file, determine the configuration change content as the incremental information of the first backup file, and send the incremental information of the first backup file to the system management module.

[0076] In some embodiments, if the first complete configuration file is changed to a second complete configuration file, the incremental information can be either the configuration changes between the second complete configuration file and the initial backup file, or the configuration changes between the second complete configuration file and the first backup file. After determining the incremental information, the determined incremental information is sent to the system management module.

[0077] In this embodiment, in response to a file backup command sent by the system management module, an initial backup file is sent to the system management module. The initial backup file is a complete configuration file for the first backup. If the initial backup file changes, incremental information of the initial backup file is determined and sent to the system management module. In this way, the second baseboard management controller first uploads the initial backup file, and only synchronizes incremental information to the system management module when the configuration changes subsequently. This ensures that the system management module can obtain a complete initial configuration baseline while significantly reducing the amount of backup data transmitted and the storage space occupied.

[0078] The following describes the application of the data update method provided in the embodiments of this application in a real-world scenario.

[0079] Currently, the Baseboard Management Controller (BMC) stores critical configurations (network, accounts, certificates, and platform policies). These configurations are typically lost if the SCM board fails or is replaced. Although manual backup is supported, this operation is often forgotten or performed inconsistently. Furthermore, replacing the SCM board requires manually updating the Unified Extensible Firmware Interface (UEFI) and Expansion Compute Controller (XCC) firmware, which is inconvenient for users.

[0080] In this embodiment, an option can be added to the management interface to enable the scheduled configuration backup function. The system will automatically perform daily backups of the selected configuration parameters. The backup data will be securely stored in persistent memory (e.g., read-only memory (ROM), ferroelectric random access memory (FRAM), or other non-volatile storage media). When a new System Configuration Module (SCM) card is installed, the system will display an option to the administrator, prompting them whether to restore the previous configuration.

[0081] In this embodiment, the system can also update the firmware of the Unified Extensible Firmware Interface (UEFI) and the Extended Compute Controller (XCC) through a trusted image on another SCM board, and allow users to choose whether to flash the firmware.

[0082] For example, such as Figure 3 As shown, the distributed system includes multiple nodes 301 and an SMM 302. Each node 301 corresponds to an SCM board, which integrates a BMC 3011 that stores corresponding configuration information. The BMCs 3011 of each node communicate with each other and each BMC 3011 communicates with the SMM 302. The BMCs 3011 of each node can back up their firmware to each other, and each BMC 3011 can back up its own configuration information to the SMM 302. When any SCM board is replaced, its firmware can be updated through other SCM boards, and its configuration information can be updated through the SMM 302.

[0083] In this embodiment, the System Management Module (SMM) has a built-in 64 megabytes of Serial Peripheral Interface Flash (SPI Flash), which provides ample storage space for storing configuration files for each node. The Baseboard Management Controller (BMC) encrypts the configuration files and sends them to the SMM via the Integrated Circuit Bus (I²C) or a network.

[0084] In this embodiment of the application, if the user replaces the SCM board system management module with a new one, an option will pop up for the administrator, prompting him whether to restore the previous configuration.

[0085] In this embodiment, the administrator enables the automatic backup function through the management interface. The system performs a scheduled backup process once a week, which adopts a snapshot concept (storing only incremental information). Configuration data is integrated into a secure data packet. This secure data packet is stored in persistent read-only memory (ROM). If the system configuration module (SCM) fails or is replaced, the system will prompt the administrator to restore the previous configuration. In some embodiments, the system configuration module may also prompt the administrator to update the firmware from another SCM module.

[0086] like Figure 4 As shown, this application embodiment provides a data update method, which can be implemented through steps S901 to S905: In step S901, if automatic backup is enabled in the administrator interface, the settings are saved and stored in memory through the daily scheduler.

[0087] Step S902: Determine if the SCM has malfunctioned.

[0088] In the event of a SCM failure, step S903 is executed; in the event of a normal SCM, step S902 is executed.

[0089] Step S903: Replace the SCM board.

[0090] In step S904, the system will prompt the administrator to restore the previous settings.

[0091] In step S905, the system will prompt the administrator to update the firmware from a trusted image on another SCM.

[0092] In this embodiment, a snapshot backup mechanism is used to back up the configuration file. This mechanism captures a full snapshot daily, and subsequently saves only incremental changes, enabling rapid backup and flexible restore point settings. This reduces storage usage and allows users to choose to restore to any snapshot point.

[0093] In this embodiment of the application, the system configuration module can display a snapshot list, and the user can select to restore to any snapshot point in the snapshot list, and then restore the configuration through the incremental information corresponding to the snapshot point and the original configuration.

[0094] In this embodiment, when a new SCM board is installed, the BMC of another SCM board in the chassis stores trusted UEFI and XCC firmware. Subsequently, the SMM notifies the new SCM to perform a firmware update to ensure that the firmware versions of all nodes are consistent. This method shortens recovery time and reduces user error compared to manual updates.

[0095] This application embodiment eliminates the need for administrators to manually download firmware or configuration files, offering ease of operation. Backup data can be synchronized in real time, always remaining up-to-date and ensuring high reliability. When the Security Control Card (SCM) fails, the system can quickly restore the configuration, effectively improving fault recovery speed. This solution employs an incremental snapshot mechanism, significantly reducing data storage footprint. Administrators can choose to restore the original configuration or reinitialize the configuration, and can also restore trusted UEFI and XCC firmware from other security control cards, further enhancing the flexibility of configuration and firmware recovery.

[0096] Figure 5 This is a schematic diagram of the composition structure of a data update device provided in an embodiment of this application. This data update device is applied to a system management module; as shown... Figure 5 As shown, the data update device 500 includes: a display unit 501, a first acquisition unit 502, and a transmission unit 503; wherein, Display unit 501 is used to display a configuration recovery interface including configuration recovery controls in response to the replacement operation of the first security control board corresponding to the target node in the distributed system. The first acquisition unit 502 is used to acquire the configuration file of the first baseboard management controller integrated on the first security control board in response to a trigger operation on the configuration recovery control. The transmission unit 503 is used to transmit a configuration file to the second baseboard management controller integrated on the second security control board; the second security control board is the board that is put into use after replacing the first security control board.

[0097] In some embodiments, the first acquisition unit 502 is configured to, in response to a trigger operation on the configuration recovery control, determine incremental information of the configuration file and acquire the first backup file; the first backup file is the complete configuration file of the first backup; and determine the configuration file of the first baseboard management controller based on the incremental information and the first backup file.

[0098] In some embodiments, the first acquisition unit 502 is configured to display a file selection interface in response to a trigger operation on the configuration recovery control; the file selection interface includes multiple selection controls; different selection controls correspond to backup times of different incremental information; in response to a trigger operation on the target selection control among the multiple selection controls, incremental information of the configuration file is acquired based on the target backup time corresponding to the target selection control.

[0099] In some embodiments, the first acquisition unit 502 is configured to, in response to a trigger operation on a target selection control among a plurality of selection controls, determine the target backup time corresponding to the target selection control; determine the target incremental information corresponding to the target backup time, and at least one other incremental information corresponding to all other backup times before the target backup time; and determine the target incremental information and at least one other incremental information as incremental information of the configuration file.

[0100] In some embodiments, the display unit 501 is further configured to display a firmware recovery interface including a firmware recovery control in response to a trigger operation on the configuration recovery control; the transmission unit 503 is further configured to send firmware update information to the second baseboard management controller in response to a trigger operation on the firmware recovery control; wherein the firmware update information is used to instruct the second baseboard management controller to update the firmware through the baseboard management controller integrated on other security control boards; the other security control boards are boards corresponding to other nodes in the distributed system other than the target node.

[0101] Figure 6 This is a schematic diagram of the composition structure of a data update device provided in an embodiment of this application. The data update device is applied to a second baseboard management controller integrated on a second security control board; as shown... Figure 6 As shown, the data update device 600 includes: a second acquisition unit 601 and an update unit 602; wherein, The second acquisition unit 601 is used to acquire the configuration file of the first baseboard management controller, which is integrated on the first security control board, corresponding to the target node in the distributed system. Update unit 602 is used to update configuration parameters based on the configuration file; The configuration file is a file obtained by the system management module of the distributed system in response to the trigger operation of the configuration recovery control and transmitted to the second baseboard management controller; the configuration recovery control belongs to the configuration recovery interface; the configuration recovery interface is triggered and displayed in response to the replacement operation of the first security control board.

[0102] In some embodiments, the data update apparatus further includes a receiving unit and a sending unit; the receiving unit is used to receive firmware update information sent by the system management module; the sending unit is used to send a firmware acquisition request to the baseboard management controller integrated on other security control boards in response to the firmware update information; and the update unit 602 is used to update the firmware based on the firmware package data.

[0103] In some embodiments, the sending unit is further configured to send an initial backup file to the system management module in response to a file backup instruction sent by the system management module; the initial backup file is a complete configuration file for the initial backup; and if the initial backup file changes, the incremental information of the initial backup file is determined and the incremental information is sent to the system management module.

[0104] Figure 7 This is a schematic diagram of the composition structure of a distributed system provided in an embodiment of this application, such as... Figure 7 As shown, the distributed system 700 includes a system management module 701 and multiple nodes 702; wherein, the system management module 701 is used for: In response to the replacement operation of the first security control board corresponding to the target node among multiple nodes, a configuration recovery interface including configuration recovery controls is displayed; In response to a trigger operation on the configuration recovery control, the configuration file of the first baseboard management controller integrated on the first security control board is obtained; The configuration file is transmitted to the second baseboard management controller integrated on the second security control board; the second security control board is the board that is put into use after replacing the first security control board.

[0105] The descriptions of the apparatus embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. In some embodiments, the functions or modules included in the apparatus provided in this application can be used to perform the methods described in the method embodiments above. For technical details not disclosed in the apparatus embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0106] It should be noted that, in the embodiments of this application, if the above-described data update method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the related technology, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0107] This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.

[0108] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0109] This application provides a computer program including computer-readable code. When the computer-readable code is run in a computer device, the processor in the computer device performs some or all of the steps in the above-described method.

[0110] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0111] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0112] Figure 8 This is a schematic diagram of a hardware entity of the data update device in the embodiments of this application, such as... Figure 8 As shown, the hardware entity of the data update device 800 includes: a processor 801, a communication interface 802, and a memory 803, wherein: The processor 801 typically controls the overall operation of the data update device 800, which may be to implement the data update method provided in the embodiments of this application.

[0113] The communication interface 802 enables the data update device 800 to communicate with other terminals or servers via a network.

[0114] The memory 803 is configured to store instructions and applications executable by the processor 801, and can also cache data to be processed or already processed (e.g., image data, audio data, voice communication data, and video communication data) in the processor 801 and the data update device 800. It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 801, the communication interface 802, and the memory 803 can be performed via bus 804.

[0115] This application provides a computer storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the data update method as described in any of the above embodiments.

[0116] It should be noted that the descriptions of the storage medium and device embodiments above are similar to the descriptions of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0117] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0118] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0119] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0120] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0121] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A data update method, the method being applied to a system management module of a distributed system, the method comprising: In response to the replacement operation of the first security control board corresponding to the target node in the distributed system, a configuration recovery interface including configuration recovery controls is displayed; In response to a trigger operation on the configuration recovery control, the configuration file of the first baseboard management controller integrated on the first security control board is obtained; The configuration file is transmitted to the second baseboard management controller integrated on the second security control board; The second security control board is the board that is put into use after replacing the first security control board.

2. The method according to claim 1, wherein obtaining the configuration file of the first baseboard management controller integrated on the first security control board in response to a trigger operation on the configuration recovery control includes: In response to a triggered operation on the configuration recovery control, the incremental information of the configuration file is determined, and the first backup file is obtained; The initial backup file is the complete configuration file for the initial backup. Based on the incremental information and the initial backup file, the configuration file of the first baseboard management controller is determined.

3. The method according to claim 2, wherein determining the incremental information of the configuration file in response to a trigger operation on the configuration recovery control includes: In response to a triggered operation on the configured recovery control, a file selection interface is displayed; The file selection interface includes multiple selection controls; different selection controls correspond to different backup times for incremental information. In response to a trigger operation on a target selection control among the plurality of selection controls, incremental information of the configuration file is obtained based on the target backup time corresponding to the target selection control.

4. The method according to claim 3, wherein in response to a trigger operation on a target selection control among the plurality of selection controls, obtaining incremental information of the configuration file based on the target backup time corresponding to the target selection control includes: In response to a trigger operation on a target selection control among the plurality of selection controls, the target backup time corresponding to the target selection control is determined; Determine the target incremental information corresponding to the target backup time, and at least one other incremental information corresponding to all other backup times prior to the target backup time; The target incremental information and the at least one other incremental information are determined as the incremental information of the configuration file.

5. The method according to claim 1, further comprising: In response to a trigger operation on the configuration recovery control, a firmware recovery interface including the firmware recovery control is displayed; In response to a trigger operation on the firmware recovery control, firmware update information is sent to the second baseboard management controller; The firmware update information is used to instruct the second baseboard management controller to update the firmware through the baseboard management controller integrated on other security control boards. The other security control boards are the boards corresponding to other nodes in the distributed system besides the target node.

6. A data update method, applied to a second baseboard management controller integrated on a second security control board, the method comprising: Obtain the configuration file of the first baseboard management controller, which is integrated on the first security control board, corresponding to the target node in the distributed system; Update configuration parameters based on the configuration file; The configuration file is a file obtained by the system management module of the distributed system in response to a trigger operation on the configuration recovery control and transmitted to the second baseboard management controller; the configuration recovery control belongs to the configuration recovery interface; the configuration recovery interface is triggered and displayed in response to a replacement operation of the first security control board.

7. The method according to claim 6, further comprising: Receive firmware update information sent by the system management module; In response to the firmware update information, a firmware acquisition request is sent to the baseboard management controller integrated on other security control boards; Receive firmware package data sent by the baseboard management controller integrated on other security control boards; Update the firmware based on the firmware package data.

8. The method according to claim 6, further comprising: In response to a file backup command sent by the system management module, the system management module sends the first backup file. The initial backup file is the complete configuration file for the initial backup. If the initial backup file changes, the incremental information of the initial backup file is determined and sent to the system management module.

9. A data updating apparatus, the apparatus comprising: The display unit is used to respond to the replacement operation of the first security control board corresponding to the target node in the distributed system and display a configuration recovery interface including configuration recovery controls. The first acquisition unit is configured to acquire the configuration file of the first baseboard management controller integrated on the first security control board in response to a trigger operation on the configuration recovery control. The transmission unit is used to transmit the configuration file to the second baseboard management controller integrated on the second security control board; The second security control board is the board that is put into use after replacing the first security control board.

10. A distributed system, the distributed system comprising a system management module and multiple nodes; wherein, The system management module is used for: In response to the replacement operation of the first security control board corresponding to the target node among the plurality of nodes, a configuration recovery interface including configuration recovery controls is displayed; In response to a trigger operation on the configuration recovery control, the configuration file of the first baseboard management controller integrated on the first security control board is obtained; The configuration file is transmitted to the second baseboard management controller integrated on the second security control board; The second security control board is the board that is put into use after replacing the first security control board.

Images