WO2019019607A1 - 数据备份方法、装置及系统 - Google Patents

数据备份方法、装置及系统 Download PDF

Info

Publication number
WO2019019607A1
WO2019019607A1 PCT/CN2018/075665 CN2018075665W WO2019019607A1 WO 2019019607 A1 WO2019019607 A1 WO 2019019607A1 CN 2018075665 W CN2018075665 W CN 2018075665W WO 2019019607 A1 WO2019019607 A1 WO 2019019607A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
data
backup
backup data
platform
Prior art date
Application number
PCT/CN2018/075665
Other languages
English (en)
French (fr)
Inventor
杨坤
卢忱
谢芳
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US16/634,382 priority Critical patent/US20210096962A1/en
Priority to EP18838066.1A priority patent/EP3660679B1/en
Publication of WO2019019607A1 publication Critical patent/WO2019019607A1/zh

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/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • 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
    • 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
    • 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
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • 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/1456—Hardware arrangements for backup
    • 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/1469—Backup restoration techniques
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614—Improving the reliability of storage systems
    • G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure

Definitions

  • the present disclosure relates to the field of communications, and in particular, to a data backup method, apparatus, and system.
  • the backup method in the related art is mainly performed between the active and standby nodes.
  • the backup takes place between the active and standby nodes.
  • the backup node needs to be consistent with the hardware of the primary node.
  • the backup node works normally, the backup node does not access the system.
  • the primary node performs the backup operation.
  • the backup node fails, the backup node is directly switched to the system for use; or the backup occurs between the primary device and the standby device. After the primary device fails, the primary and secondary devices are switched.
  • the backup device takes over the primary device. Work with the device.
  • the related technology almost always uses a dedicated backup node to back up the master node data.
  • This method requires more dedicated backup nodes, and these dedicated backup nodes only serve as backups when their primary nodes are working normally, and the backup nodes are not deleted. Backup data that has expired, which consumes more resources and can only be applied to important nodes in the system. Therefore, the prior art is not applicable to networks that are limited in size, cannot afford backup nodes, and have no special important nodes.
  • the present disclosure proposes a method for a network that cannot use a dedicated backup node to save node storage space by deleting invalid backup data without requiring a dedicated backup node.
  • the embodiment of the present disclosure provides a data backup method, device, and system, to at least solve the problem of wasting resources when using the backup data of the active and standby nodes in the related art.
  • a data backup method including: receiving, by a second node, backup data sent by a first node according to a first period, wherein the first node and the second node cooperate with each other a node; the second node deletes the locally saved backup data of the first node according to the request of the first node.
  • the method further includes: when the first node is offline, the second node sends the first node to the data platform. Backup data.
  • the sending, by the second node, the backup data of the first node to the data platform the second node sending a backup data recovery request message to the data platform, and receiving the feedback from the data platform After the backup data resumes accepting the message, the second node sends the backup data saved locally by the first node to the data platform.
  • the method further includes: receiving, by the second node, backup data sent by the data platform. a message; the second node deletes backup data that has been sent locally to the first node of the data platform.
  • the backup data includes: data generated by the first node from the last time the backup data is sent to the second node to the current time.
  • the backup data recovery request message includes a start time and an end time of the first node in the local backup of the collaborative node.
  • the backup data recovery acceptance message includes a start time and an end time of the data platform that the data platform wishes to restore the first node.
  • deleting, by the second node, the locally saved backup data of the first node according to the request of the first node includes: deleting, by the second node, the locally saved first according to the request of the first node Backing up data, wherein the first backup data is data that the first node has sent to the data platform;
  • the method further includes: when receiving the backup data sent by the first node, deleting, by the second node, the locally saved second backup data that exceeds the local storage capacity, until the local storage capacity is not exceeded. So far, the second backup data is determined according to the backup time.
  • the method further includes: the second node verifying the correctness of the backup data; when the backup data is correct, the The two nodes send a backup data reception confirmation message to the first node.
  • the backup data confirmation message is fed back after the data platform confirms the correctness of the received backup data.
  • the second node is a terminal or a gateway
  • the first node is a terminal or a gateway
  • another data backup method including: a first node sending backup data to a second node according to a first period, wherein the first node and the second node cooperate with each other And the first node uploads the original data of the first node to the data platform according to the second period; the first node requests the second node to delete the locally saved backup data.
  • the second period is greater than the first period.
  • the method further includes: the first node sending backup data to the third node according to the third period, wherein the first node and the third node are mutually cooperative nodes.
  • the second node and the third node when the first node is offline, send a backup data recovery request message to the data platform; in the second node and the third node One of the nodes receives the backup data recovery acceptance message sent by the data platform, and the other node receives the backup data recovery rejection message sent by the data platform; and receives the backup data to restore the node receiving the message to the data platform.
  • the backup data recovery request message includes a start time and an end time of the first node being locally backed up by the collaboration node.
  • the backup data recovery acceptance message includes a start time and an end time of the data platform that the data platform wishes to restore the first node.
  • the requesting, by the first node, the second node to delete the locally saved backup data includes: the first node requesting the second node to delete locally saved first backup data, where A backup data is data that the first node has sent to the data platform.
  • the method further includes: the first node receiving the receiving confirmation message of the original data.
  • the receiving confirmation message is sent by the data platform after verifying the correctness of the original data.
  • the second node is a terminal or a gateway
  • the first node is a terminal or a gateway
  • the third node is a terminal or a gateway.
  • a data backup apparatus which is applied to a second node, and includes: a backup module, configured to receive backup data sent by a first node according to a first period, wherein the first node And the second node is a cooperative node; the deleting module is configured to delete the locally saved backup data of the first node according to the request of the first node.
  • another data backup apparatus which is applied to a first node, and includes: a sending module, configured to send backup data to a second node according to a first period, wherein the first node And the second node is a cooperative node; the uploading module is configured to upload the original data of the first node to the data platform according to the second period; and the requesting module is configured to request the second node to delete the locally saved Describe the backup data.
  • a data backup system including: a first node and a second node, a data platform, wherein the first node and the second node are mutually cooperative nodes;
  • the first node includes: a sending module, configured to send backup data to the second node according to the first period; and the uploading module is configured to upload the original data of the first node to the data platform according to the second period; the request module is set to
  • the second node includes: a backup module, configured to receive backup data sent by the first node according to the first period; and a deleting module, configured to be according to the first
  • the request of the node deletes the backup data of the first node saved locally;
  • the data platform is configured to receive the original data uploaded by the first node.
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the data of the first node is backed up by the second node, and the backup data saved locally is deleted according to the request of the first node, which solves the problem of wasting resources when using the backup data of the active and standby nodes in the related technology, and guarantees the data.
  • storage resources are saved and resource utilization is improved.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a data backup method in accordance with an embodiment of the present disclosure
  • FIG. 3 is a flow chart of another data backup method in accordance with an embodiment of the present disclosure.
  • FIG. 4 is a structural block diagram of a data backup device according to an embodiment of the present disclosure.
  • FIG. 5 is a structural block diagram of another data backup apparatus according to an embodiment of the present disclosure.
  • FIG. 6 is a structural block diagram of a data backup system according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flowchart of a node backup data sending process according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of deleting node backup data according to an embodiment of the present disclosure.
  • FIG. 9 is a flow chart of restoring node data in an embodiment of the present disclosure.
  • FIG. 10 is a flow diagram of restoring node data when a plurality of cooperating nodes are included in an embodiment of the present disclosure.
  • FIG. 1 is a network architecture diagram of an embodiment of the present disclosure, where the network architecture includes: a data platform, a common node (node 1 - node n ), the central node.
  • This embodiment is applicable to a network in which a central node and a cooperative node relationship have been determined, and each node needs to upload related data to the data platform.
  • Each node has 0 to 2 cooperative nodes, and the cooperative nodes can monitor each other's survival status and back up the related data.
  • the central node has all the functions of a common node and has a specific function that is not available to ordinary nodes - the coordination of all nodes in the network is assigned according to the network topology.
  • FIG. 2 is a flowchart of a data backup method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps. :
  • Step S202 the second node receives the backup data that is sent by the first node according to the first period, where the first node and the second node are mutually cooperative nodes;
  • Step S204 the second node deletes the backup data of the locally saved first node according to the request of the first node.
  • the data of the first node is backed up by the second node, and the backup data saved locally is deleted according to the request of the first node, which solves the problem of wasting resources when using the backup data of the active and standby nodes in the related technology, and guarantees the data.
  • the backup data are saved and resource utilization is improved.
  • the second node of the execution entity of the foregoing step may be any node in the network, such as a gateway node, a terminal, a smart grid node, a network element, etc., but is not limited thereto.
  • FIG. 3 is a flowchart of another data backup method according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes The following steps:
  • Step S302 the first node sends backup data to the second node according to the first period, where the first node and the second node are mutually cooperative nodes;
  • Step S304 the first node uploads the original data of the first node to the data platform according to the second period.
  • the second period is greater than the first period;
  • Step S306 the first node requests the second node to delete the locally saved backup data.
  • the first node of the execution entity of the foregoing step may be any node in the network, such as a gateway node, a terminal, a smart grid node, a network element, etc., but is not limited thereto.
  • the method further includes: when the first node is offline, the second node sends the backup data of the first node to the data platform.
  • the sending, by the second node, the backup data of the first node to the data platform includes:
  • the second node sends a backup data recovery request message to the data platform.
  • the second node After receiving the backup data recovery acceptance message fed back by the data platform, the second node sends the backup data saved locally by the first node to the data platform.
  • the method further includes:
  • the second node receives the backup data acknowledgement packet sent by the data platform.
  • the backup data acknowledgement packet is sent after the data platform confirms the correctness of the received backup data.
  • the second node deletes backup data that has been sent locally to the first node of the data platform.
  • the backup data includes: data generated by the first node from the last time the backup data is sent to the second node to the current time. That is, the data generated in one time period.
  • the backup data recovery request message includes a start time and an end time of the first node in the local backup of the collaborative node.
  • the backup data recovery acceptance message includes a start time and an end time of the data platform that the data platform wants to restore the first node.
  • the deleting, by the second node, the backup data of the locally saved first node according to the request of the first node includes: deleting, by the second node, the locally saved first backup data according to the request of the first node, where the first backup data is The data that the first node has sent to the data platform.
  • the second node may delete the locally saved second backup data that exceeds the local storage capacity when receiving the backup data sent by the first node.
  • the local storage capacity is not exceeded, and the second backup data is determined according to the backup time. The earlier the time, the higher the priority.
  • the method further includes:
  • the second node verifies the correctness of the backup data.
  • the second node sends a data backup data confirmation message to the first node.
  • the specific process includes: the first node generates backup data according to the first period; the first node initiates a data backup request message to the second node; the second node sends the consent to send the backup message; the first node sends the backup data to the second node.
  • the second node verifies the correctness of the backup data sent by the first node; the second node sends a data backup data confirmation message to the first node.
  • the first node when there are multiple coordinated nodes, including the third node, the first node sends backup data to the third node according to the third period, where the first node and the third node are mutually cooperative nodes, and the data is restored.
  • the process includes:
  • the one of the second node and the third node receives the backup data recovery acceptance message sent by the data platform, and the other node receives the backup data recovery rejection message sent by the data platform.
  • the node that receives the backup data recovery acceptance message sends the backup data of the first node to the data platform, and the node that receives the backup data recovery rejection message deletes the backup data of the first node.
  • the requesting, by the first node, the second node to delete the locally saved backup data includes: the first node requesting the second node to delete locally saved first backup data, where A backup data is data that the first node has sent to the data platform.
  • the method further includes: receiving, by the first node, the acknowledgement packet of the original data, optionally The receiving confirmation message is sent by the data platform after verifying the correctness of the original data, and may also be sending and receiving an acknowledgement message after the data platform has saved the original data.
  • a data backup device and a system are provided, which are used to implement the foregoing embodiments and preferred embodiments, and are not described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 4 is a structural block diagram of a data backup apparatus according to an embodiment of the present disclosure. As shown in FIG. 4, it may be applied to a second node, where the apparatus includes:
  • the backup module 40 is configured to receive backup data that is sent by the first node according to the first period, where the first node and the second node are mutually cooperative nodes;
  • the deleting module 42 is configured to delete the backup data of the locally saved first node according to the request of the first node.
  • FIG. 5 is a structural block diagram of another data backup apparatus according to an embodiment of the present disclosure. As shown in FIG. 5, it may be applied to a first node, where the apparatus includes:
  • the sending module 50 is configured to send backup data to the second node according to the first period, where the first node and the second node are mutually cooperative nodes;
  • the uploading module 52 is configured to upload the original data of the first node to the data platform according to the second period.
  • the second period is greater than the first period;
  • the requesting module 54 is configured to request the second node to delete the locally saved backup data.
  • FIG. 6 is a structural block diagram of a data backup system according to an embodiment of the present disclosure. As shown in FIG. 6, the method includes: a first node 60, a second node 62, and a data platform 64, wherein the first node and the second node cooperate with each other. node;
  • the first node 60 includes:
  • the sending module 600 is configured to send backup data to the second node according to the first period
  • the uploading module 602 is configured to upload the original data of the first node to the data platform according to the second period.
  • the second period is greater than the first period;
  • the requesting module 604 is configured to request the second node to delete the locally saved backup data.
  • the second node 62 includes:
  • the backup module 620 is configured to receive backup data that is sent by the first node according to the first period;
  • the deleting module 622 is configured to delete the locally saved backup data of the first node according to the request of the first node;
  • the data platform 64 is configured to receive original data uploaded by the first node.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • This embodiment describes the purpose of inter-node backup, that is, when the node is abnormally offline, data loss can be reduced.
  • This embodiment describes the rules for inter-node backup.
  • This embodiment describes a rule for a node to delete its collaborative node backup, that is, its collaborative node requests the node to delete the corresponding backup after uploading data to the data platform.
  • This embodiment also describes two cases and rules for the node to restore its offline collaborative node data to the data platform, that is, there is one cooperative node or two cooperative nodes.
  • This embodiment also includes the following embodiments.
  • This embodiment provides a node data backup method, which reduces data loss when a node is abnormally offline by data backup between the coordinated nodes.
  • t Define t as the time interval for the backup process to take place when the node is working normally.
  • the time interval needs to be mutually agreed according to network conditions and self-conditions after the collaborative node selection ends, and the time interval must be more than 2 times smaller than the time interval for the node to upload data to the data platform. This time interval can be different between different pairs of cooperative nodes in the network.
  • FIG. 7 is a schematic diagram of a node backup data sending process according to an embodiment. This figure is the backup process between any pair of collaborative nodes in the network. This process needs to be performed between all the cooperative nodes in the network.
  • the node m (corresponding to the first node in the above embodiment) and the node n (corresponding to the second node in the above embodiment) are mutually cooperative nodes.
  • Step S101 Node m generates backup data
  • Step S102 Node m initiates a backup request message to node n.
  • Step S103 Node n sends a message to node m to agree to send a backup message.
  • Step S104 Node m sends backup data to node n
  • Step S105 The node n checks the correctness of the backup data sent by the node m.
  • Step S106 Node n sends a backup data confirmation message to node m.
  • the above process is only a one-way process for the node m to send backup data to the node n, and the same process node n should send the backup data to the node m so that the backup is bidirectional.
  • the backup data should contain all the data from the time when the last node m sent the backup data to the node n to the current time.
  • the backup request packet should contain the timestamp T, which is the time at which the node m generates backup data for this backup.
  • FIG. 8 is a flowchart of deleting node backup data according to an embodiment of the present disclosure, including:
  • Step S201 After completing the process of uploading data to the data platform, the node m sends a backup deletion request message to the node n.
  • Step S202 The node n deletes the corresponding backup data according to the backup deletion request.
  • Step S203 Node n sends a backup deletion confirmation message to node m.
  • the backup deletion request message should include a timestamp T, which is the time at which the node m sends data to the data platform this time.
  • Node n should delete all data in the backup before the time T according to the timestamp T.
  • the node backup data deletion method embodiment becomes: the node m and the node n are mutually cooperative nodes.
  • the node n deletes the backup data every time the node m sends the backup data, and deletes the data exceeding the capacity from the earliest time to the latest at the time.
  • FIG. 9 is a flowchart of restoring node data according to an embodiment of the present disclosure. Figure, including:
  • Step S301 Node n sends a data recovery request message to the data platform.
  • Step S302 The data platform checks the time when the node m uploads the data last time.
  • Step S303 The data platform sends a consent data recovery message to the node n.
  • Step S304 The node n searches for the backup data of the node m according to the consent data recovery message.
  • Step S305 Node n sends backup data of node m to the data platform.
  • Step S306 The data platform verifies the backup data.
  • Step S307 The data platform sends a backup data confirmation message to the node n.
  • Step S308 Node n deletes the backup data of the node m.
  • FIG. 10 is a plurality of embodiments of the present disclosure.
  • a flowchart for restoring node data when cooperating nodes including:
  • Step S401 Node n and node k both send data recovery request messages to the data platform.
  • Step S402 The data platform checks the time when the node m uploads the data last time and selects a node as a data recovery node according to the data recovery request message sent by the node n and the node k, where the node n is selected.
  • Step S403 The data platform sends a consent data recovery message to the node n, and sends a reject data recovery message to the node k.
  • Step S404 The node n searches for the backup data of the node m according to the consent data recovery message, and the node k deletes the backup data of the node m.
  • Step S405 Node n sends backup data of node m to the data platform.
  • Step S406 The data platform verifies the backup data.
  • Step S407 The data platform sends a backup data confirmation message to the node n.
  • Step S408 Node n deletes backup data of node m
  • the data recovery request message should include the start time and end time of the node m backup. It is agreed that the data recovery message should include the start time and end time of the node m backup data that the data platform wants to obtain after checking the data.
  • the rule for the data platform to select the data recovery node is that the node m backup included in the node can fill the missing node m data of the data platform, that is, the start time and the end time of the node m backup included in the data recovery request message. To judge.
  • a method for backing up and restoring a coordinated node by the embodiment when a node in the network is abnormally offline, the data loss can be minimized.
  • the node data backup method embodiment can save the node data redundantly, so that the node data recovery method embodiment can be implemented after the node is abnormally offline.
  • the node backup data deletion method embodiment can delete data that is not saved in time, and saves node storage space.
  • the node data recovery method embodiment can recover the data loss caused by the abnormal offline node.
  • the application scenarios of the embodiments include various types, such as the smart grid, by monitoring the power load, formulating a power supply plan and a price adjustment plan to ensure the safety, reliability, and economy of the power consumption.
  • the smart grid needs to minimize the data loss caused by the abnormal offline of the equipment.
  • the collected data is reported to the data platform at regular intervals.
  • the collaborative nodes need to back up data with each other, and when the collaborative node cannot be connected, the collaborative node replaces the previously collected data to the data platform to minimize data loss.
  • Embodiments of the present disclosure also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs, according to the stored program code in the storage medium, the backup data that is sent by the first node according to the first period, where the first node and the second node are mutually cooperative nodes;
  • the processor performs, according to the stored program code in the storage medium, deleting the backup data of the locally saved first node according to the request of the first node.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.
  • the present disclosure is applicable to the communication field, and solves the problem of wasting resources when using the backup data of the active and standby nodes in the related art, and saves storage resources and improves resource utilization under the premise of ensuring data backup.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种数据备份方法、装置及系统，该方法包括：第二节点接收第一节点根据第一周期发送的备份数据，其中，第一节点与第二节点互为协同节点（S202）；第二节点根据第一节点的请求删除本地保存的第一节点的备份数据（S204）。解决了相关技术中采用主备节点备份数据时浪费资源的问题，在保证数据备份的前提下，节约了存储资源，提高了资源利用率。

