CN111966520A - Database high availability switching method, device and system - Google Patents

Abstract

The present application relates to a database high-availability switching method, which includes: connecting and acquiring data from multiple database servers, configuring each database server as a master-slave master database and a standby database; monitoring all currently running master databases and backup databases in real time. Standby database; when the standby database is abnormal, stop monitoring the standby database and the main database corresponding to the standby database, and issue an alarm; when the main database is abnormal and the standby database corresponding to the main database is normal, close the main database, and set the corresponding The standby database is upgraded to the new primary database. When the master node, the master database, is abnormal or down, it can automatically switch to the slave node, the standby database, and continue to provide database services. Moreover, in the present application, all the main databases and standby databases currently running can be monitored in real time through the monitoring and management device, without requiring a large amount of additional server resources for support.

Description

Database high availability switching method, device and system

technical field

The present application relates to the technical field of database management, and in particular, to a method, device and system for high-availability switching of databases.

Background technique

In the prior art, most databases are in a single-node master-slave mode. When the master node is abnormal or downtime, it cannot be quickly recovered, which will result in service unavailability for a long time. Moreover, the existing database high availability is generally in the form of a real-time application cluster, which needs to consume a large amount of server resources.

SUMMARY OF THE INVENTION

In order to overcome the problems existing in the related art at least to a certain extent, the present application provides a database high-availability switching method, device and system.

The scheme of this application is as follows:

According to a first aspect of the embodiments of the present application, a method for switching high availability of a database is provided, including:

Connect and obtain data from multiple database servers, and configure each database server as a master-slave master database and a standby database;

Real-time monitoring of all the main and standby databases currently running;

When the standby database is abnormal, stop monitoring the standby database and the main database corresponding to the standby database, and give an alarm;

When the main library is abnormal and the standby library corresponding to the main library is normal, the main library is closed, and the standby library corresponding to the main library is upgraded to a new main library.

Preferably, in an achievable manner of the present application, the real-time monitoring of all the main and standby databases currently running, specifically includes:

Initiating a detection to the standby database every preset time to detect the running state of the standby database;

If the standby database runs abnormally, it is determined that the standby database is abnormal;

If the standby database is running normally, perform table building and reading and writing operations on the main database corresponding to the standby database;

If the table building and reading and writing operations cannot be performed on the main library within a preset number of times, it is determined that the main library is abnormal.

Preferably, in an achievable manner of the present application, it also includes:

Perform table building read and write operations on the new main library, if the new main library is successfully built with table read and write operations, then judged as successful switching; if the new main library is performed with table construction read and write operations If it fails, it is judged that the handover fails.

Preferably, in an achievable manner of the present application, it also includes:

If the switch is successful, the internal staff will be notified through the preset communication method;

If the switching fails, the internal staff will be notified through the preset communication method, and the abnormal information generated by the switching failure will be written into the log.

Preferably, in an achievable manner of the present application, it also includes:

A new standby database is reconfigured for the new primary database, and the new primary database and the new standby database are monitored in real time.

Preferably, in an achievable manner of the present application, it also includes:

When the standby database is abnormal, the abnormal information generated by the abnormality of the standby database is written into a log.

Preferably, in an achievable manner of the present application, the database server is configured with a master database and a backup database in a master-slave form through a high-availability database solution.

According to a second aspect of the embodiments of the present application, a database high-availability switching device is provided, including:

processor and memory;

The processor and the memory are connected through a communication bus:

Wherein, the processor is used to call and execute the program stored in the memory;

The memory is used to store a program, and the program is at least used to execute the method for switching high availability of a database according to any one of the above.

According to a third aspect of the embodiments of the present application, a database high-availability switching system is provided, including:

Monitoring and management equipment, multiple database servers;

The monitoring and management devices are respectively connected to each of the database servers;

The database servers are all configured with master and slave databases in master and slave form;

The monitoring and management device is used for real-time monitoring of all the main libraries and standby libraries currently running; when an abnormality occurs in the standby libraries, it stops monitoring the main libraries corresponding to the standby libraries and the standby libraries, and gives an alarm ; When the main library is abnormal and the standby library corresponding to the main library is normal, the main library is closed, and the standby library corresponding to the main library is upgraded to a new main library.

Preferably, in an achievable manner of the present application, each of the database servers is equipped with Oracle software;

