CN111258814B - Database backup fault tolerance method, system, terminal and storage medium - Google Patents
Database backup fault tolerance method, system, terminal and storage medium Download PDFInfo
- Publication number
- CN111258814B CN111258814B CN202010033225.2A CN202010033225A CN111258814B CN 111258814 B CN111258814 B CN 111258814B CN 202010033225 A CN202010033225 A CN 202010033225A CN 111258814 B CN111258814 B CN 111258814B
- Authority
- CN
- China
- Prior art keywords
- time
- data
- backup
- log
- filing
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a database backup fault-tolerant method, a system, a terminal and a storage medium, comprising the following steps: setting backup waiting time; receiving and caching an archiving log of a main library, and recording the caching time of the archiving log; judging whether the cache time reaches the backup waiting time: and if so, updating corresponding data of the backup database according to the filing log. The invention can improve the fault tolerance of the backup database and effectively avoid the problem that important data cannot be recovered due to misoperation of the main database on the premise of ensuring data synchronization.
Description
Technical Field
The invention relates to the technical field of data storage, in particular to a database backup fault tolerance method, a database backup fault tolerance system, a database backup fault tolerance terminal and a database backup fault tolerance storage medium.
Background
The Dataguard is a high availability scheme commonly used by oracle databases, the data of a main library is synchronized to a standby library, and the common synchronization method is that the filing logs of the main library are automatically synchronized to the standby library, and the standby library applies the filing logs to realize the synchronization of the data of the main library and the standby library. After the primary and secondary libraries normally complete the first synchronous configuration, the newly generated filing log of the primary library is automatically synchronized to the host of the secondary library, and then the secondary library applies the filing log synchronized by the primary library, so that the data of the secondary library and the primary library can basically keep quasi-real-time consistency. Any operation (whether right or wrong) performed by the main library is synchronously provided for the standby library through the Dataguard function, when some error operations are performed on the main library, such as deleting table data, deleting tables and the like, the standby library also performs corresponding operations, and the standby library cannot distinguish which correct ones are incorrect, so that data before the error operations cannot be obtained in the standby library through a simple method, the database backup may be required to be used for recovering the database to find back the data before the error operations, and the process takes a long time and has a large influence on services.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, the present invention provides a database backup fault tolerance method, system, terminal and storage medium, so as to solve the above-mentioned technical problems.
In a first aspect, the present invention provides a fault-tolerant method for database backup, including:
setting backup waiting time;
receiving and caching an archiving log of a main library, and recording the caching time of the archiving log;
judging whether the cache time reaches the backup waiting time:
and if so, updating corresponding data of the backup database according to the filing log.
Further, the recording the cache time of the archive log comprises:
reading the SCN number of the filing log;
looking up the starting time corresponding to the SCN number in a sys _ scon _ time table;
collecting the current time of the system;
and calculating the time difference between the current time and the starting time, and outputting the time difference as the buffer time.
Further, the updating the corresponding data of the backup library according to the filing log includes:
reading the update data and the data position in the filing log;
positioning data to be replaced in the standby database according to the data position;
and replacing the data to be replaced by the updating data.
Further, the method further comprises:
receiving a data calling command from a main library;
searching backup data and a corresponding filing log in a backup database according to the data calling command;
extracting the update data in the corresponding archive log;
marking the creation time of the backup data and the update data respectively;
and outputting the backup data and the updating data with the creation time marks.
In a second aspect, the present invention provides a database backup fault tolerance system, including:
a time setting unit configured to set a backup waiting time;
the time recording unit is configured for receiving and caching the filing log of the master library and recording the caching time of the filing log;
the time judging unit is configured to judge whether the cache time reaches the backup waiting time;
and the updating execution unit is configured to update corresponding data of the backup library according to the filing log if the caching time reaches the backup waiting time.
Further, the time recording unit includes:
the information reading module is configured for reading the SCN number of the filing log;
the time conversion module is configured to query a start time corresponding to the SCN number in a sys.smon _ SCN _ time table;
the time acquisition module is configured for acquiring the current time of the system;
and the time difference making module is configured to calculate the time difference between the current time and the starting time and output the time difference as the cache time.
Further, the update execution unit includes:
the log reading module is configured to read the update data and the data position in the filing log;
the replacement positioning module is configured to position the data to be replaced in the standby database according to the data position;
and the replacement execution module is configured to replace the data to be replaced with the updated data.
Further, the system further comprises:
the command receiving unit is configured to receive a data calling command from the master library;
the backup searching unit is configured to search backup data and corresponding filing logs in the backup library according to the data calling command;
a data extraction unit configured to extract update data in the corresponding archive log;
a time marking unit configured to mark creation times of the backup data and the update data, respectively;
and the data output unit is configured to output the backup data with the creation time stamp and the update data.
In a third aspect, a terminal is provided, including:
a processor, a memory, wherein,
the memory is used for storing a computer program which,
the processor is used for calling and running the computer program from the memory so as to make the terminal execute the method of the terminal.
In a fourth aspect, a computer storage medium is provided having stored therein instructions that, when executed on a computer, cause the computer to perform the method of the above aspects.
The beneficial effect of the invention is that,
the database backup fault-tolerant method, the system, the terminal and the storage medium provided by the invention have the advantages that the backup waiting time is set, a time difference is kept between the backup database and the main database during data updating, the cache time of the filing log received by the backup database from the main database is recorded, and after the cache time reaches the preset waiting time, the corresponding data of the backup database is updated according to the content of the filing log. The invention can improve the fault tolerance of the backup database and effectively avoid the problem that important data cannot be recovered due to misoperation of the main database on the premise of ensuring data synchronization.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention.
FIG. 2 is a schematic block diagram of a system of one embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The following explains key terms appearing in the present invention.
SCN: (System Change Number SCN) is a Number that is automatically maintained by the DBMS to accumulate increments after the Oracle database is updated.
FIG. 1 is a schematic flow diagram of a method of one embodiment of the invention. The execution subject in fig. 1 may be a database backup fault tolerant system.
As shown in fig. 1, the method 100 includes:
and 140, if yes, updating corresponding data of the backup database according to the filing log.
In order to facilitate understanding of the present invention, the database backup fault-tolerant method provided by the present invention is further described below by using the principle of the database backup fault-tolerant method of the present invention and combining the process of performing fault-tolerant design on the database backup in the embodiment.
Specifically, the database backup fault tolerance method includes:
and S1, setting the backup waiting time.
Setting backup waiting time according to the needs of users, wherein the waiting time can be flexibly adjusted to take effect at any time according to needs, such as: when the master library deletes one table by mistake, and the parameter "master-slave library time difference" is set to 120 (i.e. 2 hours), that is, the slave library will execute the operation of deleting the table after two hours. If the table and the data are obtained in the shortest time in order to make the data in the table in the latest state as possible, the application of the backup library to the archive log needs to be accelerated, and the application of the backup library to the archive log can be accelerated by shortening the backup waiting time.
And S2, receiving and caching the archive log of the master library, and recording the caching time of the archive log.
And after the data of the main library is updated, an archive log is generated and sent to the standby library. The archive log generated by the master library for each update has an SCN number that is automatically maintained by the DBMS to accumulate an incremental number. Each SCN corresponds to a time, the two are in one-to-one correspondence, the correspondence between the SCN and the time is stored in a sys.
Therefore, after receiving the filing log of the master library, caching the filing log, extracting the SCN number of the filing log, and searching the time corresponding to the extracted SCN number in the sys. And collecting the current time of the database management end system, calculating the time difference between the current time and the starting time, and recording the time difference as the cache time.
S3, judging whether the cache time reaches the backup waiting time: and if so, updating corresponding data of the backup database according to the filing log.
Judging whether the cache time obtained in the step S2 reaches the waiting time set in the step S1, if so, executing the following steps:
and reading the updating data and the data position in the filing log, positioning the data to be replaced in the standby database according to the data position, and replacing the data to be replaced in the standby database by using the updating data. And deleting the archiving log after the replacement is completed.
If a data calling command from the main library is received, the backup data and the corresponding filing log in the standby library are searched according to the data calling command, wherein if the caching time of the corresponding filing log does not reach the waiting time, the backup data and the corresponding filing log can be searched, and if the caching time of the corresponding filing log reaches the waiting time and data replacement is completed, the corresponding filing log is already cleared and cannot be searched.
If the corresponding filing log can be found, extracting the updating data in the corresponding filing log, respectively marking the creation time of the backup data and the updating data, and outputting the backup data and the updating data with the creation time marks.
If the corresponding filing log cannot be searched, only the searched backup data is output.
As shown in fig. 2, the system 200 includes:
a time setting unit 210 configured to set a backup waiting time;
the time recording unit 220 is configured to receive and cache the archive log of the master library, and record the cache time of the archive log;
a time determining unit 230 configured to determine whether the cache time reaches the backup waiting time;
and the update executing unit 240 is configured to update the corresponding data of the backup repository according to the archive log if the caching time reaches the backup waiting time.
Optionally, as an embodiment of the present invention, the time recording unit includes:
the information reading module is configured for reading the SCN number of the filing log;
the time conversion module is configured to query a start time corresponding to the SCN number in a sys.smon _ SCN _ time table;
the time acquisition module is configured for acquiring the current time of the system;
and the time difference making module is configured to calculate the time difference between the current time and the starting time and output the time difference as the cache time.
Optionally, as an embodiment of the present invention, the update performing unit includes:
the log reading module is configured to read the update data and the data position in the filing log;
the replacement positioning module is configured to position the data to be replaced in the standby database according to the data position;
and the replacement execution module is configured to replace the data to be replaced with the updated data.
Optionally, as an embodiment of the present invention, the system further includes:
the command receiving unit is configured to receive a data calling command from the master library;
the backup searching unit is configured to search backup data and corresponding filing logs in the backup library according to the data calling command;
a data extraction unit configured to extract update data in the corresponding archive log;
a time marking unit configured to mark creation times of the backup data and the update data, respectively;
and the data output unit is configured to output the backup data with the creation time stamp and the update data.
Fig. 3 is a schematic structural diagram of a terminal system 300 according to an embodiment of the present invention, where the terminal system 300 may be used to execute the database backup fault tolerance method according to the embodiment of the present invention.
The terminal system 300 may include: a processor 310, a memory 320, and a communication unit 330. The components communicate via one or more buses, and those skilled in the art will appreciate that the architecture of the servers shown in the figures is not intended to be limiting, and may be a bus architecture, a star architecture, a combination of more or less components than those shown, or a different arrangement of components.
The memory 320 may be used for storing instructions executed by the processor 310, and the memory 320 may be implemented by any type of volatile or non-volatile storage terminal or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The executable instructions in memory 320, when executed by processor 310, enable terminal 300 to perform some or all of the steps in the method embodiments described below.
The processor 310 is a control center of the storage terminal, connects various parts of the entire electronic terminal using various interfaces and lines, and performs various functions of the electronic terminal and/or processes data by operating or executing software programs and/or modules stored in the memory 320 and calling data stored in the memory. The processor may be composed of an Integrated Circuit (IC), for example, a single packaged IC, or a plurality of packaged ICs connected with the same or different functions. For example, the processor 310 may include only a Central Processing Unit (CPU). In the embodiment of the present invention, the CPU may be a single operation core, or may include multiple operation cores.
A communication unit 330, configured to establish a communication channel so that the storage terminal can communicate with other terminals. And receiving user data sent by other terminals or sending the user data to other terminals.
The present invention also provides a computer storage medium, wherein the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a Random Access Memory (RAM).
Therefore, the backup waiting time is set, a time difference is kept between the data updating of the backup library and the data updating of the main library, the cache time of the filing log received by the backup library from the main library is recorded, and when the cache time reaches the preset waiting time, the corresponding data of the backup library is updated according to the content of the filing log. The invention can improve the fault tolerance of the backup database, and effectively avoid the problem that important data cannot be recovered due to misoperation of the main database on the premise of ensuring data synchronization.
Those skilled in the art will readily appreciate that the techniques of the embodiments of the present invention may be implemented as software plus a required general purpose hardware platform. Based on such understanding, the technical solutions in the embodiments of the present invention may be embodied in the form of a software product, where the computer software product is stored in a storage medium, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like, and the storage medium can store program codes, and includes instructions for enabling a computer terminal (which may be a personal computer, a server, or a second terminal, a network terminal, and the like) to perform all or part of the steps of the method in the embodiments of the present invention.
The same and similar parts in the various embodiments in this specification may be referred to each other. Especially, for the terminal embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description in the method embodiment.
In the several embodiments provided in the present invention, it should be understood that the disclosed system and method may be implemented in other manners. For example, the above-described system embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, systems or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (6)
1. A database backup fault tolerance method is characterized by comprising the following steps:
setting backup waiting time;
receiving and caching an archiving log of a main library, and recording the caching time of the archiving log;
judging whether the cache time reaches the backup waiting time:
if yes, updating corresponding data of the backup database according to the filing log;
the updating the corresponding data of the backup database according to the filing log comprises the following steps:
reading the update data and the data position in the filing log;
positioning data to be replaced in the standby database according to the data position;
replacing the data to be replaced by the updating data;
if a data calling command from the main library is received, searching backup data and corresponding filing logs in the standby library according to the data calling command, wherein if the caching time of the corresponding filing logs does not reach the waiting time, the backup data and the corresponding filing logs can be searched, and if the caching time of the corresponding filing logs reaches the waiting time and data replacement is completed, the corresponding filing logs are already cleared and cannot be searched;
if the corresponding filing log can be found, extracting the updating data in the corresponding filing log, respectively marking the creation time of the backup data and the updating data, and outputting the backup data and the updating data with the creation time marks; and if the corresponding filing log cannot be searched, only the searched backup data is output.
2. The method of claim 1, wherein recording the cache time of the archive log comprises:
reading the SCN number of the filing log;
looking up the starting time corresponding to the SCN number in a sys _ scon _ time table;
collecting the current time of the system;
and calculating the time difference between the current time and the starting time, and outputting the time difference as the buffer time.
3. A database backup fault tolerance system, comprising:
a time setting unit configured to set a backup waiting time;
the time recording unit is configured for receiving and caching the filing log of the master library and recording the caching time of the filing log;
the time judging unit is configured to judge whether the cache time reaches the backup waiting time;
the updating execution unit is configured to update corresponding data of the backup library according to the filing log if the caching time reaches the backup waiting time;
the update execution unit includes:
the log reading module is configured to read the update data and the data position in the filing log;
the replacement positioning module is configured to position the data to be replaced in the standby database according to the data position;
the replacement execution module is configured to replace the data to be replaced with the updated data;
the system is further configured to:
if a data calling command from the main library is received, searching backup data and corresponding filing logs in the standby library according to the data calling command, wherein if the caching time of the corresponding filing logs does not reach the waiting time, the backup data and the corresponding filing logs can be searched, and if the caching time of the corresponding filing logs reaches the waiting time and data replacement is completed, the corresponding filing logs are already cleared and cannot be searched;
if the corresponding filing log can be found, extracting the updating data in the corresponding filing log, respectively marking the creation time of the backup data and the updating data, and outputting the backup data and the updating data with the creation time marks; and if the corresponding filing log cannot be searched, only the searched backup data is output.
4. The system of claim 3, wherein the time recording unit comprises:
the information reading module is configured for reading the SCN number of the filing log;
the time conversion module is configured to query a start time corresponding to the SCN number in a sys.smon _ SCN _ time table;
the time acquisition module is configured for acquiring the current time of the system;
and the time difference making module is configured to calculate the time difference between the current time and the starting time and output the time difference as the cache time.
5. A terminal, comprising:
a processor;
a memory for storing instructions for execution by the processor;
wherein the processor is configured to perform the method of any of claims 1-2.
6. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010033225.2A CN111258814B (en) | 2020-01-13 | 2020-01-13 | Database backup fault tolerance method, system, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010033225.2A CN111258814B (en) | 2020-01-13 | 2020-01-13 | Database backup fault tolerance method, system, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258814A CN111258814A (en) | 2020-06-09 |
| CN111258814B true CN111258814B (en) | 2022-08-05 |
Family
ID=70952787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010033225.2A Active CN111258814B (en) | 2020-01-13 | 2020-01-13 | Database backup fault tolerance method, system, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258814B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002021273A2 (en) * | 2000-09-08 | 2002-03-14 | Storage Technology Corporation | Self archiving log structured volume with intrinsic data protection |
| CN105095245A (en) * | 2014-05-04 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Filing log synchronizing method and system based on relevance database |
| CN107145499A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | The method and apparatus filed for ahead daily record |
-
2020
- 2020-01-13 CN CN202010033225.2A patent/CN111258814B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002021273A2 (en) * | 2000-09-08 | 2002-03-14 | Storage Technology Corporation | Self archiving log structured volume with intrinsic data protection |
| CN105095245A (en) * | 2014-05-04 | 2015-11-25 | 阿里巴巴集团控股有限公司 | Filing log synchronizing method and system based on relevance database |
| CN107145499A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | The method and apparatus filed for ahead daily record |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258814A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3435235B1 (en) | Method and device for executing data recovery operation | |
| CN109241175A (en) | Method of data synchronization, device, storage medium and electronic equipment | |
| CN110795287B (en) | Data recovery method, system, electronic equipment and computer storage medium | |
| EP3474143B1 (en) | Method and apparatus for incremental recovery of data | |
| CN109298978B (en) | Recovery method and system for database cluster of specified position | |
| EP4579475A1 (en) | Data processing method and apparatus | |
| CN111639132B (en) | Log synchronization method and device | |
| CN115408200A (en) | Data backup method, device, electronic equipment and storage medium for multiple storage engines | |
| CN109960602B (en) | Information management method, device, equipment and medium | |
| CN112612775B (en) | Data storage method, device, computer equipment and storage medium | |
| CN111400101B (en) | Data recovery method and system for deleting JFS2 file system data | |
| CN113419897A (en) | File processing method and device, electronic equipment and storage medium thereof | |
| CN111258814B (en) | Database backup fault tolerance method, system, terminal and storage medium | |
| CN112685431B (en) | Asynchronous caching method, device, system, electronic equipment and storage medium | |
| CN110554992B (en) | Distributed metadata path management method, system, terminal and storage medium | |
| WO2021082925A1 (en) | Transaction processing method and apparatus | |
| CN110147355B (en) | Data synchronization method, device and server | |
| CN108614838B (en) | User group index processing method, device and system | |
| CN117131135A (en) | A data synchronization verification method, device, equipment and storage medium | |
| CN112632191B (en) | Data processing method and system | |
| CN116737461A (en) | File data backup method, system and storage medium | |
| CN111209138A (en) | Operation and maintenance method and device of data storage system | |
| CN117609209B (en) | Data recovery method, data recovery device, data recovery equipment, and storage medium | |
| CN115168388A (en) | A method and device for generating reverse SQL statement | |
| CN114254047A (en) | Data synchronization method, system, terminal and storage medium of distributed database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Patentee after: Suzhou Yuannao Intelligent Technology Co.,Ltd. Country or region after: China Address before: Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Patentee before: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Country or region before: China |
|
| CP03 | Change of name, title or address |