CN111586099A - Cross-node data backup synchronization method and system - Google Patents
Cross-node data backup synchronization method and system Download PDFInfo
- Publication number
- CN111586099A CN111586099A CN202010253680.3A CN202010253680A CN111586099A CN 111586099 A CN111586099 A CN 111586099A CN 202010253680 A CN202010253680 A CN 202010253680A CN 111586099 A CN111586099 A CN 111586099A
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- backed
- queue
- receiving end
- 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
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000001360 synchronised effect Effects 0.000 claims abstract description 46
- 230000007246 mechanism Effects 0.000 claims description 13
- 230000000977 initiatory effect Effects 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 12
- 238000012790 confirmation Methods 0.000 claims description 9
- 238000013479 data entry Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 5
- 230000002457 bidirectional effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 238000012856 packing Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a cross-node data backup synchronization method and a cross-node data backup synchronization system, which relate to the field of data backup synchronization, and the method comprises the following steps: establishing backup synchronous links with the IP of a sending end, the IP of a receiving end and a UDP port as identifiers, wherein one backup synchronous link is used for backup synchronization of a service to be backed up; the established backup synchronous links are separated by configuring a sending end IP, a receiving end IP and a UDP port; and carrying out data backup synchronization between the sending end and the receiving end by utilizing the separated backup synchronization link. The cross-node data backup synchronization method does not distinguish the main equipment from the standby equipment, and can simultaneously backup a plurality of service data.
Description
Technical Field
The invention relates to the field of data backup synchronization, in particular to a cross-node data backup synchronization method and a cross-node data backup synchronization system.
Background
The two-layer and three-layer Protocol field LLS (Link-local Signaling) subsystem relates to management of entries such as ARP (Address Resolution Protocol) and NDP (Neighbor discovery Protocol). In the traditional networking environment, one device undertakes the access of all users, and once a fault occurs, all users are disconnected. In order to improve the network stability, a dual-computer/multi-computer redundant networking environment is deployed.
Under such circumstances, cross-device and cross-node data backup synchronization needs to be realized for the ARP/NDP and other entries. However, the industry is mainly a solution of some dual-device backup at present, and aims to solve the problem of data backup between a main device and a standby device, but the dual-device backup has the concept of the main device and the standby device, and the devices at the two ends have different statuses, and cannot both initiate a real-time backup and actively pull data to the other side.
Moreover, the current backup scheme cannot simultaneously backup data of a plurality of services, and can only backup a plurality of services one by one, which fails to meet the current requirements.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a cross-node data backup synchronization method which can simultaneously backup a plurality of service data without distinguishing a main device and a standby device.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows:
a method for synchronizing data backup across nodes comprises the following steps:
establishing backup synchronous links with the IP of a sending end, the IP of a receiving end and a UDP port as identifiers, wherein one backup synchronous link is used for backup synchronization of a service to be backed up;
the established backup synchronous links are separated by configuring a sending end IP, a receiving end IP and a UDP port;
and carrying out data backup synchronization between the sending end and the receiving end by utilizing the separated backup synchronization link.
On the basis of the technical scheme, the method also comprises the step of creating a plurality of backup channels which are identified by ID numbers and correspond to the interfaces for sending data for a backup synchronous link.
On the basis of the above technical solution, the performing data backup synchronization between the sending end and the receiving end by using the separated backup synchronization link specifically includes:
determining data to be backed up and initiating data backup according to the type of the backup;
and adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
On the basis of the above technical solution, the determining data to be backed up and initiating data backup according to the type of backup specifically includes:
when the type of backup is incremental backup, taking a newly added data table entry as data to be backed up, and initiating data backup by a sending end;
and when the type of backup is full backup, all data table entries of the sending end are used as data needing backup, and the receiving end initiates data backup based on the backup channel.
On the basis of the above technical solution, according to an interface for sending data, adding data to be backed up into a corresponding backup channel, and synchronizing the data in each backup channel from a sending end to a receiving end based on a confirmation mechanism between the sending end and the receiving end, specifically including:
adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
the sending end sends the data in the queue to be backed up to the receiving end and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
the sending end judges whether the ACK of the receiving end is received or not, and if the ACK is not received, the sending end resends the data in the queue to be confirmed; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
On the basis of the technical scheme, the method for separating the multiple backup synchronous links established by configuring the IP of the sending end, the IP of the receiving end and the UDP port specifically comprises the following steps:
the established backup synchronous links are separated by changing the configuration directions of the IP of the sending end and the IP of the receiving end and selecting different UDP ports, or selecting different IP of the receiving end and different UDP ports.
The invention aims to provide a cross-node data backup synchronization system which can simultaneously backup a plurality of service data without distinguishing a main device and a standby device.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows:
a cross-node data backup synchronization system, comprising:
the link establishing module is used for establishing a backup synchronous link with the transmitting end IP, the receiving end IP and the UDP port as identifiers, wherein one backup synchronous link is used for backing up and synchronizing a service to be backed up;
the configuration module is used for separating the established backup synchronous links by configuring the IP of the sending end, the IP of the receiving end and the UDP port;
and the data synchronization module utilizes the separated backup synchronization link to perform data backup synchronization between the sending end and the receiving end.
On the basis of the above technical solution, the link creating module is further configured to create, for a backup synchronous link, a plurality of backup tunnels identified by ID numbers and corresponding to interfaces for sending data.
On the basis of the technical scheme, the data synchronization module performs data backup synchronization between the sending end and the receiving end by using the separated backup synchronization link, and the specific process comprises the following steps:
determining data to be backed up and initiating data backup according to the type of the backup;
and adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
On the basis of the technical scheme, the data synchronization module adds the data to be backed up into the corresponding backup channel according to the interface for sending the data, synchronizes the data in each backup channel from the sending end to the receiving end based on the confirmation mechanism between the sending end and the receiving end, and the specific process comprises the following steps:
adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
the sending end sends the data in the queue to be backed up to the receiving end and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
the sending end judges whether the ACK of the receiving end is received or not, and if the ACK is not received, the sending end resends the data in the queue to be confirmed; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
Compared with the prior art, the invention has the advantages that:
the cross-node data backup synchronization method of the invention establishes a backup synchronization link based on UDP protocol, identifies a backup synchronization link by a triple (a sending end IP, a receiving end IP and a UDP port), and separates a plurality of established backup synchronization links by configuring the sending end IP, the receiving end IP and the UDP port, thereby shielding the concepts of main equipment and standby equipment, leading the equipment at two ends to be equal and simultaneously sending backup synchronization data to the opposite end. The invention is not limited to dual-computer backup and synchronization, and can be expanded to data synchronization among multiple devices. In addition, different backup synchronous links are used for different services without mutual interference, concurrence of different services is achieved, and performance is improved.
Drawings
FIG. 1 is a flowchart of a cross-node data backup synchronization method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a bidirectional backup of two devices according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating data synchronization among multiple devices according to an embodiment of the present invention;
FIG. 4 is a flow chart of incremental backup in an embodiment of the present invention;
FIG. 5 is a flowchart of full backup in an embodiment of the invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
Referring to fig. 1, an embodiment of the present invention provides a cross-node data backup synchronization method, where the method includes the following steps:
s1, establishing backup synchronous links with transmitting end IP, receiving end IP and UDP ports as identifiers, wherein one backup synchronous link is used for backup synchronization of a service to be backed up.
The backup synchronization link is created based on a User Datagram Protocol (UDP), in this embodiment, a backup synchronization link is identified by a triplet (a sending end IP, a receiving end IP, and a UDP port), and one backup synchronization link is used for backup synchronization of one type of service to be backed up.
The service to be backed up in this embodiment includes an ARP service and an ND service, where ARP is an Address Resolution Protocol (Address Resolution Protocol) used in an IPv4 Address family, and may obtain a corresponding MAC Address according to an IP Address of a network neighbor.
ND is a Neighbor Discovery and management protocol (Neighbor Discovery) used by IPv6 addresses, which functions similarly to the ARP protocol in IPv4 networks. The service to be backed up can be expanded to the backup of more table entries with the same structure according to the requirement.
Preferably, this embodiment further includes the step of creating a plurality of backup tunnels identified by ID numbers for a backup synchronization link corresponding to the interface transmitting data.
One backup synchronous link can create a plurality of backup channels, so that the multiplexing of the backup synchronous links is realized, and the expandability is provided for the identification and classification of data in the same service. The reason why the data is identified and classified is that in the backup process, it is sometimes necessary to determine which specific interface the data comes from.
And S2, separating the plurality of established backup synchronous links by configuring the IP of the sending end, the IP of the receiving end and the UDP port.
In this embodiment, the established multiple backup synchronous links may be separated by changing the configuration directions of the sending end IP and the receiving end IP and selecting different UDP ports.
Specifically, see fig. 2 for a representation:
the interfaces 1 and 2 in fig. 2 are abstracts of network devices, and are ports through which the network devices communicate with the outside world. It may be an actual physical port (rj45, optical port, etc.) or a logical virtual port (vlan subinterface, lookback port, lag port, etc.).
When the device A backs up data to the device B, the back-up synchronous link is configured to be IP _ A, IP _ B and Port _1, wherein the Port _1 is a UDP Port of the device B;
if device B needs to back up data to device a at the same time, it only needs to configure its backup synchronization link as IP _ B, IP _ a, Port _2, and Port _2 is the UDP Port of device a.
Therefore, different links can be distinguished due to different IP configuration directions and different UDP ports, different data can be backed up by different links, the links are separated, and the separation of the service and the backup direction can be realized. The concept of shielding the main device and the standby device is equivalent, the devices at the two ends are equivalent, and the backup synchronous data can be sent to the opposite end, so that the bidirectional mutual backup is realized.
In this embodiment, the established multiple backup synchronous links may be separated by selecting different receiving end IPs and different UDP ports.
Specifically, see fig. 3 for a representation:
when the device A backs up data to the device B, the back-up synchronous link is configured to be IP _ A, IP _ B and Port _1, wherein the Port _1 is a UDP Port of the device B.
If the device a needs to back up data to the device C at the same time, it only needs to configure its backup synchronous link as IP _ a, IP _ C, Port _2, and Port _2 is the UDP Port of the device C.
Similarly, if the device a needs to backup data to the device D at the same time, it only needs to configure its backup synchronous link as IP _ a, IP _ D, Port _3, and Port _3 is the UDP Port of the device D.
Therefore, the IP of the local terminal is unchanged, and different links can be distinguished when the IP of the opposite terminal is different from the UDP port, so that the technical scheme is expanded to data synchronization among a plurality of devices.
And S3, carrying out data backup synchronization between the sending end and the receiving end by utilizing the separated backup synchronization link.
Specifically, the method comprises the following steps:
s31, firstly, determining data to be backed up and initiating data backup according to the type of the backup;
and S32, adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
The validation mechanism in this embodiment is mainly implemented by the queue to be backed up and the queue to be validated.
In this embodiment, the format of the channel data packet is defined as the following table:
wherein:
and (4) version identification is carried out on the format of the message so as to be convenient for carrying out compatibility judgment on message formats of different versions in the future, and as shown in the table, the length of a version field is 2Bytes, the lengths of other fields are also shown in the table, and the following description is omitted.
msg _ len is used to identify the length of the entire message, which is typically a variable length structure that requires a length field to inform the other party that the end of the message can be identified.
msg _ type: the type of service backed up by the message is described.
backup _ id: the backup tunnel ID used by the message is described.
And the msg _ ver is a subfield version and is used for identifying version information of the msg field and processing version compatibility problems which may occur in the future.
msg _ cmd: the type of message (Request/Reply/Update/ACK/…) is described.
item _ count: the number of data table entries that the message is packed at one time is described.
SN: the message is described using a sequence number SN for finding the corresponding data item at the time of Acknowledgement (ACK).
item [ ], which represents the specific backed-up table entry data, is an array.
Although this embodiment disclosure describes and illustrates a particular channel data message format, this embodiment disclosure contemplates any suitable channel data message format.
In this embodiment, the types of backup mainly include incremental backup and full backup:
the following describes data backup synchronization during incremental backup and full backup, respectively:
referring to fig. 4, when the type of backup is incremental backup, a newly added data entry is used as data to be backed up, and the sending end initiates data backup. The incremental backup initiative is at the sending end, the sending end can send data at any time, and the receiving end is responsible for passively receiving data and receiving and processing the data.
A sending end:
s321, firstly, adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
when a new data entry is generated at a sending end, a backup channel of a backup synchronous link corresponding to the data is found according to configuration, and the backup channel is added into a queue to be backed up of the corresponding backup channel. The queue to be backed up is a linked list and follows the principle of first-in first-out.
S322, then, the sending end sends the data in the queue to be backed up to the receiving end, and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
as a better implementation manner, in this embodiment, the packing module is notified to pack and send the data of the queue to be backed up. The purpose of packing and sending is to assemble a plurality of adjacent data table items in the queue to be backed up into a UDP message, thereby avoiding one-time sending of one data table item and improving the performance. The packed message has three contents: 1. SN of the message; 2. ID number of backup channel to which message belongs; 3. the packed data payload.
And after the packaging and sending are completed, transferring the packaged data of the batch from the queue to be backed up to the queue to be confirmed of the corresponding backup channel at one time. The data table entry of the queue to be confirmed corresponds to the SN of the UDP packet sent this time, and there is only the packed data table entry in the queue.
S323, finally, the sending end judges whether an acknowledgement character ACK (Acknowledgecharacter) of the receiving end is received, and if not, the sending end resends the data in the queue to be acknowledged; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
Receiving end:
when the backup synchronous link is established, the receiving end and the transmitting end agree which UDP ports of the receiving end correspond to different backup synchronous links in advance, a UDP socket of the receiving end processes and monitors a data state all the time, and when data are received, data receiving processing is immediately carried out.
After receiving the data, the receiving end generates a corresponding ACK message according to the message SN and responds to the sending end; on the other hand, to unpack the received data and the ID number of the channel to which the data is associated, split the packed data entry of one of the data entries and store the split data entry to the corresponding module, and perform subsequent processing according to the configured channel ID number.
In this embodiment, with two queues set: the queue to be backed up, the queue to be confirmed and a sending and confirming mechanism ensure the consistency of the backup synchronous data at two ends.
Referring to fig. 5, when the type of backup is full backup, all data entries of the sending end are used as data to be backed up, and the receiving end initiates data backup based on the backup channel.
Generally, when a node is newly on-line, it needs to request all data from the opposite node, or when it needs to initiate a request for full backup.
Different from incremental backup, full backup needs to be initiated by a receiving end, an initiating instruction is a Request, and after receiving the Request instruction, an opposite end responds to a Reply and simultaneously starts a backup process.
Specifically, the initiation process is as follows:
s321', the receiving end initiates a Request (the Request is based on a backup channel and includes the ID of the backup channel), and prepares to receive data.
And S322', after receiving the Request, the sending end responds to Reply and prepares to send data. The subsequent steps are consistent with the incremental backup, namely:
s323', firstly, adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
s324', the sending end sends the data in the queue to be backed up to the receiving end, and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
s325', the sending end judges whether the ACK of the receiving end is received, if not, the data in the queue to be confirmed is sent again; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
Receiving end:
when the backup synchronous link is established, the receiving end and the transmitting end agree in advance which UDP ports of the receiving end correspond to different backup synchronous links. After receiving the Reply response, the receiving end processes the data monitoring state by the UDP socket, and immediately receives and processes the data when the data is received.
After receiving the data, the receiving end generates a corresponding ACK message according to the message SN and responds to the sending end; on the other hand, to unpack the received data and the ID number of the channel to which the data is associated, split the packed data entry of one of the data entries and store the split data entry to the corresponding module, and perform subsequent processing according to the configured channel ID number.
As can be seen from the above, in this embodiment, not only incremental backup synchronization of data but also full backup synchronization of data can be realized, that is, the cross-node data backup synchronization method in the present invention can initiate real-time backup, and can actively pull data of the other side without waiting passively, thereby well expanding the application range.
In summary, in the cross-node data backup synchronization method of the present invention, a backup synchronization link is created based on a UDP protocol, a backup synchronization link is identified by a triplet (a sending end IP, a receiving end IP, and a UDP port), and the sending end IP, the receiving end IP, and the UDP port are configured to separate multiple backup synchronization links that are created, so that the concept of a primary device and a backup device can be shielded, devices at both ends are allowed to be equal to each other, and backup synchronization data can be sent to an opposite end at the same time. The invention is not limited to dual-computer backup and synchronization, and can be expanded to data synchronization among multiple devices. In addition, different backup synchronous links are used for different services without mutual interference, concurrence of different services is achieved, and performance is improved.
The embodiment of the invention provides a cross-node data backup synchronization system, which comprises a link creation module, a configuration module and a data synchronization module.
And the link establishing module is used for establishing a backup synchronous link with the transmitting end IP, the receiving end IP and the UDP port as identifiers, wherein one backup synchronous link is used for backup synchronization of a service to be backed up.
And the configuration module is used for separating the plurality of established backup synchronous links by configuring the IP of the sending end, the IP of the receiving end and the UDP port.
And the data synchronization module utilizes the separated backup synchronization link to perform data backup synchronization between the sending end and the receiving end.
Further, the link creating module is further configured to create, for a backup synchronization link, a plurality of backup tunnels identified by ID numbers and corresponding to interfaces for sending data.
Further, the data synchronization module performs data backup synchronization between the transmitting end and the receiving end by using the separated backup synchronization link, and the specific process includes:
determining data to be backed up and initiating data backup according to the type of the backup;
and adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
Further, the data synchronization module adds the data to be backed up into the corresponding backup channel according to the interface for sending the data, and synchronizes the data in each backup channel from the sending end to the receiving end based on the confirmation mechanism between the sending end and the receiving end, and the specific process includes:
adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
the sending end sends the data in the queue to be backed up to the receiving end and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
the sending end judges whether the ACK of the receiving end is received or not, and if the ACK is not received, the sending end resends the data in the queue to be confirmed; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
Further, the configuring module separates the multiple backup synchronous links by configuring the sending end IP, the receiving end IP, and the UDP port, and specifically includes:
the established backup synchronous links are separated by changing the configuration directions of the IP of the sending end and the IP of the receiving end and selecting different UDP ports, or selecting different IP of the receiving end and different UDP ports.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A method for synchronizing data backup across nodes is characterized by comprising the following steps:
establishing backup synchronous links with the IP of a sending end, the IP of a receiving end and a UDP port as identifiers, wherein one backup synchronous link is used for backup synchronization of a service to be backed up;
the established backup synchronous links are separated by configuring a sending end IP, a receiving end IP and a UDP port;
and carrying out data backup synchronization between the sending end and the receiving end by utilizing the separated backup synchronization link.
2. A method for data backup synchronization across nodes as claimed in claim 1, further comprising the step of creating a plurality of backup tunnels for a backup synchronization link, identified by ID numbers, corresponding to interfaces sending data.
3. The method for data backup synchronization across nodes according to claim 2, wherein the performing data backup synchronization between the sending end and the receiving end by using the separated backup synchronization link specifically includes:
determining data to be backed up and initiating data backup according to the type of the backup;
and adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
4. The method for synchronizing data backup across nodes according to claim 3, wherein the determining data to be backed up and initiating data backup according to the type of backup specifically comprises:
when the type of backup is incremental backup, taking a newly added data table entry as data to be backed up, and initiating data backup by a sending end;
and when the type of backup is full backup, all data table entries of the sending end are used as data needing backup, and the receiving end initiates data backup based on the backup channel.
5. The method according to claim 3 or 4, wherein the data to be backed up is added to the corresponding backup channel according to the interface for sending the data, and the data in each backup channel is synchronized from the sending end to the receiving end based on the acknowledgement mechanism between the sending end and the receiving end, specifically comprising:
adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
the sending end sends the data in the queue to be backed up to the receiving end and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
the sending end judges whether the ACK of the receiving end is received or not, and if the ACK is not received, the sending end resends the data in the queue to be confirmed; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
6. The method for data backup synchronization across nodes according to claim 1, wherein a plurality of established backup synchronization links are separated by configuring a sending end IP, a receiving end IP and a UDP port, and specifically comprises:
the established backup synchronous links are separated by changing the configuration directions of the IP of the sending end and the IP of the receiving end and selecting different UDP ports, or selecting different IP of the receiving end and different UDP ports.
7. A cross-node data backup synchronization system, comprising:
the link establishing module is used for establishing a backup synchronous link with the transmitting end IP, the receiving end IP and the UDP port as identifiers, wherein one backup synchronous link is used for backing up and synchronizing a service to be backed up;
the configuration module is used for separating the established backup synchronous links by configuring the IP of the sending end, the IP of the receiving end and the UDP port;
and the data synchronization module utilizes the separated backup synchronization link to perform data backup synchronization between the sending end and the receiving end.
8. The system of claim 7, wherein the link creation module is further configured to create a plurality of backup tunnels for a backup synchronization link, the backup tunnels identified by an ID number and corresponding to an interface through which data is sent.
9. The system according to claim 8, wherein the data synchronization module performs data backup synchronization between the transmitting end and the receiving end by using a separated backup synchronization link, and the specific process includes:
determining data to be backed up and initiating data backup according to the type of the backup;
and adding the data to be backed up into the corresponding backup channels according to the interfaces for sending the data, and synchronizing the data in each backup channel from the sending end to the receiving end based on a confirmation mechanism between the sending end and the receiving end.
10. The system according to claim 9, wherein the data synchronization module adds data to be backed up to the corresponding backup tunnels according to interfaces for sending the data, and synchronizes the data in each backup tunnel from the sending end to the receiving end based on an acknowledgement mechanism between the sending end and the receiving end, and the specific process includes:
adding data to be backed up into a queue to be backed up of a corresponding backup channel according to an interface for sending the data;
the sending end sends the data in the queue to be backed up to the receiving end and transfers the data in the queue to be backed up to the queue to be confirmed of the backup channel;
the sending end judges whether the ACK of the receiving end is received or not, and if the ACK is not received, the sending end resends the data in the queue to be confirmed; if the data in the queue to be backed up is not received, the data in the queue to be backed up is continuously sent to a receiving end, and the data in the queue to be backed up is transferred to the queue to be backed up of the backup channel until no data exists in the queue to be backed up and the queue to be backed up, and the data in the queue to be backed up is removed, and the data in the queue to be backed up is further judged whether the data in the queue to be backed up is empty or not.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010253680.3A CN111586099B (en) | 2020-04-01 | 2020-04-01 | Cross-node data backup synchronization method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010253680.3A CN111586099B (en) | 2020-04-01 | 2020-04-01 | Cross-node data backup synchronization method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111586099A true CN111586099A (en) | 2020-08-25 |
| CN111586099B CN111586099B (en) | 2023-03-24 |
Family
ID=72126084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010253680.3A Active CN111586099B (en) | 2020-04-01 | 2020-04-01 | Cross-node data backup synchronization method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111586099B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103701843A (en) * | 2012-09-27 | 2014-04-02 | 中国移动通信集团广东有限公司 | Information synchronization data transmission method and system |
| CN103957155A (en) * | 2014-05-06 | 2014-07-30 | 华为技术有限公司 | Message transmission method and device and interconnection interface |
| WO2018036173A1 (en) * | 2016-08-23 | 2018-03-01 | 华为技术有限公司 | Network load balancing method, device and system |
| CN109656999A (en) * | 2018-10-11 | 2019-04-19 | 平安科技（深圳）有限公司 | Method of data synchronization, equipment, storage medium and the device of big data quantity |
-
2020
- 2020-04-01 CN CN202010253680.3A patent/CN111586099B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103701843A (en) * | 2012-09-27 | 2014-04-02 | 中国移动通信集团广东有限公司 | Information synchronization data transmission method and system |
| CN103957155A (en) * | 2014-05-06 | 2014-07-30 | 华为技术有限公司 | Message transmission method and device and interconnection interface |
| WO2018036173A1 (en) * | 2016-08-23 | 2018-03-01 | 华为技术有限公司 | Network load balancing method, device and system |
| CN109656999A (en) * | 2018-10-11 | 2019-04-19 | 平安科技（深圳）有限公司 | Method of data synchronization, equipment, storage medium and the device of big data quantity |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111586099B (en) | 2023-03-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111865779B (en) | A route synchronization method and cross-device link aggregation group | |
| CN111740899B (en) | ARP request message forwarding method, cross-device link aggregation group and network device | |
| CN101207604B (en) | Virtual machine system and communication processing method thereof | |
| CN102404146B (en) | Master-slave switching method, network device and DHCP server | |
| EP2458782A1 (en) | Method for multiplexing hot backup ports and network system thereof | |
| EP1892929A1 (en) | A method, an apparatus and a system for message transmission | |
| CN108173691B (en) | Cross-device aggregation method and device | |
| CN105024855A (en) | Distributed cluster management system and method | |
| CN106899507B (en) | message sending method and device | |
| CN112822085B (en) | Network deployment method and system | |
| CN110868278B (en) | Method for dual-computer redundancy of communication front-end processor of rail transit comprehensive monitoring system | |
| CN111865704A (en) | Data transmission method, system and network equipment | |
| CN106341249A (en) | Redundant port switching method and device | |
| JP6571400B2 (en) | Router device, redundancy method and redundancy program | |
| CN102447703B (en) | A kind of heat backup method and system, CGN equipment | |
| CN111586099B (en) | Cross-node data backup synchronization method and system | |
| CN104579809B (en) | The detection method and equipment of a kind of stacking splitting | |
| CN1668030B (en) | System and method for processing field frames and network equipment for multi-protocol applications in communication networks | |
| CN113497752A (en) | Message sending method, first network equipment and network system | |
| WO2023231836A1 (en) | File synchronization method, apparatus, device, and storage medium | |
| JP3506327B2 (en) | High speed/high reliability ethernet transmission method and I/F device | |
| EP3422676A1 (en) | Method and device for forwarding a data packet | |
| CN106686657B (en) | MLAG dual-homing access IP network link load balancing method | |
| CN112462647B (en) | Radio station network control system and method | |
| CN108965126B (en) | Message forwarding method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240626 Address after: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee after: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region after: China Patentee after: Wuhan Changjiang Computing Technology Co.,Ltd. Address before: 430000 No. 6, High-tech Fourth Road, Donghu High-tech Development Zone, Wuhan City, Hubei Province Patentee before: FIBERHOME TELECOMMUNICATION TECHNOLOGIES Co.,Ltd. Country or region before: China |