Description

数据备份方法、装置及系统 技术领域
本公开涉及通信领域，具体而言，涉及一种数据备份方法、装置及系统。
背景技术
相关技术中的备份方法中主要是由主备节点间进行，备份发生在主备节点之间，需要备份节点与主节点硬件一致，当主节点正常工作时，备份节点不接入系统，只需对主节点进行备份操作，当主节点故障时，直接将备份节点切换到系统中使用；或者是备份发生在主用设备及备用设备之间，主用设备故障后进行主备设备切换，备用设备接替主用设备的工作。
相关技术几乎都是使用专用的备份节点备份主节点数据，这种方式要求较多的专用备份节点，而这些专用备份节点在其主节点正常工作时只起到备份作用，且备份节点不会删除已经失效的备份数据，这消耗了较多资源，因此只能运用于系统中重要节点上。所以现有技术对规模有限、无法负担备份节点、无特殊重要节点的网络并不适用。本公开针对无法使用专用备份节点的网络提出了一种无需专用备份节点且能够通过删除无效备份数据节约节点存储空间的方法。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本公开实施例提供了一种数据备份方法、装置及系统，以至少解决相关技术中采用主备节点备份数据时浪费资源的问题。
根据本公开的一个实施例，提供了一种数据备份方法，包括：第二节点接收第一节点根据第一周期发送的备份数据，其中，所述第一节点与所述第二节点互为协同节点；所述第二节点根据所述第一节点的请求删除本地保存的所述第一节点的备份数据。
可选地，在第二节点根据第一周期对第一节点进行数据备份之后，所述方法还包括：在所述第一节点离线时，所述第二节点向数据平台发送所述第一节点的备份数据。
可选地，所述第二节点向数据平台发送所述第一节点的备份数据包括：所述第二节点向所述数据平台发送备份数据恢复请求报文；在接收到所述数据平台反馈的备份数据恢复接受报文后，所述第二节点向所述数据平台发送所述第一节点在本地保存的备份数据。
可选地，在所述第二节点向所述数据平台发送所述第一节点在本地保存的备份数据之后，所述方法还包括：所述第二节点接收所述数据平台发送的备份数据确认报文；所述第二节点删除本地已经发送给所述数据平台的所述第一节点的备份数据。
可选地，所述备份数据包括：所述第一节点从上次向所述第二节点发送备份数据起至当前时间内所生成的数据。
可选地，所述备份数据恢复请求报文中包含所述第一节点在协同节点本地备份的起始时 间和结束时间。
可选地，所述备份数据恢复接受报文中包含所述数据平台希望恢复所述第一节点的备份数据的起始时间及结束时间。
可选地，所述第二节点根据所述第一节点的请求删除本地保存的所述第一节点的备份数据包括：所述第二节点根据所述第一节点的请求删除本地保存的第一备份数据，其中，所述第一备份数据为所述第一节点已经发送给所述数据平台的数据；
可选地，所述方法还包括：所述第二节点在接收所述第一节点发送的备份数据时，删除本地保存的超出本地存储容量的第二备份数据，直到所述本地存储容量未超出为止，其中，所述第二备份数据根据备份时间确定。
可选地，在第二节点接收第一节点根据第一周期发送的备份数据之后，还包括：所述第二节点验证所述备份数据的正确性；在所述备份数据正确时，所述第二节点向第一节点发送备份数据接收确认报文。
可选地，所述备份数据确认报文是所述数据平台确认接收到的备份数据的正确性后反馈的。
可选地，所述第二节点为终端或者网关，所述第一节点为终端或者网关。
根据本公开的一个实施例，提供了另一种数据备份方法，包括：第一节点根据第一周期向第二节点发送备份数据，其中，所述第一节点与所述第二节点互为协同节点；所述第一节点根据第二周期将所述第一节点的原始数据上传到数据平台；所述第一节点请求所述第二节点删除本地保存的所述备份数据。
可选地，所述第二周期大于所述第一周期。
可选地，所述方法还包括：所述第一节点根据第三周期向第三节点发送备份数据，其中，所述第一节点与所述第三节点互为协同节点。
可选地，在所述第一节点离线时，所述第二节点和所述第三节点向所述数据平台发送备份数据恢复请求报文；所述第二节点和所述第三节点中的其中一个节点接收所述数据平台发送的备份数据恢复接受报文，另一个节点接收所述数据平台发送的备份数据恢复拒绝报文；接收所述备份数据恢复接受报文的节点向所述数据平台发送所述第一节点的备份数据，接收所述备份数据恢复拒绝报文的节点删除所述第一节点的备份数据。
可选地，所述备份数据恢复请求报文中包含所述第一节点在协同节点本地备份的起始时间和结束时间。
可选地，所述备份数据恢复接受报文中包含所述数据平台希望恢复所述第一节点的备份数据的起始时间及结束时间。
可选地，所述第一节点请求所述第二节点删除本地保存的所述备份数据包括：所述第一节点请求所述第二节点删除本地保存的第一备份数据，其中，所述第一备份数据为所述第一节点已经发送给所述数据平台的数据。
可选地，在所述第一节点请求所述第二节点删除本地保存的所述备份数据之前，所述方法还包括：所述第一节点接收所述原始数据的接收确认报文。
可选地，所述接收确认报文是所述数据平台在验证所述原始数据的正确性后发送的。
可选地，所述第二节点为终端或者网关，所述第一节点为终端或者网关。
可选地，所述第三节点为终端或者网关。
根据本公开的另一个实施例，提供了一种数据备份装置，应用在第二节点，包括：备份模块，设置为接收第一节点根据第一周期发送的备份数据，其中，所述第一节点与所述第二节点互为协同节点；删除模块，设置为根据所述第一节点的请求删除本地保存的所述第一节点的备份数据。
根据本公开的另一个实施例，提供了另一种数据备份装置，应用在第一节点，包括：发送模块，设置为根据第一周期向第二节点发送备份数据，其中，所述第一节点与所述第二节点互为协同节点；上传模块，设置为根据第二周期将所述第一节点的原始数据上传到数据平台；请求模块，设置为请求所述第二节点删除本地保存的所述备份数据。
根据本公开的又一个实施例，提供了一种数据备份系统，包括：第一节点和第二节点，数据平台，其中，所述第一节点与所述第二节点互为协同节点；所述第一节点包括：发送模块，设置为根据第一周期向第二节点发送备份数据；上传模块，设置为根据第二周期将所述第一节点的原始数据上传到数据平台；请求模块，设置为请求所述第二节点删除本地保存的所述备份数据；所述第二节点包括：备份模块，设置为接收第一节点根据第一周期发送的备份数据；删除模块，设置为根据所述第一节点的请求删除本地保存的所述第一节点的备份数据；所述数据平台，设置为接收所述第一节点上传的原始数据。
根据本公开的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
接收第一节点根据第一周期发送的备份数据，其中，所述第一节点与所述第二节点互为协同节点；
根据所述第一节点的请求删除本地保存的所述第一节点的备份数据。
通过本公开，通过第二节点备份第一节点的数据，并根据第一节点的请求删除在本地保存的备份数据，解决了相关技术中采用主备节点备份数据时浪费资源的问题，在保证数据备份的前提下，节约了存储资源，提高了资源利用率。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是本公开实施例的网络构架图；
图2是根据本公开实施例的一种数据备份方法的流程图；
图3是根据本公开实施例的另一种数据备份方法的流程图；
图4是根据本公开实施例的一种数据备份装置的结构框图；
图5是根据本公开实施例的另一种数据备份装置的结构框图；
图6是根据本公开实施例的数据备份系统的结构框图；
图7为本实施例提供的节点备份数据发送流程示意图；
图8是本公开实施例的删除节点备份数据的流程图；
图9是本公开实施例的恢复节点数据的流程图；
图10是本公开实施例包括多个协同节点时恢复节点数据的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图1所示的网络架构上，如图1所示，图1是本公开实施例的网络构架图，该网络架构包括：数据平台、普通节点(节点1-节点n)、中心节点。本实施例适用于一个中心节点及协同节点关系已经确定的网络中，每个节点均需要向数据平台上传相关数据。其中，每个节点有0～2个协同节点，协同节点间能够相互监测对方存活状态，备份对方相关数据。中心节点具有普通节点的所有功能，且拥有一项普通节点所没有的特定功能——根据网络拓扑分配网络中所有节点的协同关系。
在本实施例中提供了一种运行于上述网络架构的一种数据备份方法，图2是根据本公开实施例的一种数据备份方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，第二节点接收第一节点根据第一周期发送的备份数据，其中，第一节点与第二节点互为协同节点；
步骤S204，第二节点根据第一节点的请求删除本地保存的第一节点的备份数据。
通过上述步骤，通过第二节点备份第一节点的数据，并根据第一节点的请求删除在本地保存的备份数据，解决了相关技术中采用主备节点备份数据时浪费资源的问题，在保证数据备份的前提下，节约了存储资源，提高了资源利用率。
可选地，上述步骤的执行主体第二节点可以为网络中的任一节点，如网关节点，终端，智能电网节点，网元等，但不限于此。
在本实施例中提供了一种运行于上述网络架构的另一种数据备份方法，图3是根据本公开实施例的另一种数据备份方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，第一节点根据第一周期向第二节点发送备份数据，其中，第一节点与第二节点互为协同节点；
步骤S304，第一节点根据第二周期将第一节点的原始数据上传到数据平台，优选的，第二周期大于第一周期；
步骤S306，第一节点请求第二节点删除本地保存的备份数据。
可选地，上述步骤的执行主体第一节点可以为网络中的任一节点，如网关节点，终端，智能电网节点，网元等，但不限于此。
可选地，在第二节点根据第一周期对第一节点进行数据备份之后，方法还包括：在第一节点离线时，第二节点向数据平台发送第一节点的备份数据。
可选地，第二节点向数据平台发送第一节点的备份数据包括：
S11，第二节点向数据平台发送备份数据恢复请求报文；
S12，在接收到数据平台反馈的备份数据恢复接受报文后，第二节点向数据平台发送第一节点在本地保存的备份数据。
可选地，在第二节点向数据平台发送第一节点在本地保存的备份数据之后，方法还包括：
S21，第二节点接收数据平台发送的备份数据确认报文，可选的，备份数据确认报文是数据平台确认收到的备份数据的正确性后发送的；
S22，第二节点删除本地已经发送给数据平台的第一节点的备份数据。
可选的，备份数据包括：第一节点从上次向第二节点发送备份数据起至当前时间内所生成的数据。即一个时间周期内产生的数据。
可选的，备份数据恢复请求报文中包含第一节点在协同节点本地备份的起始时间和结束时间。
可选的，备份数据恢复接受报文中包含数据平台希望恢复第一节点的备份数据的起始时间及结束时间。
可选的，第二节点根据第一节点的请求删除本地保存的第一节点的备份数据包括：第二节点根据第一节点的请求删除本地保存的第一备份数据，其中，第一备份数据为第一节点已经发送给数据平台的数据。
作为另外一个可选的方案，可以不根据第一节点的请求来执行，包括：第二节点在接收第一节点发送的备份数据时，删除本地保存的超出本地存储容量的第二备份数据，直到本地存储容量未超出为止，其中，第二备份数据根据备份时间确定。时间越早，优先级越高。
可选的，在第二节点接收第一节点根据第一周期发送的备份数据之后，还包括：
S31，第二节点验证备份数据的正确性；
S32，在备份数据正确时，第二节点向第一节点发送数据备份数据确认报文。
具体的过程包括：第一节点根据第一周期生成备份数据；第一节点向第二节点发起数据备份请求报文；第二节点发送同意备份发送报文；第一节点向第二节点发送备份数据；第二节点验证第一节点所发送备份数据的正确性；第二节点向第一节点发送数据备份数据确认报文。
在本实施例中，在存在多个协同节点时，包括第三节点，第一节点根据第三周期向第三节点发送备份数据，其中，第一节点与第三节点互为协同节点，数据恢复的流程包括：
S41，在第一节点离线时，第二节点和第三节点向数据平台发送备份数据恢复请求报文；
S42，所述第二节点和所述第三节点中的其中一个节点接收所述数据平台发送的备份数据恢复接受报文，另一个节点接收所述数据平台发送的备份数据恢复拒绝报文；
S43，接收所述备份数据恢复接受报文的节点向所述数据平台发送所述第一节点的备份数据，接收所述备份数据恢复拒绝报文的节点删除所述第一节点的备份数据。
可选的，所述第一节点请求所述第二节点删除本地保存的所述备份数据包括：所述第一节点请求所述第二节点删除本地保存的第一备份数据，其中，所述第一备份数据为所述第一节点已经发送给所述数据平台的数据。
可选的，在所述第一节点请求所述第二节点删除本地保存的所述备份数据之前，所述方法还包括：所述第一节点接收所述原始数据的接收确认报文，可选的，所述接收确认报文是所述数据平台在验证所述原始数据的正确性后发送的，同时也可以是在数据平台已经保存完成原始数据后发送接收确认报文。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种数据备份装置、系统，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本公开实施例的一种数据备份装置的结构框图，如图4所示，可以应用在第二节点，该装置包括：
备份模块40，用于接收第一节点根据第一周期发送的备份数据，其中，第一节点与第二节点互为协同节点；
删除模块42，用于根据第一节点的请求删除本地保存的第一节点的备份数据。
图5是根据本公开实施例的另一种数据备份装置的结构框图，如图5所示，可以应用在第一节点，该装置包括：
发送模块50，用于根据第一周期向第二节点发送备份数据，其中，第一节点与第二节点互为协同节点；
上传模块52，用于根据第二周期将第一节点的原始数据上传到数据平台，优选的，第二周期大于第一周期；
请求模块54，用于请求所述第二节点删除本地保存的所述备份数据。
图6是根据本公开实施例的数据备份系统的结构框图，如图6所示，包括：第一节点60，第二节点62，数据平台64，其中，第一节点与第二节点互为协同节点；
第一节点60包括：
发送模块600，用于根据第一周期向第二节点发送备份数据；
上传模块602，用于根据第二周期将第一节点的原始数据上传到数据平台，优选的，第二周期大于第一周期；
请求模块604，用于请求所述第二节点删除本地保存的所述备份数据；
第二节点62包括：
备份模块620，用于接收第一节点根据第一周期发送的备份数据；
删除模块622，用于根据所述第一节点的请求删除本地保存的所述第一节点的备份数据；
数据平台64，用于接收第一节点上传的原始数据。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例是根据本公开的可选实施例，用于结合具体的场景和实例对本申请进行详细和补充说明：
本实施例描述了协同节点间备份的目的，即在节点异常离线时，能够减小数据损失。
本实施例描述了协同节点间备份的规则。
本实施例描述了节点删除其协同节点备份的规则，即其协同节点向数据平台上传数据后请求该节点删除相应备份。
本实施例还描述了节点向数据平台恢复其离线协同节点数据的两种情况及规则，即有一个协同节点或两个协同节点的情况。
在一个中心节点及协同节点关系已经确定的网络中，所有节点需要向数据平台上传相关数据。其中，为了减小数据平台的网络压力，节点向数据平台上传数据的时间间隔较大，如果节点因网络异常等原因离线，可能造成较多数据的丢失。首先，协同节点间以相较于节点向平台上传数据的时间间隔较小的时间间隔相互备份数据。当某节点通过监测发现其协同节点已经离线时，再由该节点向平台上传备份数据以减小数据丢失。
本实施例还包括以下实施例。
节点数据备份方法实施例
本实施例提供了一种节点数据备份方法，通过协同节点间的数据备份，在节点异常离线时，减少数据损失。
定义t为节点正常工作时进行备份流程的时间间隔。该时间间隔需要在协同节点选择结束后协同节点间根据网络条件及自身条件交互商定，该时间间隔必须较节点向数据平台上传数据的时间间隔小2倍以上。网络中不同对协同节点间该时间间隔可以不同。
请参考图7，图7为本实施例提供的节点备份数据发送流程示意图。该图为网络中任意一对协同节点间的备份流程，网络中所有协同节点间均需要进行此流程。节点m(对应于上述实施例中的第一节点)与节点n(对应于上述实施例中的第二节点)互为协同节点。
步骤S101：节点m生成备份数据
步骤S102：节点m向节点n发起备份请求报文
步骤S103：节点n向节点m发送同意备份发送报文
步骤S104：节点m向节点n发送备份数据
步骤S105：节点n校验节点m发来的备份数据的正确性
步骤S106：节点n向节点m发送备份数据确认报文
上述流程仅为节点m向节点n发送备份数据的单向流程，应有相同流程节点n向节点m发送备份数据使备份为双向。
备份数据应包含上次节点m向节点n发送备份数据时生成备份数据的时间到当前时间的所有数据。
备份请求报文中应该包含时间戳T，T为节点m本次备份生成备份数据的时间。
节点备份数据删除方法实施例
本实施例需要在节点向数据平台发送数据后执行。节点m与节点n之间需要进行的步骤参考图8，图8是本公开实施例的删除节点备份数据的流程图，包括：
步骤S201：节点m完成向数据平台上传数据流程后，向节点n发送备份删除请求报文
步骤S202：节点n根据备份删除请求删除相应备份数据
步骤S203：节点n向节点m发送备份删除确认报文
备份删除请求报文中应该包含时间戳T，T为节点m本次向数据平台发送数据的时间。
节点n应根据时间戳T删除备份中时间在T之前的所有数据。
可选的，在节点计算存储能力较弱，无法保存协同节点两次向数据平台上传的时间间隔间的所有数据时，节点备份数据删除方法实施例变为：节点m与节点n互为协同节点，节点n在每次节点m发送备份数据时进行备份数据删除，每次从时间最早向时间最晚删除超出容量的数据。
节点数据恢复方法实施例
本实施例需要在节点监测到其协同节点离线后执行。节点m只有一个协同节点n时，当节点n监测到其协同节点m离线后，节点n及数据平台之间数据恢复需要进行步骤参考图9，图9是本公开实施例的恢复节点数据的流程图，包括：
步骤S301：节点n向数据平台发送数据恢复请求报文
步骤S302：数据平台检查节点m上次上传数据的时间
步骤S303：数据平台向节点n发送同意数据恢复报文
步骤S304：节点n根据同意数据恢复报文查找节点m的备份数据
步骤S305：节点n向数据平台发送节点m的备份数据
步骤S306：数据平台校验备份数据
步骤S307：数据平台向节点n发送备份数据确认报文
步骤S308：节点n删除节点m的备份数据。
节点m拥有两个协同节点，节点n与节点k时，节点m异常离线后，节点n、节点k及数据平台之间数据恢复需要进行步骤参考图10，图10是本公开实施例包括多个协同节点时恢复节点数据的流程图，包括：
步骤S401：节点n与节点k均向数据平台发送数据恢复请求报文
步骤S402：数据平台检查节点m上次上传数据的时间并根据节点n与节点k发送的数 据恢复请求报文选择一个节点作为数据恢复节点，这里选择了节点n
步骤S403：数据平台向节点n发送同意数据恢复报文，向节点k发送了拒绝数据恢复报文
步骤S404：节点n根据同意数据恢复报文查找节点m的备份数据，节点k删除节点m的备份数据
步骤S405：节点n向数据平台发送节点m的备份数据
步骤S406：数据平台校验备份数据
步骤S407：数据平台向节点n发送备份数据确认报文
步骤S408：节点n删除节点m的备份数据
其中，数据恢复请求报文中应该包含节点m备份的起始时间及结束时间。同意数据恢复报文中应包含数据平台检查数据后希望获得的节点m备份数据的起始时间及结束时间。
数据平台选择数据恢复节点的规则为，该节点包含的节点m备份能够填补较多的数据平台缺失的节点m数据，即根据数据恢复请求报文中包含的节点m备份的起始时间及结束时间来判断。
通过本实施例的一种协同节点备份及恢复的方法。依据本备份及恢复方法，在网络中某一节点异常离线时，能最大程度的减小数据损失。通过节点数据备份方法实施例能将节点数据冗余保存，以便节点数据恢复方法实施例能在节点异常离线后实施。通过节点备份数据删除方法实施例能够及时删除无需保存的数据，节约节点存储空间。通过节点数据恢复方法实施例能够恢复异常离线节点带来的数据损失。
实施例的应用场景包括多种，如智能电网通过监测用电负荷，制订供电计划和价格调节方案，确保电力用电的安全性、可靠性和经济性。当电网中某些电力设备因为负荷过重跳闸，或因为自然/人为因素遭到破坏时，智能电网需要尽可能减小由于设备异常离线带来的数据损失。但由于目前智能电网采用中心式结构，采集的数据定时上报数据平台，当某个电力设备出现问题时，可能造成较多的数据丢失。因此需要协同节点之间相互备份数据，并且在发现协同节点无法连接时，代替协同节点将之前备份的采集数据上报数据平台，最大程度减小数据损失。
实施例4
本公开的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收第一节点根据第一周期发送的备份数据，其中，第一节点与第二节点互为协同节点；
S2，根据第一节点的请求删除本地保存的第一节点的备份数据。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行接收第一节点根 据第一周期发送的备份数据，其中，第一节点与第二节点互为协同节点；
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行根据第一节点的请求删除本地保存的第一节点的备份数据。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。
工业实用性
本公开适用于通信领域，用以解决相关技术中采用主备节点备份数据时浪费资源的问题，在保证数据备份的前提下，节约了存储资源，提高了资源利用率。

Claims (28)

  1. 一种数据备份方法，包括：
    第二节点接收第一节点根据第一周期发送的备份数据，其中，所述第一节点与所述第二节点互为协同节点；
    所述第二节点根据所述第一节点的请求删除本地保存的所述第一节点的备份数据。
  2. 根据权利要求1所述的方法，其中，在第二节点根据第一周期对第一节点进行数据备份之后，所述方法还包括：
    在所述第一节点离线时，所述第二节点向数据平台发送所述第一节点的备份数据。
  3. 根据权利要求2所述的方法，其中，所述第二节点向数据平台发送所述第一节点的备份数据包括：
    所述第二节点向所述数据平台发送备份数据恢复请求报文；
    在接收到所述数据平台反馈的备份数据恢复接受报文后，所述第二节点向所述数据平台发送所述第一节点在本地保存的备份数据。
  4. 根据权利要求3所述的方法，其中，在所述第二节点向所述数据平台发送所述第一节点在本地保存的备份数据之后，所述方法还包括：
    所述第二节点接收所述数据平台发送的备份数据确认报文；
    所述第二节点删除本地已经发送给所述数据平台的所述第一节点的备份数据。
  5. 根据权利要求1所述的方法，其中，所述备份数据包括：所述第一节点从上次向所述第二节点发送备份数据起至当前时间内所生成的数据。
  6. 根据权利要求3所述的方法，其中，所述备份数据恢复请求报文中包含所述第一节点在协同节点本地备份的起始时间和结束时间。
  7. 根据权利要求3所述的方法，其中，所述备份数据恢复接受报文中包含所述数据平台希望恢复所述第一节点的备份数据的起始时间及结束时间。
  8. 根据权利要求1所述的方法，其中，所述第二节点根据所述第一节点的请求删除本地保存的所述第一节点的备份数据包括：
    所述第二节点根据所述第一节点的请求删除本地保存的第一备份数据，其中，所述第一备份数据为所述第一节点已经发送给数据平台的数据。
  9. 根据权利要求1或8所述的方法，其中，所述方法还包括：
    所述第二节点在接收所述第一节点发送的备份数据时，删除本地保存的超出本地存储容量的第二备份数据，直到所述本地存储容量未超出为止，其中，所述第二备份数据根据备份时间确定。
  10. 根据权利要求1所述的方法，其中，在第二节点接收第一节点根据第一周期发送的备份数据之后，所述方法还包括：
    所述第二节点验证所述备份数据的正确性；
    在所述备份数据正确时，所述第二节点向第一节点发送备份数据接收确认报文。
  11. 根据权利要求4所述的方法，其中，所述备份数据确认报文是所述数据平台确认接收到的备份数据的正确性后反馈的。
  12. 根据权利要求1所述的方法，其中，所述第二节点为终端或者网关，所述第一节点为终端或者网关。
  13. 一种数据备份方法，包括：
    第一节点根据第一周期向第二节点发送备份数据，其中，所述第一节点与所述第二节点互为协同节点；
    所述第一节点根据第二周期将所述第一节点的原始数据上传到数据平台；
    所述第一节点请求所述第二节点删除本地保存的所述备份数据。
  14. 根据权利要求13所述的方法，其中，所述第二周期大于所述第一周期。
  15. 根据权利要求13所述的方法，其中，所述方法还包括：
    所述第一节点根据第三周期向第三节点发送备份数据，其中，所述第一节点与所述第三节点互为协同节点。
  16. 根据权利要求15所述的方法，其中，所述方法还包括：
    在所述第一节点离线时，所述第二节点和所述第三节点向所述数据平台发送备份数据恢复请求报文；
    所述第二节点和所述第三节点中的其中一个节点接收所述数据平台发送的备份数据恢复接受报文，另一个节点接收所述数据平台发送的备份数据恢复拒绝报文；
    接收所述备份数据恢复接受报文的节点向所述数据平台发送所述第一节点的备份数据，接收所述备份数据恢复拒绝报文的节点删除所述第一节点的备份数据。
  17. 根据权利要求16所述的方法，其中，所述备份数据恢复请求报文中包含所述第一节点在协同节点本地备份的起始时间和结束时间。
  18. 根据权利要求16所述的方法，其中，所述备份数据恢复接受报文中包含所述数据平台希望恢复所述第一节点的备份数据的起始时间及结束时间。
  19. 根据权利要求13所述的方法，其中，所述第一节点请求所述第二节点删除本地保存的所述备份数据包括：
    所述第一节点请求所述第二节点删除本地保存的第一备份数据，其中，所述第一备份数据为所述第一节点已经发送给所述数据平台的数据。
  20. 根据权利要求13所述的方法，其中，在所述第一节点请求所述第二节点删除本地保存的所述备份数据之前，所述方法还包括：
    所述第一节点接收所述原始数据的接收确认报文。
  21. 根据权利要求20所述的方法，其中，所述接收确认报文是所述数据平台在验证所述原始数据的正确性后发送的。
  22. 根据权利要求13所述的方法，其中，所述第二节点为终端或者网关，所述第一节点为终端或者网关。
  23. 根据权利要求15所述的方法，其中，所述第三节点为终端或者网关。
  24. 一种数据备份装置，应用在第二节点，包括：
    备份模块，设置为接收第一节点根据第一周期发送的备份数据，其中，所述第一节点与所述第二节点互为协同节点；
    删除模块，设置为根据所述第一节点的请求删除本地保存的所述第一节点的备份数据。
  25. 一种数据备份装置，应用在第一节点，包括：
    发送模块，设置为根据第一周期向第二节点发送备份数据，其中，所述第一节点与所述第二节点互为协同节点；
    上传模块，设置为根据第二周期将所述第一节点的原始数据上传到数据平台；
    请求模块，设置为请求所述第二节点删除本地保存的所述备份数据。
  26. 一种数据备份系统，包括：
    第一节点和第二节点，数据平台，其中，所述第一节点与所述第二节点互为协同节点；
    所述第一节点包括：
    发送模块，设置为根据第一周期向第二节点发送备份数据；
    上传模块，设置为根据第二周期将所述第一节点的原始数据上传到数据平台；
    请求模块，设置为请求所述第二节点删除本地保存的所述备份数据；
    所述第二节点包括：
    备份模块，设置为接收第一节点根据第一周期发送的备份数据；
    删除模块，设置为根据所述第一节点的请求删除本地保存的所述第一节点的备份数据；
    所述数据平台，设置为接收所述第一节点上传的原始数据。
  27. 一种存储介质，其中，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至23中任一项所述的方法。
  28. 一种处理器，其中，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至23中任一项所述的方法。
PCT/CN2018/075665 2017-07-28 2018-02-07 数据备份方法、装置及系统 WO2019019607A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/634,382 US20210096962A1 (en) 2017-07-28 2018-02-07 Data backup method, device and system
EP18838066.1A EP3660679B1 (en) 2017-07-28 2018-02-07 Data backup method, device and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710633057.9 2017-07-28
CN201710633057.9A CN109308233A (zh) 2017-07-28 2017-07-28 数据备份方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2019019607A1 true WO2019019607A1 (zh) 2019-01-31

Family

ID=65040911

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/075665 WO2019019607A1 (zh) 2017-07-28 2018-02-07 数据备份方法、装置及系统

Country Status (4)

Country Link
US (1) US20210096962A1 (zh)
EP (1) EP3660679B1 (zh)
CN (1) CN109308233A (zh)
WO (1) WO2019019607A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11132267B1 (en) * 2020-07-16 2021-09-28 EMC IP Holding Company LLC Ability to maintain RPO in clustered environment with failed nodes/disks
CN114764377A (zh) * 2020-12-30 2022-07-19 花瓣云科技有限公司 一种数据备份方法、电子设备、数据备份系统及芯片系统
CN114844774B (zh) * 2022-04-24 2023-07-14 重庆长安汽车股份有限公司 一种车载以太环网的冗余通信系统、方法及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1747347A (zh) * 2004-09-07 2006-03-15 华为技术有限公司 一种分布式配置数据库系统的备份方法
CN101599079A (zh) * 2009-07-22 2009-12-09 中国科学院计算技术研究所 一种备份数据集中存储的管理方法
CN101996108A (zh) * 2009-08-18 2011-03-30 中兴通讯股份有限公司 一种分布式环境的备份和恢复方法及其系统
CN106357811A (zh) * 2016-10-25 2017-01-25 广东欧珀移动通信有限公司 一种备份数据的删除方法、装置及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7328366B2 (en) * 2003-06-06 2008-02-05 Cascade Basic Research Corp. Method and system for reciprocal data backup
CN101207621B (zh) * 2007-11-29 2010-12-01 上海交通大学 Af-dstc协作通信协议中降低中断概率的功率分配方法
US20100131696A1 (en) * 2008-11-21 2010-05-27 Pratt Thomas L System and Method for Information Handling System Data Redundancy
CN101860418B (zh) * 2009-04-10 2013-01-16 华为技术有限公司 一种无线网络协作方法及系统、网络节点
CN105354108B (zh) * 2014-08-22 2020-01-07 中兴通讯股份有限公司 一种数据备份方法及节点
CN105760245B (zh) * 2016-02-03 2019-03-26 华为技术有限公司 一种存储数据的方法及装置
CN113505024B (zh) * 2021-07-08 2024-02-23 网易（杭州）网络有限公司 联盟链的数据处理方法、装置、电子设备及存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1747347A (zh) * 2004-09-07 2006-03-15 华为技术有限公司 一种分布式配置数据库系统的备份方法
CN101599079A (zh) * 2009-07-22 2009-12-09 中国科学院计算技术研究所 一种备份数据集中存储的管理方法
CN101996108A (zh) * 2009-08-18 2011-03-30 中兴通讯股份有限公司 一种分布式环境的备份和恢复方法及其系统
CN106357811A (zh) * 2016-10-25 2017-01-25 广东欧珀移动通信有限公司 一种备份数据的删除方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3660679A4 *

Also Published As

Publication number Publication date
EP3660679A4 (en) 2021-05-12
EP3660679A1 (en) 2020-06-03
US20210096962A1 (en) 2021-04-01
EP3660679B1 (en) 2024-03-06
CN109308233A (zh) 2019-02-05

Similar Documents

Publication Publication Date Title
Ramesh et al. A secured database monitoring method to improve data backup and recovery operations in cloud computing
CN104092718B (zh) 分布式系统及分布式系统中配置信息的更新方法
CN103744809B (zh) 基于vrrp的车辆信息管理系统双机热备方法
WO2019184285A1 (zh) 通信设备、节点的连接方法、存储介质、电子装置
CN110032478B (zh) 一种主备中心数据实时同步方法、装置、系统及存储介质
CN112291298B (zh) 异构系统的数据传输方法、装置、计算机设备和存储介质
WO2019019607A1 (zh) 数据备份方法、装置及系统
WO2019128670A1 (zh) 用于在分布式系统中使管理能力自恢复的方法和装置
WO2024103594A1 (zh) 容器容灾方法、系统、装置、设备及计算机可读存储介质
WO2017028375A1 (zh) 一种版本升级方法及系统
WO2014177085A1 (zh) 分布式多副本数据存储方法及装置
CN115277727B (zh) 一种数据灾备方法、系统、装置及存储介质
CN103428288A (zh) 基于分区状态表和协调节点的副本同步方法
CN102831038B (zh) Enum-dns的容灾方法及enum-dns
EP3031172B1 (en) Managing data feeds
CN110620798B (zh) Ftp连接的控制方法、系统、设备和存储介质
CN113821168A (zh) 一种共享存储迁移系统、方法及电子设备和存储介质
CN106027661A (zh) 数据集群存储终端
WO2015101026A1 (zh) 分布式流处理系统的容错方法、节点及系统
CN104468674B (zh) 数据迁移方法及装置
WO2019000954A1 (zh) 监测节点存活状态的方法、装置及系统
CN104391926B (zh) 一种同步数据复制方法及装置
CN109587189B (zh) 节点管理方法及装置
CN112948177A (zh) 一种容灾备份方法、装置、电子设备及存储介质
CN109947593B (zh) 数据容灾方法、系统、策略仲裁装置和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18838066

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018838066

Country of ref document: EP

Effective date: 20200228