TWI881649B - Method of recovering a configuration file - Google Patents

Abstract

In a method of recovering a configuration file，a baseboard management controller is configured to perform the steps of: determining whether a current configuration file, a to-be-compared checksum and a backup configuration file are stored in a storage module; when it is determined that the current configuration file, the to-be-compared checksum and the backup configuration file are stored, obtaining a current checksum corresponding to the current configuration file, and determining whether the current checksum is consistent with the to-be-compared checksum; when it is determined that the current checksum is not consistent with the to-be-compared checksum, using the backup configuration file as the current configuration file; obtaining a to-be-updated checksum corresponding to the current configuration file, and using the to-be-updated checksum as the to-be-compared checksum; and coping the current configuration file to obtain a copied configuration file, and using the copied configuration file as the backup configuration file.

Description

Configuration file recovery method

The present invention relates to a recovery method, and more particularly to a configuration file recovery method.

The Baseboard Management Controller (BMC) accesses relevant parameters as a configuration file during the system initialization process when the computer is turned on, and updates the configuration file at any time during system operation. If the BMC encounters an unexpected power outage when writing the configuration file to the memory, the configuration file data may be incompletely written, causing the configuration file to be abnormal or damaged, resulting in initialization failure at the next startup, which in turn causes the system to be abnormal (for example, unexpected behaviors such as repeated startup). The existing method of handling abnormal configuration files is mostly to restore the abnormal configuration file to the factory settings, so that the configuration file is restored to a normal state so that the system can be initialized smoothly. However, since the configuration file is restored to the factory settings, users will need to reconfigure system parameters when using the system in the future, causing inconvenience to users.

Therefore, how to keep the configuration file normal and initialize the system smoothly while minimizing the impact on user convenience has become one of the issues that the relevant technical fields want to solve.

Therefore, the purpose of the present invention is to provide a configuration file recovery method, which can overcome at least one disadvantage of the prior art.

Therefore, the present invention provides a configuration file recovery method, which utilizes a baseboard management controller and is executed when the baseboard management controller performs a boot initialization procedure, and includes the following steps: (A) determining whether a storage module connected to the baseboard management controller stores a current configuration file, a verification code to be compared, and a backup configuration file; (B) when it is determined that the storage module stores the current configuration file, the verification code to be compared, and the backup configuration file, obtaining a corresponding (C) when it is determined that the current verification code is not consistent with the verification code to be compared, using the backup configuration file as the current configuration file; (D) obtaining a verification code to be updated corresponding to the current configuration file, and using the verification code to be updated as the verification code to be compared; and (E) copying the current configuration file to obtain a copy configuration file, and using the copy configuration file as the backup configuration file.

The utility model has the following effects: by determining whether the current check code of the current configuration file at the time of this startup is consistent with the check code to be compared at the previous startup, it is determined whether the current configuration file is abnormal, and when an abnormality occurs, the abnormal current configuration file is replaced by the backup configuration file at the previous startup, thereby ensuring the normality of the current configuration file and enabling the initialization of the system to proceed smoothly. In addition, since the configuration file generated by the last startup before the current startup is used as the backup configuration file for recovery, the user does not need to reset the system parameters after initialization using the backup configuration file, thereby avoiding the inconvenience brought to the user by restoring the current configuration file to the factory settings.

Before the present invention is described in detail, it should be noted that similar elements are represented by the same reference numerals in the following description.

Referring to FIG. 1 and FIG. 2 , a configuration file recovery method of an embodiment of the present invention is executed by a baseboard management controller 1 electrically connected to a storage module 2. In this embodiment, the storage module 2 can be implemented as a flash memory, for example. When a computer device equipped with the baseboard management controller 1 is powered on, the baseboard management controller 1 performs a power-on initialization procedure and executes the configuration file recovery method at the same time. The configuration file recovery method includes the following steps S21 to S27.

In step S21, the baseboard management controller 1 determines whether a current configuration file, a verification code to be compared, and a backup configuration file are stored in the storage module 2. The step S21 is used to determine whether the computer device is powered on for the first time. When at least one of the current configuration file, the verification code to be compared, and the backup configuration file is not stored in the storage module 2, the computer device is powered on for the first time, and the process proceeds to step S22 to obtain the current configuration file; when the baseboard management controller 1 determines that the current configuration file, the verification code to be compared, and the backup configuration file are stored in the storage module 2, the computer device is not powered on for the first time, and the process proceeds to step S23 to determine whether the current configuration file is normal.

In step S22, the baseboard management controller 1 continues to execute the power-on initialization program to obtain an initial configuration file as the current configuration file. Since the baseboard management controller 1 is powered on for the first time, there is no corresponding current configuration file, so it is necessary to wait for the power-on initialization program to be executed and then generate the initial configuration file, thereby obtaining the required current configuration file. In this embodiment, the baseboard management controller 1 uses an inotify module in a Linux operating system to monitor whether the initial configuration file is established. When the initial configuration file is established, the inotify module issues a creation notification indicating that the initial configuration file has been established. When the baseboard management controller 1 receives the creation notification, the baseboard management controller 1 uses the initial configuration file as the current configuration file. Thereafter, the process proceeds to step S25 to enable a configuration file monitoring program.

In step S23, the baseboard management controller 1 obtains a current verification code corresponding to the current configuration file, and determines whether the current verification code is consistent with the verification code to be compared, thereby determining whether the current configuration file is normal. In this embodiment, the current verification code is generated by the baseboard management controller 1 according to the content in the current configuration file using an md5sum hashing algorithm. When the baseboard management controller 1 determines that the current verification code is inconsistent with the verification code to be compared, the current configuration file is abnormal, and the process proceeds to step S24; when the baseboard management controller 1 determines that the current verification code is consistent with the verification code to be compared, the current configuration file is normal, and the process proceeds to step S25 to activate the configuration file monitoring program.

