WO2016026306A1 - 一种数据备份方法、系统、节点及计算机存储介质 - Google Patents
一种数据备份方法、系统、节点及计算机存储介质 Download PDFInfo
- Publication number
- WO2016026306A1 WO2016026306A1 PCT/CN2015/076055 CN2015076055W WO2016026306A1 WO 2016026306 A1 WO2016026306 A1 WO 2016026306A1 CN 2015076055 W CN2015076055 W CN 2015076055W WO 2016026306 A1 WO2016026306 A1 WO 2016026306A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- backup
- service node
- node
- rule
- policy
- Prior art date
Links
- 238000003860 storage Methods 0.000 title claims abstract description 179
- 238000000034 method Methods 0.000 title claims abstract description 80
- 230000008569 process Effects 0.000 claims description 28
- 238000009826 distribution Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000004590 computer program Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 238000013500 data storage Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000001172 regenerating effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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
Definitions
- the present invention relates to data storage technologies, and in particular, to a data backup method, system, node, and computer storage medium.
- a distributed storage system is a non-central distributed cluster composed of a plurality of server nodes interconnected.
- the server nodes in the cluster accept operations such as writing, reading, updating, and deleting, and are responsible for data storage.
- a complete data set is managed according to a certain partitioning rule divided into several subsets of data, and at least one copy is stored for reliability. All copies of each data subset are uniformly stored on multiple storage nodes according to a certain distribution rule, and multiple copies of the same data subset are synchronized with each other by using a master-slave method.
- data backup is a key problem that is difficult to solve, especially for regular automatic data backup according to the needs of operation and maintenance.
- high reliability and high disaster tolerance are the advantages of distributed storage systems, they still cannot cope well with some extreme situations. Therefore, for some important data in the production environment, there are still regular periods for security reasons. The need to back up your data.
- the first solution is that the client obtains server-side data in a query or traversal manner and stores it on the client.
- the disadvantage of this scheme is that data backup cannot be performed in parallel, and it is difficult to complete data backup in a limited time when the data size is large.
- the second solution is to separately export the data on each node and use centralized storage.
- the disadvantages of this technique are: first, because there is no centralized backup mechanism control, so that multiple storage sections After the copy is separately exported, it is not easy to merge multiple duplicate copy data, resulting in waste of storage resources; and, because there is no centralized backup mechanism control, all data subsets need to be backed up for each backup operation. The backup took too long.
- the embodiments of the present invention provide a data backup method, system, node, and storage medium, which can implement centralized control of the backup mechanism in the distributed storage system and shorten the time of data backup.
- An embodiment of the present invention provides a data backup method, where the method includes:
- the master collaboration service node After determining that the collaboration service node is the master control collaboration service node, the master collaboration service node obtains the backup rule
- the master cooperative service node When the backup trigger condition is met, the master cooperative service node initiates a backup operation according to the backup rule.
- the master cooperative service node initiates a backup operation according to the backup rule, including:
- the master cooperative service node generates a backup policy according to the backup rule and the data backup situation in the storage node, writes the backup policy into the distributed file lock service node, and sends the backup policy to all storage nodes. , so that all storage nodes perform backup operations according to the backup policy.
- the determining a collaboration service node as a master control collaboration service node includes: all collaboration service nodes initiating a contention control flow to the distributed file lock service node, so that the distributed file lock service node
- the collaborative service node that first completes the contention control process is determined to be a master cooperative service node, and the contention result determined by the distributed file lock service node is obtained.
- the method when the collaboration service node determines to be a non-mastered collaboration service node, And the method further includes: before the master collaboration service node sends the backup policy to all storage nodes, or all storage nodes perform a backup operation according to the backup policy, the method further includes:
- all the cooperative service nodes re-initiate a contention control flow to the distributed file lock service node, so that the distributed file lock service node will first complete the cooperation of the competition control process.
- the service node re-determines the master cooperative service node, and obtains the competition result determined by the distributed file lock service node.
- the master cooperative service node sets a timer according to the backup period in the backup rule; the satisfying the backup trigger condition includes: the timer expires, and determines that the backup trigger condition is met;
- the method further includes: the re-determined master cooperative service node acquires a backup rule, and determines whether the current time meets the preset trigger according to the backup period in the backup rule. Condition, obtain the judgment result;
- the master cooperative service node regenerates the backup policy according to the backup rule and the data backup situation in the storage node, and sends the backup policy to all Storage node
- the timer is reset according to the backup rule, and when the timer expires, according to the backup rule and the data backup in the storage node The situation regenerates the backup policy and sends the backup policy to all storage nodes.
- the method when the master cooperative service node finds that the storage node is faulty, the method further includes:
- the master cooperative service node regenerates a backup policy, and sends the regenerated backup policy to another storage node that takes over the failed storage node, so that the other storage node performs a backup operation according to the backup policy. .
- the master cooperative service node obtains a backup rule, including:
- the master cooperative service node obtains a backup rule from the distributed file lock service node;
- the master cooperative service node directly obtains a backup rule from a console operated by the user.
- the backup rule includes: a trigger period of each backup, a data set to be backed up, a backup target device, and backup attribute information.
- the data backup case includes a distribution of data subsets in the data set in the storage node, a data synchronization condition between at least one copy of the data subset, and a backup record of all data sets.
- the method further includes: the master cooperative service node acquiring backup progress of all storage nodes at a preset time interval, and writing the backup progress to the distributed file lock service node.
- the embodiment of the present invention further provides a node, where the node is a collaboration service node, and the node includes: an acquiring unit and a triggering unit;
- the obtaining unit is configured to acquire a backup rule after the collaborative service node determines to be a master service node
- the triggering unit is configured to initiate a backup operation according to the backup rule acquired by the acquiring unit when the backup triggering condition is met.
- the triggering unit is configured to generate a backup policy according to the backup rule acquired by the acquiring unit and the data backup situation in the storage node, and write the backup policy into the distributed file lock service node. And sending the backup policy to all storage nodes, so that all storage nodes perform backup operations according to the backup policy.
- the node further includes a first contention processing unit configured to initiate a contention control flow to the distributed file lock service node, such that the distributed file lock service node will first complete the contention control
- the collaborative service node of the process determines a master cooperative service node; obtains a competition result determined by the distributed file lock service node.
- the node further includes a first contention processing unit configured to: when the collaborative service node determines to be a non-master service node, and the master cooperative service node sends the backup policy to all storage nodes Or, when all the storage nodes perform the backup operation according to the backup policy, and find that the master cooperative service node fails, re-initiate a contention control right flow to the distributed file lock service node, so that the distributed file lock service
- the node re-determines the collaborative service node that first completes the contention control process to the master cooperative service node, and obtains the contention result determined by the distributed file lock service node.
- the triggering unit is configured to: when the collaborative service node determines the master cooperative service node, set a timer according to a backup period in the backup rule, and determine that the timer meets when the timer expires. Backup trigger condition;
- the triggering unit is further configured to: after the collaborative service node re-determines the master cooperative service node, obtain a backup rule, determine whether the current time meets the preset trigger condition according to the backup period in the backup rule, and obtain a determination result; And when the determining result is that the current time meets the preset triggering condition, the master cooperative service node regenerates the backup policy according to the backup rule and the data backup situation in the storage node, and sends the backup policy to all a storage node; when the determination result is that the current time does not meet the preset trigger condition, the timer is reset according to the backup rule, and when the timer expires, according to the backup rule and the storage node The data backup situation regenerates the backup policy and sends the backup policy to all storage nodes.
- the triggering unit is further configured to: when the storage node is found to be faulty, regenerate the backup policy, and send the regenerated backup policy to another storage node that takes over the failed storage node. So that the other storage node performs a backup operation according to the backup policy.
- the obtaining unit is configured to obtain a backup rule from the distributed file lock service node; or directly obtain a backup rule from a console operated by the user.
- the node further includes a first receiving unit and a first sending unit;
- the first receiving unit is configured to acquire backup progress of all storage nodes at preset time intervals
- the first sending unit is configured to send the backup progress obtained by the first receiving unit to a distributed file lock service node.
- An embodiment of the present invention further provides a data backup system, where the system includes: a collaboration service node, a distributed file lock service node, and a storage node;
- the collaboration service node is configured to determine a backup rule after the master collaboration service node is configured; and when the backup trigger condition is met, generate a backup policy according to the backup rule and the data backup situation in the storage node, a backup policy is written into the distributed file lock service node, and the backup policy is sent to all storage nodes;
- the distributed file lock service node is configured to receive a backup policy sent by the collaboration service node, and save the backup policy;
- the storage node is configured to receive a backup policy sent by the collaboration service node, and perform a backup operation according to the backup policy.
- the distributed file lock service node is further configured to receive a contention control control flow sent by all the cooperative service nodes, and determine a collaboration service node that first completes the contention control process as the primary Control the collaboration service node to send contention results to all collaboration service nodes.
- the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the data backup method according to the embodiment of the invention.
- the data backup method, the node, and the computer storage medium provided by the embodiments of the present invention obtain the backup after the collaborative service node is the master control collaboration service node. a rule; when the backup trigger condition is met, the master cooperative service node initiates a backup operation according to the backup rule.
- the centralized control of the backup mechanism in the distributed storage system is realized by the master cooperative service node, which overcomes the centralized control of the data backup in the prior art, improves the data reliability of the distributed storage system, and improves the production environment.
- the ease of use of the dimension; and the backup operation of all storage nodes is triggered by the master cooperative service node, so that all storage nodes can perform data backup in parallel, which greatly shortens the time of data backup.
- FIG. 1 is a schematic flowchart of a data backup method according to Embodiment 1 of the present invention.
- FIG. 2 is a schematic flowchart of a data backup method according to Embodiment 2 of the present invention.
- FIG. 3 is a schematic flowchart of a method for processing a fault in a data backup process according to Embodiment 3 of the present invention
- FIG. 4 is a schematic structural diagram of a data backup system according to an embodiment of the present invention.
- FIG. 5 is a schematic structural diagram of a structure of a collaboration service node according to an embodiment of the present invention.
- FIG. 1 is a schematic flowchart of a data backup method according to Embodiment 1 of the present invention. step:
- Step 101 After determining that a collaborative service node is a master cooperative service node, the master cooperative service node acquires a backup rule.
- the number of the cooperative service nodes is at least two, so that the requirements for disaster recovery after the fault, capacity expansion, and the like can be satisfied.
- the determining that a collaborative service node is a master control collaboration service node includes: all the collaboration service nodes initiate a contention control control process to the distributed file lock service node, and the first implementation is completed.
- the collaborative service node of the competition control process determines the master cooperative service node.
- all the collaboration service nodes initiate a contention control process to the distributed file lock service node
- all the collaboration service nodes create a file on the distributed file lock service node, and only one collaboration service node is created first.
- the collaborative service node that is created first is determined to be a master cooperative service node.
- the backup rule is a scheduled backup rule, and specifically includes: a trigger period of each backup, a data set to be backed up, a backup target device, and backup attribute information; wherein the backup attribute information is an incremental backup or a full backup Attribute information; specifically, the incremental backup refers to backing up all the changed data after the last backup; the full backup refers to backing up all the data.
- the master cooperative service node obtains a backup rule, including:
- the master cooperative service node obtains a backup rule from the distributed file lock service node;
- the master cooperative service node directly obtains a backup rule from a console operated by the user.
- the master cooperative service node may query whether the backup rule is stored in the distributed file lock service node, and when it is determined that the backup file is stored in the distributed file lock service node, the distributed file is Obtaining the backup rule in the lock service node; when it is determined that the backup rule is not stored in the distributed file lock service node, the backup rule may be directly obtained from the console operated by the user;
- the master cooperative service node can also obtain the backup rule directly from the console operated by the user. After the master cooperative service node obtains the backup rule directly from the console operated by the user, the backup rule is written into the backup rule. The distributed file lock service node is replaced with a backup rule stored in the distributed file lock service node.
- the console is initially connected to any one of the at least two collaboration service nodes, and after determining the master collaboration service node, the console passes through the connected
- the cooperative service node obtains an address of the master cooperative service node, and establishes a connection with the master cooperative service node according to an address of the master cooperative service node.
- the console has a human-computer interaction interface, and a user may set a backup rule on the console, and the console sends the backup rule to the master cooperative service node;
- the console can initiate a backup at any time.
- Step 102 When the backup trigger condition is met, the master cooperative service node initiates a backup operation according to the backup rule.
- the master cooperative service node initiates a backup operation according to the backup rule, including:
- the master cooperative service node generates a backup policy according to the backup rule and the data backup situation in the storage node, writes the backup policy into the distributed file lock service node, and sends the backup policy to all storage nodes. , so that all storage nodes perform backup operations according to the backup policy.
- the backup trigger condition may be: a trigger period of each backup set in the backup rule, a timer is set according to the trigger period, and when the timer expires, it is determined to be satisfied.
- the backup triggering condition may be that the backup triggering condition is directly controlled from the console operated by the user, that is, the user directly triggers the backup through the console, and the console sends a backup instruction to the master cooperative service node. When the master cooperative service node receives the backup instruction, it determines that the backup trigger condition is met.
- the data backup situation includes: a distribution of data subsets in the data set in the storage node, a data synchronization situation between at least one copy of the data subset, and a backup record of all data sets.
- the master cooperative service node generates a backup policy according to the backup rule and the data backup situation in the storage node, which specifically includes:
- the master cooperative service node sets a timer according to a trigger period of each backup, and the master cooperative service node sends the generated backup policy to the storage section when the timer expires a point, thereby triggering a backup operation; the master cooperative service node determines, according to the backup attribute information, whether the attribute to be backed up is a full backup or an incremental backup, and further according to the data set to be backed up according to the backup rule and The backup attribute information determines a data set to be backed up; the master cooperative service node determines a storage location of the backup data according to the backed up target device.
- the master cooperative service node may further determine a backup policy according to the data backup situation; for example, setting only a complete copy for data backup in the backup policy, and the incomplete copy does not participate in data backup, then the master
- the control collaboration service node identifies a complete copy in at least one copy of the same subset of data, sets a data backup from which the storage node where the copy resides, and a target device that backs up the data and the target device on the target device storage location.
- the number of the distributed file lock service nodes is at least two, so as to meet the requirements of disaster recovery after disaster, capacity expansion, and the like.
- the distributed file lock service node is mainly configured to store a backup policy, and backup rules, configuration information or other management information; and, by the distributed file lock service node, which of the at least two collaborative service nodes can be determined to collaborate
- the service node acts as the master collaboration service node.
- the method further includes:
- the re-determined master cooperative service node acquires a backup rule, and generates a backup policy according to the backup rule and the data backup situation in the storage node.
- the re-determined master cooperative service node may obtain a backup policy from the distributed file lock service node, and reset a timer according to the backup policy; and the original master cooperation If the service node recovers from failure, it is an ordinary collaborative service node.
- the master cooperative service node sets a timer according to the backup period in the backup rule; the satisfying the backup trigger condition includes: the timer expires to determine that the backup trigger condition is met;
- the method further includes: the re-determined master cooperative service node acquires a backup rule, and determines whether the current time meets the preset trigger according to the backup period in the backup rule. Condition, obtain the judgment result;
- the master cooperative service node When the judgment result is that the current time meets a preset trigger condition, the master cooperative service node immediately sends the backup policy to all storage nodes;
- the timer is reset according to the backup rule, and when the timer expires, the backup policy is sent to all storage nodes.
- the current time is a time for re-determining the master cooperative service node; whether the current time meets a preset trigger condition, including: setting a time threshold in advance, and subtracting the time threshold from the current time to obtain a time threshold a time point t′, if the time point t′ is within a time period from the current time, including a time point at which a backup should be triggered, and according to the backup record in the distributed file lock service node, the time period is not The time point of the previous backup is completed, and it is determined that the current time meets the preset trigger condition, that is, the master cooperative service node immediately sends the backup policy to all storage nodes; when the current time does not meet the above conditions, If the current time does not meet the preset trigger condition, the master cooperative service node sets a timer according to the preset trigger condition, and sends the backup policy to all storage nodes when the timer expires.
- a preset trigger condition including: setting a time threshold in advance, and subtracting the time threshold from the current
- the method when the master cooperative service node finds that the storage node is faulty, the method further includes:
- the storage node may send a backup progress to the master cooperative service node at a first time interval during the backup process, and the master control cooperation service node does not receive any of the second time interval.
- the storage node may be determined to be faulty and the fault cannot be repaired; then the master cooperative service node modifies the backup policy, and arranges other storage nodes to take over the failed storage.
- the node sends the backup progress sent by the storage node to the other storage node, so that the other storage node backs up the data that has not been backed up according to the backup progress.
- the master cooperative service node acquires backup progress of all storage nodes at preset time intervals, and writes the backup progress to the distributed file lock service node.
- the master cooperative service node acquires the backup success information of the storage node, and writes the backup success information to the distributed file lock service node.
- the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the data backup method according to the embodiment of the invention.
- FIG. 2 is a schematic flowchart of a data backup method according to Embodiment 2 of the present invention; as shown in FIG. 2, the method includes:
- Step 201 The collaboration service node A and the collaboration service node B initiate a contention control flow to the distributed file lock service node.
- Step 202 The collaborative service node A competes successfully and becomes the master cooperative service node.
- Step 203 The collaboration service node A queries whether the backup rule, the backup policy, and the backup record exist in the distributed file lock service node.
- Step 204 When there are backup rules, backup policies, and When the record is backed up, the distributed file lock service node sends the backup rule, the backup policy, and the backup record to the collaboration service node A.
- Step 205 The collaborative service node A determines whether a backup operation is currently being performed. When the result of the determination is yes, the collaborative service node A takes over the current backup operation control.
- Step 206 The collaboration service node A determines whether the backup operation is currently being performed. When the result of the determination is no, the collaboration service node A determines whether the data backup of the current period is missed; when the result of the determination is yes, the collaboration The service node A immediately initiates a backup operation; when the result of the determination is no, a timer is set for the next backup operation according to the backup rule.
- Step 207 The console connects to the collaboration service node A.
- Step 208 The user sets a backup rule on the console, and the collaboration service node A is indicated by the console.
- Step 209 The collaborative service node A writes the backup rule to the distributed file lock service node.
- Step 210 The collaboration service node A returns the write result of the backup rule to the console.
- Step 211 The collaboration service node A sets a timer according to the backup rule, and when the timer expires, triggers a backup operation to generate a backup policy.
- Step 212 The collaboration service node A writes the backup policy to the distributed file lock service node.
- Step 213 The collaboration service node A delivers the backup policy to all storage nodes.
- Step 214 All storage nodes perform a backup operation to a specified location of the target backup device according to the backup policy.
- Step 215 All storage nodes feed back the backup progress to the collaboration service node A at a preset time during the backup process.
- Step 216 The collaboration service node A records the backup progress in the distributed file lock service node.
- Step 217 The collaborative service node A writes a backup success record to the distributed file lock service node after all storage node backups are completed.
- Step 218 The collaboration service node A sets a timer for the next backup operation.
- FIG. 3 is a schematic flowchart of a method for processing a fault in the data backup process according to the third embodiment of the present invention.
- Step 301 The master cooperative service node discovers that the storage node A is disconnected, and the master cooperative service node determines that the network fault may be caused, or the storage node A fails.
- Step 302 The master cooperative service node waits for the storage node A to recover.
- Step 303 The storage node A is also waiting to re-establish the chain with the master cooperative service node.
- Step 304 The storage node A temporarily terminates the ongoing data transmission to the target backup device.
- Step 305 After the pre-configured time, the master cooperative service node finds that the connection with the storage node A is still unsuccessful, and the master cooperative service node discards the storage node A and regenerates the backup policy. The work of storage node A is handed over to storage node B to continue execution.
- Step 306 The master collaboration service node writes the regenerated backup policy into the distributed file lock service node.
- Step 307 The master collaboration service node sends the regenerated backup policy to the storage node B.
- Step 308 The storage node B takes over the storage node A, continues to perform the backup operation, and sends the data to the target backup device.
- FIG. 4 is a schematic structural diagram of a data backup system according to an embodiment of the present invention; as shown in FIG. 4, the system includes: a collaboration service node 41, and a distributed file lock service. Node 42 and storage node 43; wherein
- the collaboration service node 41 is configured to obtain a backup rule after determining the master cooperative service node; and when the backup trigger condition is met, according to the backup rule and the number of the storage node Generating a backup policy according to the backup situation, writing the backup policy to the distributed file lock service node 42, and sending the backup policy to all storage nodes 43;
- the distributed file lock service node 42 is configured to receive a backup policy sent by the collaboration service node 41, and save the backup policy.
- the storage node 43 is configured to receive a backup policy sent by the collaboration service node 41, and perform a backup operation according to the backup policy.
- the number of the cooperative service node 41, the distributed file lock service node 42 and the storage node 43 are both at least two, so as to meet the requirements of disaster recovery after disaster, capacity expansion, and the like. .
- the specific process by which the collaboration service node 41 determines the master control collaboration service node includes:
- All of the collaborative service nodes 41 initiate a contention control flow to the distributed file lock service node 42 to cause the distributed file lock service node 42 to determine the collaborative service node 41 that first completed the contention control process as the master control a collaboration service node that obtains a competition result determined by the distributed file lock service node 42;
- the distributed file lock service node 42 is further configured to receive the contention control flow sent by all the cooperation service nodes 41, and determine the cooperation service node 41 that first completes the competition control process as the master control cooperation.
- the service node sends a contention result to all of the collaboration service nodes 41.
- the collaborative service node that is created first is determined to be the master cooperative service node.
- the collaboration service node 41 is configured to obtain a backup rule from the distributed file lock service node 42; or directly obtain a backup rule from the console 44 operated by the user.
- the backup rule includes: a trigger period of each backup, a data set to be backed up, a backup target device, and backup attribute information.
- the data backup situation includes: a distribution of data subsets in the data set in the storage node, data synchronization between at least one copy of the data subset, and a backup record of all data sets.
- the backup trigger condition may be: a trigger period of each backup set in the backup rule, a timer is set according to the trigger period, and when the timer expires, it is determined to be satisfied.
- the backup triggering condition may be that the backup triggering condition is directly controlled from the console operated by the user, that is, the user directly triggers the backup through the console, and the console sends a backup instruction to the master cooperative service node. When the master cooperative service node receives the backup instruction, it determines that the backup trigger condition is met.
- the data backup situation includes: a distribution of data subsets in the data set in the storage node, a data synchronization situation between at least one copy of the data subset, and a backup record of all data sets.
- the master cooperative service node generates a backup policy according to the backup rule and the data backup situation in the storage node, which specifically includes:
- the master cooperative service node sets a timer according to a trigger period of each backup, and the master cooperative service node sends the generated backup policy to the storage node when the timer expires, thereby triggering a backup operation; Determining, according to the backup attribute information, whether the attribute to be backed up is a full backup or an incremental backup, and further determining, according to the data set to be backed up in the backup rule and the backup attribute information, a backed up data set; the master cooperative service node determines a storage location of the backup data according to the backed up target device.
- the master cooperative service node may further determine a backup policy according to the data backup situation; for example, setting only a complete copy for data backup in the backup policy, and the incomplete copy does not participate in data backup, then the master Controlling the collaboration service node in at least one of the same subset of data A complete copy is identified in the copy, and the data storage from which the storage node where the copy is located is set, and the target device that backs up the data and the storage location on the target device.
- the distributed file lock service node 42 when the backup policy is not stored in the distributed file lock service node 42, the distributed file lock service node 42 receives and saves the backup policy sent by the collaboration service node 41 as the master cooperative service node.
- the distributed file lock service node 42 receives the backup policy and replaces the backup policy stored by itself.
- the collaboration service node 41 is further configured to determine that the non-master cooperative service node is before the master cooperative service node sends the backup policy to all storage nodes, or During the backup operation performed by the storage node according to the backup policy, when the master cooperative service node is found to be faulty, the contention control right flow is re-initiated to the distributed file lock service node, so that the distributed file lock service node will The collaborative service node that first completes the contention control process re-determines the master cooperative service node, and obtains the competition result determined by the distributed file lock service node.
- the collaboration service node 41 is further configured to determine whether the current time meets the preset trigger condition after the main control cooperation service node is re-determined, and obtain a determination result; when the determination result is that the current time meets the preset When the condition is triggered, the backup policy is regenerated according to the backup rule and the data backup situation in the storage node, and the backup policy is sent to all the storage nodes 43; when the determination result is that the current time does not meet the preset trigger condition And setting a timer according to the preset trigger condition, when the timer expires, regenerating a backup policy according to the backup rule and the data backup condition in the storage node, and sending the backup policy to all storage nodes 43.
- the collaboration service node 41 is further configured to: after determining that the storage node is faulty, regenerate the backup policy, and send the regenerated backup policy to Replacing the other storage nodes of the storage node that have failed so that the other storage nodes perform a backup operation according to the backup policy.
- the storage node 43 is further configured to send a backup progress to the collaboration service node 41 as a master collaboration service node at a preset time interval during a backup operation;
- the collaboration service node 41 which is the master collaboration service node, is further configured to receive the backup progress acquired by the storage node 43 at preset time intervals, and write the backup progress to the distributed file lock service node 42.
- FIG. 5 is a schematic structural diagram of a cooperative service node according to an embodiment of the present invention.
- the collaborative service node includes: an acquiring unit 411 and trigger unit 412; wherein
- the obtaining unit 411 is configured to acquire a backup rule after the collaborative service node determines to be a master service node;
- the triggering unit 412 is configured to initiate a backup operation according to the backup rule acquired by the acquiring unit when the backup triggering condition is met.
- the triggering unit 412 is configured to generate a backup policy according to the backup rule acquired by the obtaining unit 411 and the data backup situation in the storage node, and write the backup policy into the distributed file lock service node, and The backup policy is sent to all storage nodes, so that all storage nodes perform backup operations according to the backup policy.
- the node further includes a first contention processing unit 413 configured to initiate a contention control flow to the distributed file lock service node, so that the distributed file lock service node will first complete the contention control
- the collaborative service node of the process determines a master cooperative service node; obtains a competition result determined by the distributed file lock service node.
- the node further includes a first contention processing unit 413 configured to: when the collaborative service node determines to be a non-master service node, and the master cooperative service node sends the backup policy to all storage nodes Before, or when all storage nodes perform a backup operation according to the backup policy, when the master cooperative service node fails, it is re-distributed
- the file lock service node initiates a contention control right process, so that the distributed file lock service node re-determines the cooperation service node that first completes the contention control process to the master control cooperation service node, and obtains the distributed file lock service node. Determine the outcome of the competition.
- the triggering unit 412 is configured to: when the collaborative service node determines the master cooperative service node, set a timer according to the backup period in the backup rule, and determine that the backup trigger condition is met when the timer expires. ;
- the triggering unit 412 is further configured to: after the collaborative service node re-determines the master cooperative service node, obtain a backup rule, determine, according to the backup period in the backup rule, whether the current time meets a preset trigger condition, and obtain a determination result.
- the master cooperative service node regenerates the backup policy according to the backup rule and the data backup situation in the storage node, and sends the backup policy to All the storage nodes;
- the timer is reset according to the backup rule, and when the timer expires, according to the backup rule and the storage node
- the data backup situation in the process regenerates the backup policy and sends the backup policy to all storage nodes.
- the triggering unit 412 is further configured to: when the storage node is found to be faulty, regenerate the backup policy, and send the regenerated backup policy to another storage that takes over the failed storage node. a node, so that the other storage node performs a backup operation according to the backup policy.
- the obtaining unit 411 is configured to obtain a backup rule from the distributed file lock service node; or directly obtain a backup rule from a console operated by the user.
- the node further includes a first receiving unit 415 and a first sending unit 414; wherein
- the first receiving unit 415 is configured to acquire backup progress of all storage nodes at preset time intervals
- the first sending unit 414 is further configured to: the obtained by the first receiving unit 415 The backup progress is sent to the distributed file lock service node.
- the acquiring unit 411 and the triggering unit 412 in the cooperative service node may be used by a central processing unit (CPU) and a digital signal processor (DSP) in the cooperative service node. (Digital Signal Processor) or a Field-Programmable Gate Array (FPGA) implementation;
- the first transmitting unit 414 of the cooperative service node may be used by a transmitter in the cooperative service node or Transmitting an antenna implementation;
- the first contention processing unit 413 of the cooperative service node may be implemented by a CPU, a DSP, or an FPGA in the cooperative service node in combination with a transceiver or a transceiver antenna;
- the first receiving unit 415 can be implemented by a receiver or a receiving antenna in the cooperative service node in an actual application.
- embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
- the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
- the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
- These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
- the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
- the embodiment of the invention realizes the centralized control of the backup mechanism in the distributed storage system by the master cooperative service node, overcomes the centralized control of the data backup in the prior art, improves the data reliability of the distributed storage system, and the production The ease of use of environmental operation and maintenance; and the backup operation of all storage nodes is triggered by the master cooperative service node, so that all storage nodes can perform data backup in parallel, which greatly shortens the time of data backup.
Abstract
本发明实施例公开了一种数据备份方法、系统、节点及计算机存储介质；其中，所述数据备份方法包括：确定一协作服务节点为主控协作服务节点后，所述主控协作服务节点获取备份规则；在满足备份触发条件时，所述主控协作服务节点依据所述备份规则发起备份操作。
Description
本发明涉及数据存储技术，具体涉及一种数据备份方法、系统、节点及计算机存储介质。
分布式存储系统是由若干服务器节点互相连接构成的无中心的分布式集群，集群中的服务器节点接受写入、读取、更新、删除等操作，并负责数据的存储。在分布式存储系统中，完整的数据集是根据一定的分区规则划分为若干个数据子集来管理的，并且出于可靠性需要会存储至少一个副本。各数据子集的所有副本，会根据一定的分布规则均匀地存放在多个存储节点上，同一个数据子集的多副本间采用主从(Master-Slave)方式互相进行数据同步。
在分布式存储系统中，数据备份是比较难以解决的关键问题，尤其是根据运维的需要进行定期的自动数据备份。虽然高可靠、高容灾性是分布式存储系统的优势，但仍然无法很好的应对某些极端的情况，因此对于生产环境中某些重要的数据来说，出于安全考虑，仍然有定期对数据进行备份的需要。
现有技术中，分布式系统的数据备份通常采用两种方式：
第一种方案是客户端以查询或遍历的方式获得服务器端的数据并存储在客户端。这种方案的缺点在于数据备份不能并行实行，在数据规模较大时很难在有限的时间完成数据备份。
第二种方案是将各个节点上的数据分别导出，并采用集中存储。这种技术的缺点在于：首先，由于没有集中的备份机制控制，使得多个存储节
点上分别将副本导出后不易将多个重复的副本数据进行合并，导致存储资源浪费；并且，由于没有集中的备份机制的控制，使得每次备份操作时需将全部的数据子集进行备份，导致备份的时间过长。
发明内容
为解决现有存在的技术问题，本发明实施例提供一种数据备份方法、系统、节点及存储介质，能够实现分布式存储系统中备份机制的集中控制，且缩短数据备份的时间。
为达到上述目的，本发明实施例的技术方案是这样实现的：
本发明实施例提供了一种数据备份方法，所述方法包括：
确定一协作服务节点为主控协作服务节点后，所述主控协作服务节点获取备份规则；
在满足备份触发条件时，所述主控协作服务节点依据所述备份规则发起备份操作。
在另一实施例中，所述主控协作服务节点依据所述备份规则发起备份操作，包括：
所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
在另一实施例中，所述确定一协作服务节点为主控协作服务节点，包括：所有协作服务节点向分布式文件锁服务节点发起竞争控制权流程，以使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
在另一实施例中，当所述协作服务节点确定为非主控协作服务节点时，
在所述主控协作服务节点将所述备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，所述方法还包括：
发现所述主控协作服务节点故障时，所有协作服务节点重新向分布式文件锁服务节点发起竞争控制权流程，以使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
在另一实施例中，所述主控协作服务节点中依据备份规则中的备份周期设置定时器；所述满足备份触发条件，包括：所述定时器时间到，确定满足备份触发条件；
相应的，当重新确定主控协作服务节点之后，所述方法还包括：重新确定的所述主控协作服务节点获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；
当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点；
当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点。
在另一实施例中，当所述主控协作服务节点发现存储节点发生故障时，所述方法还包括：
所述主控协作服务节点重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
在另一实施例中，所述主控协作服务节点获取备份规则，包括：
所述主控协作服务节点从分布式文件锁服务节点中获取备份规则；或者，
所述主控协作服务节点从用户操作的控制台中直接获得备份规则。
在另一实施例中，所述备份规则包括：每次备份的触发周期、要备份的数据集、备份的目标设备以及备份属性信息。
在另一实施例中，所述数据备份情况包括：数据集中的数据子集在存储节点中的分布情况、数据子集的至少一个副本之间的数据同步情况、以及所有数据集的备份记录。
在另一实施例中，所述方法还包括：所述主控协作服务节点按预设时间间隔获取所有存储节点的备份进度，将所述备份进度写入分布式文件锁服务节点。
本发明实施例还提供了一种节点，所述节点为协作服务节点；所述节点包括：获取单元和触发单元；其中，
所述获取单元，配置为当所述协作服务节点确定为主控服务节点后，获取备份规则；
所述触发单元，配置为在满足备份触发条件时，依据所述获取单元获取的备份规则发起备份操作。
在另一实施例中，所述触发单元，配置为根据所述获取单元获取的备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
在另一实施例中，所述节点还包括第一竞争处理单元，配置为向分布式文件锁服务节点发起竞争控制权流程，使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点；获得所述分布式文件锁服务节点确定的竞争结果。
在另一实施例中，所述节点还包括第一竞争处理单元，配置为当所述协作服务节点确定为非主控服务节点时，且主控协作服务节点将备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，发现所述主控协作服务节点发生故障时，重新向分布式文件锁服务节点发起竞争控制权流程，使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
在另一实施例中，所述触发单元，配置为所述协作服务节点确定为主控协作服务节点时，依据备份规则中的备份周期设置定时器，在所述定时器时间到时，确定满足备份触发条件；
所述触发单元，还配置为当所述协作服务节点重新确定主控协作服务节点之后，获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点；当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点。
在另一实施例中，所述触发单元，还配置为当发现存储节点发生故障时，重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
在另一实施例中，所述获取单元，配置为从分布式文件锁服务节点中获取备份规则；或者，从用户操作的控制台中直接获得备份规则。
在另一实施例中，所述节点还包括第一接收单元和第一发送单元；其中，
所述第一接收单元，配置为按预设时间间隔获取所有存储节点的备份进度；
所述第一发送单元，配置为将所述第一接收单元获得的所述备份进度发送至分布式文件锁服务节点。
本发明实施例还提供了一种数据备份系统，所述系统包括：协作服务节点、分布式文件锁服务节点和存储节点；其中，
所述协作服务节点，配置为确定为主控协作服务节点后，获取备份规则；在满足备份触发条件时，根据所述备份规则及所述存储节点中的数据备份情况生成备份策略，将所述备份策略写入所述分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点；
所述分布式文件锁服务节点，配置为接收所述协作服务节点发送的备份策略，保存所述备份策略；
所述存储节点，配置为接收所述协作服务节点发送的备份策略，根据所述备份策略执行备份操作。
在另一实施例中，所述分布式文件锁服务节点，还配置为接收到所有所述协作服务节点发送的竞争控制权流程，将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点，向所有协作服务节点发送竞争结果。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行本发明实施例所述的数据备份方法。
本发明实施例提供的数据备份方法、节点及计算机存储介质，在确定一协作服务节点为主控协作服务节点后，所述主控协作服务节点获取备份
规则；在满足备份触发条件时，所述主控协作服务节点依据所述备份规则发起备份操作。如此，通过主控协作服务节点实现了分布式存储系统中备份机制的集中控制，克服了现有技术中不能实现数据备份的集中控制，提升了分布式存储系统的数据可靠性，以及生产环境运维的易用性；并且通过主控协作服务节点触发所有存储节点的备份操作，使得所有存储节点能够并行进行数据备份，大大缩短了数据备份的时间。
图1为本发明实施例一的数据备份方法的流程示意图；
图2为本发明实施例二的数据备份方法的流程示意图；
图3为本发明实施例三的数据备份过程中发生故障的处理方法流程示意图；
图4为本发明实施例的数据备份系统的组成架构示意图；
图5为本发明实施例的协作服务节点的组成结构示意图。
下面结合附图及具体实施例对本发明作进一步详细的说明。
本发明实施例提供了一种数据备份方法，所述数据备份方法应用于主控协作服务节点中；图1为本发明实施例一的数据备份方法的流程示意图；如图1所示，包括以下步骤：
步骤101：确定一协作服务节点为主控协作服务节点后，所述主控协作服务节点获取备份规则。
在本实施例中，所述协作服务节点的数量为至少两个，以便能够满足故障后的容灾、以及容量扩展等需要。
这里，所述确定一协作服务节点为主控协作服务节点，包括：所有协作服务节点向分布式文件锁服务节点发起竞争控制权流程，将最先完成所
述竞争控制流程的协作服务节点确定为主控协作服务节点。
具体的，所有协作服务节点向分布式文件锁服务节点发起竞争控制权流程时，所有协作服务节点在所述分布式文件锁服务节点上创建一个文件，其中只有一个协作服务节点最先创建完成，则最先创建完成的所述协作服务节点确定为主控协作服务节点。
其中，所述备份规则是定时备份规则，具体包括：每次备份的触发周期、要备份的数据集、备份的目标设备以及备份属性信息；其中，所述备份属性信息为增量备份或全量备份等属性信息；具体的，所述增量备份指的是在上一次备份后，对所有发生变化的数据进行备份；所述全量备份指的是对所有数据进行备份。
本实施例中，所述主控协作服务节点获取备份规则，包括：
所述主控协作服务节点从分布式文件锁服务节点中获取备份规则；或者，
所述主控协作服务节点从用户操作的控制台中直接获得备份规则。
具体的，所述主控协作服务节点可在所述分布式文件锁服务节点查询是否存储备份规则，当确定所述分布式文件锁服务节点中存储有备份规则时，则从所述分布式文件锁服务节点中获取所述备份规则；当确定所述分布式文件锁服务节点中未存储有备份规则时，可从用户操作的控制台中直接获得备份规则；
当然，所述主控协作服务节点也可以直接从用户操作的控制台中获得备份规则，当所述主控协作服务节点直接从用户操作的控制台中获得备份规则后，将所述备份规则写入所述分布式文件锁服务节点中，以替换所述分布式文件锁服务节点中已存储的备份规则。
具体的，所述控制台最初与所述至少两个协作服务节点中的任一协作服务节点连接，当确定出主控协作服务节点后，所述控制台通过连接的所
述协作服务节点获得所述主控协作服务节点的地址，根据所述主控协作服务节点的地址与所述主控协作服务节点建立连接。
作为一种实施方式，所述控制台具有人机交互界面，用户可在所述控制台上设置备份规则，所述控制台将所述备份规则发送至所述主控协作服务节点；其中，所述控制台可随时发起备份。
步骤102：在满足备份触发条件时，所述主控协作服务节点依据所述备份规则发起备份操作。
这里，所述主控协作服务节点依据所述备份规则发起备份操作，包括：
所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
本实施例中，所述备份触发条件可以是：在所述备份规则中设定的每次备份的触发周期，根据所述触发周期设定定时器，当所述定时器时间到时，确定满足备份触发条件；所述备份触发条件还可以是从用户操作的控制台中直接控制触发，即用户通过所述控制台直接触发备份，所述控制台向所述主控协作服务节点下发备份指令，所述主控协作服务节点接收到所述备份指令时，确定满足备份触发条件。
其中，所述数据备份情况包括：数据集中的数据子集在存储节点中的分布情况、数据子集的至少一个副本之间的数据同步情况、以及所有数据集的备份记录。
具体的，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况生成备份策略，具体包括：
所述主控协作服务节点根据每次备份的触发周期设定定时器，所述主控协作服务节点在所述定时器时间到时，将生成的备份策略发送至存储节
点，从而触发备份操作；所述主控协作服务节点根据所述备份属性信息确定待备份的属性是全量备份还是增量备份，进一步的根据所述备份规则中的所述要备份的数据集以及所述备份属性信息确定要备份的数据集；所述主控协作服务节点根据所述备份的目标设备确定备份数据的存储位置。
所述主控协作服务节点还可根据所述数据备份情况确定备份策略；例如：在所述备份策略中设定只有完整的副本进行数据备份，不完整的副本不参与数据备份，则所述主控协作服务节点在同一个数据子集的至少一个副本中识别出完整的副本，设定从哪一个副本所在的存储节点开始进行数据备份，以及备份数据的目标设备和在所述目标设备上的存储位置。
在本实施例中，所述分布式文件锁服务节点的数量为至少两个，以便能够满足故障后的容灾、以及容量扩展等需要。
这里，所述分布式文件锁服务节点主要配置为存储备份策略，以及备份规则、配置信息或其他管理信息；并且，通过所述分布式文件锁服务节点可以确定至少两个协作服务节点中哪个协作服务节点作为主控协作服务节点。
在本实施例中，当所述协作服务节点确定为非主控协作服务节点时，在所述主控协作服务节点将所述备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，所述方法还包括：
发现所述主控协作服务节点故障时，所有协作服务节点向分布式文件锁服务节点发起竞争控制权流程，将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，
重新确定的所述主控协作服务节点获取备份规则，根据所述备份规则及存储节点中的数据备份情况生成备份策略。
其中，重新确定的所述主控协作服务节点可从所述分布式文件锁服务节点中获取备份策略，根据所述备份策略重新设置定时器；而原主控协作
服务节点若故障恢复，则为普通的协作服务节点。
基于上述实施例，所述主控协作服务节点中依据备份规则中的备份周期设置定时器；所述满足备份触发条件，包括：所述定时器时间到，确定满足备份触发条件；
相应的，当重新确定主控协作服务节点之后，所述方法还包括：重新确定的所述主控协作服务节点获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；
当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点立即将所述备份策略发送至所有存储节点；
当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，将所述备份策略发送至所有存储节点。
具体的，所述当前时间为重新确定所述主控协作服务节点的时间；所述当前时间是否满足预设触发条件，包括：预先设定一个时间阈值，以当前时间减去这个时间阈值获得一个时间点t’，如果所述时间点t’距离所述当前时间的时间段内，包含一次应当触发备份的时间点，且根据分布式文件锁服务节点中的备份记录，所述时间段内不包含上一次备份完成的时间点，则确定当前时间满足预设触发条件，即所述主控协作服务节点立即将所述备份策略发送至所有存储节点；当所述当前时间不满足上述条件时，则确定当前时间不满足预设触发条件，则所述主控协作服务节点依据所述预设触发条件设置定时器，在所述定时器时间到时，将所述备份策略发送至所有存储节点。
在本实施例中，当所述主控协作服务节点发现存储节点发生故障时，所述方法还包括：
所述主控协作服务节点重新生成备份策略，将重新生成的所述备份策
略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
具体的，所述存储节点在备份过程中，可按第一时间间隔向所述主控协作服务节点发送备份进度，则当所述主控协作服务节点超过第二时间间隔仍未收到任一存储节点发送的备份进度时，可确定所述任一存储节点发生故障且所述故障无法修复；则所述主控协作服务节点修改所述备份策略，安排其他存储节点接替发生故障的所述存储节点，并将所述存储节点上一次发送的备份进度发送至所述其他存储节点，使得所述其他存储节点依据所述备份进度将尚未进行备份的数据进行备份。
在本实施例中，所述主控协作服务节点按预设时间间隔获取所有存储节点的备份进度，将所述备份进度写入分布式文件锁服务节点。
在本实施例中，当所有存储节点的备份操作完成后，所述主控协作服务节点获取存储节点的备份成功信息，将所述备份成功信息写入分布式文件锁服务节点。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行本发明实施例所述的数据备份方法。
本发明实施例还提供了一种数据备份方法；图2为本发明实施例二的数据备份方法的流程示意图；如图2所示，所述方法包括：
步骤201：协作服务节点A和协作服务节点B向分布式文件锁服务节点发起竞争控制权流程。
步骤202：协作服务节点A竞争成功，成为主控协作服务节点。
步骤203：协作服务节点A在所述分布式文件锁服务节点中查询是否存在备份规则、备份策略和备份记录。
步骤204：当所述分布式文件锁服务节点中存在备份规则、备份策略和
备份记录时，所述分布式文件锁服务节点将所述备份规则、备份策略和备份记录发送至所述协作服务节点A。
步骤205：协作服务节点A判断当前是否正在进行备份操作，当判断的结果为是时，所述协作服务节点A接管当前的备份操作控制。
步骤206：协作服务节点A判断当前是否正在进行备份操作，当判断的结果为否时，所述协作服务节点A判断是否错过了本周期的数据备份；当判断的结果为是时，所述协作服务节点A立即发起备份操作；当判断的结果为否时，则根据所述备份规则，为下一次备份操作设置定时器。
步骤207：控制台连接协作服务节点A。
步骤208：用户在控制台上设置备份规则，由控制台指示协作服务节点A。
步骤209：协作服务节点A将备份规则写入分布式文件锁服务节点。
步骤210：协作服务节点A向控制台返回备份规则的写入结果。
步骤211：协作服务节点A根据备份规则设置定时器，在定时器时间到时，触发备份操作，生成备份策略。
步骤212：协作服务节点A将备份策略写入分布式文件锁服务节点。
步骤213：协作服务节点A将备份策略下发至所有存储节点。
步骤214：所有存储节点根据备份策略，向目标备份设备的指定位置执行备份操作。
步骤215：所有存储节点在备份过程中按预设时间向协作服务节点A反馈备份进度。
步骤216：协作服务节点A将备份进度记录在分布式文件锁服务节点中。
步骤217：协作服务节点A在所有存储节点备份完成后，向分布式文件锁服务节点写入备份成功记录。
步骤218：协作服务节点A为下一次备份操作设置定时器。
本发明实施例还提供了一种在数据备份过程中发生故障的处理方法；图3为本发明实施例三的数据备份过程中发生故障的处理方法流程示意图；本实施例基于图2所示的数据备份方法，且应用与步骤214之后，步骤215之前；如图3所示，所述处理方法包括：
步骤301：主控协作服务节点发现与存储节点A断链，所述主控协作服务节点判断可能是网络故障，或者所述存储节点A发生故障。
步骤302：主控协作服务节点等待存储节点A恢复。
步骤303：存储节点A同样在等待与所述主控协作服务节点重新建链。
步骤304：存储节点A暂时终止正在进行的对目标备份设备的数据发送。
步骤305：经过预先配置时间后，所述主控协作服务节点发现与所述存储节点A建链仍未成功，则所述主控协作服务节点放弃所述存储节点A，重新生成备份策略，将存储节点A的工作交给存储节点B继续执行。
步骤306：主控协作服务节点将重新生成的备份策略写入分布式文件锁服务节点中。
步骤307：主控协作服务节点将重新生成的备份策略下发给存储节点B。
步骤308：存储节点B接替存储节点A，继续执行备份操作，将数据发送至目标备份设备。
本发明实施例还提供了一种数据备份系统；图4为本发明实施例的数据备份系统的组成架构示意图；如图4所示，所述系统包括：协作服务节点41、分布式文件锁服务节点42和存储节点43；其中，
所述协作服务节点41，配置为确定为主控协作服务节点后，获取备份规则；在满足备份触发条件时，根据所述备份规则及所述存储节点中的数
据备份情况生成备份策略，将所述备份策略写入所述分布式文件锁服务节点42中，并将所述备份策略发送至所有存储节点43；
所述分布式文件锁服务节点42，配置为接收所述协作服务节点41发送的备份策略，保存所述备份策略；
所述存储节点43，配置为接收所述协作服务节点41发送的备份策略，根据所述备份策略执行备份操作。
在本实施例中，所述协作服务节点41、所述分布式文件锁服务节点42和所述存储节点43的数量均为至少两个，以便能够满足故障后的容灾、以及容量扩展等需要。
具体的，所述协作服务节点41确定为主控协作服务节点的具体过程包括：
所有所述协作服务节点41向分布式文件锁服务节点42发起竞争控制权流程，以使所述分布式文件锁服务节点42将最先完成所述竞争控制流程的协作服务节点41确定为主控协作服务节点，获得所述分布式文件锁服务节点42确定的竞争结果；
其中，所述分布式文件锁服务节点42，还配置为接收到所有所述协作服务节点41发送的竞争控制权流程，将最先完成所述竞争控制流程的协作服务节点41确定为主控协作服务节点，向所有协作服务节点41发送竞争结果。
具体的，所有协作服务节点41向分布式文件锁服务节点42发起竞争控制权流程时，所有协作服务节点41在所述分布式文件锁服务节点42上创建一个文件，其中只有一个协作服务节点最先创建完成，则最先创建完成的所述协作服务节点确定为主控协作服务节点。
具体的，所述协作服务节点41，配置为从分布式文件锁服务节点42中获取备份规则；或者，从用户操作的控制台44中直接获得备份规则。
所述备份规则包括：每次备份的触发周期、要备份的数据集、备份的目标设备以及备份属性信息。
所述数据备份情况包括：数据集中的数据子集在存储节点中的分布情况、数据子集的至少一个副本之间的数据同步情况、以及所有数据集的备份记录。
本实施例中，所述备份触发条件可以是：在所述备份规则中设定的每次备份的触发周期，根据所述触发周期设定定时器，当所述定时器时间到时，确定满足备份触发条件；所述备份触发条件还可以是从用户操作的控制台中直接控制触发，即用户通过所述控制台直接触发备份，所述控制台向所述主控协作服务节点下发备份指令，所述主控协作服务节点接收到所述备份指令时，确定满足备份触发条件。
其中，所述数据备份情况包括：数据集中的数据子集在存储节点中的分布情况、数据子集的至少一个副本之间的数据同步情况、以及所有数据集的备份记录。
具体的，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况生成备份策略，具体包括：
所述主控协作服务节点根据每次备份的触发周期设定定时器，所述主控协作服务节点在所述定时器时间到时，将生成的备份策略发送至存储节点，从而触发备份操作；所述主控协作服务节点根据所述备份属性信息确定待备份的属性是全量备份还是增量备份，进一步的根据所述备份规则中的所述要备份的数据集以及所述备份属性信息确定要备份的数据集；所述主控协作服务节点根据所述备份的目标设备确定备份数据的存储位置。
所述主控协作服务节点还可根据所述数据备份情况确定备份策略；例如：在所述备份策略中设定只有完整的副本进行数据备份，不完整的副本不参与数据备份，则所述主控协作服务节点在同一个数据子集的至少一个
副本中识别出完整的副本，设定从哪一个副本所在的存储节点开始进行数据备份，以及备份数据的目标设备和在所述目标设备上的存储位置。
本实施例中，当所述分布式文件锁服务节点42中未存储有备份策略时，所述分布式文件锁服务节点42接收并保存作为主控协作服务节点的协作服务节点41发送的备份策略；当用户通过控制台64修改备份策略时，所述分布式文件锁服务节点42接收所述备份策略，并替换自身存储的备份策略。
依据本发明的另一实施例，所述协作服务节点41，还配置为确定为非主控协作服务节点时，在所述主控协作服务节点将所述备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，发现所述主控协作服务节点故障时，重新向分布式文件锁服务节点发起竞争控制权流程，以使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
进一步地，所述协作服务节点41，还配置为重新确定为主控协作服务节点之后，判断当前时间是否满足预设触发条件，获得判断结果；当所述判断结果为所述当前时间满足预设触发条件时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点43；当所述判断结果为所述当前时间不满足预设触发条件时，依据所述预设触发条件设置定时器，在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点43。
依据本发明的另一实施例，所述协作服务节点41，还配置为确定为主控协作服务节点后，发现存储节点发生故障时，重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
依据本发明的另一实施例，所述存储节点43，还配置为在备份操作过程中，按预设时间间隔向作为主控协作服务节点的所述协作服务节点41发送备份进度；
所述作为主控协作服务节点的所述协作服务节点41，还配置为接收所述存储节点43按预设时间间隔获取的备份进度，将所述备份进度写入分布式文件锁服务节点42。
本发明实施例还提供了一种节点，所述节点为协作服务节点；图5为本发明实施例的协作服务节点的组成结构示意图；如图5所示，所述协作服务节点包括：获取单元411和触发单元412；其中，
所述获取单元411，配置为当所述协作服务节点确定为主控服务节点后，获取备份规则；
所述触发单元412，配置为在满足备份触发条件时，依据所述获取单元获取的备份规则发起备份操作。
具体的，所述触发单元412，配置为根据所述获取单元411获取的备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
作为一种实施方式，所述节点还包括第一竞争处理单元413，配置为向分布式文件锁服务节点发起竞争控制权流程，使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点；获得所述分布式文件锁服务节点确定的竞争结果。
作为另一种实施方式，所述节点还包括第一竞争处理单元413，配置为当所述协作服务节点确定为非主控服务节点时，且主控协作服务节点将备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，发现所述主控协作服务节点发生故障时，重新向分布式
文件锁服务节点发起竞争控制权流程，使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
具体的，所述触发单元412，配置为所述协作服务节点确定为主控协作服务节点时，依据备份规则中的备份周期设置定时器，在所述定时器时间到时，确定满足备份触发条件；
所述触发单元412，还配置为当所述协作服务节点重新确定主控协作服务节点之后，获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点；当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点。
作为又一种实施方式，所述触发单元412，还配置为当发现存储节点发生故障时，重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
具体的，所述获取单元411，配置为从分布式文件锁服务节点中获取备份规则；或者，从用户操作的控制台中直接获得备份规则。
所述节点还包括第一接收单元415和第一发送单元414；其中，
所述第一接收单元415，配置为按预设时间间隔获取所有存储节点的备份进度；
所述第一发送单元414，还配置为将所述第一接收单元415获得的所述
备份进度发送至分布式文件锁服务节点。
本实施例中，所述协作服务节点中的获取单元411和触发单元412在实际应用中，均可由所述协作服务节点中的中央处理器(CPU，Central Processing Unit)、数字信号处理器(DSP，Digital Signal Processor)或可编程门阵列(FPGA，Field－Programmable Gate Array)实现；所述协作服务节点中的第一发送单元414在实际应用中，均可由所述协作服务节点中的发射机或发射天线实现；所述协作服务节点中的第一竞争处理单元413在实际应用中，可由所述协作服务节点中的CPU、DSP或FPGA结合收发机或收发天线实现；所述协作服务节点中的第一接收单元415在实际应用中，可由所述协作服务节点中的接收机或接收天线实现。
本领域技术人员应当理解，本发明实施例的协作服务节点中各处理单元的功能，可参照前述数据备份方法的相关描述而理解，本发明实施例的协作服务节点中各处理单元，可通过实现本发明实施例所述的功能的模拟电路而实现，也可以通过执行本发明实施例所述的功能的软件在智能终端上的运行而实现。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得
通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
本发明实施例通过主控协作服务节点实现了分布式存储系统中备份机制的集中控制，克服了现有技术中不能实现数据备份的集中控制，提升了分布式存储系统的数据可靠性，以及生产环境运维的易用性；并且通过主控协作服务节点触发所有存储节点的备份操作，使得所有存储节点能够并行进行数据备份，大大缩短了数据备份的时间。
Claims (21)
- 一种数据备份方法，所述方法包括：确定一协作服务节点为主控协作服务节点后，所述主控协作服务节点获取备份规则；在满足备份触发条件时，所述主控协作服务节点依据所述备份规则发起备份操作。
- 根据权利要求1所述的方法，其中，所述主控协作服务节点依据所述备份规则发起备份操作，包括：所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
- 根据权利要求1所述的方法，其中，所述确定一协作服务节点为主控协作服务节点，包括：所有协作服务节点向分布式文件锁服务节点发起竞争控制权流程，以使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
- 根据权利要求1所述的方法，其中，当所述协作服务节点确定为非主控协作服务节点时，在所述主控协作服务节点将所述备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，所述方法还包括：发现所述主控协作服务节点故障时，所有协作服务节点重新向分布式文件锁服务节点发起竞争控制权流程，以使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
- 根据权利要求4所述的方法，其中，所述主控协作服务节点中依据备份规则中的备份周期设置定时器；所述满足备份触发条件，包括：所述定时器时间到，确定满足备份触发条件；相应的，当重新确定主控协作服务节点之后，所述方法还包括：重新确定的所述主控协作服务节点获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点；当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点。
- 根据权利要求1所述的方法，其中，当所述主控协作服务节点发现存储节点发生故障时，所述方法还包括：所述主控协作服务节点重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
- 根据权利要求1所述的方法，其中，所述主控协作服务节点获取备份规则，包括：所述主控协作服务节点从分布式文件锁服务节点中获取备份规则；或者，所述主控协作服务节点从用户操作的控制台中直接获得备份规则。
- 根据权利要求1所述的方法，其中，所述备份规则包括：每次备份的触发周期、要备份的数据集、备份的目标设备以及备份属性信息。
- 根据权利要求2所述的方法，其中，所述数据备份情况包括：数据集中的数据子集在存储节点中的分布情况、数据子集的至少一个副本之间的数据同步情况、以及所有数据集的备份记录。
- 根据权利要求1所述的方法，其中，所述方法还包括：所述主控协作服务节点按预设时间间隔获取所有存储节点的备份进度，将所述备份进度写入分布式文件锁服务节点。
- 一种节点，所述节点为协作服务节点；所述节点包括：获取单元和触发单元；其中，所述获取单元，配置为当所述协作服务节点确定为主控服务节点后，获取备份规则；所述触发单元，配置为在满足备份触发条件时，依据所述获取单元获取的备份规则发起备份操作。
- 根据权利要求11所述的节点，其中，所述触发单元，配置为根据所述获取单元获取的备份规则及存储节点中的数据备份情况生成备份策略，将所述备份策略写入分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点，使所有存储节点根据所述备份策略执行备份操作。
- 根据权利要求11所述的节点，其中，所述节点还包括第一竞争处理单元，配置为向分布式文件锁服务节点发起竞争控制权流程，使所述分布式文件锁服务节点将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点；获得所述分布式文件锁服务节点确定的竞争结果。
- 根据权利要求11所述的节点，其中，所述节点还包括第一竞争处理单元，配置为当所述协作服务节点确定为非主控服务节点时，且主控协作服务节点将备份策略发送至所有存储节点之前、或所有存储节点根据所述备份策略执行备份操作过程中，发现所述主控协作服务节点发生故障时，重新向分布式文件锁服务节点发起竞争控制权流程，使所述分布式文件锁 服务节点将最先完成所述竞争控制流程的协作服务节点重新确定为主控协作服务节点，获得所述分布式文件锁服务节点确定的竞争结果。
- 根据权利要求14所述的节点，其中，所述触发单元，配置为所述协作服务节点确定为主控协作服务节点时，依据备份规则中的备份周期设置定时器，在所述定时器时间到时，确定满足备份触发条件；所述触发单元，还配置为当所述协作服务节点重新确定主控协作服务节点之后，获取备份规则，依据所述备份规则中的备份周期判断当前时间是否满足预设触发条件，获得判断结果；当所述判断结果为所述当前时间满足预设触发条件时，所述主控协作服务节点根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点；当所述判断结果为所述当前时间不满足预设触发条件时，依据所述备份规则重新设置定时器，并在所述定时器时间到时，根据所述备份规则及存储节点中的数据备份情况重新生成备份策略，将所述备份策略发送至所有存储节点。
- 根据权利要求11所述的节点，其中，所述触发单元，还配置为当发现存储节点发生故障时，重新生成备份策略，将重新生成的所述备份策略发送至接替发生故障的所述存储节点的其他存储节点，以使所述其他存储节点依据所述备份策略执行备份操作。
- 根据权利要求11所述的节点，其中，所述获取单元，配置为从分布式文件锁服务节点中获取备份规则；或者，从用户操作的控制台中直接获得备份规则。
- 根据权利要求11所述的节点，其中，所述节点还包括第一接收单元和第一发送单元；其中，所述第一接收单元，配置为按预设时间间隔获取所有存储节点的备份 进度；所述第一发送单元，配置为将所述第一接收单元获得的所述备份进度发送至分布式文件锁服务节点。
- 一种数据备份系统，所述系统包括：协作服务节点、分布式文件锁服务节点和存储节点；其中，所述协作服务节点，配置为确定为主控协作服务节点后，获取备份规则；在满足备份触发条件时，根据所述备份规则及所述存储节点中的数据备份情况生成备份策略，将所述备份策略写入所述分布式文件锁服务节点中，并将所述备份策略发送至所有存储节点；所述分布式文件锁服务节点，配置为接收所述协作服务节点发送的备份策略，保存所述备份策略；所述存储节点，配置为接收所述协作服务节点发送的备份策略，根据所述备份策略执行备份操作。
- 根据权利要求19所述的系统，其中，所述分布式文件锁服务节点，还配置为接收到所有所述协作服务节点发送的竞争控制权流程，将最先完成所述竞争控制流程的协作服务节点确定为主控协作服务节点，向所有协作服务节点发送竞争结果。
- 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至10任一项所述的数据备份方法。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP15833967.1A EP3185125B1 (en) | 2014-08-22 | 2015-04-08 | Data backup method, system, node and computer storage media |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410419266.X | 2014-08-22 | ||
| CN201410419266.XA CN105354108B (zh) | 2014-08-22 | 2014-08-22 | 一种数据备份方法及节点 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016026306A1 true WO2016026306A1 (zh) | 2016-02-25 |
Family
ID=55330082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/076055 WO2016026306A1 (zh) | 2014-08-22 | 2015-04-08 | 一种数据备份方法、系统、节点及计算机存储介质 |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP3185125B1 (zh) |
| CN (1) | CN105354108B (zh) |
| WO (1) | WO2016026306A1 (zh) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756918A (zh) * | 2019-03-26 | 2019-05-14 | 京信通信系统（中国）有限公司 | 数据备份方法、装置、计算机设备和存储介质 |
| CN111240899A (zh) * | 2020-01-10 | 2020-06-05 | 北京百度网讯科技有限公司 | 状态机复制方法、装置、系统及存储介质 |
| CN111404647A (zh) * | 2019-01-02 | 2020-07-10 | 中兴通讯股份有限公司 | 一种节点协同关系的控制方法及相关设备 |
| CN113190619A (zh) * | 2021-04-29 | 2021-07-30 | 优刻得科技股份有限公司 | 分布式kv数据库的数据读写方法、系统、设备和介质 |
| US11237449B2 (en) | 2015-10-06 | 2022-02-01 | View, Inc. | Controllers for optically-switchable devices |
| WO2022143158A1 (zh) * | 2020-12-30 | 2022-07-07 | 花瓣云科技有限公司 | 一种数据备份方法、电子设备、数据备份系统及芯片系统 |
| US11796885B2 (en) | 2012-04-17 | 2023-10-24 | View, Inc. | Controller for optically-switchable windows |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106330945B (zh) * | 2016-08-31 | 2020-04-24 | 北京信安世纪科技股份有限公司 | 数字证书同步方法、数字签名服务器及数字证书同步系统 |
| CN108241544B (zh) * | 2016-12-23 | 2023-06-06 | 中科星图股份有限公司 | 一种基于集群的故障处理方法 |
| CN109308233A (zh) * | 2017-07-28 | 2019-02-05 | 中兴通讯股份有限公司 | 数据备份方法、装置及系统 |
| CN107992326B (zh) * | 2017-12-19 | 2021-03-23 | 上海新炬网络技术有限公司 | 基于Struts2框架的Java自动化代码发布方法 |
| CN108170559A (zh) * | 2017-12-22 | 2018-06-15 | 维沃移动通信有限公司 | 一种数据备份方法及终端 |
| CN108874918B (zh) * | 2018-05-30 | 2021-11-26 | 郑州云海信息技术有限公司 | 一种数据处理装置、数据库一体机及其数据处理方法 |
| CN111459718B (zh) * | 2020-03-31 | 2024-02-09 | 珠海格力电器股份有限公司 | 一种多终端系统及其数据备份方法和存储介质 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042662A (zh) * | 2006-03-08 | 2007-09-26 | 国际商业机器公司 | 用于管理分布式应用环境中的数据备份的系统和方法 |
| CN101252603A (zh) * | 2008-04-11 | 2008-08-27 | 清华大学 | 基于存储区域网络san的集群分布式锁管理方法 |
| CN103186554A (zh) * | 2011-12-28 | 2013-07-03 | 阿里巴巴集团控股有限公司 | 分布式数据镜像方法及存储数据节点 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102693168B (zh) * | 2011-03-22 | 2014-12-31 | 中兴通讯股份有限公司 | 一种数据备份恢复的方法、系统和服务节点 |
| CN102123054A (zh) * | 2011-04-19 | 2011-07-13 | 北京神州数码思特奇信息技术股份有限公司 | 一种管理控制云计算网络技术系统 |
| US20140149346A1 (en) * | 2012-02-28 | 2014-05-29 | Gigaspaces Ltd. | System and method for maintaining distributed data transaction atomicity and isolation during a replication to a different target cluster |
| US9218374B2 (en) * | 2012-06-13 | 2015-12-22 | Commvault Systems, Inc. | Collaborative restore in a networked storage system |
| CN103793425B (zh) * | 2012-10-31 | 2017-07-14 | 国际商业机器公司 | 用于分布式系统的数据处理方法及装置 |
| CN103873501B (zh) * | 2012-12-12 | 2017-07-18 | 华中科技大学 | 一种云备份系统及其数据备份方法 |
-
2014
- 2014-08-22 CN CN201410419266.XA patent/CN105354108B/zh active Active
-
2015
- 2015-04-08 WO PCT/CN2015/076055 patent/WO2016026306A1/zh active Application Filing
- 2015-04-08 EP EP15833967.1A patent/EP3185125B1/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042662A (zh) * | 2006-03-08 | 2007-09-26 | 国际商业机器公司 | 用于管理分布式应用环境中的数据备份的系统和方法 |
| CN101252603A (zh) * | 2008-04-11 | 2008-08-27 | 清华大学 | 基于存储区域网络san的集群分布式锁管理方法 |
| CN103186554A (zh) * | 2011-12-28 | 2013-07-03 | 阿里巴巴集团控股有限公司 | 分布式数据镜像方法及存储数据节点 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP3185125A4 * |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11796885B2 (en) | 2012-04-17 | 2023-10-24 | View, Inc. | Controller for optically-switchable windows |
| US11237449B2 (en) | 2015-10-06 | 2022-02-01 | View, Inc. | Controllers for optically-switchable devices |
| CN111404647A (zh) * | 2019-01-02 | 2020-07-10 | 中兴通讯股份有限公司 | 一种节点协同关系的控制方法及相关设备 |
| CN111404647B (zh) * | 2019-01-02 | 2023-11-28 | 中兴通讯股份有限公司 | 一种节点协同关系的控制方法及相关设备 |
| CN109756918A (zh) * | 2019-03-26 | 2019-05-14 | 京信通信系统（中国）有限公司 | 数据备份方法、装置、计算机设备和存储介质 |
| CN109756918B (zh) * | 2019-03-26 | 2022-05-06 | 京信网络系统股份有限公司 | 数据备份方法、装置、计算机设备和存储介质 |
| CN111240899A (zh) * | 2020-01-10 | 2020-06-05 | 北京百度网讯科技有限公司 | 状态机复制方法、装置、系统及存储介质 |
| CN111240899B (zh) * | 2020-01-10 | 2023-07-25 | 北京百度网讯科技有限公司 | 状态机复制方法、装置、系统及存储介质 |
| WO2022143158A1 (zh) * | 2020-12-30 | 2022-07-07 | 花瓣云科技有限公司 | 一种数据备份方法、电子设备、数据备份系统及芯片系统 |
| CN113190619A (zh) * | 2021-04-29 | 2021-07-30 | 优刻得科技股份有限公司 | 分布式kv数据库的数据读写方法、系统、设备和介质 |
| CN113190619B (zh) * | 2021-04-29 | 2022-12-27 | 优刻得科技股份有限公司 | 分布式kv数据库的数据读写方法、系统、设备和介质 |
Also Published As
| Publication number | Publication date |
|---|---|
| EP3185125B1 (en) | 2019-04-03 |
| CN105354108B (zh) | 2020-01-07 |
| EP3185125A4 (en) | 2018-01-03 |
| CN105354108A (zh) | 2016-02-24 |
| EP3185125A1 (en) | 2017-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016026306A1 (zh) | 一种数据备份方法、系统、节点及计算机存储介质 | |
| US10795788B2 (en) | Remote data replication method and system | |
| US9367598B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| CN103473277B (zh) | 文件系统的快照方法和装置 | |
| US9251230B2 (en) | Exchanging locations of an out of synchronization indicator and a change recording indicator via pointers | |
| WO2018098972A1 (zh) | 一种日志恢复方法、存储装置和存储节点 | |
| CN109144785B (zh) | 用于备份数据的方法和装置 | |
| US20170168756A1 (en) | Storage transactions | |
| CN104750738B (zh) | 一种更新数据信息的方法、数据节点、管理节点及系统 | |
| CN108255638B (zh) | 一种快照回滚方法及装置 | |
| CN110825562B (zh) | 数据备份方法、装置、系统和存储介质 | |
| US8612799B2 (en) | Method and apparatus of backing up subversion repository | |
| CN109976942B (zh) | 一种数据备份和恢复方法、备份服务器和源服务器 | |
| CN106873902B (zh) | 一种文件存储系统、数据调度方法及数据节点 | |
| CN106855869B (zh) | 一种实现数据库高可用的方法、装置和系统 | |
| CN115729749A (zh) | 一种数据备份方法及系统 | |
| EP2372552B1 (en) | Automated relocation of in-use multi-site protected data storage | |
| CN103970620B (zh) | 一种准连续性数据复制方法及装置 | |
| WO2017067397A1 (zh) | 一种数据恢复方法和装置 | |
| WO2017080362A1 (zh) | 数据管理方法及装置 | |
| CN110825758A (zh) | 一种交易处理的方法及装置 | |
| CN113515574B (zh) | 一种数据同步方法及装置 | |
| CN113297134B (zh) | 数据处理系统及数据处理方法、装置、电子设备 | |
| CN111522688B (zh) | 分布式系统的数据备份方法及装置 | |
| CN114443356A (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: 15833967 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| REEP | Request for entry into the european phase |
Ref document number: 2015833967 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2015833967 Country of ref document: EP |