CN111966520A - Database high-availability switching method, device and system - Google Patents
Database high-availability switching method, device and system Download PDFInfo
- Publication number
- CN111966520A CN111966520A CN202010794037.1A CN202010794037A CN111966520A CN 111966520 A CN111966520 A CN 111966520A CN 202010794037 A CN202010794037 A CN 202010794037A CN 111966520 A CN111966520 A CN 111966520A
- Authority
- CN
- China
- Prior art keywords
- library
- standby
- main
- database
- abnormal
- 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
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000002159 abnormal effect Effects 0.000 claims abstract description 48
- 238000012544 monitoring process Methods 0.000 claims abstract description 42
- 238000004891 communication Methods 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a database high-availability switching method, which comprises the following steps: connecting and acquiring data of a plurality of database servers, and configuring each database server into a master database and a slave database in a master-slave mode; monitoring all the main libraries and the standby libraries which are running at present in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library into a new main library. When the main node, namely the main library, is abnormal or down, the main node, namely the standby library, can be automatically switched to the slave node, namely the standby library, and the database service is continuously provided. In addition, in the application, all the main libraries and the standby libraries which are currently running can be monitored in real time through the monitoring management equipment, and extra large amount of server resources are not needed for supporting.
Description
Technical Field
The present application relates to the field of database management technologies, and in particular, to a method, a device, and a system for database high availability switching.
Background
In the prior art, most databases are in a single-node master-slave mode, and when a master node is abnormal or crashes, the master node cannot be quickly recovered, so that services cannot be used for a long time. Moreover, the existing database is highly available and generally in a real-time application cluster form, and a large amount of server resources are consumed.
Disclosure of Invention
In order to overcome the problems in the related art at least to a certain extent, the application provides a database high-availability switching method, device and system.
The scheme of the application is as follows:
according to a first aspect of embodiments of the present application, a database high availability switching method is provided, including:
connecting and acquiring data of a plurality of database servers, and configuring each database server into a master database and a slave database in a master-slave mode;
monitoring all the main libraries and the standby libraries which are currently running in real time;
when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm;
and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library to a new main library.
Preferably, in an implementation manner of the present application, the monitoring all the main libraries and standby libraries currently running in real time specifically includes:
initiating detection to the standby library once every preset time, and detecting the running state of the standby library;
if the standby library is abnormal in operation, judging that the standby library is abnormal;
if the standby library runs normally, performing table building read-write operation on a main library corresponding to the standby library;
and if the table building read-write operation cannot be carried out on the main library within the preset times, judging that the main library is abnormal.
Preferably, in an implementation manner of the present application, the method further includes:
performing table building read-write operation on the new master library, and if the table building read-write operation on the new master library is successful, judging that the switching is successful; and if the table building read-write operation on the new master library fails, judging that the switching fails.
Preferably, in an implementation manner of the present application, the method further includes:
if the switching is successful, informing internal workers through a preset communication mode;
and if the switching fails, informing internal workers in a preset communication mode, and writing abnormal information generated by the switching failure into a log.
Preferably, in an implementation manner of the present application, the method further includes:
and reconfiguring a new standby library for the new main library, and monitoring the new main library and the new standby library in real time.
Preferably, in an implementation manner of the present application, the method further includes:
and when the standby library is abnormal, writing abnormal information generated by the abnormal standby library into a log.
Preferably, in an implementable manner of the present application, the database server is configured as a master library and a slave library in a master-slave fashion by means of a high availability database schema.
According to a second aspect of the embodiments of the present application, there is provided a database high availability switching apparatus, including:
a processor and a memory;
the processor and the memory are connected through a communication bus:
the processor is used for calling and executing the program stored in the memory;
the memory is used for storing a program, and the program is at least used for executing the database high availability switching method.
According to a third aspect of the embodiments of the present application, there is provided a database high availability switching system, including:
a monitoring management device, a plurality of database servers;
the monitoring management equipment is respectively connected with each database server;
the database servers are all configured into a master library and a slave library in master-slave mode;
the monitoring management equipment is used for monitoring all the main libraries and the standby libraries which are currently running in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library to a new main library.
Preferably, in an implementation manner of the present application, each of the database servers is loaded with Oracle software;
the monitoring management equipment deploys Python3 software, Oracle software and open-source Python extension module allowing access to Oracle database server
The technical scheme provided by the application can comprise the following beneficial effects: because a plurality of database server data are connected and obtained in the application, each database server is configured into a master database and a slave database in a master-slave mode; monitoring all the main libraries and the standby libraries which are running at present in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library into a new main library. When the main node, namely the main library, is abnormal or down, the main node, namely the standby library, can be automatically switched to the slave node, namely the standby library, and the database service is continuously provided. In addition, in the application, all the main libraries and the standby libraries which are currently running can be monitored in real time through the monitoring management equipment, and extra large amount of server resources are not needed for supporting.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic flowchart of a database high availability handover method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart of an actual runtime of a database high availability switching method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a database high availability switching device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a database high availability switching system according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 is a schematic flowchart of a database high availability switching method according to an embodiment of the present application, and referring to fig. 1, a database high availability switching method includes:
s11: connecting and acquiring data of a plurality of database servers, and configuring each database server into a master database and a slave database in a master-slave mode;
s12: monitoring all the main libraries and the standby libraries which are running at present in real time;
s13: when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm;
s14: and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library into a new main library.
In this embodiment, a plurality of database servers may be monitored simultaneously, and each database server may be configured in a different environment.
Preferably, each database server is loaded with Oracle software;
correspondingly, the monitoring management device deploys Python3 software, Oracle software, and an open-source Python extension module allowing access to the Oracle database server.
Preferably, the monitoring management device adopts an ODM monitoring management machine.
Because a plurality of database server data are connected and obtained in the application, each database server is configured into a master database and a slave database in a master-slave mode; monitoring all the main libraries and the standby libraries which are running at present in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library into a new main library. When the main node, namely the main library, is abnormal or down, the main node, namely the standby library, can be automatically switched to the slave node, namely the standby library, and the database service is continuously provided. In addition, in the application, all the main libraries and the standby libraries which are currently running can be monitored in real time through the monitoring management equipment, and extra large amount of server resources are not needed for supporting.
Further, referring to fig. 2, monitoring all the currently running primary libraries and standby libraries in real time specifically includes:
initiating detection to the standby database every preset time, and detecting the running state of the standby database;
if the operation of the standby library is abnormal, judging that the standby library is abnormal;
if the standby library runs normally, performing table building read-write operation on the main library corresponding to the standby library;
and if the table-building read-write operation cannot be carried out on the main library within the preset times, judging that the main library is abnormal.
The preset time can be one second, namely, the detection is initiated to the standby library every other one second to detect the running state of the standby library. And when the standby library runs normally, performing table building read-write operation on the main library corresponding to the standby library.
The preset times can be three times, namely when the table building read-write operation cannot be carried out on the master library for three consecutive times, the master library is judged to be abnormal.
The database high availability switching method in some embodiments, with reference to fig. 2, further includes:
performing table building read-write operation on the new main library, and if the table building read-write operation on the new main library is successful, judging that the switching is successful; and if the table building read-write operation on the new main library fails, judging that the switching fails.
And after the standby library is upgraded to a new main library, performing table building read-write operation on the new main library to prevent the new main library from being incapable of normally providing data support. And after the new master library is confirmed to be successfully subjected to table building read-write operation, judging that the switching is successful.
Preferably, the new master library is tested by performing multiple table-building read-write operations, such as three times.
The database high availability switching method in some embodiments, with reference to fig. 2, further includes:
if the switching is successful, informing internal workers through a preset communication mode;
and if the switching fails, informing internal workers in a preset communication mode, and writing abnormal information generated by the switching failure into a log.
The preset communication mode can be a nail mode, a mail mode and the like.
And the switching is successful and failed, and the switching is informed to internal workers in the modes of nailing, mail and the like.
When the switching fails, the abnormal information generated by the switching failure is written into a log, so that internal workers can conveniently check the failure reason so as to process the failure.
The database high availability switching method in some embodiments, with reference to fig. 2, further includes:
and reconfiguring the new main library with the new standby library, and monitoring the new main library and the new standby library in real time.
After the standby library is upgraded to a new main library, the new standby library needs to be reconfigured for the new main library, and the new main library and the new standby library are monitored in real time so as to prevent the new main library from being abnormal or down.
The database high availability switching method in some embodiments, with reference to fig. 2, further includes:
and when the standby library is abnormal, writing abnormal information generated by the abnormality of the standby library into a log.
When the standby library is abnormal, the abnormal information generated by the abnormal standby library is written into the log, so that internal workers can conveniently check the failure reason, and the processing is convenient.
In some embodiments, the database server is configured as a master library and a slave library in a master-slave manner through a high-availability database scheme.
Preferably, a database scheme is adopted, wherein the database scheme is a high-availability database scheme introduced by oracle corporation, and ensures data synchronization between a primary node and a standby node through log synchronization, so that rapid database switching and catastrophic recovery can be realized. The Data Guard simply sets up the database on the software and does not need to purchase any additional components. The user can realize the synchronization of the main database and the standby database under the condition of little influence on the main database. While the data differences between the host and the standby are limited to the online log portion.
A database high availability switching apparatus, referring to fig. 3, comprising:
process, 21 and memory 22;
the processor 21 is connected to the memory 22 by a communication bus:
the processor 21 is configured to call and execute a program stored in the memory 22;
a memory 22 for storing a program for performing at least the database high availability switching method as in any of the above embodiments.
A database high availability switching system, referring to fig. 4, comprising:
a monitoring management device 31, a plurality of database servers 32;
the monitoring management device 31 is connected with each database server 32;
the database servers 32 are configured as a master library and a slave library in master-slave form;
the monitoring management device 31 is used for monitoring all the main libraries and the standby libraries which are currently running in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library into a new main library.
In some embodiments of the database high availability switching system, each database server 32 is loaded with Oracle software;
the monitoring management device 31 deploys Python3 software, Oracle software, and an open source Python extension module that allows access to the Oracle database server.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (10)
1. A database high-availability switching method is characterized by comprising the following steps:
connecting and acquiring data of a plurality of database servers, and configuring each database server into a master database and a slave database in a master-slave mode;
monitoring all the main libraries and the standby libraries which are currently running in real time;
when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm;
and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library to a new main library.
2. The method according to claim 1, wherein the monitoring, in real time, all the primary libraries and the backup libraries currently running specifically includes:
initiating detection to the standby library once every preset time, and detecting the running state of the standby library;
if the standby library is abnormal in operation, judging that the standby library is abnormal;
if the standby library runs normally, performing table building read-write operation on a main library corresponding to the standby library;
and if the table building read-write operation cannot be carried out on the main library within the preset times, judging that the main library is abnormal.
3. The method of claim 2, further comprising:
performing table building read-write operation on the new master library, and if the table building read-write operation on the new master library is successful, judging that the switching is successful; and if the table building read-write operation on the new master library fails, judging that the switching fails.
4. The method of claim 3, further comprising:
if the switching is successful, informing internal workers through a preset communication mode;
and if the switching fails, informing internal workers in a preset communication mode, and writing abnormal information generated by the switching failure into a log.
5. The method of claim 1, further comprising:
and reconfiguring a new standby library for the new main library, and monitoring the new main library and the new standby library in real time.
6. The method of claim 1, further comprising:
and when the standby library is abnormal, writing abnormal information generated by the abnormal standby library into a log.
7. The method of claim 1, wherein the database server is configured as a master library and a slave library in a master-slave fashion via a high availability database schema.
8. A database high availability switching device, comprising:
a processor and a memory;
the processor and the memory are connected through a communication bus:
the processor is used for calling and executing the program stored in the memory;
the memory for storing a program for performing at least the database high availability switching method of any one of claims 1-7.
9. A database high availability switching system, comprising:
a monitoring management device, a plurality of database servers;
the monitoring management equipment is respectively connected with each database server;
the database servers are all configured into a master library and a slave library in master-slave mode;
the monitoring management equipment is used for monitoring all the main libraries and the standby libraries which are currently running in real time; when the standby library is abnormal, stopping monitoring the standby library and the main library corresponding to the standby library, and giving an alarm; and when the main library is abnormal and the standby library corresponding to the main library is normal, closing the main library and upgrading the standby library corresponding to the main library to a new main library.
10. The database high availability switching system of claim 9, wherein each of the database servers is loaded with Oracle software;
the monitoring management device deploys Python3 software, Oracle software, and an open-source Python extension module allowing access to the Oracle database server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010794037.1A CN111966520A (en) | 2020-08-10 | 2020-08-10 | Database high-availability switching method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010794037.1A CN111966520A (en) | 2020-08-10 | 2020-08-10 | Database high-availability switching method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111966520A true CN111966520A (en) | 2020-11-20 |
Family
ID=73366238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010794037.1A Pending CN111966520A (en) | 2020-08-10 | 2020-08-10 | Database high-availability switching method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111966520A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113806121A (en) * | 2021-02-09 | 2021-12-17 | 京东科技控股股份有限公司 | Instance backup abnormity detection method and device, electronic equipment and storage medium |
| CN114785789A (en) * | 2022-04-26 | 2022-07-22 | 平安普惠企业管理有限公司 | Database fault management method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064860A (en) * | 2011-10-21 | 2013-04-24 | 阿里巴巴集团控股有限公司 | Database high availability implementation method and device |
| US20150347250A1 (en) * | 2014-05-30 | 2015-12-03 | Altibase Corp. | Database management system for providing partial re-synchronization and partial re-synchronization method of using the same |
| CN110442650A (en) * | 2019-08-09 | 2019-11-12 | 中国工商银行股份有限公司 | Database switching method, device, system, electronic equipment and storage medium |
| CN110955723A (en) * | 2019-11-15 | 2020-04-03 | 北京浪潮数据技术有限公司 | Master-slave database synchronization state monitoring method and device and electronic equipment |
| CN111460039A (en) * | 2020-04-07 | 2020-07-28 | 中国建设银行股份有限公司 | Relational database processing system, client, server and method |
-
2020
- 2020-08-10 CN CN202010794037.1A patent/CN111966520A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064860A (en) * | 2011-10-21 | 2013-04-24 | 阿里巴巴集团控股有限公司 | Database high availability implementation method and device |
| US20150347250A1 (en) * | 2014-05-30 | 2015-12-03 | Altibase Corp. | Database management system for providing partial re-synchronization and partial re-synchronization method of using the same |
| CN110442650A (en) * | 2019-08-09 | 2019-11-12 | 中国工商银行股份有限公司 | Database switching method, device, system, electronic equipment and storage medium |
| CN110955723A (en) * | 2019-11-15 | 2020-04-03 | 北京浪潮数据技术有限公司 | Master-slave database synchronization state monitoring method and device and electronic equipment |
| CN111460039A (en) * | 2020-04-07 | 2020-07-28 | 中国建设银行股份有限公司 | Relational database processing system, client, server and method |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113806121A (en) * | 2021-02-09 | 2021-12-17 | 京东科技控股股份有限公司 | Instance backup abnormity detection method and device, electronic equipment and storage medium |
| CN113806121B (en) * | 2021-02-09 | 2024-05-17 | 京东科技控股股份有限公司 | Instance backup anomaly detection method and device, electronic equipment and storage medium |
| CN114785789A (en) * | 2022-04-26 | 2022-07-22 | 平安普惠企业管理有限公司 | Database fault management method and device, electronic equipment and storage medium |
| CN114785789B (en) * | 2022-04-26 | 2024-01-16 | 永诚恒易网络科技股份有限公司 | Database fault management method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9785521B2 (en) | Fault tolerant architecture for distributed computing systems | |
| US9348573B2 (en) | Installation and fault handling in a distributed system utilizing supervisor and dependency manager nodes | |
| CN102597962B (en) | Method and system for fault management in virtual computing environments | |
| US8713350B2 (en) | Handling errors in a data processing system | |
| US10068015B2 (en) | Monitoring a monitoring-target process | |
| CN107660289B (en) | Automatic network control | |
| US20160132420A1 (en) | Backup method, pre-testing method for environment updating and system thereof | |
| US7673023B1 (en) | Method and apparatus for service processor updates | |
| WO2018095107A1 (en) | Bios program abnormal processing method and apparatus | |
| JPH05181823A (en) | Method and apparatus for controlling block in block partitioning type process environment | |
| CN111966520A (en) | Database high-availability switching method, device and system | |
| CN112199240A (en) | Method for switching nodes during node failure and related equipment | |
| CN113703823A (en) | BMC (baseboard management controller) firmware upgrading method and device, electronic equipment and storage medium | |
| US7996707B2 (en) | Method to recover from ungrouped logical path failures | |
| CN117421158A (en) | Database fault processing method, system and storage medium | |
| CN117891652A (en) | Database configuration file recovery method and related device | |
| US7467324B1 (en) | Method and apparatus for continuing to provide processing on disk outages | |
| US20120311391A1 (en) | Failure data management for a distributed computer system | |
| GB2532076A (en) | Backup method, pre-testing method for environment updating and system thereof | |
| US9274905B1 (en) | Configuration tests for computer system | |
| CN109408123B (en) | Method and device for reloading configuration file | |
| CN114201393A (en) | Software test processing method, device, equipment, medium and program product | |
| US11237914B2 (en) | Intelligent handling of consistency level of virtual machines | |
| TW200307200A (en) | Multiple fault location in a series of devices | |
| CN111581034A (en) | RAID card fault processing method and device |
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 |