In step S24, the baseboard management controller 1 uses the backup configuration file as the current configuration file. The configuration file used in the previous normal startup (ie, the backup configuration file) is used to replace the abnormal current configuration file, so that the startup initialization program and the configuration file monitoring program can continue to run smoothly.

After ensuring that the current configuration file exists (first time booting), or the current configuration file is normal (not first time booting), the baseboard management controller 1 executes the configuration file monitoring program. The configuration file monitoring program is implemented as the following steps S25-S27 in the configuration file recovery method.

In step S25, the baseboard management controller 1 obtains a verification code to be updated corresponding to the current configuration file, and uses the verification code to be updated as the verification code to be compared. In this embodiment, the verification code to be updated is generated by the baseboard management controller 1 according to the content in the current configuration file using the md5sum hash algorithm.

In step S26, the baseboard management controller 1 copies the current configuration file to obtain a copy configuration file, and uses the copy configuration file as the backup configuration file. By this step, it is ensured that the backup configuration file used for recovery at the next startup is always the latest configuration file generated at the last normal startup.

In step S27, the baseboard management controller 1 determines whether the current configuration file is updated. In the present embodiment, the baseboard management controller 1 uses the inotify module to monitor whether the current configuration file is updated. When the current configuration file is updated, the inotify module issues an update notification indicating that the current configuration file has completed updating (i.e., the current configuration file has been closed from the write mode). Therefore, the baseboard management controller 1 determines whether the current configuration file is updated by determining whether the update notification is received. When it is determined that the update notification is received, the process returns to step S25; otherwise, the process proceeds to step S27 again.

The baseboard management controller 1 repeatedly executes the configuration file monitoring program by repeatedly executing steps S25-S27 to achieve the purpose of continuously monitoring and updating the backup configuration file when the computer device is running, so that the backup configuration file is always in the latest state.

It should be noted that when the computer device is powered on for the first time, the process will only proceed to step S21, step S22 and steps S25~S27 in sequence; and when the computer device is not powered on for the first time, the process will proceed to step S21, step S23, step S24 (not executed when the current configuration file is normal) and steps S25~S27 in sequence.

In summary, by determining whether the current checksum of the current configuration file at this startup is consistent with the checksum to be compared at the previous startup, it is determined whether the current configuration file is abnormal, and when an abnormality occurs, the abnormal current configuration file is replaced by the backup configuration file at the previous startup, thereby ensuring that the current configuration file is normal and the system initialization can proceed smoothly. In addition, since the configuration file generated by the most recent startup before this startup is used as the backup configuration file for recovery, the user does not need to reset the system parameters after initialization using the backup configuration file, thereby avoiding the inconvenience brought to the user by restoring the current configuration file to the factory settings. Therefore, the purpose of the present invention can be achieved.

However, the above is only an example of the implementation of the present invention, and it should not be used to limit the scope of the implementation of the present invention. All simple equivalent changes and modifications made according to the scope of the patent application of the present invention and the content of the patent specification are still within the scope of the patent of the present invention.

1: Baseboard management controller 2: Storage module S21~S27: Steps

Other features and effects of the present invention will be clearly presented in the implementation method with reference to the drawings, wherein: FIG. 1 is a block diagram, exemplarily illustrating a baseboard management controller and a storage module used in a configuration file recovery method of an embodiment of the present invention; and FIG. 2 is a flow chart, exemplarily illustrating how the baseboard management controller of the embodiment executes the configuration file recovery method.

S21~S27: Steps

Claims (7)

A configuration file recovery method is implemented by using a baseboard management controller and when the baseboard management controller performs a boot initialization procedure, and includes the following steps: (A) determining whether a storage module connected to the baseboard management controller stores a current configuration file, a verification code to be compared, and a backup configuration file; (G) when the storage module does not store at least one of the current configuration file, the verification code to be compared, and the backup configuration file, continuing to execute the boot initialization procedure to obtain an initial configuration file as the current configuration file; (B) When it is determined that the storage module stores the current configuration file, the check code to be compared and the backup configuration file, a current check code corresponding to the current configuration file is obtained, and it is determined whether the current check code is consistent with the check code to be compared; (F) When it is determined that the current check code is consistent with the check code to be compared, step (D) is performed; (C) When it is determined that the current check code is not consistent with the check code to be compared, the backup configuration file is used as the current configuration file; (D) A check code to be updated corresponding to the current configuration file is obtained, and the check code to be updated is used as the check code to be compared; and (E) The current configuration file is copied to obtain a copy configuration file, and the copy configuration file is used as the backup configuration file. The configuration file recovery method as described in claim 1 further includes the following steps after step (E): (H) determining whether the current configuration file has been updated; and (I) when it is determined that the current configuration file has been updated, the process returns to step (D). A configuration file recovery method as described in claim 2, wherein: In step (H), it is determined whether the current configuration file is updated by determining whether an update notification is received from an operating system indicating that the current configuration file has been updated; and In step (I), when it is determined that the update notification is received, the process returns to step (D). The configuration file recovery method described in claim 3 further includes the following steps after step (H): (J) When it is determined that the update notification has not been received, the process returns to step (H). The configuration file recovery method as described in claim 1, wherein, in step (B), the current verification code is generated by the baseboard management controller based on the content in the current configuration file using an md5sum hash algorithm. The configuration file recovery method as described in claim 1, wherein, in step (D), the verification code to be updated is generated by the baseboard management controller based on the content in the current configuration file using an md5sum hash algorithm. A configuration file recovery method as described in claim 1, wherein step (D), step (E) and step (F) together serve as a configuration file monitoring program, and the configuration file monitoring program is run in parallel with the boot initialization program.

Images