CN104239548A - Database disaster recovery system and database disaster recovery method - Google Patents
Database disaster recovery system and database disaster recovery method Download PDFInfo
- Publication number
- CN104239548A CN104239548A CN201410491536.8A CN201410491536A CN104239548A CN 104239548 A CN104239548 A CN 104239548A CN 201410491536 A CN201410491536 A CN 201410491536A CN 104239548 A CN104239548 A CN 104239548A
- Authority
- CN
- China
- Prior art keywords
- server
- floating
- address
- standby server
- standby
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- 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
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
Abstract
The invention discloses a database disaster recovery system and a database disaster recovery method. The disaster recovery system comprises a main server, a first backup server, at least one second backup server, a detection unit, a floating IP control unit and a toggle script. According to the technical scheme, when the disaster recovery system stays at an initial state, the main server is configured with a first floating IP, the second backup server is configured with a second floating IP, the main server has a database writing business, and the first backup server has a data reading business, so that the load allocation of the disaster recovery system is realized; meanwhile, the detection unit detects whether the main server, the first backup server and the second backup server are abnormal or not, when at least one of the main server, the first backup server and the second backup server is abnormal, the floating IP control unit controls the first floating IP and/or the second floating IP to float to a target server, so that the active disaster recovery of the server can be realized, and the resource availability in the system can be maximally guaranteed.
Description
Technical field
The present invention relates to database technical field, particularly a kind of database disaster tolerance system and database disaster recovery method.
Background technology
Enterprise is various to database demand, and the demand especially for the full resource isolated data storehouse product of difference configuration, different capabilities, difference in functionality is day by day strong, disposes sole disposition database product at present and is difficult to the diversified demand dealing with enterprise.
The database product that market exists is deployed in physical server substantially, and this just causes migration, to back up and tackle multiple different business demand more difficult; If the empty machine under cloud computing environment directly disposes database, the IO performance of the simple Database Systems of formation can not meet demand, and the security performance of data resource is also poor.
Summary of the invention
The invention provides a kind of database disaster tolerance system and database disaster recovery method, the load that this database disaster tolerance system achieves server is shared, mutually for disaster tolerance, maximize and ensure that in system, resource can be used.
For achieving the above object, the invention provides a kind of database disaster tolerance system, comprising:
Primary server, is configured with the first Floating IP address;
First standby server and at least one second standby server, wherein the first standby server is configured with the second Floating IP address;
Detecting unit, whether abnormal for detecting described primary server, described first standby server and described second standby server;
Floating IP address control module, for when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control described first Floating IP address and/or described second Floating IP address floats to destination server;
Script controlling unit, controls described destination server and runs switching script, possess corresponding service business to make described destination server.
Alternatively, the quantity of described second standby server is one.
Alternatively, described Floating IP address control module specifically for, when detecting described primary server exception, control described first Floating IP address and float to destination server, described destination server is the second standby server.
Alternatively, described Floating IP address control module specifically for, when detecting that described first standby server is abnormal, control described second Floating IP address and float to destination server, described destination server is the second standby server.
Alternatively, described Floating IP address control module specifically for, when detecting that described primary server and described first standby server are all abnormal, control described first Floating IP address and to float and described second Floating IP address floats to destination server, described destination server is the second standby server.
Alternatively, described Floating IP address control module specifically for, when detecting that described primary server and described second standby server are all abnormal, control described first Floating IP address and float to destination server, described destination server is the first standby server.
Alternatively, described Floating IP address control module specifically for, when detecting that described first standby server and described second standby server are all abnormal, control described second Floating IP address and float to destination server, described destination server is primary server.
For achieving the above object, the invention provides a kind of database disaster recovery method, comprising:
Whether extremely, detect described primary server, described first standby server and described second standby server, described primary server is configured with the first Floating IP address, and described first standby server is configured with the second Floating IP address;
When detect in described primary server, described first standby server and described second standby server at least one abnormal time, control described first Floating IP address and/or described second Floating IP address floats to destination server;
Control described destination server and run switching script, possess corresponding service business to make described destination server.
Alternatively, the quantity of described second standby server is one.
Alternatively, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting described primary server exception, control described first Floating IP address and float to destination server, described destination server is the second standby server.
Alternatively, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described first standby server is abnormal, control described second Floating IP address and float to destination server, described destination server is the second standby server.
Alternatively, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described primary server and described first standby server are all abnormal, control described first Floating IP address and to float and described second Floating IP address floats to destination server, described destination server is the second standby server.
Alternatively, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described primary server and described second standby server are all abnormal, control described first Floating IP address and float to destination server, described destination server is the first standby server.
Alternatively, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described first standby server and described second standby server are all abnormal, control described second Floating IP address and float to destination server, described destination server is primary server.
The present invention has following beneficial effect:
The invention provides a kind of database disaster tolerance system and database disaster recovery method, this database disaster tolerance system comprises: a primary server, the first standby server, at least one second standby server, detecting unit, Floating IP address control module and a switching script, the clear in structure of this database disaster tolerance system, simple, be convenient to realize.Simultaneously, when this database disaster tolerance system is in original state, primary server is configured with the first Floating IP address, first standby server is configured with the second Floating IP address, primary server possesses data write business, first standby server possesses digital independent business, thus the load achieving database disaster tolerance system is shared.Further, whether detecting unit detects primary server, the first standby server and the second standby server in real time abnormal, when Floating IP address control module is used at least one exception when detecting in primary server, the first standby server and the second standby server, control the first Floating IP address and/or the second Floating IP address floats to destination server, thus the standby mutually disaster tolerance achieved between server, maximization ensure that in system, resource can be used, and whole disaster tolerance process is substantially without manual intervention, everything completes automatically.
Accompanying drawing explanation
The structural representation of a kind of database disaster tolerance system that Fig. 1 provides for the embodiment of the present invention one;
The process flow diagram of a kind of database disaster recovery method that Fig. 2 provides for the embodiment of the present invention two.
Embodiment
For making those skilled in the art understand technical scheme of the present invention better, below in conjunction with accompanying drawing, database disaster tolerance system provided by the invention and database disaster recovery method are described in detail.
Embodiment one
The structural representation of a kind of database disaster tolerance system that Fig. 1 provides for the embodiment of the present invention one, as shown in Figure 1: comprising: a primary server 1, first standby server 2, at least one second standby server 3 (exemplary in Fig. 1 depict), detecting unit 4, Floating IP address control module 5 and Script controlling unit 6, wherein, primary server 1 is configured with the first Floating IP address, first standby server 2 is configured with the second Floating IP address, detecting unit 4 for detect primary server 1, first standby server 2 and the second standby server 3 whether abnormal; Floating IP address control module 5 for when detect in primary server 1, first standby server 2 and the second standby server 3 at least one abnormal time, control the first Floating IP address and/or the second Floating IP address floats to destination server; Script controlling unit 6 runs for control objectives server and switches script, possesses corresponding service business to make destination server.
Particularly, when destination server configuring the first Floating IP address, if destination server runs this switching script, then destination server possesses data write business; When destination server configuring the second Floating IP address, if destination server runs this switching script, then destination server is for the read-only business of data; When destination server configuring the first Floating IP address and the second Floating IP address, if destination server runs this switching script, then destination server possesses data write business and the read-only business of data.Wherein, switch script can be pre-stored within the service catalogue of each server.
The disaster tolerance process of this database disaster tolerance system is described below in conjunction with example.Wherein, assuming that the quantity of the second standby server 3 is one.
With reference to figure 1, database disaster tolerance system original state: primary server 1 is configured with the first Floating IP address, primary server 1 possesses data write business (application program is to the server write data being configured with the first Floating IP address); First standby server 2 is configured with the second Floating IP address, and the first standby server 2 possesses digital independent business (application program reads data to being configured with the second Floating IP address); Second standby server 3 does not configure Floating IP address, and second server is in idle condition.Now, the first standby server 2 and the second standby server 3 send Data Update request to primary server 1, to realize the first standby server 2 and the second standby server 3 and the data syn-chronization in primary server 1.Meanwhile, extremely whether the detection that detecting unit 4 is real-time primary server 1, first standby server 2 and the second standby server 3.It should be noted that, but "abnormal" refers to that server hardware breaks down or server hardware does not have the service of fault server to break down here.In the present embodiment, the direction of data syn-chronization is unidirectional, can only be do not possess data write business server to possess data write business server request data synchronous.
In the present embodiment, utilize primary server 1 to bear data write business, the first standby server 2 bears digital independent business, and this database disaster tolerance system is by the mode of read and write abruption, achieve two servers sharing load, thus effectively improve the arithmetic speed of server.
Below under there are abnormal conditions at different servers, the corresponding course of work of this database disaster tolerance system is described.
Situation one, when detecting unit 4 detects that primary server 1 is abnormal, the second Floating IP address that Floating IP address control module 5 the first Floating IP address controlled on primary server 1 floats on the second standby server 3, first standby server 2 is motionless.Meanwhile, primary server 1 is taken away overhaul.It should be noted that, by arranging IP control module 5 in the present embodiment, make the first Floating IP address or the second Floating IP address when floating, the first Floating IP address or the second Floating IP address preferentially float to and are on the server of idle condition.
When the first Floating IP address floats to the second standby server 3, be the second standby server 3 and be configured with the first Floating IP address, but the second standby server 3 now does not also possess data write business.After Script controlling unit 6 controls the second standby server 3 operation switching script, the second standby server 3 possesses data write business, and application program can write data to the second standby server 3.Now, the first standby server 2 asks synchrodata to the second standby server 3.
When primary server 1 repairs and is again in database disaster tolerance system, the first Floating IP address on the second standby server 3 again floats to primary server 1, second standby server 3 and is again in idle condition.Meanwhile, Script controlling unit 6 controls primary server 1 and runs switching script, thus possesses data write business, and database disaster tolerance system returns to original state.
Situation two, when detecting unit 4 detects that the first standby server 2 is abnormal, Floating IP address control module 5 the second Floating IP address controlled on the first standby server 2 floats to the second standby server 3, and the first Floating IP address on primary server 1 is motionless.Meanwhile, the first standby server 2 is taken away overhaul.
After Script controlling unit 6 controls the second standby server 3 operation switching script, the second standby server 3 possesses digital independent business, and application program can read data to the second standby server 3.Now, only the second standby server 3 to primary business device request synchrodata.
When the first standby server 2 repairs and is again in database disaster tolerance system, the second Floating IP address on the second standby server 3 floats on the first standby server 2 again, and the second standby server 3 is in idle condition again.Meanwhile, Script controlling unit 6 controls the first standby server 2 and runs switching script, thus possesses digital independent business, and database disaster tolerance system returns to original state.
Situation three, when detecting unit 4 detects that the second standby server 3 is abnormal, the first Floating IP address and the second Floating IP address all do not move, and are directly carried out overhauling by the second standby server 3.
Situation four, when detecting unit 4 detects that primary server 1 and the first standby server 2 are all abnormal, Floating IP address control module 5 controls the first Floating IP address and to float and the second Floating IP address floats to the second standby server 3.
In situation four, specifically comprise again two kinds of situations: one, detecting unit 4 first detects that primary server 1 is abnormal, and before primary server 1 repairs, detect again that the first standby server 2 is abnormal.Its two, detecting unit 4 line first detects that the first standby server 2 is abnormal, and before the first standby server 2 repairs, detect again that primary server 1 is abnormal.
The first situation is that example is described below.
Particularly, detecting unit 4 first detects that primary server 1 is abnormal, and Floating IP address control module 5 controls the first Floating IP address and floats on the second standby server 3, and Script controlling unit 6 controls the second standby server 3 and runs switching script to possess data write business.Now, detecting unit 4 detects that again the first standby server 2 is abnormal, and Floating IP address control module 5 controls the second Floating IP address and floats on the second standby server 3, and Script controlling unit 6 controls the second standby server 3 and runs switching script to possess digital independent business.
Now, the second standby server 3 is configured with the first Floating IP address and the second Floating IP address, and the second standby server 3 possess data write business and digital independent business.
After primary server 1 repairs, the first Floating IP address on the second standby server 3 floats on primary server 1 again; After the first standby server 2 repairs, the second Floating IP address on the first standby server 2 floats on the first standby business device again.When the second standby server 3 does not configure Floating IP address, the second standby server 3 is in idle condition again, and database disaster tolerance system returns to original state.
For the second situation, Floating IP address control module 5 first controls the second Floating IP address and floats on the second standby server 3, control the first Floating IP address again to float on the second standby server 3, detailed process can refer to the description in above-mentioned first in situation, repeats no more herein.
Situation five, when detecting unit 4 detects that primary server 1 and the second standby server 3 are all abnormal, Floating IP address control module 5 controls the first Floating IP address and floats to the first standby server 2.
In situation five, specifically comprise again two kinds of situations: one, detecting unit 4 first detects that primary server 1 is abnormal, and before primary server 1 repairs, detect again that the second standby server 3 is abnormal.Its two, detecting unit 4 line first detects that the second standby server 3 is abnormal, and before the second standby server 3 repairs, detect again that primary server 1 is abnormal.
The first situation is that example is described below.
Particularly, detecting unit 4 first detects that primary server 1 is abnormal, and Floating IP address control module 5 controls the first Floating IP address and floats on the second standby server 3, and Script controlling unit 6 controls the second standby server 3 and runs switching script to possess data write business.Now, detecting unit 4 detects that again the second standby server 3 is abnormal, Floating IP address control module 5 the first Floating IP address controlled on the second standby server 3 floats on the first standby server 2, and Script controlling unit 6 controls the first standby server 2 and runs switching script to possess data write business.
Now, the first standby server 2 is configured with the first Floating IP address and the second Floating IP address, and the first standby server 2 possess data write business and digital independent business.
After primary server 1 repairs, the first Floating IP address on the first standby server 2 floats on primary server 1 again; After the second standby server 3 repairs, directly the second standby server 3 is placed in database disaster tolerance system.Database disaster tolerance system returns to original state.
For the second situation, when detecting unit 4 detect first go out the second standby server 3 abnormal time, first Floating IP address and the second Floating IP address all motionless, now detecting unit 4 detects that again primary module is abnormal, then Floating IP address control module 5 the first Floating IP address controlled on primary server 1 floats on the first standby server 2, and detailed process no longer describes.
Situation six, when detecting unit 4 detects that the first standby server 2 and the second standby server 3 are all abnormal, Floating IP address control module 5 controls the second Floating IP address and floats to primary server 1.
In situation six, specifically comprise again two kinds of situations: one, detecting unit 4 first detects that the first standby server 2 is abnormal, and before the first standby server 2 repairs, detect again that the second standby server 3 is abnormal.Its two, detecting unit 4 line first detects that the second standby server 3 is abnormal, and before the second standby server 3 repairs, detect again that the first standby server 2 is abnormal.
Be described for the first situation below.
Particularly, detecting unit 4 first detects that the first standby server 2 is abnormal, Floating IP address control module 5 controls the second Floating IP address and floats on the second standby server 3, and Script controlling unit 6 controls the second standby server 3 and runs switching script to possess data write business.Now, detecting unit 4 detects that again the second standby server 3 is abnormal, Floating IP address control module 5 the second Floating IP address controlled on the second standby server 3 floats on primary server 1, and Script controlling unit 6 controls primary server 1 and runs switching script to possess digital independent business.
Now, primary server 1 is configured with the first Floating IP address and the second Floating IP address, primary server 1 possesses data write business and digital independent business.
After the first standby server 2 repairs, the second Floating IP address on primary server 1 floats on the first standby server 2 again; After the second standby server 3 repairs, directly the second standby server 3 is placed in database disaster tolerance system.Database disaster tolerance system returns to original state.
For the second situation, when detecting unit 4 detect first go out the second standby server 3 abnormal time, first Floating IP address and the second Floating IP address all motionless, now detecting unit 4 detects that again the first spare module is abnormal, then Floating IP address control module 5 the second Floating IP address controlled on the first standby server 2 floats on primary server 1, and detailed process no longer describes.
Situation seven, when detecting unit 4 detects that primary server 1, first standby server 2 and the second standby server 3 are all abnormal, disaster tolerance failure.Therefore, when the number of the second standby server 3 is one, the maximum quantity of the abnormal server that this database disaster tolerance system can be born is two.
It should be noted that, in this enforcement, the number of the second standby server is that the situation of is to technical scheme generation restriction of the present invention, in the present invention, the quantity of the second standby server can also be two or more, and in this database disaster tolerance system the quantity of the second standby server redundancy ability is stronger more at most, but corresponding hardware cost can be increased.
The present embodiment one provides a kind of database disaster tolerance system, this database disaster tolerance system comprises: a primary server, the first standby server, at least one second standby server, detecting unit, Floating IP address control module and a switching script, the clear in structure of this database disaster tolerance system, simple, be convenient to realize.Simultaneously, when this database disaster tolerance system is in original state, primary server is configured with the first Floating IP address, first standby server is configured with the second Floating IP address, primary server possesses data write business, first standby server possesses digital independent business, thus the load achieving database disaster tolerance system is shared.Further, whether detecting unit detects primary server, the first standby server and the second standby server in real time abnormal, when Floating IP address control module is used at least one exception when detecting in primary server, the first standby server and the second standby server, control the first Floating IP address and/or the second Floating IP address floats to destination server, thus the standby mutually disaster tolerance achieved between server, maximization ensure that in system, resource can be used, and whole disaster tolerance process is substantially without manual intervention, everything completes automatically.
Embodiment two
The process flow diagram of a kind of database disaster recovery method that Fig. 2 provides for the embodiment of the present invention two, as shown in Figure 2, this database disaster recovery method based on database disaster tolerance system, the database disaster tolerance system that this database disaster tolerance system can adopt above-described embodiment one to provide, this database disaster recovery method comprises:
Step 101: whether extremely detect primary server, the first standby server and the second standby server.
Step 101 can be performed by the detecting unit in above-described embodiment one, specifically can see the description in above-described embodiment one.
When this database disaster tolerance system is in original state, primary server is configured with the first Floating IP address, and described first standby server is configured with the second Floating IP address.
Step 102: when at least one exception detected in primary server, the first standby server and the second standby server, controls the first Floating IP address and/or the second Floating IP address floats to destination server;
Step 102 can have the Floating IP address detecting unit in above-described embodiment one to perform, specifically can see the description in above-described embodiment one.
In the present embodiment, assuming that the quantity of the second standby server is one, in a step 102, the exception of the server that Floating IP address detecting unit detects can be following several situation.
Situation one, when detecting unit detects primary server exception, the first Floating IP address that Floating IP address control module controls on primary server floats to destination server, and this destination server is the second standby server.
Situation two, when detecting unit detects that the first standby server is abnormal, the second Floating IP address that Floating IP address control module controls on the first standby server floats to destination server, and this destination server is the second standby server.
Situation three, when detecting unit detects that the second standby server is abnormal, the first Floating IP address and the second Floating IP address all do not move, and are directly carried out overhauling by the second standby server.
Situation four, when detecting unit detects that primary server and the first standby server are all abnormal, Floating IP address control module controls the first Floating IP address and to float and the second Floating IP address floats to destination server, and this destination server is the second standby server.
In situation four, specifically comprise again two kinds of situations: one, detecting unit first detects primary server exception, and before primary server repairs, detect again that the first standby server is abnormal.For this kind of situation, the first Floating IP address that Floating IP address control module first controls in primary server exception floats to the second standby server, and then the second Floating IP address controlled on the first standby server floats on the second standby server.
Its two, detecting unit line first detects that the first standby server is abnormal, and detects again primary server exception before the first standby server repairs.For this kind of situation: the second Floating IP address that Floating IP address control module first controls on the first standby server floats on the second standby server, and then the first Floating IP address controlled in primary server exception floats on the second standby server.
Situation five, when detecting unit detects that primary server and the second standby server are all abnormal, Floating IP address control module controls the first Floating IP address and floats to destination server, and destination server is the first standby server.
In situation five, specifically comprise again two kinds of situations: one, detecting unit first detects primary server exception, and before primary server repairs, detect again that the second standby server is abnormal.For this kind of situation, the first Floating IP address that Floating IP address control module first controls in primary server exception floats to the second standby server, and then the first Floating IP address controlled on the second standby server floats on the first standby server.
Its two, detecting unit line first detects that the second standby server is abnormal, and detects again primary server exception before the second standby server repairs.For this kind of situation: when detecting that the second standby server is abnormal in the ban, Floating IP address control module does not do any process, when after detect primary server exception time, the first Floating IP address that Floating IP address control module controls on primary server floats on the first standby server.
Situation six, when detecting unit detects that the first standby server and the second standby server are all abnormal, Floating IP address control module controls the first Floating IP address and to float and the second Floating IP address floats to destination server, and this destination server is primary server.
In situation six, specifically comprise again two kinds of situations: one, detecting unit first detects that the first standby server is abnormal, and before the first standby server repairs, detect again that the second standby server is abnormal.For this kind of situation, the second Floating IP address that Floating IP address control module first controls in the first standby server exception floats to the second standby server, and then the second Floating IP address controlled on the second standby server floats on primary server.
Its two, detecting unit line first detects that the second standby server is abnormal, and before the second standby server repairs, detect again that the first standby server is abnormal.For this kind of situation: when detecting that the second standby server is abnormal in the ban, Floating IP address control module does not do any process, when after detect that the first standby server is abnormal time, the second Floating IP address that Floating IP address control module controls on the first standby server floats on primary server.
Step 103: control objectives server runs and switches script, possesses corresponding service business to make destination server.
Step 103 can be performed by the Script controlling unit in above-described embodiment one, specifically can see the description in above-described embodiment one.
In step 103, when destination server configuring the first Floating IP address, if destination server runs switch script, then destination server possesses data write business; When destination server configuring the second Floating IP address, if destination server runs switch script, then destination server is for the read-only business of data; When destination server configuring the first Floating IP address and the second Floating IP address, if destination server runs switch script, then destination server possesses data write business and the read-only business of data.
The present embodiment two provides a kind of database disaster recovery method, this database disaster recovery method is based on database disaster tolerance system, this database disaster tolerance system comprises: a primary server, the first standby server, at least one second standby server, detecting unit, Floating IP address control module and a switching script, the clear in structure of this database disaster tolerance system, simple, be convenient to realize.Simultaneously, when this database disaster tolerance system is in original state, primary server is configured with the first Floating IP address, first standby server is configured with the second Floating IP address, primary server possesses data write business, first standby server possesses digital independent business, thus the load achieving database disaster tolerance system is shared.Further, whether detecting unit detects primary server, the first standby server and the second standby server in real time abnormal, when Floating IP address control module is used at least one exception when detecting in primary server, the first standby server and the second standby server, control the first Floating IP address and/or the second Floating IP address floats to destination server, thus the standby mutually disaster tolerance achieved between server, maximization ensure that in system, resource can be used, and whole disaster tolerance process is substantially without manual intervention, everything completes automatically.
Be understandable that, the illustrative embodiments that above embodiment is only used to principle of the present invention is described and adopts, but the present invention is not limited thereto.For those skilled in the art, without departing from the spirit and substance in the present invention, can make various modification and improvement, these modification and improvement are also considered as protection scope of the present invention.
Claims (14)
1. a database disaster tolerance system, is characterized in that, comprising:
Primary server, is configured with the first Floating IP address;
First standby server and at least one second standby server, wherein the first standby server is configured with the second Floating IP address;
Detecting unit, whether abnormal for detecting described primary server, described first standby server and described second standby server;
Floating IP address control module, for when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control described first Floating IP address and/or described second Floating IP address floats to destination server;
Script controlling unit, running switching script for controlling described destination server, possessing corresponding service business to make described destination server.
2. database disaster tolerance system according to claim 1, is characterized in that, the quantity of described second standby server is one.
3. database disaster tolerance system according to claim 2, it is characterized in that, described Floating IP address control module specifically for, when detecting described primary server exception, control described first Floating IP address and float to destination server, described destination server is the second standby server.
4. database disaster tolerance system according to claim 2, it is characterized in that, described Floating IP address control module specifically for, when detecting that described first standby server is abnormal, control described second Floating IP address and float to destination server, described destination server is the second standby server.
5. database disaster tolerance system according to claim 2, it is characterized in that, described Floating IP address control module specifically for, when detecting that described primary server and described first standby server are all abnormal, control described first Floating IP address float and described second Floating IP address float to destination server, described destination server is the second standby server.
6. database disaster tolerance system according to claim 2, it is characterized in that, described Floating IP address control module specifically for, when detecting that described primary server and described second standby server are all abnormal, control described first Floating IP address and float to destination server, described destination server is the first standby server.
7. database disaster tolerance system according to claim 2, it is characterized in that, described Floating IP address control module specifically for, when detecting that described first standby server and described second standby server are all abnormal, control described second Floating IP address and float to destination server, described destination server is primary server.
8. a database disaster recovery method, is characterized in that, comprising:
Whether extremely, detect described primary server, described first standby server and described second standby server, described primary server is configured with the first Floating IP address, and described first standby server is configured with the second Floating IP address;
When detect in described primary server, described first standby server and described second standby server at least one abnormal time, control described first Floating IP address and/or described second Floating IP address floats to destination server;
Control described destination server and run switching script, possess corresponding service business to make described destination server.
9. database disaster recovery method according to claim 1, is characterized in that, the quantity of described second standby server is one.
10. database disaster recovery method according to claim 9, it is characterized in that, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting described primary server exception, control described first Floating IP address and float to destination server, described destination server is the second standby server.
11. database disaster recovery methods according to claim 9, it is characterized in that, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described first standby server is abnormal, control described second Floating IP address and float to destination server, described destination server is the second standby server.
12. database disaster recovery methods according to claim 9, it is characterized in that, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described primary server and described first standby server are all abnormal, control described first Floating IP address and to float and described second Floating IP address floats to destination server, described destination server is the second standby server.
13. database disaster recovery methods according to claim 9, it is characterized in that, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described primary server and described second standby server are all abnormal, control described first Floating IP address and float to destination server, described destination server is the first standby server.
14. database disaster recovery methods according to claim 9, it is characterized in that, described when detect in described primary server, described first standby server and described second standby server at least one abnormal time, control the step that described first Floating IP address or the second Floating IP address float to destination server and comprise:
When detecting that described first standby server and described second standby server are all abnormal, control described second Floating IP address and float to destination server, described destination server is primary server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410491536.8A CN104239548B (en) | 2014-09-23 | 2014-09-23 | Database disaster tolerance system and data storage capacity disaster method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410491536.8A CN104239548B (en) | 2014-09-23 | 2014-09-23 | Database disaster tolerance system and data storage capacity disaster method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104239548A true CN104239548A (en) | 2014-12-24 |
| CN104239548B CN104239548B (en) | 2018-07-31 |
Family
ID=52227607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410491536.8A Active CN104239548B (en) | 2014-09-23 | 2014-09-23 | Database disaster tolerance system and data storage capacity disaster method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104239548B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105389213A (en) * | 2015-10-26 | 2016-03-09 | 珠海格力电器股份有限公司 | Data center system and configuration method therefor |
| CN105550065A (en) * | 2015-12-11 | 2016-05-04 | 广州华多网络科技有限公司 | Database server communication management method and device |
| CN105721223A (en) * | 2016-03-30 | 2016-06-29 | 苏州美天网络科技有限公司 | Network server system with backup service function |
| CN105871608A (en) * | 2016-03-30 | 2016-08-17 | 苏州美天网络科技有限公司 | Backup server switching system for network disaster prevention |
| CN105871522A (en) * | 2016-03-30 | 2016-08-17 | 苏州美天网络科技有限公司 | Backup service system for disaster prevention of network |
| CN106161267A (en) * | 2015-03-26 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of method and system realizing server internal network interface load balancing |
| CN107957920A (en) * | 2017-10-31 | 2018-04-24 | 清远恒成智道信息科技有限公司 | Database backup system |
| CN107977466A (en) * | 2017-12-21 | 2018-05-01 | 广东小天才科技有限公司 | A kind of database upgrade method and device |
| CN108776622A (en) * | 2018-06-06 | 2018-11-09 | 北京达佳互联信息技术有限公司 | Method of data synchronization, device, computer equipment and storage medium |
| CN110297867A (en) * | 2019-06-28 | 2019-10-01 | 浪潮云信息技术有限公司 | Data-base cluster operation method and system based on domestic CPU and distributed container cluster |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6614788B1 (en) * | 1998-03-03 | 2003-09-02 | Sun Microsystems, Inc. | Network address management |
| US20080101218A1 (en) * | 2005-06-23 | 2008-05-01 | Lei Wenyang | Method and device for implementing active/standby gateway device in a network |
| CN101557315A (en) * | 2009-05-15 | 2009-10-14 | 成都市华为赛门铁克科技有限公司 | Method, device and system for active-standby switch |
| CN102257848A (en) * | 2011-05-31 | 2011-11-23 | 华为技术有限公司 | Main and secondary apparatuses conversion method betwenn communication equipment, communication equipment and system, and request equipment of system and service |
| CN102265556A (en) * | 2011-05-31 | 2011-11-30 | 华为技术有限公司 | Conversion method between an main communicational equipment and a spare communicational equipment, the communicational equipments and a service request equipment |
| CN102265555A (en) * | 2011-05-31 | 2011-11-30 | 华为技术有限公司 | Conversion method between an main communicational equipment and a spare communicational equipment, the communicational equipments and a service request equipment |
| CN103346903A (en) * | 2013-06-20 | 2013-10-09 | 北京捷成世纪科技股份有限公司 | Dual-machine backup method and device |
-
2014
- 2014-09-23 CN CN201410491536.8A patent/CN104239548B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6614788B1 (en) * | 1998-03-03 | 2003-09-02 | Sun Microsystems, Inc. | Network address management |
| US20080101218A1 (en) * | 2005-06-23 | 2008-05-01 | Lei Wenyang | Method and device for implementing active/standby gateway device in a network |
| CN101557315A (en) * | 2009-05-15 | 2009-10-14 | 成都市华为赛门铁克科技有限公司 | Method, device and system for active-standby switch |
| CN102257848A (en) * | 2011-05-31 | 2011-11-23 | 华为技术有限公司 | Main and secondary apparatuses conversion method betwenn communication equipment, communication equipment and system, and request equipment of system and service |
| CN102265556A (en) * | 2011-05-31 | 2011-11-30 | 华为技术有限公司 | Conversion method between an main communicational equipment and a spare communicational equipment, the communicational equipments and a service request equipment |
| CN102265555A (en) * | 2011-05-31 | 2011-11-30 | 华为技术有限公司 | Conversion method between an main communicational equipment and a spare communicational equipment, the communicational equipments and a service request equipment |
| CN103346903A (en) * | 2013-06-20 | 2013-10-09 | 北京捷成世纪科技股份有限公司 | Dual-machine backup method and device |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106161267A (en) * | 2015-03-26 | 2016-11-23 | 中兴通讯股份有限公司 | A kind of method and system realizing server internal network interface load balancing |
| CN105389213A (en) * | 2015-10-26 | 2016-03-09 | 珠海格力电器股份有限公司 | Data center system and configuration method therefor |
| CN105550065A (en) * | 2015-12-11 | 2016-05-04 | 广州华多网络科技有限公司 | Database server communication management method and device |
| CN105721223A (en) * | 2016-03-30 | 2016-06-29 | 苏州美天网络科技有限公司 | Network server system with backup service function |
| CN105871608A (en) * | 2016-03-30 | 2016-08-17 | 苏州美天网络科技有限公司 | Backup server switching system for network disaster prevention |
| CN105871522A (en) * | 2016-03-30 | 2016-08-17 | 苏州美天网络科技有限公司 | Backup service system for disaster prevention of network |
| CN107957920A (en) * | 2017-10-31 | 2018-04-24 | 清远恒成智道信息科技有限公司 | Database backup system |
| CN107977466A (en) * | 2017-12-21 | 2018-05-01 | 广东小天才科技有限公司 | A kind of database upgrade method and device |
| CN108776622A (en) * | 2018-06-06 | 2018-11-09 | 北京达佳互联信息技术有限公司 | Method of data synchronization, device, computer equipment and storage medium |
| CN110297867A (en) * | 2019-06-28 | 2019-10-01 | 浪潮云信息技术有限公司 | Data-base cluster operation method and system based on domestic CPU and distributed container cluster |
| CN110297867B (en) * | 2019-06-28 | 2021-08-17 | 浪潮软件集团有限公司 | Database cluster operation method and system based on domestic CPU and distributed container cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104239548B (en) | 2018-07-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104239548A (en) | Database disaster recovery system and database disaster recovery method | |
| US9141491B2 (en) | Highly available server system based on cloud computing | |
| EP3142011B1 (en) | Anomaly recovery method for virtual machine in distributed environment | |
| US8615676B2 (en) | Providing first field data capture in a virtual input/output server (VIOS) cluster environment with cluster-aware vioses | |
| CN102355369B (en) | Virtual clustered system as well as processing method and processing device thereof | |
| US8381017B2 (en) | Automated node fencing integrated within a quorum service of a cluster infrastructure | |
| US8055933B2 (en) | Dynamic updating of failover policies for increased application availability | |
| CN104408071A (en) | Distributive database high-availability method and system based on cluster manager | |
| CN111917846A (en) | Kafka cluster switching method, device and system, electronic equipment and readable storage medium | |
| CN103152419A (en) | High availability cluster management method for cloud computing platform | |
| CN103457775B (en) | A kind of high available virtual machine pond management system of based role | |
| CN105302661A (en) | System and method for implementing virtualization management platform high availability | |
| CN101819545A (en) | Method for realizing platform migration by using virtualization technology | |
| CN103581225A (en) | Distributed system node processing task method | |
| US9208039B2 (en) | System and method for detecting server removal from a cluster to enable fast failover of storage | |
| US10826812B2 (en) | Multiple quorum witness | |
| CN107729190B (en) | IO path failover processing method and system | |
| CN105554074A (en) | NAS resource monitoring system and monitoring method based on RPC communication | |
| CN106874142B (en) | Real-time data fault-tolerant processing method and system | |
| CN102708027A (en) | Method and system for avoiding outage of communication device | |
| CN110046064B (en) | Cloud server disaster tolerance implementation method based on fault drift | |
| CN102571311B (en) | Master-slave switching communication system and master-slave switching communication method | |
| CN117370316A (en) | High availability management method and device for database, electronic equipment and storage medium | |
| CN110740066B (en) | Seat-invariant cross-machine fault migration method and system | |
| CN109286583B (en) | Method, device, equipment and storage medium for managing network ports of controller |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |