CN110708203A - Fault tolerance method, device and equipment - Google Patents
Fault tolerance method, device and equipment Download PDFInfo
- Publication number
- CN110708203A CN110708203A CN201911025204.XA CN201911025204A CN110708203A CN 110708203 A CN110708203 A CN 110708203A CN 201911025204 A CN201911025204 A CN 201911025204A CN 110708203 A CN110708203 A CN 110708203A
- Authority
- CN
- China
- Prior art keywords
- file
- centralized control
- equipment
- standby
- stored
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
Abstract
The application discloses a fault tolerance method, a device and equipment, wherein the method comprises the following steps: receiving a device file issued by centralized control; updating the equipment based on the equipment file; and after determining that the device updating based on the device file fails, rolling back based on a pre-stored standby file. When the device fails to update the device based on the device file issued by the centralized control, the device rolls back based on the pre-stored standby file, and the pre-stored standby file does not cause the device to quit the centralized control.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a fault tolerance method, apparatus, and device.
Background
An Intelligent network management system (INM), also called centralized control, is a service platform integrating functions of management, monitoring, service configuration and the like, and devices distributed in various places can realize centralized management by adding centralized control. In practical application, the centralized control can issue various device files to the device, so that the device updates the device according to the device files issued by the centralized control. For example, the centralized control may issue a configuration file to the device, and the device modifies the configuration information based on the configuration file issued by the centralized control.
However, as the number of devices added to the centralized control increases, the device files issued to the devices by the centralized control are inevitably wrong, and once the devices update the devices based on the wrong device files issued by the centralized control, the devices may quit the centralized control. At present, an effective fault-tolerant mode is not available, and operation and maintenance personnel need to go to the location where the centralized control equipment exits for manual maintenance, so that obviously, the operation and maintenance cost is high.
Disclosure of Invention
In view of this, the present application provides a fault-tolerant method, apparatus and device, and for the case that the device exits from the centralized control due to the update of the wrong device file issued based on the centralized control, the device may roll back based on the standby file to maintain the network connection with the centralized control, and the field maintenance of the operation and maintenance personnel is not needed, thereby greatly saving the operation and maintenance cost.
In a first aspect, to achieve the above object, the present application provides a fault tolerance method, including:
receiving a device file issued by centralized control;
updating the equipment based on the equipment file;
and after determining that the device updating based on the device file fails, rolling back based on a pre-stored standby file.
Optionally, the device file includes a configuration file;
after determining that the device update based on the device file fails, before rolling back based on a pre-stored standby file, the method further includes:
the current configuration information is stored as a standby file.
Optionally, after determining that the device update based on the device file fails, rolling back based on a pre-stored standby file includes:
and after sending a preset message to the centralized control, if a response message from the centralized control is not received, rolling back based on the standby file.
Optionally, the device file includes a software version file;
after determining that the device update based on the device file fails, before rolling back based on a pre-stored standby file, the method further includes:
and storing the current version software as a standby file.
Optionally, after determining that the device update based on the device file fails, rolling back based on a pre-stored standby file includes:
and after determining that the device based on the software version file fails to restart, rolling back based on the standby file.
In a second aspect, the present application further provides a fault tolerant apparatus, the apparatus comprising:
the receiving module is used for receiving the equipment files issued by the centralized control;
the first updating module is used for updating equipment based on the equipment file;
and the rollback module is used for performing rollback based on a pre-stored standby file after determining that the equipment updating based on the equipment file fails.
Optionally, the device file includes a configuration file;
the device further comprises:
and the first storage module is used for storing the current configuration information as a standby file.
Optionally, the device file includes a software version file;
the device further comprises:
and the second storage module is used for storing the current version software as a standby file.
In a third aspect, the present application also provides a computer-readable storage medium having stored therein instructions that, when run on a terminal device, cause the terminal device to perform the method according to any one of the above.
In a fourth aspect, the present application further provides a fault tolerant device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, when executing the computer program, implementing the method as in any one of the above.
According to the fault-tolerant method, when the device fails to update the device based on the device file issued by the centralized control, the device rolls back based on the pre-stored standby file, and the pre-stored standby file does not cause the device to quit the centralized control, so that the device after rolling back based on the standby file can establish network connection with the centralized control, operation and maintenance personnel do not need to maintain on the spot, and the operation and maintenance cost is saved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic structural diagram of a device management system according to an embodiment of the present application;
fig. 2 is a flowchart of a fault tolerance method according to an embodiment of the present application;
fig. 3 is a flowchart of a fault tolerance method for issuing a configuration file according to an embodiment of the present application;
fig. 4 is a data interaction diagram of a fault tolerance method for configuration file delivery according to an embodiment of the present application;
FIG. 5 is a flowchart of a fault tolerance method for software upgrade according to an embodiment of the present disclosure;
FIG. 6 is a data interaction diagram of a fault tolerance method for software upgrade according to an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a fault tolerant apparatus according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a fault tolerant device according to an embodiment of the present disclosure.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Before describing the embodiments of the present application, it should be understood that the meaning of the several concepts involved is as follows:
fault tolerance refers to a method and technology that can ensure uninterrupted service supply when equipment is erroneously activated during operation.
In this scheme, fault tolerance specifically refers to a method and a technique by which a device can still maintain network connection with a centralized control when the device fails to update based on a wrong device file issued by the centralized control.
Centralized control, also called Intelligent network management system (INM), is a service platform integrating functions of management, monitoring, service configuration, etc. After the equipment is added into the centralized control, the running state of the equipment, including the CPU utilization rate, the memory utilization rate, the tunnel connection number, the tunnel connection state and the like, can be monitored by the centralized control energy, and meanwhile, the service configuration and the issuing of the equipment can be realized. The physical form of centralized control can be a software product running based on Windows X86_ 64.
In the scheme, the equipment distributed in each place can realize centralized management by adding centralized control.
Rollback (english: Rollback) refers to the act of a program or data processing error, restoring the program or data to the last correct state. Rollback includes types of program rollback and data rollback.
The above concepts are intended to be illustrative rather than restrictive, and any nomenclature is used merely for distinction and not in any limiting sense.
At present, for equipment added to centralized control, equipment update may be performed based on an erroneous equipment file issued by the centralized control, so that the centralized control is exited, and an effective fault-tolerant mode does not exist at present, so that operation and maintenance personnel need to manually maintain the equipment at the location of the equipment, thereby realizing the purpose that the equipment is added to the centralized control again, and obviously, the operation and maintenance cost is high.
The application provides a fault-tolerant method which can roll back based on a pre-stored standby file after failure of updating equipment based on an equipment file issued by centralized control so as to keep network connection between the equipment and the centralized control, does not need operation and maintenance personnel to carry out field maintenance, and saves operation and maintenance cost.
Referring to fig. 1, a schematic structural diagram of a device management system provided in the present application is shown, and the fault tolerance method provided in the present application may be applied to the device management system of fig. 1. Specifically, the device management system 100 includes a central control 110 and a device 120; the centralized control 110 is configured to manage each device 120 that joins the centralized control, and specifically includes issuing a device file to each device 120. The device 120 is configured to perform device update based on the device file after receiving the device file sent by the centralized control 110, and perform rollback based on a pre-stored standby device file after the update fails, so as to maintain network connection with the centralized control 110.
The centralized control 110 is also called an Intelligent network management system (INM), and may be implemented by a server or other devices. Device 120 may include various types of terminal devices, such as a desktop computer, and the like.
Based on the foregoing embodiments, the present application provides a fault tolerance method, and refer to fig. 2, which is a flowchart of a fault tolerance method provided in an embodiment of the present application. Specifically, the fault-tolerant method may be applied to various types of devices that have been added to the centralized control, and the fault-tolerant method includes:
s201: and receiving the equipment file issued by the centralized control.
The device file refers to a file that needs to be issued to the device in the process of managing the device by centralized control, for example, a configuration file containing configuration modification information of the device, or a software version file containing the latest version of software, and the like.
In practical application, after the device joins the centralized control, the device can maintain the network connection with the centralized control by sending the heartbeat message. Meanwhile, the device can also detect whether the centralized control has a device file which needs to be issued to the device based on the network connection with the centralized control, and if the device detects that the centralized control has the device file which needs to be issued to the device, the device can send an issuing request to the centralized control, so that the centralized control issues the device file to the device.
S202: and updating the equipment based on the equipment file.
In the embodiment of the application, after receiving the device file issued by the centralized control, the device updates the device based on the device file. For example, the device configuration information is updated based on a configuration file issued by the central control, or the device software version is updated based on a software version file issued by the central control.
S203: and after determining that the device updating based on the device file fails, rolling back based on a pre-stored standby file.
In practical applications, if there is an error in the device file sent to the device by the centralized control, and the device updates the device based on the erroneous device file, which results in a failure in updating, the device may exit the centralized control, and cannot establish a network connection with the centralized control. Based on this, in the embodiment of the application, when it is determined that the device fails to update the device based on the device file issued by the centralized control, the device rolls back based on the pre-stored standby file, and since the pre-stored standby file does not cause the device to exit the centralized control, the device that rolls back based on the standby file can establish network connection with the centralized control.
In an alternative embodiment, the pre-stored spare file may be obtained before the execution of S202. For example, before the execution of the above S202, the current configuration information of the device is saved as a standby file for rollback of the device; alternatively, prior to execution of S202 above, the current version of software being used by the device is saved as a spare file for rollback of the device.
In another alternative embodiment, the pre-stored backup file may be any version of a device file that does not cause the device to exit centralized control. For example, the pre-stored backup file may include device configuration information in any scenario where the network connection between the device and the centralized control is normal; alternatively, the pre-stored alternate file may include any version of the software of the device.
In the fault-tolerant method provided by the embodiment of the application, when the device fails to update the device based on the device file issued by the centralized control, the device rolls back based on the pre-stored standby file, and the pre-stored standby file does not cause the device to quit the centralized control, so that the device after rolling back based on the standby file can establish network connection with the centralized control, and operation and maintenance personnel do not need to maintain on the spot, thereby saving the operation and maintenance cost.
For the fault tolerance method provided by the above embodiment, the present application also provides two specific implementation manners. One of them, refer to fig. 3, which is a flowchart of a fault tolerance method for issuing a configuration file according to an embodiment of the present application. The method comprises the following steps:
s301: and receiving the configuration file issued by the centralized control.
And the configuration file is used for storing configuration information of the equipment, such as an interface IP of an external network of the equipment. When the configuration information of the equipment needs to be modified, the configuration file can be issued to the equipment through centralized control.
S302: the current configuration information is stored as a standby file.
In order to avoid that the device exits from the centralized control after the configuration information of the device is modified based on the configuration file issued by the centralized control, in the embodiment of the application, before the device is updated based on the configuration file issued by the centralized control, the current configuration information of the device is firstly stored as a standby file.
S303: and modifying the current configuration information of the equipment based on the configuration file so as to realize equipment updating.
In order to modify the configuration information of the device, in the embodiment of the present application, after receiving the configuration file issued by the centralized control, the current configuration information of the device is modified based on the configuration file, so as to update the configuration information of the device.
S304: and after sending a preset message to the centralized control, if a response message from the centralized control is not received, rolling back based on the standby file.
Since the device may exit the centralized control after modifying the configuration information based on the configuration file issued by the centralized control, in the embodiment of the present application, it is further determined whether the device exits the centralized control after the configuration information modification is completed, and if it is determined that the device exits the centralized control, it is described that the current configuration information modification of the device fails.
In an optional implementation manner, the device may determine whether the device exits the centralized control by sending a preset message to the centralized control. Specifically, the device may send a configuration success notification message to the centralized control, and if a response message from the centralized control is not received within a certain time, it may be said that the device has exited the centralized control.
In order to further ensure the accuracy of determining whether the device exits from the centralized control by the way of sending the preset message to the centralized control by the device, the embodiment of the present application may also determine whether the device exits from the centralized control by the way of sending a configuration success notification message to the centralized control for multiple times. For example, the device may send a configuration success notification message to the centralized control at least three times, and if the device has not received a response message from the centralized control yet, it may be more accurate to indicate that the device has exited the centralized control.
In the embodiment of the application, after the device is determined to quit the centralized control, the device is rolled back based on the standby file, so that the device after rolling back can join the centralized control again. Specifically, since the standby file stores the device configuration information before the device update, and the configuration information does not cause the device to exit the centralized control, the device configuration information is rolled back based on the standby file, and it can be ensured that the device that has finished rolling back can join the centralized control again.
In practical application, after the device rolls back based on the standby file, the device can rejoin the centralized control in a heartbeat message mode and the like, so that the device can send a configuration failure notification message to the centralized control based on the network connection reestablished between the device and the centralized control, so as to notify the centralized control that the configuration is failed to be issued. After receiving the configuration failure notification message, the centralized control may check the issued configuration file to obtain a correct configuration file, and then issue the configuration file to the device again, and finally complete the update of the configuration information of the device. For the subsequent processing manner, the embodiment of the present application is not described again.
In order to facilitate a clearer understanding of the embodiment of the present application, the embodiment of the present application further provides a specific implementation manner of the fault tolerance method for issuing the configuration file, and refer to fig. 4, which is a data interaction diagram of the fault tolerance method for issuing the configuration file provided by the embodiment of the present application. The method comprises the following steps:
s401: the device detects whether the centralized control has a configuration file issuing requirement, and if the configuration file issuing requirement exists, the S402 is executed.
S402: and sending a configuration file issuing request message to the centralized control.
S403: and the centralized control issues a configuration file to the equipment.
S404: the device stores the current configuration information as a standby file.
S405: and the equipment modifies the configuration information based on the configuration file issued by the centralized control.
S406: and after the configuration information is modified, sending a configuration success notification message to the centralized control.
S407: and if the response message from the centralized control is not received, rolling back based on the backup file.
S408: and after the equipment joins the centralized control again, sending a configuration failure notification message to the centralized control.
In the fault-tolerant method for issuing the configuration files provided by the embodiment of the application, when the device determines that the device update based on the configuration files issued by the centralized control fails, the device rolls back based on the pre-stored standby files, and the pre-stored standby files do not cause the device to quit the centralized control, so that the device after rolling back based on the standby files can establish network connection with the centralized control, operation and maintenance personnel do not need to maintain on site, and the operation and maintenance cost is saved.
In another specific implementation manner, an embodiment of the present application further provides a fault tolerance method for software upgrade, and referring to fig. 5, a flowchart of the fault tolerance method for software upgrade provided in the embodiment of the present application is shown.
S501: and receiving a software version file issued by centralized control.
The software version file may include any version of software, such as the latest version of software. When the software of the equipment needs to be upgraded, the software version file can be transmitted to the equipment through centralized control.
S502: and setting the current version software as a standby version.
In order to avoid the problem that the device cannot be connected with the centralized control because the software in the software version file issued based on the centralized control cannot restart the device, the current version software is firstly set as the standby version before the device is restarted based on the software issued based on the centralized control in the embodiment of the application.
S503: and setting the software in the software version file issued by the centralized control as a master version, and guiding the equipment to load the master version to restart the equipment.
In order to upgrade the software version, in the embodiment of the present application, after receiving a software version file issued by a central controller, the software in the software version file is set as a master version, and a loader of a device is guided to load the master version, so that the device is restarted.
S504: and after determining that the equipment based on the software version file fails to restart, guiding the equipment to load the standby version to restart the equipment.
Because the device rebooting based on the master version may have a problem of rebooting failure, and further, the device may not be connected to the centralized control, in the embodiment of the present application, it needs to determine whether the device rebooting based on the master version fails, and if it is determined that the device rebooting fails, it is indicated that this software upgrade of the device fails.
In an alternative embodiment, the device may determine whether the device has failed to restart by counting the number of times of restart failure. Specifically, when the restart failure frequency reaches a preset threshold, the device may determine that the restart failure of the device is caused by a software upgrade problem, and then guide a loading program of the device to load the backup version, thereby implementing the restart of the device.
Because the network connection between the device and the centralized control can be ensured by the device based on the running of the software of the standby version before the device is restarted based on the software issued by the centralized control, the rollback is carried out by the device restarting method based on the software of the standby version in the embodiment of the application, and the device can be ensured to be added into the centralized control again after the device is restarted successfully.
In practical application, after the device is restarted based on the standby version, the device can rejoin the centralized control in the forms of heartbeat messages and the like, so that the device can send an upgrade failure notification message to the centralized control based on the network connection reestablished between the device and the centralized control, so as to notify the centralized control of the software upgrade failure. After receiving the upgrade failure notification message, the centralized control can check the issued software version file to obtain a correct software version file, and then issue the software version file to the device again, and finally complete the software upgrade of the device. For the subsequent processing manner, the embodiment of the present application is not described again.
In order to facilitate a clearer understanding of the embodiments of the present application, the embodiments of the present application further provide a specific implementation of a fault tolerance method for software upgrade, and refer to fig. 6, which is a data interaction diagram of a fault tolerance method for software upgrade provided in the embodiments of the present application. The method comprises the following steps:
s601: the device detects whether the latest version of software exists in the centralized control, and if so, executes S602.
S602: and sending an issuing request message of the latest version software to the centralized control.
S603: and the centralized control issues a software version file containing the latest version software to the equipment.
S604: the equipment sets the current version software as the standby version.
S605: the device sets the latest version software in the software version file issued by the centralized control as the master version, and guides the device to load the master version to restart the device.
S606: and counting the restart failure times of the equipment, and guiding the equipment to load the standby version to restart the equipment when the restart failure times of the equipment reach a preset threshold value.
S607: and after the equipment is determined to be restarted successfully, the equipment rejoins the centralized control and sends an upgrade failure notification message to the centralized control.
In the fault-tolerant method for software upgrading provided by the embodiment of the application, when the device determines that the device restart based on the software version file issued by the centralized control fails, the device restart based on the software of the standby version ensures that the network connection can be established between the successfully restarted device and the centralized control, and the operation and maintenance cost is saved without the on-site maintenance of operation and maintenance personnel.
Based on the description of the above method embodiment, the present application further provides a fault tolerant apparatus, and referring to fig. 7, a schematic structural diagram of the fault tolerant apparatus provided in the embodiment of the present application is shown, where the apparatus includes:
a receiving module 701, configured to receive a device file issued by centralized control;
a first update module 702, configured to perform device update based on the device file;
a rollback module 703, configured to perform rollback based on a pre-stored standby file after it is determined that the device update based on the device file fails.
In an alternative embodiment, the device file comprises a configuration file;
the device further comprises:
and the first storage module is used for storing the current configuration information as a standby file.
Specifically, the rollback module is specifically configured to:
and after sending a preset message to the centralized control, if a response message from the centralized control is not received, rolling back based on the standby file.
In another alternative embodiment, the device file comprises a software version file;
the device further comprises:
and the second storage module is used for storing the current version software as a standby file.
Specifically, the rollback module is specifically configured to:
and after determining that the device based on the software version file fails to restart, rolling back based on the standby file.
In the error-tolerant device provided by the embodiment of the application, when it is determined that the device update of the device file issued based on the centralized control fails, the device is rolled back based on the pre-stored standby file, and the device does not exit the centralized control due to the pre-stored standby file, so that the device after rolling back based on the standby file can establish network connection with the centralized control, and operation and maintenance personnel do not need to maintain on the spot, thereby saving the operation and maintenance cost.
In addition, an embodiment of the present application further provides a fault tolerant device, as shown in fig. 8, which may include:
a processor 801, a memory 802, an input device 803, and an output device 804. The number of processors 601 in the fault tolerant device may be one or more, and one processor is taken as an example in fig. 8. In some embodiments of the invention, the processor 801, the memory 802, the input device 803 and the output device 804 may be connected by a bus or other means, wherein the connection by the bus is exemplified in fig. 8.
The memory 802 may be used to store software programs and modules, and the processor 801 executes various functional applications and data processing of the fault tolerant device by operating the software programs and modules stored in the memory 802. The memory 802 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required for at least one function, and the like. Further, the memory 802 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. The input device 803 may be used to receive input numeric or character information and generate signal inputs related to user settings and functional control of the fault tolerant apparatus.
Specifically, in this embodiment, the processor 801 loads an executable file corresponding to a process of one or more application programs into the memory 802 according to the following instructions, and the processor 801 runs the application programs stored in the memory 802, thereby implementing various functions in the fault tolerance method.
In addition, the present application also provides a computer-readable storage medium, in which instructions are stored, and when the instructions are executed on a terminal device, the terminal device is caused to execute the fault tolerance method.
It is understood that for the apparatus embodiments, since they correspond substantially to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The fault-tolerant method, device and equipment provided by the embodiment of the present application are introduced in detail, a specific example is applied in the text to explain the principle and the implementation of the present application, and the description of the embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A fault tolerant method, the method comprising:
receiving a device file issued by centralized control;
updating the equipment based on the equipment file;
and after determining that the device updating based on the device file fails, rolling back based on a pre-stored standby file.
2. The method of claim 1, wherein the device file comprises a configuration file;
after determining that the device update based on the device file fails, before rolling back based on a pre-stored standby file, the method further includes:
the current configuration information is stored as a standby file.
3. The method of claim 2, wherein the rolling back based on the pre-stored spare file after determining that the device update based on the device file fails comprises:
and after sending a preset message to the centralized control, if a response message from the centralized control is not received, rolling back based on the standby file.
4. The method of claim 1, wherein the device file comprises a software version file;
after determining that the device update based on the device file fails, before rolling back based on a pre-stored standby file, the method further includes:
and storing the current version software as a standby file.
5. The method of claim 4, wherein rolling back based on a pre-stored spare file after determining that the device update based on the device file fails comprises:
and after determining that the device based on the software version file fails to restart, rolling back based on the standby file.
6. A fault tolerant apparatus, said apparatus comprising:
the receiving module is used for receiving the equipment files issued by the centralized control;
the first updating module is used for updating equipment based on the equipment file;
and the rollback module is used for performing rollback based on a pre-stored standby file after determining that the equipment updating based on the equipment file fails.
7. The apparatus of claim 6, wherein the device file comprises a configuration file;
the device further comprises:
and the first storage module is used for storing the current configuration information as a standby file.
8. The apparatus of claim 6, wherein the device file comprises a software version file;
the device further comprises:
and the second storage module is used for storing the current version software as a standby file.
9. A computer-readable storage medium having stored therein instructions that, when executed on a terminal device, cause the terminal device to perform the method of any one of claims 1-5.
10. A fault tolerant device, comprising: memory, a processor, and a computer program stored on the memory and executable on the processor, when executing the computer program, implementing the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911025204.XA CN110708203A (en) | 2019-10-25 | 2019-10-25 | Fault tolerance method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911025204.XA CN110708203A (en) | 2019-10-25 | 2019-10-25 | Fault tolerance method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110708203A true CN110708203A (en) | 2020-01-17 |
Family
ID=69203589
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911025204.XA Pending CN110708203A (en) | 2019-10-25 | 2019-10-25 | Fault tolerance method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110708203A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113722007A (en) * | 2021-08-24 | 2021-11-30 | 杭州迪普科技股份有限公司 | Configuration method, device and system of VPN branch equipment |
| CN115878225A (en) * | 2023-02-22 | 2023-03-31 | 中航金网(北京)电子商务有限公司 | Method, device, system, equipment and readable storage medium for processing configuration file |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1968098A (en) * | 2006-05-10 | 2007-05-23 | 华为技术有限公司 | Method for configuring network element device |
| US20120254136A1 (en) * | 2011-03-29 | 2012-10-04 | Kaseya International Limited | Method and apparatus of securely processing data for file backup, de-duplication, and restoration |
| CN104899065A (en) * | 2015-06-11 | 2015-09-09 | 武汉虹信通信技术有限责任公司 | Method and system for batch online recovery and software online upgrading |
| CN107547245A (en) * | 2017-05-27 | 2018-01-05 | 新华三技术有限公司 | A kind of version upgrading method and device |
-
2019
- 2019-10-25 CN CN201911025204.XA patent/CN110708203A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1968098A (en) * | 2006-05-10 | 2007-05-23 | 华为技术有限公司 | Method for configuring network element device |
| US20120254136A1 (en) * | 2011-03-29 | 2012-10-04 | Kaseya International Limited | Method and apparatus of securely processing data for file backup, de-duplication, and restoration |
| CN104899065A (en) * | 2015-06-11 | 2015-09-09 | 武汉虹信通信技术有限责任公司 | Method and system for batch online recovery and software online upgrading |
| CN107547245A (en) * | 2017-05-27 | 2018-01-05 | 新华三技术有限公司 | A kind of version upgrading method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113722007A (en) * | 2021-08-24 | 2021-11-30 | 杭州迪普科技股份有限公司 | Configuration method, device and system of VPN branch equipment |
| CN113722007B (en) * | 2021-08-24 | 2023-11-03 | 杭州迪普科技股份有限公司 | Configuration method, device and system of VPN branch equipment |
| CN115878225A (en) * | 2023-02-22 | 2023-03-31 | 中航金网(北京)电子商务有限公司 | Method, device, system, equipment and readable storage medium for processing configuration file |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2972870B1 (en) | Coordinating fault recovery in a distributed system | |
| CN107526659B (en) | Method and apparatus for failover | |
| US8495618B1 (en) | Updating firmware in a high availability enabled computer system | |
| US20140376362A1 (en) | Dynamic client fail-over during a rolling patch installation based on temporal server conditions | |
| US10880153B2 (en) | Method and system for providing service redundancy between a master server and a slave server | |
| WO2017028375A1 (en) | Version upgrading method and system | |
| CN107153559A (en) | The application program updating method of a kind of electronic equipment | |
| CN113051110A (en) | Cluster switching method, device and equipment | |
| CN112100005A (en) | Redis copy set implementation method and device | |
| CN110708203A (en) | Fault tolerance method, device and equipment | |
| CN112434008A (en) | Distributed database upgrading method, device and medium | |
| CN106533751B (en) | SDN controller cluster merging method and device | |
| CN114531373A (en) | Node state detection method, node state detection device, equipment and medium | |
| CN114064438A (en) | Database fault processing method and device | |
| CN114338363A (en) | Continuous integration method, device, equipment and storage medium | |
| CN109104292B (en) | Update deployment processing method, related device, and computer-readable storage medium | |
| CN112261164A (en) | Logic clock synchronization method and device and central time service cluster | |
| CN111984287A (en) | Equipment upgrading method and system | |
| CN113778607A (en) | Method and device for realizing high availability of virtual machine, cloud management platform and storage medium | |
| CN112751693A (en) | Data processing method and device of distributed storage system and electronic equipment | |
| CN103780433B (en) | Self-healing type virtual resource configuration management data architecture | |
| CN113687867B (en) | Shutdown method, system, equipment and storage medium of cloud platform cluster | |
| CN115629785A (en) | Upgrading method, electronic device and storage medium | |
| CN104866380A (en) | Method and device for processing state transition of cluster management system | |
| CN114860322A (en) | Substrate management controller, control method and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200117 |
|
| RJ01 | Rejection of invention patent application after publication |