CN114253770B - Master-slave backup system of database - Google Patents
Master-slave backup system of database Download PDFInfo
- Publication number
- CN114253770B CN114253770B CN202111551558.5A CN202111551558A CN114253770B CN 114253770 B CN114253770 B CN 114253770B CN 202111551558 A CN202111551558 A CN 202111551558A CN 114253770 B CN114253770 B CN 114253770B
- Authority
- CN
- China
- Prior art keywords
- database
- database server
- slave
- master
- data
- 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
- 238000000034 method Methods 0.000 claims abstract description 51
- 230000008569 process Effects 0.000 claims abstract description 36
- 238000012545 processing Methods 0.000 claims abstract description 21
- 230000010076 replication Effects 0.000 claims abstract description 21
- 230000007246 mechanism Effects 0.000 claims abstract description 18
- 238000009825 accumulation Methods 0.000 claims abstract description 4
- 230000008859 change Effects 0.000 claims abstract description 4
- 230000015654 memory Effects 0.000 claims description 10
- 230000001360 synchronised effect Effects 0.000 claims description 9
- 239000003795 chemical substances by application Substances 0.000 claims description 4
- 238000011084 recovery Methods 0.000 claims description 4
- 238000013500 data storage Methods 0.000 abstract description 2
- 238000009826 distribution Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000000926 separation method Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005315 distribution function Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/275—Synchronous replication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Computational Linguistics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a master-slave backup system of a database, which comprises: the system comprises a master database server and a plurality of slave database servers, wherein the master database server is used for receiving the table structure change DLL operation of the database by the service end, and the slave database server is used for receiving the query DML operation of the data by the service end; the master database server and the slave database server are respectively provided with a cache layer and a database synchronization layer, and the cache layer and the database synchronization layer are respectively connected with the service end data; the cache layer is used for starting a first master-slave replication mechanism to process first type of service data, when a service end does not read the required service data in the cache layer, the database synchronization layer is read, the reading operation is counted, and after the counting accumulation exceeds a set value, the service data is updated in the cache layer; and the database synchronization layer is used for starting a second master-slave replication mechanism to process the second class of service data. The invention improves the processing efficiency of the database by providing a plurality of data storage modes.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a master-slave backup system of a database.
Background
Currently, in project or website design, a master-slave backup of a database is often required. In a production environment, in order to prevent data loss caused by server fault accidents or various sudden crisis conditions, a master-slave backup is made on a database by creating a master database slave database. At least two servers are prepared, one is a master database server, the other is a slave database server, and the master database server can be switched to the slave database server to work continuously after the master database server fails to serve as a backup database, so that data loss is avoided.
However, the existing database master-slave backup method has time delay in master-slave backup of the database, and has higher service requirement on database instantaneity, thereby seriously affecting the consistency of data.
Disclosure of Invention
In view of the above problems, the present invention aims to provide a master-slave backup system of a database, which improves the processing speed of a big data service and the processing efficiency of the database by providing multiple data storage modes.
The invention aims to achieve the aim, and the aim is achieved by the following technical scheme: a master-slave backup system for a database, comprising: the system comprises a master database server and a plurality of slave database servers, wherein the master database server is used for receiving the table structure change DLL operation of the database by the service end, and the slave database server is used for receiving the query DML operation of the data by the service end; the master database server and the slave database server are respectively provided with a cache layer and a database synchronization layer, and the cache layer and the database synchronization layer are respectively connected with the service end data; the cache layer is arranged in the memories of the master database server and the slave database server and is used for starting a first master-slave replication mechanism to process first service data, when a service end does not read the required service data in the cache layer, the service end reads the service data from the database synchronization layer, counts the read operation, and updates the service data into the cache layer after the count accumulation exceeds a set value; the database synchronization layer is arranged in the hard disks of the master database server and the slave database server and is used for starting a second master-slave replication mechanism to process second-class service data.
Further, the first master-slave replication mechanism includes:
initializing a master database server and a slave database server at a cache layer;
the master database server synchronizes the write operation of the service end to the slave database server.
Further, the initializing the master database server and the slave database server at the cache layer specifically includes:
the slave database server sends a synchronous command to the master database server to request synchronous connection;
the main database server receives the synchronous command, the background starts the process, the data snapshot is saved to the data file, and the main database server records all operations for modifying the database;
the master database server continues to record database operation, and simultaneously sends data files to the slave server, and data snapshots of the data files read by the slave database server are saved and loaded into a memory area for database recovery;
the master database server transmits all operation data of the buffer to the slave database server, reads from the database server, and executes in the database.
Further, the main database server records all operations of modifying the database specifically include:
the master database server records all operations that modify the database after saving the data snapshot and saves it to the caching layer.
Further, the database synchronization layer includes:
and the proxy unit is used for judging the request data and sending the request data to the master database server or the slave database server according to the type of the request data.
Further, the second master-slave replication mechanism includes:
the agent unit is used for distributing the request data;
and carrying out master-slave backup of the database by using the log file.
Further, the distributing of the request data by the proxy unit includes:
the agent unit judges the type of the request data after receiving the request data;
if the request data is a write operation, the request data is sent to a main database server;
if the request data is read operation, judging the corresponding service type, and sending the service type to the corresponding slave database server according to the service type.
Further, the master-slave backup of the database by using the log file includes:
the master database server records the database operation to the log file in series;
starting a read-write process from a database server, and copying the log file to a relay log of the database server;
the slave database server starts the SQL procedure, executes the relay log, and applies the update to the current slave database server.
Further, the step of starting a read-write process from the database server and copying the log file to the own relay log specifically includes:
and starting a read-write process from the database server, reading a log file of the main database server through the I/O process, and copying the log file to a relay log of the main database server.
Further, the first type of service data is service data with processing frequency higher than a preset frequency threshold, and the second type of service data is service data with processing frequency lower than the preset frequency threshold.
Compared with the prior art, the invention has the beneficial effects that: the invention discloses a master-slave backup system of a database, which improves the existing master-slave backup mode, layers the architecture, increases a buffer layer processing mode for frequent data service, and for common service, processes the read-write separation mode for the database according to the processing speed of write service being slower than that of read service.
It can be seen that the present invention has outstanding substantial features and significant advances over the prior art, as well as the benefits of its implementation.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a system configuration diagram of a first embodiment of the present invention.
Fig. 2 is a schematic diagram of the system operation according to the second embodiment of the present invention.
Fig. 3 is a schematic diagram of a master-slave copy process of a cache layer according to a second embodiment of the present invention.
FIG. 4 is a schematic diagram of a master-slave replication process of a database distribution layer according to a second embodiment of the present invention.
Detailed Description
The core of the invention is to provide a master-slave backup system of a database, and the existing master-slave backup method of the database has delay in master-slave backup of the database, has higher service requirement on real-time performance of the database, and seriously affects the consistency of data.
The master-slave backup system of the database provided by the invention improves the existing master-slave backup mode, and defines a two-layer architecture: a caching layer and a database synchronization layer. By classifying the services, the first layer realizes frequent service processing and reading in the cache layer, the second layer establishes a master multi-slave architecture mode in the database synchronization layer, firstly separates read-write data into master and slave database servers for operation respectively, and then deploys different slave database servers according to different service functions, thereby realizing real-time backup of the database and avoiding the problem of asynchronous service caused by backup delay.
In order to better understand the aspects of the present invention, the present invention will be described in further detail with reference to the accompanying drawings and detailed description. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Embodiment one:
as shown in fig. 1, this embodiment provides a master-slave backup system of a database, including: the system comprises a master database server and a plurality of slave database servers, wherein the master database server is used for receiving the table structure change DLL operation of the database by the service end, and the slave database server is used for receiving the query DML operation of the data by the service end; the master database server and the slave database server are respectively provided with a cache layer and a database synchronization layer, and the cache layer and the database synchronization layer are respectively connected with the service end data.
And the cache layer is arranged in the memories of the master database server and the slave database server and is used for starting a first master-slave replication mechanism to process the first type of service data, when the service end does not read the required service data in the cache layer, the service end reads the service data from the database synchronization layer, counts the read operation, and updates the service data into the cache layer after the count accumulation exceeds a set value.
The database synchronization layer is arranged in the hard disks of the master database server and the slave database server and is used for starting a second master-slave replication mechanism to process the second type of service data. The first type of service data is service data with processing frequency higher than a preset frequency threshold value, and the second type of service data is service data with processing frequency lower than the preset frequency threshold value.
After the first master-slave replication mechanism is started by the cache layer, the initialization of the master database server and the slave database server is firstly carried out on the cache layer. The master database server then synchronizes the write operations of the service side to the slave database server.
As an example, the execution of the first master-slave replication mechanism includes the steps of:
1. the slave database server sends a synchronization command to the master database server requesting a synchronization connection.
2. The main database server receives the synchronous command, the background starts the process, the data snapshot is saved to the data file, and the main database server records all operations for modifying the database.
3. And the master database server continues to record database operation, simultaneously sends the data file to the slave server, and the data snapshot of the data file read from the database server is stored and loaded into the memory area for database recovery.
4. The master database server transmits all operation data of the buffer to the slave database server, reads from the database server, and executes in the database.
In the third step, the main database server records all operations of modifying the database specifically include: the master database server records all operations that modify the database after saving the data snapshot and saves it to the caching layer.
As an example, the database synchronization layer also has a data distribution function, and thus, the data synchronization layer further includes a proxy unit for judging the request data, and transmitting the request data to the master database server or the slave database server according to the type of the request data.
When the database synchronization layer starts the second master-slave replication mechanism, the proxy unit is used for distributing the request data. Then, master-slave backup of the database is performed using the log file.
Specifically, the second master-slave replication mechanism is performed as follows:
firstly, judging the type of request data after the proxy unit receives the request data; if the request data is a write operation, the request data is sent to a main database server; if the request data is read operation, judging the corresponding service type, and sending the service type to the corresponding slave database server according to the service type. After the data distribution is completed, the main database server serially records the database operation to a log file; at this time, a read-write process is started from the database server, the log file of the main database server is read through an I/O process, and the log file is copied to a relay log of the main database server; and finally, opening the SQL procedure from the database server, executing the relay log, and applying the update to the current slave database server.
The embodiment provides a master-slave backup system of a database, which improves the existing master-slave backup mode, layers the architecture, increases a buffer layer processing mode for frequent data service, and for common service, processes the read-write separation mode for the database according to the processing speed of write service being slower than that of read service.
Embodiment two:
based on the first embodiment, the invention also discloses a master-slave backup system of the database, which is divided into two layers: a cache layer and a database synchronization layer. As shown in fig. 2, the cache layer processes high-frequency service data, and the database synchronization layer processes normal service data. And the cache layer and the database synchronization layer respectively perform real-time backup. When the application reads the high-frequency service, the cache layer is accessed, if the cache layer fails to find the related service, the database synchronization layer is accessed, the reading operation is counted, and after the accumulated value exceeds the set value, the data is updated into the database of the cache layer. In the database synchronization layer, a master-multi-slave deployment mode is adopted, namely 1 master database server and N slave database servers are deployed according to specific service function division. The main database server is responsible for receiving the operation of the business end for changing the DDL of the table structure of the database, and receiving the operation of the business end for inquiring the DML of the data from the database server.
Specifically, the implementation mechanism of the system is as follows:
1. master-slave replication of the caching layer: the buffer area is located in the memory for reading operation, and the business reads data from the buffer area, so that the data reading and writing efficiency is improved. The buffer takes a master multi-slave mode. The master database server is responsible for writing operations of users, and the slave database server is responsible for receiving reading operations of users.
As shown in fig. 3, the master-slave replication process of the cache layer is specifically as follows:
first, initialization of a cache layer is performed:
(1) The slave database server sends a synchronization command to the master database server requesting a synchronization connection.
(2) The main database server receives the synchronous command, the background starts the process, the data snapshot is saved to the data file, and meanwhile, the main database server records all operations of modifying the database after saving the snapshot and saves the operation to the buffer area.
(3) And the master data server continues to record database operation, simultaneously sends the data file to the slave database server, reads the data file snapshot from the database server, saves the data file snapshot, and loads the data file snapshot into the memory area for database recovery.
(4) The master database server transmits all operation data of the buffer to the slave database server, reads from the database server, and executes in the database. The slave server is initialized up to this point. A read operation from the user may be accepted from the database server.
After the initialization is completed, the master database server synchronizes the writing operation of the user to the slave database server, and the master and slave begin to work normally. Thus, incremental synchronization of the database is realized.
2. Master-slave replication of the database distribution layer. As shown in fig. 4, the master-slave replication process of the database distribution layer is specifically as follows:
first, data distribution is performed. Because the database part is stored in the disk, a master multi-slave service read-write separation mode is adopted, when the service end sends the request data to the built-in proxy unit, the proxy unit judges the request data and sends the request data to different database servers according to different request types. If the read operation is the read operation, judging the service type, and distributing the service type to different slave database servers according to the service type.
Then, a master-slave backup of the database is performed. The method specifically comprises the following three steps:
A. the master database server serially records database operations to the log file.
B. And starting a read-write process from the database server, reading the log file of the main database server through the I/O process, and copying the log file to the self relay log.
C. And opening the SQL procedure from the database server, executing the relay log, and applying the update to the server.
The embodiment provides a master-slave backup system of a database, and a double-layer processing mechanism is established at a database end. And the front client distributes the service, the frequent service is sent to the cache layer for processing, if the cache layer fails to read the related service, the database synchronization layer is read, and the data is written into the cache layer. The database end receives the common business process, and the proxy unit distributes the business. The master database server is responsible for accepting write operations and the slave database server is responsible for accepting read operations. The read operations are distributed to different slave servers depending on the distinction of the traffic types. The database synchronization layer can adopt a read-write separation mode according to different processing time of read-write operation, write operation is distributed to the master database server, and read operation is distributed to the slave database server. Meanwhile, synchronous operation of the master database server and the slave database server is realized.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the method disclosed in the embodiment, since it corresponds to the system disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided by the present invention, it should be understood that the disclosed systems, and methods may be implemented in other ways. For example, the system embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, system or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in the embodiments of the present invention may be integrated in one processing unit, or each module may exist alone physically, or two or more modules may be integrated in one unit.
Similarly, each processing unit in the embodiments of the present invention may be integrated in one functional module, or each processing unit may exist physically, or two or more processing units may be integrated in one functional module.
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. The software modules may be disposed 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.
Finally, it is further noted that relational terms such as first and second, and the like are 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. Moreover, 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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above describes the master-slave backup system of the database provided by the invention in detail. The principles and embodiments of the present invention have been described herein with reference to specific examples, the description of which is intended only to facilitate an understanding of the method of the present invention and its core ideas. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the invention can be made without departing from the principles of the invention and these modifications and adaptations are intended to be within the scope of the invention as defined in the following claims.
Claims (6)
1. A master-slave backup system for a database, comprising: the system comprises a master database server and a plurality of slave database servers, wherein the master database server is used for receiving the table structure change DLL operation of the database by the service end, and the slave database server is used for receiving the query DML operation of the data by the service end;
the master database server and the slave database server are respectively provided with a cache layer and a database synchronization layer, and the cache layer and the database synchronization layer are respectively connected with the service end data;
the cache layer is arranged in the memories of the master database server and the slave database server and is used for starting a first master-slave replication mechanism to process first service data, when a service end does not read the required service data in the cache layer, the service end reads the service data from the database synchronization layer, counts the read operation, and updates the service data into the cache layer after the count accumulation exceeds a set value;
the database synchronization layer is arranged in the hard disks of the master database server and the slave database server and is used for starting a second master-slave replication mechanism to process second-class service data;
the first master-slave replication mechanism includes:
initializing a master database server and a slave database server at a cache layer;
the master database server synchronizes the writing operation of the service end to the slave database server;
the database synchronization layer includes:
the proxy unit is used for judging the request data and sending the request data to the master database server or the slave database server according to the type of the request data;
the second master-slave replication mechanism includes:
the agent unit is used for distributing the request data;
carrying out master-slave backup of the database by using the log file;
the first type of service data is service data with processing frequency higher than a preset frequency threshold value, and the second type of service data is service data with processing frequency lower than the preset frequency threshold value.
2. The master-slave backup system of the database according to claim 1, wherein the initializing of the master database server and the slave database server is performed at the cache layer, specifically comprising:
the slave database server sends a synchronous command to the master database server to request synchronous connection;
the main database server receives the synchronous command, the background starts the process, the data snapshot is saved to the data file, and the main database server records all operations for modifying the database;
the master database server continues to record database operation, and simultaneously sends data files to the slave server, and data snapshots of the data files read by the slave database server are saved and loaded into a memory area for database recovery;
the master database server transmits all operation data of the buffer to the slave database server, reads from the database server, and executes in the database.
3. The master-slave backup system of a database according to claim 2, wherein the master database server record modifies all operations of the database in particular by:
the master database server records all operations that modify the database after saving the data snapshot and saves it to the caching layer.
4. The master-slave backup system of a database according to claim 1, wherein the distributing of the request data by the proxy unit comprises:
the agent unit judges the type of the request data after receiving the request data;
if the request data is a write operation, the request data is sent to a main database server;
if the request data is read operation, judging the corresponding service type, and sending the service type to the corresponding slave database server according to the service type.
5. The master-slave backup system of the database according to claim 1, wherein the master-slave backup of the database using log files comprises:
the master database server records the database operation to the log file in series;
starting a read-write process from a database server, and copying the log file to a relay log of the database server;
the slave database server starts the SQL procedure, executes the relay log, and applies the update to the current slave database server.
6. The master-slave backup system of the database according to claim 5, wherein the slave database server starts a read-write process to copy the log file to the own relay log, and specifically comprises:
and starting a read-write process from the database server, reading a log file of the main database server through the I/O process, and copying the log file to a relay log of the main database server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111551558.5A CN114253770B (en) | 2021-12-17 | 2021-12-17 | Master-slave backup system of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111551558.5A CN114253770B (en) | 2021-12-17 | 2021-12-17 | Master-slave backup system of database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114253770A CN114253770A (en) | 2022-03-29 |
| CN114253770B true CN114253770B (en) | 2023-12-26 |
Family
ID=80792786
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111551558.5A Active CN114253770B (en) | 2021-12-17 | 2021-12-17 | Master-slave backup system of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114253770B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12095862B1 (en) * | 2023-04-06 | 2024-09-17 | Zhejiang Lab | Data processing system and method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591964A (en) * | 2011-12-30 | 2012-07-18 | 北京新媒传信科技有限公司 | Implementation method and device for data reading-writing splitting system |
| CN102622427A (en) * | 2012-02-27 | 2012-08-01 | 杭州闪亮科技有限公司 | Method and system for read-write splitting database |
| CN105302676A (en) * | 2014-07-28 | 2016-02-03 | 浙江大华技术股份有限公司 | Method and apparatus for transmitting host and backup mechanism data of distributed file system |
| CN106874281A (en) * | 2015-12-11 | 2017-06-20 | 北京新媒传信科技有限公司 | Realize the method and apparatus that data base read-write is separate |
| CN107301179A (en) * | 2016-04-14 | 2017-10-27 | 北京京东尚科信息技术有限公司 | The method and apparatus of data base read-write separation |
| CN108509636A (en) * | 2018-04-10 | 2018-09-07 | 浙江知水信息技术有限公司 | It is a kind of to realize that the big data of read and write abruption manages disaster recovery method based on partition table technology |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN111475519A (en) * | 2020-04-01 | 2020-07-31 | 深圳市思迪信息技术股份有限公司 | Data caching method and device |
-
2021
- 2021-12-17 CN CN202111551558.5A patent/CN114253770B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591964A (en) * | 2011-12-30 | 2012-07-18 | 北京新媒传信科技有限公司 | Implementation method and device for data reading-writing splitting system |
| CN102622427A (en) * | 2012-02-27 | 2012-08-01 | 杭州闪亮科技有限公司 | Method and system for read-write splitting database |
| CN105302676A (en) * | 2014-07-28 | 2016-02-03 | 浙江大华技术股份有限公司 | Method and apparatus for transmitting host and backup mechanism data of distributed file system |
| CN106874281A (en) * | 2015-12-11 | 2017-06-20 | 北京新媒传信科技有限公司 | Realize the method and apparatus that data base read-write is separate |
| CN107301179A (en) * | 2016-04-14 | 2017-10-27 | 北京京东尚科信息技术有限公司 | The method and apparatus of data base read-write separation |
| CN108509636A (en) * | 2018-04-10 | 2018-09-07 | 浙江知水信息技术有限公司 | It is a kind of to realize that the big data of read and write abruption manages disaster recovery method based on partition table technology |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN111475519A (en) * | 2020-04-01 | 2020-07-31 | 深圳市思迪信息技术股份有限公司 | Data caching method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114253770A (en) | 2022-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11153380B2 (en) | Continuous backup of data in a distributed data store | |
| JP6777673B2 (en) | In-place snapshot | |
| US11120152B2 (en) | Dynamic quorum membership changes | |
| US9507843B1 (en) | Efficient replication of distributed storage changes for read-only nodes of a distributed database | |
| US11755415B2 (en) | Variable data replication for storage implementing data backup | |
| US10579610B2 (en) | Replicated database startup for common database storage | |
| US10437721B2 (en) | Efficient garbage collection for a log-structured data store | |
| US9842031B1 (en) | Incremental updates to user transaction state at read-only nodes of a distributed database | |
| US10747746B2 (en) | Efficient read replicas | |
| EP2973054B1 (en) | Database system with database engine and separate distributed storage service | |
| US9424140B1 (en) | Providing data volume recovery access in a distributed data store to multiple recovery agents | |
| US9672237B2 (en) | System-wide checkpoint avoidance for distributed database systems | |
| US9280591B1 (en) | Efficient replication of system transactions for read-only nodes of a distributed database | |
| US20140279930A1 (en) | Fast crash recovery for distributed database systems | |
| US10303564B1 (en) | Reduced transaction I/O for log-structured storage systems | |
| US10885023B1 (en) | Asynchronous processing for synchronous requests in a database | |
| US10223184B1 (en) | Individual write quorums for a log-structured distributed storage system | |
| US20240028598A1 (en) | Transaction Processing Method, Distributed Database System, Cluster, and Medium | |
| CN114253770B (en) | Master-slave backup system of database | |
| CN118260362A (en) | Multistage distributed data partition storage method, equipment and medium | |
| CN108241701A (en) | A kind of method for improving MySQL high availability |
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 |