The monitoring and management device deploys Python3 software, Oracle software, and an open source Python extension module that allows access to the Oracle database server

The technical solution provided by the present application may include the following beneficial effects: due to the connection and acquisition of multiple database server data in the present application, each database server is configured as a master database and a backup database in the form of master and slave; real-time monitoring of all currently running databases The main database and the standby database; when the standby database is abnormal, stop monitoring the main database corresponding to the standby database and the standby database, and issue an alarm; when the main database is abnormal and the standby database corresponding to the main database is normal, close the main database and reset the main database to the main database. The standby database corresponding to the database is upgraded to the new primary database. When the master node, the master database, is abnormal or down, it can automatically switch to the slave node, the standby database, and continue to provide database services. Moreover, in the present application, all the main databases and standby databases currently running can be monitored in real time through the monitoring and management device, without the need for a large amount of additional server resources for support.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not limiting of the present application.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the 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 switching method provided by an embodiment of the present application;

FIG. 2 is a schematic flowchart of an actual runtime of a database high availability switching method provided by an embodiment of the present application;

3 is a schematic structural diagram of a database high-availability switching device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a database high-availability switching system provided by an embodiment of the present application.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as recited in the appended claims.

FIG. 1 is a schematic flowchart of a database high availability switching method provided by an embodiment of the present application. Referring to FIG. 1, a database high availability switching method includes:

S11: Connect to and obtain data from multiple database servers, and configure each database server as a master-slave master database and a standby database;

S12: Real-time monitoring of all the main and standby databases currently running;

S13: When the standby database is abnormal, stop monitoring the standby database and the main database corresponding to the standby database, and issue an alarm;

S14: When the main library is abnormal and the standby library corresponding to the main library is normal, the main library is closed, and the standby library corresponding to the main library is upgraded to a new main library.

In this embodiment, multiple database servers can be monitored at the same time, and each database server can be configured in a different environment.

Preferably, each database server is equipped with Oracle software;

Correspondingly, the monitoring and management device deploys Python3 software, Oracle software, and an open source Python extension module that allows access to the Oracle database server.

Preferably, the monitoring and management device adopts an ODM monitoring and management machine.

Due to the connection and acquisition of data from multiple database servers in this application, each database server is configured as a master-slave master database and a backup database; all currently running master databases and backup databases are monitored in real time; when an exception occurs in the backup database , stop monitoring the standby database and the main database corresponding to the standby database, and issue an alarm; when the main database is abnormal and the standby database corresponding to the main database is normal, close the main database, and upgrade the standby database corresponding to the main database to the new main database. When the master node, the master database, is abnormal or down, it can automatically switch to the slave node, the standby database, and continue to provide database services. Moreover, in the present application, all the main databases and standby databases currently running can be monitored in real time through the monitoring and management device, without requiring a large amount of additional server resources for support.

Further, referring to Figure 2, real-time monitoring of all the main and standby databases currently running, including:

Initiate a test to the standby database every preset time to detect the running status of the standby database;

If the standby database runs abnormally, it is judged that the standby database is abnormal;

If the standby database is running normally, perform table creation and read and write operations on the main database corresponding to the standby database;

If the table creation and read/write operations cannot be performed on the main library within the preset number of times, it is determined that the main library is abnormal.

The preset time can be one second, that is, a test is initiated to the standby database every one second to detect the running status of the standby database. When the standby database is running normally, perform table creation and read and write operations on the main database corresponding to the standby database.

The preset number of times can be three times, that is, when the main library cannot be created or read and written for three consecutive times, it is determined that the main library is abnormal.

The database high-availability switching method in some embodiments, referring to FIG. 2 , further includes:

Perform table building read and write operations on the new main database. If the table building read and write operations on the new main database are successful, the switch is judged to be successful; if the new main database table building read and write operations fail, it is judged as a switch. fail.

After upgrading the standby database to the new primary database, perform table building and reading and writing operations on the new primary database to prevent the new primary database from providing data support normally. After confirming that the new main database successfully performs the table building and reading and writing operations, it is judged that the switching is successful.

Preferably, the new main library is tested for multiple times of table creation and read and write operations, such as three times.

The database high-availability switching method in some embodiments, referring to FIG. 2 , further includes:

If the switch is successful, the internal staff will be notified through the preset communication method;

If the switching fails, the internal staff will be notified through the preset communication method, and the abnormal information generated by the switching failure will be written into the log.

The default communication method can be DingTalk, mail, etc.

Regardless of the success or failure of the switch, the internal staff will be informed through DingTalk, email, etc.

When the switching fails, the abnormal information generated by the switching failure is written into the log, so that the internal staff can check the failure reason for processing.

The database high-availability switching method in some embodiments, referring to FIG. 2 , further includes:

Reconfigure the new standby database for the new primary database, and monitor the new primary database and the new standby database in real time.

After the standby database is upgraded to the new primary database, it is necessary to reconfigure the new standby database for the new primary database, and monitor the new primary database and the new standby database in real time to prevent abnormality or downtime of the new primary database.

The database high-availability switching method in some embodiments, referring to FIG. 2 , further includes:

When the standby database is abnormal, the abnormal information generated by the abnormality of the standby database is written into the log.

When an exception occurs in the standby database, the abnormal information generated by the abnormality of the standby database is written into the log, so that the internal staff can check the failure reason for processing.

In the database high availability switching method in some embodiments, the database server is configured with a master database and a standby database in a master-slave form through a high-availability database scheme.

Preferably, the DataGuard solution is adopted. The DataGuard solution is a high-availability database solution launched by Oracle Corporation. It uses log synchronization between the primary node and the standby node to ensure data synchronization, and can realize rapid database switching and disaster recovery. Data Guard just sets the database on the software, and does not need to purchase any additional components. Users can synchronize the primary and secondary databases with little impact on the primary database. The data difference between the active and standby servers is limited to the online log part.

A database high-availability switching device, referring to Figure 3, includes:

processing, 21 and memory 22;

The processor 21 is connected with the memory 22 through a communication bus:

Wherein, the processor 21 is used for calling and executing the program stored in the memory 22;

The memory 22 is used for storing a program, and the program is at least used for executing the database high-availability switching method in any of the above embodiments.

A database high-availability switching system, referring to Figure 4, includes:

Monitoring and management equipment 31, multiple database servers 32;

The monitoring and management device 31 is respectively connected to each database server 32;

The database servers 32 are all configured as master and slave databases in the form of master and slave databases;

The monitoring and management device 31 is used for real-time monitoring of all the main libraries and standby libraries currently running; when the standby library is abnormal, it stops monitoring the main library corresponding to the standby library and the standby library, and gives an alarm; when the main library is abnormal and the main library corresponds to When the standby database is normal, close the main database and upgrade the standby database corresponding to the main database to the new main database.

In the database high-availability switching system in some embodiments, each database server 32 is equipped with Oracle software;

The monitoring and management device 31 deploys Python3 software, Oracle software, and an open source Python extension module that allows access to the Oracle database server.

It can be understood that, the same or similar parts in the above embodiments may refer to each other, and the content not described in detail in some embodiments may refer to the same or similar content in other embodiments.

It should be noted that, in the description of the present application, the terms "first", "second", etc. are only used for the purpose of description, and should not be construed as indicating or implying relative importance. Also, in the description of this application, unless otherwise specified, the meaning of "plurality" means at least two.

Any description of a process or method in the flowcharts or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing a specified logical function or step of the process , and the scope of the preferred embodiments of the present application includes alternative implementations in which the functions may be performed out of the order shown or discussed, including performing the functions substantially concurrently or in the reverse order depending upon the functions involved, which should It is understood by those skilled in the art to which the embodiments of the present application belong.

It should be understood that various parts of this application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, 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, it can be implemented by any one or a combination of the following techniques known in the art: Discrete logic circuits, application specific integrated circuits with suitable combinational logic gates, Programmable Gate Arrays (PGA), Field Programmable Gate Arrays (FPGA), etc.

Those skilled in the art can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, and the program can be stored in a computer-readable storage medium. When executed, one or a combination of the steps of the method embodiment is included.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, and the like.

In the description of this specification, description with reference to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc., mean specific features described in connection with the embodiment or example , structure, material or feature is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms 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 the embodiments of the present application have been shown and described above, it should be understood that the above embodiments are exemplary and should not be construed as limitations to the present application. Embodiments are subject to variations, modifications, substitutions and variations.

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.

Images