CN112631839A - Method, device and equipment for realizing data backup - Google Patents
Method, device and equipment for realizing data backup Download PDFInfo
- Publication number
- CN112631839A CN112631839A CN202011640262.6A CN202011640262A CN112631839A CN 112631839 A CN112631839 A CN 112631839A CN 202011640262 A CN202011640262 A CN 202011640262A CN 112631839 A CN112631839 A CN 112631839A
- Authority
- CN
- China
- Prior art keywords
- data
- data table
- file
- backup
- distinguishing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 69
- 230000001360 synchronised effect Effects 0.000 claims description 48
- 230000008569 process Effects 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000010076 replication Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000001960 triggered effect Effects 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/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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2082—Data synchronisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a method, a device and equipment for realizing data backup, wherein a first data table comprising data to be written is obtained from a cache region of a main cluster, a second data table of a backup cluster is established according to the first data table, and data backup is realized on the basis of not influencing the running condition of the main cluster by adopting an asynchronous backup mode. Acquiring a third data table from the storage area of the main cluster; comparing whether the service data in the third data table is consistent with the backup data in the second data table; if the service data are inconsistent with the backup data, the data different from the backup data in the service data are used as distinguishing data; and writing the distinguishing data into a second data table by using a target storage file corresponding to the distinguishing data acquired from the storage area of the main cluster. The consistency check of the data in the main cluster and the data in the standby cluster are realized, when the data in the main cluster and the data in the standby cluster are inconsistent, the re-backup of the distinguished data is realized, and the requirement of data backup under extreme conditions is met.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a method, an apparatus, and a device for implementing data backup.
Background
The HBase database stores more data, which may cause failure to provide external services when a cluster in the HBase database fails. In order to ensure that the HBase database can normally and stably provide services to the outside, a primary cluster and a backup cluster are usually established in the HBase database, and data of the primary cluster is backed up to the backup cluster, so that when the primary cluster fails, the backup cluster is switched to provide services to the outside.
At present, the main and standby clusters of the HBase database are easily influenced by the running state of the main cluster when the data backup is realized. When the main cluster is down, partial data cannot be backed up, and the data consistency of the main cluster and the standby cluster cannot be ensured.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, and a device for implementing data backup, which can ensure that data in a primary cluster and a secondary cluster are consistent after a failure occurs in the primary cluster, and meet a data backup requirement.
In order to solve the above problem, the technical solution provided by the embodiment of the present application is as follows:
in a first aspect, the present application provides a method for implementing data backup, where the method includes:
acquiring a first data table comprising data to be written from a cache region of a main cluster, and establishing a second data table of a standby cluster according to the first data table;
acquiring a third data table from the storage area of the main cluster, wherein the third data table is established by writing data to be written in the first data table into the main cluster;
comparing whether the service data in the third data table is consistent with the backup data in the second data table;
if the service data are inconsistent with the backup data, taking the data in the service data, which is different from the backup data, as distinguishing data;
and acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table by using the target storage file.
In a possible implementation manner, the obtaining a target storage file corresponding to the difference data from the storage area of the main cluster, and writing the difference data into the second data table by using the target storage file includes:
acquiring a target data identifier corresponding to the distinguishing data from the third data table;
determining target file information of a target storage file according to the target data identifier, and generating task information by using the target file information;
taking a data table with distinguishing data in the third data table as a first distinguishing data table;
acquiring a target storage file by using a target data identifier corresponding to the distinguishing data in the first distinguishing data table;
establishing a synchronous task by using the task information and the target storage file;
judging whether the synchronous task is successfully established; if so, calling a synchronization tool to execute the synchronization task so that the synchronization tool writes the distinguishing data into a second distinguishing data table according to the target storage file; the second distinguishing data table is a data table corresponding to the first distinguishing data table in the second data table.
In a possible implementation manner, the obtaining a target storage file by using a target data identifier corresponding to the distinguishing data in the first distinguishing data table includes:
acquiring a target data identifier of the first distinguishing data from the first distinguishing data table;
if the acquisition is successful, scanning a file storage area corresponding to the first distinguishing data table from the first distinguishing data according to the target data identification to acquire a target storage file corresponding to the distinguishing data;
and if the acquisition is unsuccessful, scanning the file storage area corresponding to the first distinguishing data table to acquire a target storage file.
In a possible implementation manner, after the establishing of the synchronization task by using the task information and the target storage file, the method further includes:
if the synchronous task is not successfully established, establishing the synchronous task again according to the task information and the target storage file;
and returning to execute the steps of judging whether the synchronous task is successfully established and the subsequent steps until the synchronous task is successfully established or the number of times of establishing the synchronous task reaches a first preset number.
In a possible implementation manner, if the number of times of establishing the synchronization task reaches a first preset number of times, the method further includes:
acquiring a file name of the target storage file, and writing the file name into a first backup failure file directory;
obtaining a file name writing result, and judging whether writing the file name into a first backup failure file directory is successful or not;
if not, writing the file name into the first backup failure file directory again;
and returning and executing the obtained file name writing result, judging whether the file name is successfully written into the first backup failure file directory or not, and performing the subsequent steps until the file name is successfully written into the first backup failure file directory or the number of times of writing the file name reaches a second preset number.
In a possible implementation manner, after the obtaining a target storage file corresponding to the difference data and writing the difference data into the second data table by using the target storage file, the method further includes:
acquiring a data writing result, and determining whether the distinguishing data is successfully written into the second data table according to the data writing result;
if the data is unsuccessful, the target storage file is reused to write the distinguishing data into the second data table;
and returning to execute the obtained data writing result, determining whether the distinguishing data is successfully written into the second data table according to the data writing result, and performing subsequent steps until the distinguishing data is successfully written into the second data table, or the number of times of writing the distinguishing data into the second data table reaches a third preset number.
In a second aspect, the present application provides an apparatus for implementing data backup, the apparatus comprising:
the device comprises a first acquisition unit, a second acquisition unit and a first storage unit, wherein the first acquisition unit is used for acquiring a first data table containing data to be written from a cache region of a main cluster and establishing a second data table of a standby cluster according to the first data table;
a second obtaining unit, configured to obtain a third data table from a storage area of the main cluster, where the third data table is created by writing data to be written in the first data table into the main cluster;
the comparison unit is used for comparing whether the service data in the third data table is consistent with the backup data in the second data table;
a determining unit, configured to, if the service data is inconsistent with the backup data, use data different from the backup data in the service data as distinguishing data;
a first writing unit, configured to obtain a target storage file corresponding to the difference data from the storage area of the main cluster, and write the difference data into the second data table by using the target storage file.
In one possible implementation manner, the first writing unit includes:
the first obtaining subunit is configured to obtain, from the third data table, a target data identifier corresponding to the distinguishing data;
the generating subunit is used for determining target file information of the target storage file according to the target data identifier and generating task information by using the target file information;
a determining subunit, configured to use a data table with difference data in the third data table as a first difference data table;
the second obtaining subunit is configured to obtain a target storage file by using a target data identifier corresponding to the difference data in the first difference data table;
the establishing unit is used for establishing a synchronous task by utilizing the task information and the target storage file;
the judging and executing unit is used for judging whether the synchronous task is successfully established; if so, calling a synchronization tool to execute the synchronization task so that the synchronization tool writes the distinguishing data into a second distinguishing data table according to the target storage file; the second distinguishing data table is a data table corresponding to the first distinguishing data table in the second data table.
In a possible implementation manner, the second obtaining subunit is specifically configured to obtain a target data identifier of the first difference data from the first difference data table;
if the acquisition is successful, scanning a file storage area corresponding to the first distinguishing data table from the first distinguishing data according to the target data identification to acquire a target storage file corresponding to the distinguishing data;
and if the acquisition is unsuccessful, scanning the file storage area corresponding to the first distinguishing data table to acquire a target storage file.
In one possible implementation, the apparatus further includes:
the reestablishing unit is used for reestablishing the synchronous task according to the task information and the target storage file if the synchronous task is not established successfully;
and the first execution unit is used for returning and executing the steps of judging whether the synchronous task is successfully established and the follow-up steps until the synchronous task is successfully established or the number of times of establishing the synchronous task reaches a first preset number.
In a possible implementation manner, if the number of times of establishing the synchronization task reaches a first preset number of times, the apparatus further includes:
the third obtaining subunit is configured to obtain a file name of the target storage file, and write the file name into the first backup failure file directory;
the fourth obtaining subunit is configured to obtain a file name writing result, and determine whether writing the file name into the first backup failure file directory is successful;
the writing subunit is used for writing the file name into the first backup failure file directory again if the file name is not written into the first backup failure file directory;
and the execution subunit is used for returning the writing result of the acquired file name, judging whether the file name is successfully written into the first backup failure file directory or not and judging the subsequent steps until the file name is successfully written into the first backup failure file directory or the number of times of writing the file name reaches a second preset number.
In a possible implementation manner, after the obtaining a target storage file corresponding to the difference data and writing the difference data into the second data table by using the target storage file, the apparatus further includes:
a third obtaining unit, configured to obtain a data writing result, and determine whether to successfully write the difference data into the second data table according to the data writing result;
a second writing unit, configured to, if unsuccessful, reuse the target storage file to write the difference data into the second data table;
and the second execution unit is used for returning and executing the obtained data writing result, determining whether the distinguishing data is successfully written into the second data table according to the data writing result and subsequent steps until the distinguishing data is successfully written into the second data table or the number of times of writing the distinguishing data into the second data table reaches a third preset number.
In a possible implementation manner, if the number of times of writing the distinguishing data into the second data table reaches a third preset number, the apparatus further includes:
a fourth obtaining unit, configured to obtain a file name of the target storage file, and write the file name into a second backup failure file directory;
a fifth obtaining unit, configured to obtain a file name writing result, and determine whether writing the file name into the second backup failure file directory is successful;
the third writing unit is used for rewriting the file name into the second backup failure file directory if the file name is not written into the second backup failure file directory;
and the third execution unit is used for returning the writing result of the acquired file name, judging whether the file name is successfully written into the second backup failure file directory or not and judging the subsequent steps until the file name is successfully written into the second backup failure file directory or the number of times of writing the file name reaches a fourth preset number.
In a third aspect, the present application provides an apparatus for implementing data backup, including: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is used for storing one or more programs, the one or more programs comprising instructions, which when executed by the processor, cause the processor to perform the method of the above embodiment.
In a fourth aspect, the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a terminal device, the instructions cause the terminal device to perform the method according to the foregoing embodiment.
Therefore, the embodiment of the application has the following beneficial effects:
according to the method, the device and the equipment for realizing data backup, a first data table comprising data to be written is obtained from a cache region of a main cluster, and a second data table of a backup cluster is established according to the first data table. By adopting the asynchronous backup mode, data backup can be realized on the basis of not influencing the running condition of the main cluster. Acquiring a third data table from the storage area of the main cluster, wherein the third data table is established by writing the first data table into the main cluster; comparing whether the service data in the third data table is consistent with the backup data in the second data table; if the service data are inconsistent with the backup data, taking the data in the service data, which is different from the backup data, as distinguishing data; and acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table by using the target storage file. Therefore, consistency check can be carried out on the data in the main cluster and the data in the standby cluster, and when the data in the main cluster and the data in the standby cluster are inconsistent, the distinguished data can be backed up again. Therefore, data backup is realized after the main cluster is abnormal, the data consistency in the main cluster and the standby cluster is ensured, and the requirement of data backup under extreme conditions can be met.
Drawings
Fig. 1 is a schematic view of a scenario of a method for implementing data backup according to an embodiment of the present application;
fig. 2 is a flowchart of a method for implementing data backup according to an embodiment of the present application;
fig. 3 is a schematic view of a scenario of a method for implementing data backup according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an apparatus for implementing data backup according to an embodiment of the present disclosure.
Detailed Description
In order to facilitate understanding and explaining the technical solutions provided by the embodiments of the present application, the following description will first describe the background art of the present application.
After researching the data backup mode in the traditional HBase database, the inventor finds that the traditional HBase database mostly adopts a synchronous data backup mode, and a part of data backup mode needs to occupy more resources of a main cluster, so that the operation performance of the main cluster is influenced. In addition, when part of the main cluster nodes fail, the synchronous data backup mode backups the data to be backed up in the failed main cluster nodes to the backup cluster through the normally operating main cluster nodes. However, when all the nodes of the primary cluster fail, the data to be backed up cannot be determined, so that part of the data cannot be backed up in the backup cluster, and the data in the primary and backup clusters are inconsistent.
Based on this, an embodiment of the present application provides a method for implementing data backup, where a first data table including data to be written is obtained from a cache region of a main cluster, a second data table of a backup cluster is established according to the first data table, and data backup can be implemented on the basis of not affecting an operating condition of the main cluster by using an asynchronous backup manner. Acquiring a third data table from the storage area of the main cluster, wherein the third data table is established by writing the first data table into the main cluster; comparing whether the service data in the third data table is consistent with the backup data in the second data table; if the service data are inconsistent with the backup data, taking the data in the service data, which is different from the backup data, as distinguishing data; and acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table by using the target storage file. Therefore, consistency check can be carried out on the data in the main cluster and the data in the standby cluster, and when the data in the main cluster and the data in the standby cluster are inconsistent, the distinguished data can be backed up again. Therefore, data backup is realized after the main cluster is abnormal, the data consistency in the main cluster and the standby cluster is ensured, and the requirement of data backup under extreme conditions can be met.
In order to facilitate understanding of the method for implementing data backup provided in the embodiment of the present application, the following description is made with reference to a scenario example shown in fig. 1. Referring to fig. 1, the figure is a schematic view of a scenario of a method for implementing data backup according to an embodiment of the present application. The method for realizing data backup provided by the embodiment of the application can be applied to data backup of an HBase database.
In practical applications, the HBase database uses HDFS (Hadoop Distributed File System) as an underlying storage System. And the main HBase cluster acquires the written data and uses HBase Replication to realize asynchronous synchronization of the data of the main and standby clusters. And the main HBase cluster and the standby HBase cluster respectively store the obtained data into the corresponding HDFS clusters. And carrying out consistency check on data stored in the main and standby clusters according to the main HDFS cluster and the standby HDFS cluster. And if the difference data exist, rewriting the difference data in the main cluster into the standby HDFS cluster by using the HFile of the difference data stored in the main HDFS cluster, so as to realize the data consistency of the main and standby clusters.
In order to facilitate understanding of the technical solutions provided by the embodiments of the present application, a method for implementing data backup provided by the embodiments of the present application is described below with reference to the accompanying drawings.
Referring to fig. 2, the figure is a flowchart of a method for implementing data backup according to an embodiment of the present application, where the method includes steps S201 to S205.
S201: and acquiring a first data table comprising data to be written from a cache region of the main cluster, and establishing a second data table of the standby cluster according to the first data table.
When writing data into the primary cluster, the data needs to be stored in the cache area. And the main cluster acquires the data to be written from the buffer area and writes the data to be written into the database. For the HBase database, the cache area may specifically be a storage area where the HLog file is located.
And acquiring a first data table from a cache region of the main cluster, wherein the first data table is a data table comprising data to be written which needs to be backed up at this time. And establishing a corresponding second data table in the standby cluster according to the obtained first data table. The second data table is stored in a storage area of the standby cluster, for example, a standby HDFS cluster corresponding to the standby HBase cluster.
S202: and acquiring a third data table from the storage area of the main cluster, wherein the third data table is established by writing the data to be written in the first data table into the main cluster.
After the data backup is performed, the backup data needs to be checked to ensure that the backup data and the service data are consistent.
And acquiring a third data table from the storage area of the main cluster, wherein the third data table is obtained after the data to be written is stored, and the third data table can be established by writing the data to be written in the first data table into the main cluster.
S203: and comparing whether the service data in the third data table is consistent with the backup data in the second data table.
The second data table and the third data table are established according to the data to be written in the first data table, and under a normal condition, the data in the second data table and the data in the third data table are consistent, so that the data in the third data table is backed up.
And acquiring the service data in the third data table and the backup data in the second data table. The service data in the third data table is data stored in the main cluster and used for providing services for the outside, and the backup data in the second data table is backup data stored in the backup cluster and corresponding to the service data. And comparing the service data with the backup data, and checking whether the service data and the backup data have consistency.
It should be noted that, in the embodiment of the present application, the time for performing data consistency check in the active/standby cluster is not limited. In a possible implementation, the check time may be preset, and the comparison between the service data and the backup data is triggered periodically. In another possible implementation manner, the consistency check on the backup data of this time may be performed after the backup of the service data is performed. In another possible implementation manner, the consistency check may also be performed on the backup data after the primary cluster is failed to repair.
S204: and if the service data are inconsistent with the backup data, taking the data different from the backup data in the service data as distinguishing data.
If the service data and the backup data are inconsistent, the backup data needs to be updated to ensure consistency of the backup data and the service data. And taking the data which is inconsistent with the backup data in the service data as the distinguishing data, and rewriting the distinguishing data into the backup cluster for backup.
S205: and acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table by using the target storage file.
And acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table according to the target storage file.
It should be noted that the service data and the backup data are not consistent, for example, the number of the service data and the backup data is not consistent, or the field values corresponding to the service data and the backup data are different. If the difference data is missing data in the backup data, the difference data is written into the second data table, so that the consistency of the service data and the backup data can be realized. If the differentiated data is different from the backup data in fields, the corresponding data in the backup data needs to be deleted, and then the differentiated data is written to prevent repeated storage of the data and storage of abnormal data.
An embodiment of the present invention provides a specific implementation manner for obtaining a target storage file corresponding to the difference data from a storage area of the main cluster, and writing the difference data into the second data table by using the target storage file, please refer to the following.
Based on the relevant contents of S201 to S205, it can be known that by writing the data to be written in the first data table in the cache region into the backup cluster, asynchronous data backup can be implemented, and the influence of data backup on the operation of the primary cluster is reduced. In addition, through the consistency check of the service data and the backup data, the differentiated data can be backed up again when the service data is inconsistent with the backup data, the data backup can be realized after the main cluster fails, and the data backup under extreme conditions can be met.
In a possible implementation manner, the obtaining a target storage file corresponding to the difference data from the storage area of the main cluster, and writing the difference data into the second data table by using the target storage file includes the following six steps:
a1: and acquiring a target data identifier corresponding to the distinguishing data from the third data table.
First, when the difference data is backed up again, it is necessary to write the difference data in the storage file corresponding to the difference data.
The third data table stores target data identifiers corresponding to the distinguishing data, and the target data identifiers have related information of the distinguishing data and can be used for determining storage positions of target storage files corresponding to the distinguishing data in the storage area. The target data identifier corresponding to the distinguishing data may specifically be a rowkey of the distinguishing data.
A2: and determining target file information of a target storage file according to the target data identifier, and generating task information by using the target file information.
The target data identification has related target file information of the target storage file corresponding to the distinguishing data. And generating corresponding task information by using the obtained target file information, wherein the task information is used for establishing a synchronous task and realizing data synchronization of the distinguishing data.
A3: and taking the data table with the distinguishing data in the third data table as a first distinguishing data table.
It is understood that the third data table is all the data tables related to the current consistency check, and some of the data tables in the third data table may have different data. And taking the data table with the distinguishing data as a first distinguishing data table, so that the first distinguishing data table can be conveniently processed subsequently, and a target storage file corresponding to the distinguishing data is obtained.
The first distinguishing data table may be determined based on a table name of a data table having the distinguishing data in the first data table. In a possible implementation manner, a table name of a data table of the distinguishing data may be obtained, and column information of the configuration table may be configured according to the table name.
A4: and acquiring a target storage file by using the target data identifier corresponding to the distinguishing data in the first distinguishing data table.
And the storage position of the target storage file is arranged in the target data identifier corresponding to the distinguishing data in the first distinguishing data table, and the target storage file is obtained by utilizing the target data identifier.
The embodiment of the present application further provides a specific implementation manner for obtaining the target storage file by using the target data identifier corresponding to the distinguishing data in the first distinguishing data table, please refer to the following.
A5: and establishing a synchronous task by using the task information and the target storage file.
And establishing a corresponding synchronous task according to the established task information and the acquired target storage file. The synchronization task may be specifically a MapReduce task.
A6: judging whether the synchronous task is successfully established; if so, calling a synchronization tool to execute the synchronization task so that the synchronization tool writes the distinguishing data into a second distinguishing data table according to the target storage file; the second distinguishing data table is a data table corresponding to the first distinguishing data table in the second data table.
In some cases, the synchronization task may not be successfully established, and a determination may need to be made as to whether the synchronization task was successfully established. If the sync task is successfully established, a sync tool may be invoked to perform the sync task.
When the synchronization task is a MapReduce task, the corresponding synchronization tool calculates a model for MapReduce.
The synchronization tool may write the distinct data into the backup table corresponding to the first distinct data table using the target storage file based on the established synchronization task. The backup table corresponding to the first distinguishing data table may be the second distinguishing data table, and the second distinguishing data table may be a data table determined from the second data table and having a name identical to that of the first distinguishing data table.
In response to the situation that the synchronization task cannot be successfully established, the embodiment of the present application further provides a specific implementation manner when the synchronization task is not successfully established, please refer to the following.
In a possible implementation manner, the first area data table has more data, and in order to improve the efficiency of acquiring the target storage file corresponding to the distinct data, the target data identifier of the first distinct data may be acquired, and the scan area is limited by using the target data identifier.
The embodiment of the present application provides a specific implementation manner for obtaining a target storage file by using a target data identifier corresponding to distinguishing data in the first distinguishing data table, which specifically includes the following three steps:
b1: and acquiring the target data identification of the first distinguishing data from the first distinguishing data table.
In order to reduce the amount of data to be scanned, the target data identification of the first distinctive data is acquired from the first distinctive data table. By acquiring the target data identifier of the first distinguishing data, the distinguishing data can be scanned from the first distinguishing data, so that the data scanning quantity is reduced, and the efficiency of acquiring the target storage file is improved.
B2: if the data are successfully acquired, scanning the data in the first distinguishing data table from the first distinguishing data according to the target data identification, and acquiring a target storage file corresponding to the distinguishing data.
If the target data identifier of the first distinguishing data can be obtained, scanning the data in the first distinguishing data table from the first distinguishing data according to the target data identifier to obtain a target storage file corresponding to the distinguishing data in the first distinguishing data table.
In a possible implementation manner, after the target data identifier of the first distinct data is obtained, the object in the SCAN command may be set by using the target data identifier of the first distinct data, and then the SCAN command is invoked to perform data scanning.
B3: and if the acquisition is unsuccessful, scanning the data in the first distinguishing data table to acquire a target storage file corresponding to the distinguishing data.
If the target data identifier of the first distinguishing data cannot be obtained, all data in the first distinguishing data table needs to be scanned, and a target storage file corresponding to the distinguishing data is obtained.
Specifically, if the target data identifier of the first distinct data cannot be obtained, the SCAN command may be directly invoked to SCAN all data in the first distinct data table.
Based on the above, by obtaining the target data identifier of the first distinct data, the data scanning range can be reduced, and the efficiency of obtaining the target storage file of the distinct data can be improved.
In one possible implementation, the sync task may be reestablished if it is not successfully established.
Specifically, after the task information and the target storage file are used to establish the synchronization task, the method further includes:
if the synchronous task is not successfully established, establishing the synchronous task again according to the task information and the target storage file;
and returning to execute the steps of judging whether the synchronous task is successfully established and the subsequent steps until the synchronous task is successfully established or the number of times of establishing the synchronous task reaches a first preset number.
In one possible implementation, there may be instances where the sync task fails to establish. After the synchronous task is established, whether the synchronous task is established successfully is judged. If the synchronous task is failed to be established, the task information and the target storage file are required to be reused for establishing the synchronous task. Until the synchronous task is successfully established or the number of times of reestablishing the synchronous task reaches a first preset number. The first preset number of times may be determined according to the read-write resources of the cluster, for example, the first preset number of times may be 4 times.
In the embodiment of the application, the fault tolerance of the data backup can be improved by reestablishing the synchronization task after the synchronization task is established unsuccessfully.
Further, if the number of times of establishing the synchronization task reaches a first preset number of times, the method further includes:
acquiring a file name of the target storage file, and writing the file name into a first backup failure file directory;
obtaining a file name writing result, and judging whether writing the file name into a first backup failure file directory is successful or not;
if not, writing the file name into the first backup failure file directory again;
and returning and executing the obtained file name writing result, judging whether the file name is successfully written into the first backup failure file directory or not, and performing the subsequent steps until the file name is successfully written into the first backup failure file directory or the number of times of writing the file name reaches a second preset number.
In a possible implementation manner, after the synchronization tasks are reestablished for the first preset number of times, the synchronization tasks may still not be successfully established, and the synchronization tool cannot be called to execute the synchronization tasks to implement the backups of the differentiated data. Correspondingly, the difference data needs to be recorded, so that other methods are subsequently adopted to backup the difference data.
And acquiring the file name of the target storage file, and writing the file name into the first backup failure file directory. The first backup failure file directory is a directory of target storage files that are pre-established for storing the differential data of the backup failure. The first backup failure file directory can be used for inquiring to obtain the differential data of the backup failure, so that further data backup is facilitated.
After writing the file name into the first backup failure file directory, it is also necessary to verify whether the writing is successful, so as to avoid missing part of the file name. Specifically, a file name writing result may be obtained, and whether all the file names to be written at this time are written into the first backup failure file directory is determined according to the file name writing result. And if the file name is unsuccessful, writing the file name into the first backup failure file directory again, acquiring a new file name writing result, and judging whether the file name is successfully written into the first backup failure file directory again. If not, continuing to execute the writing and subsequent judging steps until the file name is successfully written into the first backup failure file directory or the rewriting times reach a second preset time. The second preset number of times may be a preset number of times of repeatedly attempting to write the file name into the first backup failure file directory, and specifically, the second preset number of times may be 4 times.
In a possible implementation manner, before the file name is rewritten into the first failed backup file directory, the file name written into the first failed backup file directory last time needs to be deleted, so as to ensure that the failed backup directory does not have a duplicate file name.
Based on the above, by writing the file name into the first backup failure file directory, it is convenient to determine the differential data of the backup failure through the first backup failure file directory, so as to perform other backup processes on the differential data of the backup failure subsequently. And whether the file name is successfully written into the first backup failure file directory is verified, so that the fault tolerance is improved.
In one possible implementation, a backup failure may also occur when the differentiated data is backed up.
Based on this, an embodiment of the present application provides a method for implementing data backup, where after the target storage file corresponding to the difference data is obtained and the difference data is written into the second data table by using the target storage file, the method further includes:
acquiring a data writing result, and determining whether the distinguishing data is successfully written into the second data table according to the data writing result;
if the data is unsuccessful, the target storage file is reused to write the distinguishing data into the second data table;
and returning to execute the obtained data writing result, determining whether the distinguishing data is successfully written into the second data table according to the data writing result, and performing subsequent steps until the distinguishing data is successfully written into the second data table, or the number of times of writing the distinguishing data into the second data table reaches a third preset number.
And the data writing result is the data writing result of the differential data backup realized by calling the synchronization tool to execute the synchronization task. It is possible to determine whether all the difference data is written in the second data table using the data writing result.
If the difference data is not successfully written into the second data table, the difference data is written into the second data table by using the target storage file, a new data writing result is obtained, and whether the difference data is successfully written into the second data table is judged. If the difference data is not successfully written, the difference data is continuously written until the difference data is successfully written into the second data table or the number of times of repeatedly executing the difference data writing operation reaches a third preset number. The third preset number may be a preset number of writing the distinguishing data, and specifically, the third preset number may be 4.
It should be noted that before the difference data is written into the second data table by reusing the target storage file, the last written difference data may be deleted from the second data table to avoid repeated writing.
In the embodiment of the present application, after the difference data is written into the second data table, whether the difference data exists in the second data table is checked to ensure that all the difference data is correctly written into the second data table, so as to implement a complete backup of the difference data. In addition, if the writing fails, the writing operation can be repeatedly executed, and the fault tolerance of the differentiated data backup is improved.
Further, if the number of times of writing the difference data into the second data table reaches a third preset number of times, the method further includes:
acquiring a file name of the target storage file, and writing the file name into a second backup failure file directory;
obtaining a file name writing result, and judging whether writing the file name into a second backup failure file directory is successful or not;
if not, writing the file name into the second backup failure file directory again;
and returning and executing the obtained file name writing result, judging whether the file name is successfully written into the second backup failure file directory or not, and performing the subsequent steps until the file name is successfully written into the second backup failure file directory or the number of times of writing the file name reaches a fourth preset number.
When the difference data cannot be written into the second data table, the difference data needs to be recorded so as to be backed up by other methods in the following process. In the embodiment of the present application, the method for writing the file name of the target storage file into the second failed backup file directory and the method for checking whether the writing is successful are similar to the above-mentioned method for writing the file name of the target storage file after the synchronization task is failed into the first failed backup file directory and the method for checking whether the writing is successful. For a specific implementation, please refer to the above, which is not described herein again.
It should be noted that, in the embodiment of the present application, the second failed backup file directory may be the same as the first failed backup file directory, or may be a different failed backup file directory. The fourth preset number of times may be a preset number of times of repeatedly attempting to write the file name into the second backup failure file directory, and specifically, the fourth preset number of times may be 4 times, which is the same as the second preset number of times.
In a possible implementation manner, before the file name is rewritten into the second failed backup file directory, the file name written into the second failed backup file directory last time needs to be deleted, so as to ensure that the second failed backup directory does not have a duplicate file name.
Based on the above, by writing the file name into the second backup failure file directory, it is convenient to determine the differential data of the backup failure through the second backup failure file directory, so as to perform other backup processes on the differential data of the backup failure subsequently. And whether the file name is successfully written into the second backup failure file directory is verified, so that the fault tolerance is improved.
Referring to fig. 3, this figure is a schematic view of a scenario of a method for implementing data backup according to an embodiment of the present application.
And after the service data in the third data table is compared with the backup data in the second data table to be inconsistent, acquiring a target data identifier corresponding to the distinguishing data from the third data table, and generating task information by using the target data identifier. And then, acquiring the table name of the data table of the distinguishing data from the third data table, configuring the column information of the configuration table according to the table name, and determining the first distinguishing data table. And acquiring the target data identification of the first distinguishing data from each first distinguishing data table. If the first distinguishing data table is successfully obtained, carrying out partial scanning on the first distinguishing data table; and if the acquisition is unsuccessful, performing full-table scanning on the first distinguishing data table to finally obtain the target storage file. And establishing a synchronous task by using the target storage file and the task information, judging whether the synchronous task is successfully established, and if not, reestablishing. The number of times the synchronization task is established is less than or equal to 4 times. If the establishment is successful, the synchronization tool is used for executing the synchronization task and writing the distinguishing data into the second data table. And acquiring a data writing result, and judging whether the distinguishing data is successfully written into the second data table. And if not, rewriting, wherein the rewriting times are less than or equal to 4. And if the synchronous task cannot be established or the differential data cannot be successfully written, writing the file name of the target storage file into the backup failure file directory. And judging whether the file name is successfully written into the backup failure file directory, if not, rewriting, wherein the rewriting times are less than or equal to 4.
Based on the method for implementing data backup provided by the above method embodiment, an embodiment of the present application further provides a device for implementing data backup, and the device for implementing data backup will be described below with reference to the accompanying drawings.
Referring to fig. 4, this figure is a schematic structural diagram of an apparatus for implementing data backup according to an embodiment of the present application. As shown in fig. 4, the apparatus for implementing data backup includes:
a first obtaining unit 401, configured to obtain a first data table including data to be written from a cache region of a main cluster, and establish a second data table of a standby cluster according to the first data table;
a second obtaining unit 402, configured to obtain a third data table from the storage area of the master cluster, where the third data table is created by writing data to be written in the first data table into the master cluster;
a comparing unit 403, configured to compare whether the service data in the third data table is consistent with the backup data in the second data table;
a determining unit 404, configured to, if the service data is inconsistent with the backup data, use data different from the backup data in the service data as distinguishing data;
a first writing unit 405, configured to obtain a target storage file corresponding to the difference data from the storage area of the main cluster, and write the difference data into the second data table by using the target storage file.
In one possible implementation manner, the first writing unit 405 includes:
the first obtaining subunit is configured to obtain, from the third data table, a target data identifier corresponding to the distinguishing data;
the generating subunit is used for determining target file information of the target storage file according to the target data identifier and generating task information by using the target file information;
a determining subunit, configured to use a data table with difference data in the third data table as a first difference data table;
the second obtaining subunit is configured to obtain a target storage file by using a target data identifier corresponding to the difference data in the first difference data table;
the establishing unit is used for establishing a synchronous task by utilizing the task information and the target storage file;
the judging and executing unit is used for judging whether the synchronous task is successfully established; if so, calling a synchronization tool to execute the synchronization task so that the synchronization tool writes the distinguishing data into a second distinguishing data table according to the target storage file; the second distinguishing data table is a data table corresponding to the first distinguishing data table in the second data table.
In a possible implementation manner, the second obtaining subunit is specifically configured to obtain a target data identifier of the first difference data from the first difference data table;
if the acquisition is successful, scanning a file storage area corresponding to the first distinguishing data table from the first distinguishing data according to the target data identification to acquire a target storage file corresponding to the distinguishing data;
and if the acquisition is unsuccessful, scanning the file storage area corresponding to the first distinguishing data table to acquire a target storage file.
In one possible implementation, the apparatus further includes:
the reestablishing unit is used for reestablishing the synchronous task according to the task information and the target storage file if the synchronous task is not established successfully;
and the first execution unit is used for returning and executing the steps of judging whether the synchronous task is successfully established and the follow-up steps until the synchronous task is successfully established or the number of times of establishing the synchronous task reaches a first preset number.
In a possible implementation manner, if the number of times of establishing the synchronization task reaches a first preset number of times, the apparatus further includes:
the third obtaining subunit is configured to obtain a file name of the target storage file, and write the file name into the first backup failure file directory;
the fourth obtaining subunit is configured to obtain a file name writing result, and determine whether writing the file name into the first backup failure file directory is successful;
the writing subunit is used for writing the file name into the first backup failure file directory again if the file name is not written into the first backup failure file directory;
and the execution subunit is used for returning the writing result of the acquired file name, judging whether the file name is successfully written into the first backup failure file directory or not and judging the subsequent steps until the file name is successfully written into the first backup failure file directory or the number of times of writing the file name reaches a second preset number.
In a possible implementation manner, after the obtaining a target storage file corresponding to the difference data and writing the difference data into the second data table by using the target storage file, the apparatus further includes:
a third obtaining unit, configured to obtain a data writing result, and determine whether to successfully write the difference data into the second data table according to the data writing result;
a second writing unit, configured to, if unsuccessful, reuse the target storage file to write the difference data into the second data table;
and the second execution unit is used for returning and executing the obtained data writing result, determining whether the distinguishing data is successfully written into the second data table according to the data writing result and subsequent steps until the distinguishing data is successfully written into the second data table or the number of times of writing the distinguishing data into the second data table reaches a third preset number.
In a possible implementation manner, if the number of times of writing the distinguishing data into the second data table reaches a third preset number, the apparatus further includes:
a fourth obtaining unit, configured to obtain a file name of the target storage file, and write the file name into a second backup failure file directory;
a fifth obtaining unit, configured to obtain a file name writing result, and determine whether writing the file name into the second backup failure file directory is successful;
the third writing unit is used for rewriting the file name into the second backup failure file directory if the file name is not written into the second backup failure file directory;
and the third execution unit is used for returning the writing result of the acquired file name, judging whether the file name is successfully written into the second backup failure file directory or not and judging the subsequent steps until the file name is successfully written into the second backup failure file directory or the number of times of writing the file name reaches a fourth preset number.
Based on the method for implementing data backup provided by the foregoing method embodiment, an embodiment of the present application further provides a device for implementing data backup, including: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is used for storing one or more programs, the one or more programs comprising instructions, which when executed by the processor, cause the processor to perform the method of the above embodiment.
Based on the method for implementing data backup provided in the foregoing method embodiment, an embodiment of the present application also provides a computer-readable storage medium, where an instruction is stored in the computer-readable storage medium, and when the instruction runs on a terminal device, the terminal device is caused to execute the method described in the foregoing embodiment.
It should be noted that, in the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the system or the device disclosed by the embodiment, the description is simple because the system or the device corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for implementing data backup, the method comprising:
acquiring a first data table comprising data to be written from a cache region of a main cluster, and establishing a second data table of a standby cluster according to the first data table;
acquiring a third data table from the storage area of the main cluster, wherein the third data table is established by writing data to be written in the first data table into the main cluster;
comparing whether the service data in the third data table is consistent with the backup data in the second data table;
if the service data are inconsistent with the backup data, taking the data in the service data, which is different from the backup data, as distinguishing data;
and acquiring a target storage file corresponding to the distinguishing data from the storage area of the main cluster, and writing the distinguishing data into the second data table by using the target storage file.
2. The method according to claim 1, wherein the obtaining a target storage file corresponding to the difference data from the storage area of the main cluster, and writing the difference data into the second data table by using the target storage file comprises:
acquiring a target data identifier corresponding to the distinguishing data from the third data table;
determining target file information of a target storage file according to the target data identifier, and generating task information by using the target file information;
taking a data table with distinguishing data in the third data table as a first distinguishing data table;
acquiring a target storage file by using a target data identifier corresponding to the distinguishing data in the first distinguishing data table;
establishing a synchronous task by using the task information and the target storage file;
judging whether the synchronous task is successfully established; if so, calling a synchronization tool to execute the synchronization task so that the synchronization tool writes the distinguishing data into a second distinguishing data table according to the target storage file; the second distinguishing data table is a data table corresponding to the first distinguishing data table in the second data table.
3. The method according to claim 2, wherein the obtaining the target storage file by using the target data identifier corresponding to the distinguishing data in the first distinguishing data table comprises:
acquiring a target data identifier of the first distinguishing data from the first distinguishing data table;
if the acquisition is successful, scanning a file storage area corresponding to the first distinguishing data table from the first distinguishing data according to the target data identification to acquire a target storage file corresponding to the distinguishing data;
and if the acquisition is unsuccessful, scanning the file storage area corresponding to the first distinguishing data table to acquire a target storage file.
4. The method of claim 2, wherein after said establishing a synchronization task using said task information and said target storage file, said method further comprises:
if the synchronous task is not successfully established, establishing the synchronous task again according to the task information and the target storage file;
and returning to execute the steps of judging whether the synchronous task is successfully established and the subsequent steps until the synchronous task is successfully established or the number of times of establishing the synchronous task reaches a first preset number.
5. The method of claim 4, wherein if the number of times the sync task is established reaches a first predetermined number of times, the method further comprises:
acquiring a file name of the target storage file, and writing the file name into a first backup failure file directory;
obtaining a file name writing result, and judging whether writing the file name into a first backup failure file directory is successful or not;
if not, writing the file name into the first backup failure file directory again;
and returning and executing the obtained file name writing result, judging whether the file name is successfully written into the first backup failure file directory or not, and performing the subsequent steps until the file name is successfully written into the first backup failure file directory or the number of times of writing the file name reaches a second preset number.
6. The method according to claim 1, wherein after the obtaining of the target storage file corresponding to the difference data and the writing of the difference data into the second data table by using the target storage file, the method further comprises:
acquiring a data writing result, and determining whether the distinguishing data is successfully written into the second data table according to the data writing result;
if the data is unsuccessful, the target storage file is reused to write the distinguishing data into the second data table;
and returning to execute the obtained data writing result, determining whether the distinguishing data is successfully written into the second data table according to the data writing result, and performing subsequent steps until the distinguishing data is successfully written into the second data table, or the number of times of writing the distinguishing data into the second data table reaches a third preset number.
7. The method of claim 6, wherein if the number of times the difference data is written into the second data table reaches a third predetermined number, the method further comprises:
acquiring a file name of the target storage file, and writing the file name into a second backup failure file directory;
obtaining a file name writing result, and judging whether writing the file name into a second backup failure file directory is successful or not;
if not, writing the file name into the second backup failure file directory again;
and returning and executing the obtained file name writing result, judging whether the file name is successfully written into the second backup failure file directory or not, and performing the subsequent steps until the file name is successfully written into the second backup failure file directory or the number of times of writing the file name reaches a fourth preset number.
8. An apparatus for implementing data backup, the apparatus comprising:
the device comprises a first acquisition unit, a second acquisition unit and a first storage unit, wherein the first acquisition unit is used for acquiring a first data table containing data to be written from a cache region of a main cluster and establishing a second data table of a standby cluster according to the first data table;
a second obtaining unit, configured to obtain a third data table from a storage area of the main cluster, where the third data table is created by writing data to be written in the first data table into the main cluster;
the comparison unit is used for comparing whether the service data in the third data table is consistent with the backup data in the second data table;
a determining unit, configured to, if the service data is inconsistent with the backup data, use data different from the backup data in the service data as distinguishing data;
a first writing unit, configured to obtain a target storage file corresponding to the difference data from the storage area of the main cluster, and write the difference data into the second data table by using the target storage file.
9. An apparatus for implementing data backup, comprising: a processor, a memory, a system bus;
the processor and the memory are connected through the system bus;
the memory is to store one or more programs, the one or more programs comprising instructions, which when executed by the processor, cause the processor to perform the method of any of claims 1-7.
10. A computer-readable storage medium having stored therein instructions that, when executed on a terminal device, cause the terminal device to perform the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011640262.6A CN112631839A (en) | 2020-12-31 | 2020-12-31 | Method, device and equipment for realizing data backup |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011640262.6A CN112631839A (en) | 2020-12-31 | 2020-12-31 | Method, device and equipment for realizing data backup |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112631839A true CN112631839A (en) | 2021-04-09 |
Family
ID=75290485
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011640262.6A Pending CN112631839A (en) | 2020-12-31 | 2020-12-31 | Method, device and equipment for realizing data backup |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631839A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113064909A (en) * | 2021-06-03 | 2021-07-02 | 广州宸祺出行科技有限公司 | Data synchronization verification method and device |
| CN115361269A (en) * | 2022-07-08 | 2022-11-18 | 福建新大陆通信科技股份有限公司 | Hot backup method for emergency broadcasting equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160203201A1 (en) * | 2015-01-14 | 2016-07-14 | Alibaba Group Holding Limited | Data backup method and apparatus |
| CN106502840A (en) * | 2016-10-25 | 2017-03-15 | 广东欧珀移动通信有限公司 | A kind of data back up method, apparatus and system |
| CN108123976A (en) * | 2016-11-30 | 2018-06-05 | 阿里巴巴集团控股有限公司 | Data back up method, apparatus and system between cluster |
| CN111880956A (en) * | 2020-07-24 | 2020-11-03 | 北京达佳互联信息技术有限公司 | Data synchronization method and device |
-
2020
- 2020-12-31 CN CN202011640262.6A patent/CN112631839A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160203201A1 (en) * | 2015-01-14 | 2016-07-14 | Alibaba Group Holding Limited | Data backup method and apparatus |
| CN106502840A (en) * | 2016-10-25 | 2017-03-15 | 广东欧珀移动通信有限公司 | A kind of data back up method, apparatus and system |
| CN108123976A (en) * | 2016-11-30 | 2018-06-05 | 阿里巴巴集团控股有限公司 | Data back up method, apparatus and system between cluster |
| CN111880956A (en) * | 2020-07-24 | 2020-11-03 | 北京达佳互联信息技术有限公司 | Data synchronization method and device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113064909A (en) * | 2021-06-03 | 2021-07-02 | 广州宸祺出行科技有限公司 | Data synchronization verification method and device |
| CN115361269A (en) * | 2022-07-08 | 2022-11-18 | 福建新大陆通信科技股份有限公司 | Hot backup method for emergency broadcasting equipment |
| CN115361269B (en) * | 2022-07-08 | 2023-05-30 | 福建新大陆通信科技股份有限公司 | Hot backup method for emergency broadcasting equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107291787B (en) | Main and standby database switching method and device | |
| US9753954B2 (en) | Data node fencing in a distributed file system | |
| US8650272B2 (en) | Distributed transaction processing system having resource managers that collaborate to decide whether to commit or abort a transaction in response to failure of a transaction manager | |
| CN111124755A (en) | Cluster node fault recovery method and device, electronic equipment and storage medium | |
| CN112631839A (en) | Method, device and equipment for realizing data backup | |
| CN110677280B (en) | Service node switching method, device, equipment and computer readable storage medium | |
| US5301311A (en) | Control method for preventing incorrect reset of common resource and multicomputer system executing the method | |
| CN107016016B (en) | Data processing method and device | |
| CN107870982B (en) | Data processing method, system and computer readable storage medium | |
| CN111309524A (en) | Distributed storage system fault recovery method, device, terminal and storage medium | |
| CN112181720A (en) | Virtual data center backup method and device based on cloud management platform | |
| CN109165112B (en) | Fault recovery method, system and related components of metadata cluster | |
| CN111240892A (en) | Data backup method and device | |
| US8612799B2 (en) | Method and apparatus of backing up subversion repository | |
| US10372682B2 (en) | Maintaining data integrity | |
| CN108733808B (en) | Big data software system switching method, system, terminal equipment and storage medium | |
| CN111159298B (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN108959548B (en) | Service request processing method and device | |
| CN113596195B (en) | Public IP address management method, device, main node and storage medium | |
| CN111226200B (en) | Method, device and distributed system for creating consistent snapshot for distributed application | |
| CN114756408A (en) | Metadata backup recovery method and device, electronic equipment and storage medium | |
| CN115827657A (en) | Database data synchronization method, storage medium and device | |
| CN111209138A (en) | Operation and maintenance method and device of data storage system | |
| CN111427718B (en) | File backup method, file recovery method and file recovery device | |
| CN113806309A (en) | Metadata deleting method, system, terminal and storage medium based on distributed lock |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |