CN112256484A - Data backup method, device and system - Google Patents
Data backup method, device and system Download PDFInfo
- Publication number
- CN112256484A CN112256484A CN202011197179.6A CN202011197179A CN112256484A CN 112256484 A CN112256484 A CN 112256484A CN 202011197179 A CN202011197179 A CN 202011197179A CN 112256484 A CN112256484 A CN 112256484A
- Authority
- CN
- China
- Prior art keywords
- primary key
- key identifier
- storage component
- target
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- 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/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present specification provides a method, an apparatus and a system for data backup, the method comprising: receiving a data synchronization request sent by a standby node device, wherein the data synchronization request carries a second primary key identifier, judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the standby node device, and if so, synchronizing data information corresponding to the first primary key identifier to the standby node device. By the method, the technical problem that the service is provided due to inconsistent information synchronization of the main node and the standby node can be solved.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for data backup.
Background
High availability is used to describe the ability of a computer system to provide services continuously and without interruption. Currently, services provided by computer systems are generally accessed by different terminals through a network. If a certain computer providing service cannot provide service under the condition of hardware, network or system failure, the computer node is called as down, and if only one computer providing service exists, the failure can cause the system to completely lose continuous service capability and cannot ensure high availability. Based on the scenario, the current main-stream solution is to use a master-slave mode, which includes different forms such as one master-slave mode and one master-slave mode, and when the master node cannot provide the service, the slave node continues to provide the service to the outside, thereby ensuring high availability of the service.
The floating IP is an IP which can temporarily exist on the main node or the standby node, can float on the main node and the standby node, and only one node is provided with the floating IP at the same time.
The dual-computer hot standby is a high-availability implementation mode and adopts a master-slave mode. At present, most of mainstream application software and database software have a scheme of supporting dual-computer hot standby. Such as MySQL, Postgresql and other databases, the data synchronization between the main and standby databases can be realized by modifying the corresponding configuration, and the dual-computer hot standby is realized.
The high availability of the dual-computer hot standby is realized on the premise that the state of the standby node is up (serviceable) when the main node is down, the data of the standby node and the data of the main node can be kept consistent, and the standby node does not have problems in taking over the failed main node to provide service to the outside. If the standby node is down first, the data of the main and standby nodes can not be kept consistent, then the main node is down, the standby node is up again, and when the standby node takes over the main node to provide service to the outside, a part of the data of the main node which is not synchronized to the standby node can be lost. The standby node provides the updated data of the service to the outside at the moment, the master node cannot be informed due to the down of the master node, and if the standby node is down at the moment and the master node is up again, the updated data of the standby node is lost. Under the scene that the master node and the standby node are alternately up and down, the data consistency is difficult to guarantee.
Disclosure of Invention
The specification provides a data backup method, device and system, and by the method, the technical problem that service is provided due to inconsistent information synchronization between a main node and a standby node can be solved.
An embodiment of the present specification provides a data backup method, which is applied to a storage component, where the storage component is respectively connected to a master node device and a backup node device, and the method includes:
receiving a data synchronization request sent by the standby node equipment, wherein the data synchronization request carries a second primary key identifier;
judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the device;
and if so, synchronizing the data information corresponding to the first primary key identifier to the standby node equipment.
The embodiment shows that the standby node device can actively acquire the data information corresponding to the primary key identifier from the storage component, so that the situation that the data in the standby node device is inconsistent with the data in the primary node device can be avoided.
Optionally, the method for obtaining the primary key identifier table includes:
receiving a target primary key identifier sent by a master node device, wherein the target primary key identifier is used for identifying a task to be executed by the master node device;
and recording the acquired target primary key identification in the primary key identification table.
Through the embodiment, when the main node processes the task to be executed, the main key identifier and the data information corresponding to the task to be executed can be actively sent to the storage component, so that the data stored in the storage component is ensured to be the latest data.
Optionally, the method further includes:
receiving target data information which is sent by the main node equipment and corresponds to the target main key identification;
and correspondingly storing the target data information and the target primary key identification.
An embodiment of the present specification further provides a data backup method, where the method is applied to a master node device, where the master node device is connected to a storage component, and the method includes:
executing the target task to be executed;
synchronizing a target primary key identifier to a storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
and synchronizing data information corresponding to the target primary key identification to the storage component so that the data information is synchronized by the standby node equipment connected with the storage component.
It can be seen from the foregoing embodiments that the master node device may actively synchronize the primary key identifier of the task to be executed and the corresponding data information being processed by the master node device with the storage component, so that the standby power saving device acquires the data information from the storage component under the preset condition.
Optionally, after synchronizing the target primary key identifier to the storage component, setting data compensation timing for the target primary key identifier;
and detecting whether the target primary key identification exists in the storage component or not after the data supplement timing is overtime, and synchronizing data information corresponding to the target primary key identification to the storage component if the target primary key identification exists.
An embodiment of the present specification further provides a data backup method, where the method is applied to a standby node device, and the standby node device is connected to the storage component, where the method includes:
monitoring a second primary key identifier newly added in the storage component;
judging whether data information corresponding to the second primary key identification exists or not;
and if the data synchronization request does not exist, sending a data synchronization request to the storage component, wherein the data synchronization request carries the second primary key identifier, so that the storage component sends data information corresponding to the second primary key identifier according to the data synchronization request.
The embodiment shows that the standby node device can monitor whether the storage component has the newly added primary key identifier in real time, and if so, can acquire the data information from the storage component when the data information corresponding to the newly added primary key identifier is not stored.
Optionally, if it is determined that data information corresponding to the second primary key identifier exists, the method further includes:
and sending a deletion notification to the storage component, wherein the deletion notification carries a second primary key identifier, so that the storage component deletes the second primary key identifier after receiving the deletion notification.
An embodiment of the present specification further provides a data backup system, where the data backup system includes: the system comprises a storage component, and a main node device and a standby node device which are connected with the storage component;
the main node equipment executes a target task to be executed and synchronizes a target main key identification and data information corresponding to the target main key identification to a storage component, wherein the target main key identification is used for identifying the target task to be executed;
the standby node equipment monitors a newly added target primary key identifier in the storage component, judges whether data information corresponding to the newly added target primary key identifier exists or not, and sends a data synchronization request to the storage component if the data information does not exist, wherein the data synchronization request carries the target primary key identifier;
and the storage component receives a data synchronization request sent by the standby node equipment, and sends data information corresponding to the target primary key identification to the standby node equipment according to the target primary key identification carried in the data synchronization request.
An embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a storage component, where the storage component is respectively connected to a master node device and a backup node device, and the apparatus includes:
the receiving module is used for receiving a data synchronization request sent by the standby node equipment, wherein the data synchronization request carries a second primary key identifier;
the processing module is used for judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the processing module;
the processing module is further configured to synchronize data information corresponding to the first primary key identifier to the standby node device if it is determined that the first primary key identifier exists.
An embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a master node device, and the master node device is connected to the storage component, and the apparatus includes:
the execution module is used for executing the target task to be executed;
the processing module is used for synchronizing a target primary key identifier to the storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
the processing module is further configured to synchronize data information corresponding to the target primary key identifier with the storage component, so that the data information is synchronized by the standby node device connected to the storage component.
An embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a standby node device, and the standby node device is connected to the storage component, and the apparatus includes:
the monitoring module is used for monitoring the newly added second primary key identifier in the storage component;
the processing module is used for judging whether data information corresponding to the second primary key identification exists or not;
and the processing module is further configured to send a data synchronization request to the storage component when the data synchronization request does not exist, where the data synchronization request carries the second primary key identifier, so that the storage component sends data information corresponding to the second primary key identifier according to the data synchronization request.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.
Fig. 1 is a schematic flowchart of a data backup method according to an embodiment of the present disclosure;
fig. 2 is a schematic architecture diagram of a data backup method according to an embodiment of the present disclosure.
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 specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms object, first, second, third, etc. may be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In this specification, the storage component may be a storage-capable server (distributed server), such as a zookeeper component.
At present, in the process of storing by using a zookeeper component, a master node and a standby node write the same temporary node a in the zookeeper, the successfully written node is used as a master working node to process services, and the unsuccessfully written node is used as a standby working node to not process services. When the working node fails down, the standby working node automatically finishes ascending.
Specifically, when the main and Standby nodes are online, the temporary node A is registered in the zookeeper and the IP address of the main and Standby nodes is written in, the database of the node X which is successfully registered is switched to an Active state, the database of the node Y which is failed to register is switched to a Standby state, and after the switching is completed, the main and Standby nodes monitor the temporary node A on the zookeeper.
When a node X where an Active database is located is offline, a temporary node A on a zookeeper disappears and sends a broadcast notice to all nodes monitoring the node A (X and Y, only Y receives the broadcast message because the X is offline), in order to prevent the database from carrying out invalid Active-Standby switching (the node X is recovered immediately after being offline, and the Active-Standby switching is not needed at this time), the node Y waits for 5 seconds after receiving a broadcast event and then registers the temporary node A to the zookeeper again and writes an IP address of the node Y into the temporary node A, the database is switched to an Active state if the registration is successful, and the Standby state of the database is maintained if the registration is failed.
And after the node X is online, registering the temporary node A with the zookeeper again, and after the registration fails, switching the database to a Standby state (because the node Y successfully registers the node A in the step 2, the temporary node A already exists), so that the master-Standby exchange of the database nodes X and Y is completed.
However, when there is a scenario where the main and standby nodes alternate up/down, the backup working node fails down, incremental data of the main working node cannot be synchronously provided, the backup node cannot maintain data consistency with the main node, and when the backup node up, the main node down and the backup node up will lose the incremental data of the last main working node.
In order to solve the above technical problem, an embodiment of the present specification provides a method for backing up data, where as shown in fig. 1, the method is applied to a storage component, and the storage component is respectively connected to a primary node device and a secondary node device, and the method includes:
s101, receiving a data synchronization request sent by standby node equipment, wherein the data synchronization request carries a second primary key identifier;
s102, judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the user or not;
and S103, if the data information exists, synchronizing the data information corresponding to the first primary key identifier to the standby node equipment.
In this embodiment, the storage component may obtain a primary key identifier of a task (to-be-executed task) being processed by the primary node device and corresponding data information, and may send the corresponding data information to the standby node device when the standby node device sends a data synchronization request, so that the standby node device can synchronize to the latest data information.
In step S101, the standby node device may monitor a change condition of a primary key identifier in the storage component in real time, and when it is known that a primary key identifier is newly added in the storage component (for example, it is monitored that a second primary key identifier is newly added in the storage component), may send a data synchronization request to the storage component, and add the second primary key identifier in the data synchronization request, so that the storage component knows that data information needs to be synchronized.
In an implementation manner, since the databases between the master node device and the standby node device may communicate with each other (to implement the master-standby function), when the master node executes a target task to be executed, the generated data may be sent to the database of the standby node device through the database of the master node device, so as to implement the master-standby data synchronization function.
Before step S101 is executed, when the standby node device learns that the second primary key identifier is newly added to the storage component, it may be determined whether data information corresponding to the second component identifier exists, and if so, it indicates that the standby node device has passed through the data information corresponding to the second component identifier from the database of the primary node device.
At this time, the standby node device may choose not to send the data synchronization request to the storage component, or may choose to send a deletion notification to the storage component, where the deletion notification carries the second primary key identifier, so that the storage component deletes the second primary key identifier after receiving the deletion notification, thereby saving the storage resource of the storage component.
If the data information does not exist, the standby node equipment fails to pass through the data information from the main node equipment, and at this time, the standby node equipment can send a data synchronization request to the storage component to acquire corresponding data information, so that data synchronization is realized.
In step S102, after receiving the data synchronization request sent by the standby node device, the storage component may search, according to the second primary key identifier carried by the storage component, whether there is a matched first primary key identifier from the primary key identifier table (it is emphasized that the first primary key identifier and the second primary key identifier are only distinguished for clarity of description, when the first primary key identifier matches the second primary key identifier, it may be considered that the first primary key identifier is the same as the second primary key identifier), and if there is a data synchronization request, the storage component sends data information corresponding to the first primary key identifier to the standby node device.
In this embodiment, the primary key identifier table stored by the storage component may be generated by the storage component according to the primary key identifier transmitted by the master node device. Wherein the primary key identifier may be a take id of the message.
Specifically, as shown in fig. 2, an embodiment of the present specification further provides a data backup method, where the method is applied to a master node device, and the master node device is connected to a storage component, and the method includes:
s201, executing a target task to be executed;
s202, synchronizing a target primary key identifier to a storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
s203, synchronizing the data information corresponding to the target primary key identification to the storage component so that the data information is synchronized by the standby node equipment connected with the storage component.
After step S202 is executed, the master node device may set data compensation timing for the target primary key identifier sent to the storage component, where the data compensation time may be set to 5 seconds, 10 seconds, and the like, check whether the target primary key identifier still exists in the storage component after the data compensation time is expired, and synchronize data information corresponding to the target primary key identifier with the storage component if the target primary key identifier exists.
As described in the foregoing embodiment, a synchronization channel may exist between the databases of the master node device and the standby node device, and when the master node device processes the target task to be executed, the master node device may have already sent the data information of the target task to be executed to the standby node device.
And after the master node device sends the target primary key identifier to the storage component, the standby node device may obtain the target primary key identifier (where the target primary key identifier obtained by the standby node device is the second primary key identifier in the foregoing embodiment), at this time, after the standby node device determines that data information corresponding to the target primary key identifier already exists in the database, a deletion notification may be sent to the storage component to notify the storage component of deleting the target primary key identifier, and this step may be completed within 3 seconds (only reference time is mentioned here).
And the data compensation timing set by the master node device is greater than the 3 seconds, for example, set to 5 seconds, when the master node device checks that the target master key identifier still exists in the storage component, it may be considered that the standby node device does not send a deletion notification to the storage component (that is, the standby node device is not synchronized with the master node device), at this time, the standby node device needs to acquire the data information corresponding to the target master key identifier from the storage component, and then the master node device sends the data information corresponding to the target master key identifier to the storage component. On the contrary, if the target primary key identifier does not exist in the storage component, the standby node device is considered to have synchronized data from the primary node device, and at this time, the primary node device does not send the data information to the storage component.
In this embodiment, the primary key identifier table in the storage component is a table generated according to the target primary key identifier sent by the primary node device and according to the target primary key identifier, and each target primary key identifier in the primary key identifier table is associated with corresponding data information.
The embodiment shows that the standby node device can actively acquire the data information corresponding to the primary key identifier from the storage component, so that the situation that the data in the standby node device is inconsistent with the data in the primary node device can be avoided.
An embodiment of the present specification further provides a data backup system, where the data backup system includes: the system comprises a storage component, and a main node device and a standby node device which are connected with the storage component;
s303, the main node equipment executes a target task to be executed, and synchronizes a target main key identifier and data information corresponding to the target main key identifier to a storage component, wherein the target main key identifier is used for identifying the target task to be executed;
s304, the standby node equipment monitors a newly added target primary key identifier in the storage component, judges whether data information corresponding to the newly added target primary key identifier exists or not, and sends a data synchronization request to the storage component if the data information does not exist, wherein the data synchronization request carries the target primary key identifier;
s305, the storage component receives a data synchronization request sent by the standby node equipment, and sends data information corresponding to a target primary key identifier to the standby node equipment according to the target primary key identifier carried in the data synchronization request.
Based on the same concept as the method and system, an embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a storage component, the storage component is respectively connected to a master node device and a backup node device, and the apparatus includes:
the receiving module is used for receiving a data synchronization request sent by the standby node equipment, wherein the data synchronization request carries a second primary key identifier;
the processing module is used for judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the processing module;
the processing module is further configured to synchronize data information corresponding to the first primary key identifier to the standby node device if it is determined that the first primary key identifier exists.
An embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a master node device, and the master node device is connected to the storage component, and the apparatus includes: the execution module is used for executing the target task to be executed;
the processing module is used for synchronizing a target primary key identifier to the storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
the processing module is further configured to synchronize data information corresponding to the target primary key identifier with the storage component, so that the data information is synchronized by the standby node device connected to the storage component.
An embodiment of the present specification further provides a data backup apparatus, where the apparatus is applied to a standby node device, and the standby node device is connected to the storage component, and the apparatus includes:
the monitoring module is used for monitoring the newly added second primary key identifier in the storage component;
the processing module is used for judging whether data information corresponding to the second primary key identification exists or not;
and the processing module is further configured to send a data synchronization request to the storage component when the data synchronization request does not exist, where the data synchronization request carries the second primary key identifier, so that the storage component sends data information corresponding to the second primary key identifier according to the data synchronization request.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.
Claims (11)
1. A method for backing up data is applied to a storage component, wherein the storage component is respectively connected with a main node device and a standby node device, and the method comprises the following steps:
receiving a data synchronization request sent by the standby node equipment, wherein the data synchronization request carries a second primary key identifier;
judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the device;
and if so, synchronizing the data information corresponding to the first primary key identifier to the standby node equipment.
2. The method of claim 1, wherein obtaining the primary key identification table comprises:
receiving a target primary key identifier sent by a master node device, wherein the target primary key identifier is used for identifying a task to be executed by the master node device;
and recording the acquired target primary key identification in the primary key identification table.
3. The method of claim 2, further comprising:
receiving target data information which is sent by the main node equipment and corresponds to the target main key identification;
and correspondingly storing the target data information and the target primary key identification.
4. A method for backing up data, the method being applied to a main node device, the main node device being connected to a storage component, the method comprising:
executing the target task to be executed;
synchronizing a target primary key identifier to a storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
and synchronizing data information corresponding to the target primary key identification to the storage component so that the data information is synchronized by the standby node equipment connected with the storage component.
5. The method of claim 4, further comprising:
after synchronizing a target primary key identifier to a storage component, setting data compensation timing for the target primary key identifier;
and detecting whether the target primary key identification exists in the storage component or not after the data supplement timing is overtime, and synchronizing data information corresponding to the target primary key identification to the storage component if the target primary key identification exists.
6. A method for data backup, which is applied to a backup node device, wherein the backup node device is connected with a storage component, and the method comprises:
monitoring a second primary key identifier newly added in the storage component;
judging whether data information corresponding to the second primary key identification exists or not;
and if the data synchronization request does not exist, sending a data synchronization request to the storage component, wherein the data synchronization request carries the second primary key identifier, so that the storage component sends data information corresponding to the second primary key identifier according to the data synchronization request.
7. The method according to claim 6, wherein if it is determined that there exists data information corresponding to the second primary key identifier, the method further comprises:
and sending a deletion notification to the storage component, wherein the deletion notification carries a second primary key identifier, so that the storage component deletes the second primary key identifier after receiving the deletion notification.
8. A data backup system, characterized in that the data backup system comprises: the system comprises a storage component, and a main node device and a standby node device which are connected with the storage component;
the main node equipment executes a target task to be executed and synchronizes a target main key identification and data information corresponding to the target main key identification to a storage component, wherein the target main key identification is used for identifying the target task to be executed;
the standby node equipment monitors a newly added target primary key identifier in the storage component, judges whether data information corresponding to the newly added target primary key identifier exists or not, and sends a data synchronization request to the storage component if the data information does not exist, wherein the data synchronization request carries the target primary key identifier;
and the storage component receives a data synchronization request sent by the standby node equipment, and sends data information corresponding to the target primary key identification to the standby node equipment according to the target primary key identification carried in the data synchronization request.
9. A data backup device is characterized in that the device is applied to a storage component, the storage component is respectively connected with a main node device and a standby node device, and the device comprises:
the receiving module is used for receiving a data synchronization request sent by the standby node equipment, wherein the data synchronization request carries a second primary key identifier;
the processing module is used for judging whether a first primary key identifier matched with the second primary key identifier exists in a primary key identifier table stored by the processing module;
the processing module is further configured to synchronize data information corresponding to the first primary key identifier to the standby node device if it is determined that the first primary key identifier exists.
10. An apparatus for data backup, the apparatus being applied to a main node device, the main node device being connected to a storage component, the apparatus comprising:
the execution module is used for executing the target task to be executed;
the processing module is used for synchronizing a target primary key identifier to the storage component so that the storage component generates a primary key identifier table according to the target primary key identifier, wherein the target primary key identifier is used for identifying the target task to be executed;
the processing module is further configured to synchronize data information corresponding to the target primary key identifier with the storage component, so that the data information is synchronized by the standby node device connected to the storage component.
11. An apparatus for data backup, the apparatus being applied to a backup node device, the backup node device being connected to a storage component, the apparatus comprising:
the monitoring module is used for monitoring the newly added second primary key identifier in the storage component;
the processing module is used for judging whether data information corresponding to the second primary key identification exists or not;
and the processing module is further configured to send a data synchronization request to the storage component when the data synchronization request does not exist, where the data synchronization request carries the second primary key identifier, so that the storage component sends data information corresponding to the second primary key identifier according to the data synchronization request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011197179.6A CN112256484A (en) | 2020-10-30 | 2020-10-30 | Data backup method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011197179.6A CN112256484A (en) | 2020-10-30 | 2020-10-30 | Data backup method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112256484A true CN112256484A (en) | 2021-01-22 |
Family
ID=74268399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011197179.6A Pending CN112256484A (en) | 2020-10-30 | 2020-10-30 | Data backup method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112256484A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116909760A (en) * | 2023-09-13 | 2023-10-20 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160041859A1 (en) * | 2014-08-11 | 2016-02-11 | Sas Institute Inc. | Synchronization testing of active clustered servers |
| CN106817402A (en) * | 2016-11-29 | 2017-06-09 | 上海亿账通互联网科技有限公司 | Data cached processing method and processing device |
| CN110602168A (en) * | 2019-08-13 | 2019-12-20 | 平安科技（深圳）有限公司 | Data synchronization method and device, computer equipment and storage medium |
| CN110636128A (en) * | 2019-09-20 | 2019-12-31 | 苏州浪潮智能科技有限公司 | Data synchronization method, system, electronic equipment and storage medium |
-
2020
- 2020-10-30 CN CN202011197179.6A patent/CN112256484A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160041859A1 (en) * | 2014-08-11 | 2016-02-11 | Sas Institute Inc. | Synchronization testing of active clustered servers |
| CN106817402A (en) * | 2016-11-29 | 2017-06-09 | 上海亿账通互联网科技有限公司 | Data cached processing method and processing device |
| CN110602168A (en) * | 2019-08-13 | 2019-12-20 | 平安科技（深圳）有限公司 | Data synchronization method and device, computer equipment and storage medium |
| CN110636128A (en) * | 2019-09-20 | 2019-12-31 | 苏州浪潮智能科技有限公司 | Data synchronization method, system, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116909760A (en) * | 2023-09-13 | 2023-10-20 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
| CN116909760B (en) * | 2023-09-13 | 2023-11-28 | 中移(苏州)软件技术有限公司 | Data processing method, device, readable storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6202067B1 (en) | Method and apparatus for correct and complete transactions in a fault tolerant distributed database system | |
| US6438707B1 (en) | Fault tolerant computer system | |
| US8103635B2 (en) | Reinstatement of database system in an automatic failover configuration | |
| CN107153660B (en) | Fault detection processing method and system for distributed database system | |
| CN109005045B (en) | Main/standby service system and main node fault recovery method | |
| US20030149735A1 (en) | Network and method for coordinating high availability system services | |
| US20080052327A1 (en) | Secondary Backup Replication Technique for Clusters | |
| TWI677797B (en) | Management method, system and equipment of master and backup database | |
| CN108989391B (en) | Consistency processing method and system | |
| JPH09251404A (en) | Check point generation method | |
| WO2012071920A1 (en) | Method, system, token conreoller and memory database for implementing distribute-type main memory database system | |
| CN109144748B (en) | Server, distributed server cluster and state driving method thereof | |
| CN109324942B (en) | Double-activity processing method, device, system, equipment and storage medium for microservice | |
| CN110109772B (en) | CPU restarting method, communication equipment and readable storage medium | |
| CN114297296A (en) | Server active-standby switching system for broadcasting | |
| CN106254814B (en) | Conference recovery method, service management center and system | |
| CN109189854B (en) | Method and node equipment for providing continuous service | |
| CN111049886A (en) | Multi-region SDN controller data synchronization method, server and system | |
| CN112256484A (en) | Data backup method, device and system | |
| CN112000444B (en) | Database transaction processing method and device, storage medium and electronic equipment | |
| WO2021115043A1 (en) | Distributed database system and data disaster backup drilling method | |
| KR101430570B1 (en) | Distributed computing system and recovery method thereof | |
| CN108009045B (en) | Method and device for processing faults of main and standby databases | |
| CN112052127A (en) | Data synchronization method and device for dual-computer hot standby environment | |
| CN114301763A (en) | Distributed cluster fault processing method and system, electronic device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210122 |
|
| RJ01 | Rejection of invention patent application after publication |