CN111143323B - MPP database management method, device and system - Google Patents
MPP database management method, device and system Download PDFInfo
- Publication number
- CN111143323B CN111143323B CN201911211383.6A CN201911211383A CN111143323B CN 111143323 B CN111143323 B CN 111143323B CN 201911211383 A CN201911211383 A CN 201911211383A CN 111143323 B CN111143323 B CN 111143323B
- Authority
- CN
- China
- Prior art keywords
- backup
- space
- object page
- snapshot
- target
- 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; 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/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- 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
Abstract
The embodiment of the application provides an MPP database management method, device and system, in the backup process of each backup object, a snapshot identifier of each piece of record information in each backup object page corresponding to the backup object is recorded as a snapshot backup identifier, only the modified record information is recorded through a snapshot backup space allocated for the backup object page, the modification state of each backup object page is recorded through a first bitmap space, and the modification state of each piece of record information in the backup object page is recorded through a second bitmap space. Therefore, in the backup process, only modified recording information, snapshot identification and some modification states need to be recorded, backup of a whole amount of data files is not needed, storage space consumed in backup can be effectively saved, time consumed in backup is reduced, influence on upper-layer services is reduced as far as possible, in addition, independent backup can be realized for data objects, and normal service operation of other data objects is not influenced.
Description
Technical Field
The application relates to the technical field of databases, in particular to a method, a device and a system for managing an MPP database.
Background
At present, In a data backup and Recovery scheme for an MPP (Massive Parallel Processing) database, a PITR (Point-In-Time-Recovery, Point-In-Time-based failure Recovery) backup Recovery scheme is generally adopted, In the backup Recovery scheme, a basic backup needs to be performed for backing up a full number of data files at first, and when the data volume of the data files is large, each full-level backup consumes a very large storage space.
In addition, performing the basic backup under the condition of a large amount of data may also result in a large amount of time consumed in the whole backup process, and although the backup recovery scheme may recover to any time point between the start of the backup and the end of the backup, the archived log information may also need to be reapplied, which may also be very time consuming in the reapplication process.
Meanwhile, in the backup and recovery scheme, only the whole backup and recovery of the database can be performed each time, and the backup and recovery of a certain specific object (such as a certain large table) level cannot be realized, so that the flexibility in the whole backup or recovery process is poor.
Disclosure of Invention
In view of this, an object of the present application is to provide an MPP database management method, apparatus and system, which do not need to perform backup of a full amount of data files, can effectively save a storage space consumed during backup, reduce time consumed by backup, reduce influence on upper layer services as much as possible, and can implement separate backup for data objects without influencing normal service operations of other data objects.
According to an aspect of the present application, there is provided an MPP database management method applied to any one of the computing nodes in an MPP database management system, the MPP database management system further including a master node connected to each of the computing nodes, the method including:
determining a corresponding snapshot backup identifier and at least one backup object according to a snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
for each backup object, allocating a corresponding first bitmap space and a snapshot backup space and a second bitmap space corresponding to each backup object page for the backup object, and recording a snapshot identifier of each piece of recorded information in each backup object page corresponding to the backup object as the snapshot backup identifier;
and recording the modification state of each backup object page through the first bitmap space, recording modified record information in the backup object page through the snapshot backup space, and recording the modification state of each record information in the backup object page through the second bitmap space.
According to another aspect of the present application, there is provided an MPP database management apparatus applied to any one of the computing nodes in the MPP database management system, the apparatus including:
the first determining module is used for determining a corresponding snapshot backup identifier and at least one backup object according to a snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
the distribution module is used for distributing a corresponding first bitmap space, a snapshot backup space and a second bitmap space corresponding to each backup object page for each backup object, and recording a snapshot identifier of each piece of recorded information in each backup object page corresponding to each backup object as the snapshot backup identifier;
and the recording module is used for recording the modification state of each backup object page through the first bitmap space, recording modified record information in the backup object page through the snapshot backup space, and recording the modification state of each record information in the backup object page through the second bitmap space.
According to another aspect of the present application, there is provided an MPP database management system comprising a master node and at least one compute node;
the main node is used for sending a snapshot backup instruction to the computing node;
the computing node is used for determining a corresponding snapshot backup identifier and at least one backup object according to the snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
the computing node is used for allocating a corresponding first bitmap space, a snapshot backup space and a second bitmap space corresponding to each backup object page for each backup object, and recording a snapshot identifier of each piece of recording information in each backup object page corresponding to each backup object as the snapshot backup identifier;
the computing node is configured to record a modification state of each backup object page through the first bitmap space, record modified record information in the backup object page through the snapshot backup space, and record a modification state of each record information in the backup object page through the second bitmap space.
According to another aspect of the present application, there is provided a computing node comprising a machine-readable storage medium having stored thereon machine-executable instructions and a processor, which when executed by the processor, implements the MPP database management method described above.
According to another aspect of the present application, there is provided a readable storage medium having stored therein machine executable instructions that, when executed, implement the MPP database management method described above.
Based on any one of the above aspects, in the backup process of each backup object, the snapshot identifier that records each piece of record information in each backup object page corresponding to the backup object is a snapshot identifier, only modified record information is recorded through a snapshot backup space allocated for the backup object page, the modification state of each backup object page is recorded through a first bitmap space, and the modification state of each piece of record information in the backup object page is recorded through a second bitmap space. Therefore, in the backup process, only modified recording information, snapshot identification and some modification states need to be recorded, backup of a whole amount of data files is not needed, storage space consumed in backup can be effectively saved, time consumed in backup is reduced, influence on upper-layer services is reduced as far as possible, in addition, independent backup can be realized for data objects, and normal service operation of other data objects is not influenced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram illustrating an application scenario of an MPP database management system provided in an embodiment of the present application;
FIG. 2 illustrates one of the flow diagrams of an MPP database management method provided by an embodiment of the present application;
fig. 3 shows one of the explanatory diagrams of the first bitmap space and the snapshot backup space and the second bitmap space corresponding to each backup object page provided in the embodiment of the present application;
fig. 4 shows a second illustrative diagram of the first bitmap space and the snapshot backup space and the second bitmap space corresponding to each backup object page provided in the embodiment of the present application;
fig. 5 is a second schematic flowchart illustrating an MPP database management method according to an embodiment of the present application;
fig. 6 shows one of the functional block diagrams of the MPP database management apparatus provided in the embodiment of the present application;
fig. 7 shows a second functional block diagram of an MPP database management apparatus according to an embodiment of the present application;
fig. 8 is a block diagram illustrating a structure of a computing node for implementing the MPP database management method according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.
Before describing the embodiments of the present application, the following first describes the related art and the specific technical problems of the present application in detail based on the aforementioned background art.
The online backup of the current RDBMS (Relational DataBase Management System) DataBase can be roughly classified into a logical backup and a physical backup.
The logical backup has the disadvantages that a lot of time is consumed in performing the backup process, particularly, a long time is taken for performing the backup process on the MPP database having a large amount of data, a longer time may be required for performing the operation of restoring the database from the backup data, and a table locking operation may be performed during the backup process, thereby affecting the execution of the upper layer service.
In contrast, physical backup may enable more efficient real-time backup, which may back up and restore large databases in a relatively short amount of time. In the prior art, a physical backup scheme of an MPP database based on a PITR mechanism, which is usually adopted, is not uniformly executed by a Master node, and corresponding physical backup and recovery need to be separately executed on each computing node instance.
The following first introduces the principle of the MPP database physical backup and recovery scheme of the PITR mechanism:
PITR is a database physical backup recovery technology based on MVCC (Multi-Version concurrent Control), and when PITR is recovered, all data objects including database services of the entire compute node are recovered to a specified time instead of a specific data object. In the backup process, firstly, preparation work is carried out for making a basic backup, then a basic backup file is made, actually, a data directory of the current MPP database is subjected to physical full-scale copying operation, and the backup is finished after the copying is finished.
During the recovery process, assume that at time: 2019-06-1622: 45:00 the whole MPP database management system performs service upgrade operation, but if upgrade fails in the execution process and service rollback is needed to recover data, then the current database cluster needs to be deleted, the full data file needs to be recovered by using the previously made basic backup file, meanwhile, a configuration conf file is created, the time needing recovery is configured in the conf file (2019-06-1622: 45:00), and finally, when the MPP database is started, a recovery mode is entered, the value of CHECK POINT LOCATION (namely REDO POINT value) is read from the backup history file, and then some recovery parameters are read from the conf file, wherein the time needing recovery is included. Then, the MPP database starts to redo the archived WAL (Write-Ahead Logging, pre-Write log system) log data, the redo POINT may obtain from the value of the CHECK POINT LOCATION, and copy the archived WAL log into the temporary directory, and after the recovery is completed, the WAL log in the temporary file may be deleted.
It is easy to find out that, in the above solution, although the backup may be restored to any time within the period from the start of the backup to the end of the backup, the archived WAL log needs to be reapplied, which also takes a lot of time, for example, a lot of DML (Data management Language) operations are performed during the service upgrade process, and then a lot of operation Data is recorded in the WAL log, so that it is very time consuming to redo the WAL log. In addition, in general, if the service upgrade fails, the user usually falls back to a state before the upgrade, and the recovery meaning at any time is not great.
For this reason, based on the findings of the above technical problems, the inventors propose the following technical solutions to solve the above problems. It should be noted that the above prior art solutions have shortcomings which are the results of practical and careful study of the inventor, therefore, the discovery process of the above problems and the solutions proposed by the embodiments of the present application in the following description should be the contribution of the inventor to the present application in the course of the invention creation process, and should not be understood as technical contents known by those skilled in the art.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application scenario of an MPP database management system 10 according to an embodiment of the present application. In this embodiment, the MPP database management system 10 may include a master node 200 and a plurality of computing nodes 100, and the MPP database management system may be deployed in a server or a server cluster. When the MPP database management system 10 is deployed in a server, the modules in the server may serve as the master node 200 or the computing node 100. When the MPP database management system is deployed in a server cluster, the servers in the server cluster may act as the master node 200 or the compute node 100.
Each of the computing nodes 100 and the master node 200 may be respectively disposed in separate servers, and each of the computing nodes 100 and the master node 200 are communicatively connected. The master node 200 may be used as an entry of the MPP database management system structure, so as to interact with the client and each computing node 100, and issue a task such as a data backup instruction (e.g., a snapshot backup instruction) or a data recovery instruction (e.g., a snapshot recovery instruction) to the computing node 100.
For example, when the computing node 100 receives a snapshot backup instruction issued by the main node 200, in the process of backing up each backup object, the snapshot identifier of each piece of record information in each backup object page corresponding to the backup object may be recorded as the snapshot backup identifier, only the modified record information is recorded through the snapshot backup space allocated for the backup object page, the modification state of each backup object page is recorded through the first bitmap space, and the modification state of each piece of record information in the backup object page is recorded through the second bitmap space. Therefore, in the backup process, only modified recording information, snapshot identification and some modification states need to be recorded, backup of a whole amount of data files is not needed, storage space consumed in backup can be effectively saved, time consumed in backup is reduced, influence on upper-layer services is reduced as far as possible, in addition, independent backup can be realized for data objects, and normal service operation of other data objects is not influenced.
For another example, when the computing node 100 receives a snapshot restore instruction issued by the main node 200, in the process of restoring each restored object, a first bitmap space allocated to each restored object in advance and a snapshot backup space and a second bitmap space corresponding to each restored object page may be searched, and a restore operation may be performed on each restored object according to the snapshot backup identifier, the snapshot backup space, the first bitmap space, and the second bitmap space corresponding to each restored object page. Therefore, in the recovery process, the modified record information is recovered only according to the recorded snapshot identifier and the modification state, the recovery of a full amount of data files is not needed, the time consumed by recovery can be effectively reduced, the influence on upper-layer services is reduced as much as possible, in addition, the independent recovery can be realized for the data objects, and the normal service operation of other data objects is not influenced.
It should be noted that, in the practical application, the number of the computing nodes 100 may be increased or decreased according to different requirements, so as to expand the MPP database management system 10.
Fig. 2 is a flowchart illustrating an MPP database management method provided in an embodiment of the present application, which may be executed by any one of the computing nodes 100 shown in fig. 1. The detailed steps of the MPP database management method are described below.
Step S110, determining a corresponding snapshot backup identifier and at least one backup object according to the snapshot backup instruction sent by the master node 200, where the backup object is stored through at least one backup object page.
Step S120, for each backup object, allocating a corresponding first bitmap space and a snapshot backup space and a second bitmap space corresponding to each backup object page for the backup object, and recording a snapshot identifier of each piece of recorded information in each backup object page corresponding to the backup object as a snapshot backup identifier.
Step S130, recording the modification status of each backup object page through the first bitmap space, recording the modified record information in the backup object page through the snapshot backup space, and recording the modification status of each record information in the backup object page through the second bitmap space.
Based on the above steps, in the MPP database management method provided in this embodiment, in the process of backing up each backup object, the snapshot identifier that records each piece of record information in each backup object page corresponding to the backup object is a snapshot identifier, only modified record information is recorded through a snapshot backup space allocated for the backup object page, the modification state of each backup object page is recorded through a first bitmap space, and the modification state of each piece of record information in the backup object page is recorded through a second bitmap space. Therefore, in the backup process, only modified recording information, snapshot identification and some modification states need to be recorded, backup of a whole amount of data files is not needed, storage space consumed in backup can be effectively saved, time consumed in backup is reduced, influence on upper-layer services is reduced as far as possible, in addition, independent backup can be realized for data objects, and normal service operation of other data objects is not influenced.
Therefore, when a certain backup object is subsequently restored, only the modified record information can be restored according to the modification state of each backup object page and the modification state of each record information in the object page, the restoration of a full data file is not needed, the time consumed by restoration can be effectively reduced, the influence on upper-layer services is reduced as much as possible, in addition, the independent restoration can be realized for the data object, and the normal service operation of other data objects is not influenced.
In this embodiment, the object Page (Page) is the minimum unit of data space opened up each time during the storage process of the data object, and the minimum unit is used as a separate data area for storing specific record (Tuple) information. For example, assuming that each backup object page can store 4 pieces of record information, when the record information in a certain object page exceeds 4 pieces of record information, a new object page is created, and the record information written next is stored continuously through the new object page.
In this embodiment, the backup object may be determined by the master node 200 according to the submission requirement of the client, only one backup object may be determined, or a plurality of or all backup objects may be determined, which is not specifically limited in this embodiment.
In this embodiment, the snapshot backup identifier may be automatically generated by the master node 200 when issuing the snapshot backup instruction, and may be a unique identifier used to represent the current backup process. For example, the master node 200 may generate a snapshot backup identifier according to a time when the snapshot backup instruction is issued, so as to identify a time to which each backup process belongs. Such as 201901011230 and 201901301250, may represent the average of 12 in 2019, 1, and 201901301250, respectively: 30 and in 2019, 1, 30, 12:50, and sending a snapshot backup command. On this basis, for each backup object page corresponding to the backup object, the snapshot identifier of each backup object page may be recorded as the snapshot backup identifier, so that whether to restore the record information is further determined based on the snapshot identifier of each record information in the backup object page in the subsequent restoration process.
Optionally, the snapshot identifier of each backup object page may be recorded in the transaction log information corresponding to the computing node 100, and may be backed up to the disk together with the transaction log information at each backup.
In addition, during each backup process, the computing node 100 may execute a checkpoint command together to flush current running data (e.g., the allocated first bitmap space, snapshot backup space, second bitmap space, etc.) in the memory to the disk.
In this embodiment, regarding step S120, the following describes in detail the first bitmap space established for each backup object and the snapshot backup space and the second bitmap space corresponding to each backup object page, respectively, with reference to fig. 3.
Referring to fig. 3, the backup object may refer to a data table, a database, or an entire database cluster, and may be specifically selected by the master node 200 according to a requirement of the client, for example, in this embodiment, the backup object may be a data table of a specific statistical service. As shown in fig. 3, for example, a certain backup object includes four backup object pages Page1, Page2, Page3, and Page4, a first bitmap space of the backup object may be allocated, and Page address information in the Page information is mapped to bits P1, P2, P3, and P4 of the first bitmap space according to Page information of four backup object pages Page1, Page2, Page3, and Page4, so that the pages 1, Page2, Page3, and Page4 form mapping relationships with P1, P2, P3, and P4, respectively.
Next, the bit values of P1, P2, P3, and P4 may be set to 0, respectively. The bit values of P1, P2, P3 and P4 can be used for representing the modification states of Page1, Page2, Page3 and Page 4. Taking P1 as an example, when the bit value of P1 is 0, the modified state of Page1 can be represented as an unmodified state, and when the bit value of P1 is 1, the modified state of Page1 can be represented as a modified state.
On the basis, corresponding snapshot backup areas and second bitmap spaces can be allocated for Page1, Page2, Page3 and Page4 respectively. As shown in fig. 3, taking Page as an example, Page may include four pieces of recording information Tuple, and Tuple, the snapshot backup area corresponding to Page may be used to backup the header information of Page and the modified Tuple of Tuple, and Tuple, the header information may include address information of Tuple, and Tuple in Page, so as to map the address information of Tuple, and Tuple in Page to bits T, and T of the second bitmap space corresponding to Page, respectively, so as to map Tuple, and Tuple with T, and T, respectively.
Next, the bit values of T1, T2, T3, and T4 may be set to 0, respectively. The bit values of T1, T2, T3 and T4 may be used to indicate the modification states of Tuple1, Tuple2, Tuple3 and Tuple 4. Taking T1 as an example, when the bit value of T1 is 0, the modified state of Tuple1 is represented as an unmodified state, and when the bit value of T1 is 1, the modified state of Tuple1 is represented as a modified state.
On the basis of the above description, in one possible implementation, the following is specifically described for step S130:
first, when update data written to a backup object is detected, it is possible to determine whether or not a target object page associated with the update data exists for the backup object. When there is a target object page associated with the update data, it is determined whether a modification state of the target object page currently recorded in the first bitmap space is a modified state. When the modification state of the target object page is the modified state, whether the modification state of the target record information associated with the update data in the second bitmap space corresponding to the target object page is the modified state is judged. And when the modification state of the target record information is the modified state, modifying the target record information according to the updating data, and backing up the modified target record information into the snapshot backup space.
For example, taking the example shown in fig. 3 as an example, assuming that a target object Page associated with update data exists in the backup object, the target object Page is Page4, and target record information associated with the update data in Page4 is Tuple1, it may be determined whether a bit value of P4 in the first bitmap space is 1, when the bit value of P4 is 1, it may be determined whether a bit value of T1 in the second bitmap space corresponding to Page4 is 1, when the bit value of T1 is 1, Tuple1 may be modified according to the update data, and the modified Tuple1 may be backed up in the snapshot backup space.
In another possible implementation, when there is no target object page associated with the update data, a target object page may be created, a bitmap space of the target object page is added in a first bitmap space corresponding to the backup object to record a modified state of the target object page through the bitmap space, and a corresponding second bitmap space is allocated for the target object page. Then, updating the update data into the target record information associated with the update data in the target object page, setting the modified state of the target object page to be a modified state in the added bitmap space, setting the modified state of the target record information to be a modified state in the second bitmap space, and then backing up the target record information into the snapshot backup space.
For example, based on the example shown in fig. 3, assuming that there is no target object Page associated with the update data in the backup object shown in fig. 3, that is, none of Page1, Page2, Page3 and Page4 is a target object Page associated with the update data, then, with continuing reference to fig. 4, a target object Page5 may be further created on the basis of fig. 3, a bitmap space P5 of the target object Page5 may be added to the first bitmap space corresponding to the backup object to record the modified state of Page5 by the bit value of P5, and a corresponding second bitmap space T1 may be allocated to Page 5. Then, the update data is updated into the target record information Tuple1 associated with the update data in Page5, the bit value of P5 is set to 1, and the bit value of T1 is set to 1 in the second bitmap space, after which Tuple1 is backed up into the snapshot backup space.
In another possible implementation, when the modified state of the target object page is an unmodified state, the modified state of the target object page may be set to a modified state in the first bitmap space, and after the target record information associated with the update data in the target object page is modified according to the update data, the modified state of the target record information is set to a modified state in the second bitmap space corresponding to the target object page, and then the target record information is backed up in the snapshot backup space.
For example, still taking the foregoing example as an example, when the bit value of P4 in the first bitmap space is 0, the bit value of P4 may be set to 1 in the first bitmap space, and after Tuple1 in Page4 is modified according to the update data, the bit value of T1 may be set to 1 in the second bitmap space corresponding to Page4, and then Tuple1 is backed up in the snapshot backup space.
In another possible implementation, when the modified state of the target record information is an unmodified state, the target record information may be backed up in the snapshot backup space, and then the modified state of the target record information is set to a modified state in the second bitmap space corresponding to the target object page, and the target record information is modified according to the update data.
For example, still taking the foregoing example as an example, when the bit value of T1 in the second bitmap space is 0, the current Tuple1 may be backed up into the snapshot backup space, then the bit value of T1 is set to 1 in the second bitmap space corresponding to Page4, and Tuple1 is modified according to the update data.
Based on the design, when updated data is written into the backup object each time, the modification state of each backup object page is recorded through the first bitmap space, the modified record information in the object page is recorded through the snapshot backup space, and the modification state of each record information in the object page is recorded through the second bitmap space, so that only the modified record information, the snapshot identifier and some modification states need to be recorded in the subsequent backup process, backup of a full amount of data files is not needed, the storage space consumed in backup can be effectively saved, the time consumed in backup is reduced, and the influence on upper-layer services is reduced as much as possible.
Optionally, in the process of modifying the target record information according to the update data, there may be a plurality of modification manners, which may specifically be determined according to actual service requirements, for example, new data may be inserted into the target record information, new data may be replaced with the target record information, and the like, which is not limited in this embodiment.
Based on the foregoing description, the following describes in detail the data recovery process executed by the computing node 100 with reference to fig. 5, and referring to fig. 5, after step S130, the MPP database management method provided in this embodiment may further include the following steps:
step S140, according to the snapshot restore instruction sent by the master node 200, determining a corresponding snapshot backup identifier and at least one restore object, where the restore object is stored through at least one restore object page.
Step S150, find the first bitmap space allocated to each restoration object in advance and the snapshot backup space and the second bitmap space corresponding to each restoration object page.
Step S160, a recovery operation is performed on each recovery object according to the snapshot backup identifier, the snapshot backup space, the first bitmap space, and the second bitmap space corresponding to each recovery object page.
In this embodiment, the recovery object may be determined by the master node 200 according to the submission requirement of the client, only one recovery object may be determined, or a plurality of or all recovery objects may be determined, and it is only necessary to ensure that the recovery objects are backed up in advance, which is not specifically limited in this embodiment.
In this embodiment, the snapshot backup identifier may also be determined by the master node 200 according to the submission requirement of the client, and may be used to represent which backup data object is specifically recovered in the recovery process. For example, taking the aforementioned snapshot backup identifications including 201901011230 and 201901301250 as an example, when 201901011230 is selected, it may indicate that the data objects backed up by 12:30 in 1 month and 1 day of 2019 are restored, and when 201901301250 is selected, it may indicate that the data objects backed up by 12:50 in 1 month and 30 days of 2019 are restored.
On this basis, when the computing node 100 receives the snapshot restore instruction issued by the main node 200, in the process of restoring each restored object, the first bitmap space allocated to each restored object in advance and the snapshot backup space and the second bitmap space corresponding to each restored object page may be searched, and the restore operation may be performed on each restored object according to the snapshot backup identifier, the snapshot backup space, the first bitmap space, and the second bitmap space corresponding to each restored object page. Therefore, in the recovery process, the modified record information is recovered only according to the recorded snapshot identifier and the modification state, the recovery of a full amount of data files is not needed, the time consumed by recovery can be effectively reduced, the influence on upper-layer services is reduced as much as possible, in addition, the independent recovery can be realized for the data objects, and the normal service operation of other data objects is not influenced.
In a possible implementation manner, for step S160, it may be determined, for each recovery object, whether the modified state of each recovery object page is the modified state according to the first bitmap space corresponding to the recovery object. And when the modification state of any recovery object page is the modified state, judging whether each record information corresponding to the recovery object page is the modified state according to the second bitmap space corresponding to the recovery object page. And when the modification state of any one piece of recorded information is the modified state, judging whether the pre-recorded snapshot identifier corresponding to the recorded information is matched with the snapshot backup identifier. And when the snapshot identifier corresponding to the record information is matched with the snapshot backup identifier, searching the record information from the snapshot backup space, and restoring the record information to the restoration object page.
For example, still taking the example shown in fig. 3 as an example, assuming that the backup object is a recovery object in the current recovery process, and the snapshot backup identifier determined in the current recovery process is 201901301250, it may be determined whether the modified state of Page1, Page2, Page3, and Page4 is a modified state, that is, whether the bit value of P1, P2, P3, and P4 is 1, according to the first bitmap space corresponding to the recovery object. Taking the bit value of P4 as an example of 1, it can be determined whether the Tuple1, Tuple2, Tuple3, Tuple4 corresponding to Page4 is in a modified state, that is, whether the bit value of T1, T2, T3, T4 is 1, according to the second bitmap space corresponding to Page 4. Taking the bit value of T1 as 1 as an example, it can be determined whether the snapshot flag corresponding to Tuple1 recorded in advance is 201901301250. When the snapshot corresponding to Tuple1 is identified as 201901301250, Tuple1 can be searched from the snapshot backup space and Tuple1 is restored to the current Page4, otherwise, Tuple1 is not restored.
Further, based on the same inventive concept, please refer to fig. 6, which shows a functional module schematic diagram of the MPP database management device 110 provided in the embodiment of the present application, and the embodiment may divide the functional module of the MPP database management device 110 according to the above method embodiment. For example, the functional blocks may be divided for the respective functions, or two or more functions may be integrated into one processing block. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation. For example, in the case of dividing each functional module according to each function, the MPP database management device 110 shown in fig. 6 is only a schematic device. The MPP database management device 110 may include a first determining module 111, an assigning module 112, and a recording module 113, and the functions of the functional modules of the MPP database management device 110 are described in detail below.
The first determining module 111 is configured to determine, according to a snapshot backup instruction sent by the main node 200, a corresponding snapshot backup identifier and at least one backup object, where the backup object is stored through at least one backup object page. It is understood that the first determining module 111 can be used to perform the step S110, and for the detailed implementation of the first determining module 111, reference can be made to the contents related to the step S110.
The allocating module 112 is configured to allocate, for each backup object, a corresponding first bitmap space and a snapshot backup space and a second bitmap space corresponding to each backup object page for the backup object, and record a snapshot identifier of each piece of recording information in each backup object page corresponding to the backup object as a snapshot backup identifier. It is understood that the distribution module 112 can be used to execute the above step S120, and for the detailed implementation of the distribution module 112, reference can be made to the above description regarding the step S120.
The recording module 113 is configured to record a modification state of each backup object page through a first bitmap space, record modified record information in the backup object page through a snapshot backup space, and record a modification state of each record information in the backup object page through a second bitmap space. It is understood that the recording module 113 may be configured to perform the step S130, and for the detailed implementation of the recording module 113, reference may be made to the content related to the step S130.
In a possible implementation, the recording module 113 may specifically be configured to:
when detecting the update data written into the backup object, judging whether the backup object has a target object page related to the update data;
when a target object page associated with the updating data exists, judging whether the modification state of the target object page currently recorded in the first bitmap space is a modified state;
when the modification state of the target object page is the modified state, judging whether the modification state of the target record information associated with the update data in the second bitmap space corresponding to the target object page is the modified state;
and when the modification state of the target record information is the modified state, modifying the target record information according to the updating data, and backing up the modified target record information into the snapshot backup space.
In a possible implementation manner, the recording module 113 may be further specifically configured to:
when the target object page associated with the updating data does not exist, creating the target object page, adding the bitmap space of the target object page in the first bitmap space corresponding to the backup object so as to record the modification state of the target object page through the bitmap space, and allocating a corresponding second bitmap space for the target object page;
updating the update data into target record information associated with the update data in the target object page, setting the modification state of the target object page to be a modified state in the added bitmap space, and setting the modification state of the target record information to be a modified state in the second bitmap space;
and backing up the target recording information into the snapshot backup space.
In a possible implementation manner, the recording module 113 may be further specifically configured to:
when the modification state of the target object page is an unmodified state, setting the modification state of the target object page to be a modified state in a first bitmap space, and modifying target record information related to the update data in the target object page according to the update data;
setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page;
and backing up the target recording information into the snapshot backup space.
In a possible implementation manner, the recording module 113 may be further specifically configured to:
when the modified state of the target record information is an unmodified state, backing up the target record information into a snapshot backup space;
and setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page, and modifying the target record information according to the update data.
In one possible embodiment, referring to fig. 7, the MPP database management device 110 may further include a second determining module 114, a searching module 115, and a recovering module 116, and the functions of the second determining module 114, the searching module 115, and the recovering module 116 are described in detail below.
The second determining module 114 is configured to determine, according to the snapshot restore instruction sent by the main node 200, a corresponding snapshot backup identifier and at least one restoration object, where the restoration object is stored through at least one restoration object page. It is understood that the second determining module 114 can be used to execute the step S140, and for the detailed implementation of the second determining module 114, reference can be made to the above description about the step S140.
The searching module 115 is configured to search a first bitmap space allocated to each recovery object in advance, and a snapshot backup space and a second bitmap space corresponding to each recovery object page. It is understood that the search module 115 can be used to execute the step S150, and for the detailed implementation of the search module 115, reference can be made to the above description of the step S150.
And the restoring module 116 is configured to perform a restoring operation on each restoring object according to the snapshot identifier, the snapshot backup space, the first bitmap space, and the second bitmap space corresponding to each restoring object page. It is understood that the recovery module 116 can be used to perform the step S160, and for the detailed implementation of the recovery module 116, reference can be made to the above description about the step S160.
In one possible implementation, the restore module 116 may perform a restore operation on each restore object by:
for each recovery object, judging whether the modification state of each recovery object page is a modified state or not according to the first bitmap space corresponding to the recovery object;
when the modification state of any recovery object page is the modified state, judging whether each record information corresponding to the recovery object page is the modified state according to the second bitmap space corresponding to the recovery object page;
when the modification state of any one piece of recorded information is the modified state, judging whether a pre-recorded snapshot identifier corresponding to the recorded information is matched with the snapshot backup identifier or not;
and when the snapshot identifier corresponding to the record information is matched with the snapshot backup identifier, searching the record information from the snapshot backup space, and restoring the record information to the restoration object page.
Based on the same inventive concept, please refer to fig. 8, which shows a schematic block diagram of a computing node 100 for executing the MPP database management method according to an embodiment of the present application, where the computing node 100 may include an MPP database management apparatus 110, a machine-readable storage medium 120, and a processor 130.
In this embodiment, the machine-readable storage medium 120 and the processor 130 are both located in the computing node 100 and are located separately. However, it should be understood that the machine-readable storage medium 120 may also be separate from the computing node 100 and accessible by the processor 130 through a bus interface. Alternatively, the machine-readable storage medium 120 may be integrated into the processor 130, e.g., may be a cache and/or general purpose registers.
The processor 130 is a control center of the computing node 100, connects various parts of the entire computing node 100 using various interfaces and lines, and performs various functions of the computing node 100 and processes data by running or executing software programs and/or modules stored in the machine-readable storage medium 120 and calling data stored in the machine-readable storage medium 120, thereby performing overall monitoring of the computing node 100. Alternatively, processor 130 may include one or more processing cores; for example, the processor 130 may integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a modem processor, which primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor.
The processor 130 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application-Specific Integrated Circuit (ASIC), or one or more Integrated circuits for controlling the program execution of the MPP database management method provided by the above method embodiments.
The machine-readable storage medium 120 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an Electrically Erasable programmable read-Only Memory (EEPROM), or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The machine-readable storage medium 120 may be self-contained and coupled to the processor 130 via a communication bus. The machine-readable storage medium 120 may also be integrated with the processor. The machine-readable storage medium 120 is used for storing machine-executable instructions for performing aspects of the present application. The processor 130 is configured to execute machine-executable instructions stored in the machine-readable storage medium 120 to implement the MPP database management method provided by the foregoing method embodiments.
The MPP database management device 110 may include software functional modules (e.g., the first determining module 111, the allocating module 112, and the recording module 113) stored in the machine-readable storage medium 120, and when the processor 130 executes the software functional modules in the machine-readable storage medium 120, the MPP database management method provided by the foregoing method embodiments is implemented.
Since the computing node 100 provided in the embodiment of the present application is another implementation form of the foregoing method embodiment, and the computing node 100 may be configured to execute the MPP database management method provided in the foregoing method embodiment, the technical effect obtained by the computing node 100 may refer to the foregoing method embodiment, and is not described herein again.
Further, the present application also provides a readable storage medium containing computer executable instructions, which when executed, can be used to implement the MPP database management method provided by the foregoing method embodiments.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the present application has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
The above description is only for various embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the present application, and all such changes or substitutions are included in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (15)
1. An MPP database management method applied to any one of computing nodes in an MPP database management system, the MPP database management system further including a master node connected to each of the computing nodes, the method comprising:
determining a corresponding snapshot backup identifier and at least one backup object according to a snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
for each backup object, allocating a corresponding first bitmap space and a snapshot backup space and a second bitmap space corresponding to each backup object page for the backup object, and recording a snapshot identifier of each piece of recorded information in each backup object page corresponding to the backup object as the snapshot backup identifier;
and recording the modification state of each backup object page through the first bitmap space, recording modified record information in the backup object page through the snapshot backup space, and recording the modification state of each record information in the backup object page through the second bitmap space.
2. The MPP database management method according to claim 1, wherein the step of recording the modification status of each backup object page through the first bitmap space, recording the modified log information in the backup object page through the snapshot backup space, and recording the modification status of each log information in the backup object page through the second bitmap space includes:
when detecting the update data written into the backup object, judging whether the backup object has a target object page related to the update data;
when a target object page associated with the updating data exists, judging whether the modification state of the target object page currently recorded in the first bitmap space is a modified state;
when the modification state of the target object page is a modified state, judging whether the modification state of the target record information associated with the update data in a second bitmap space corresponding to the target object page is the modified state;
and when the modification state of the target record information is a modified state, modifying the target record information according to the updating data, and backing up the modified target record information into the snapshot backup space.
3. The MPP database management method according to claim 2, wherein the step of recording the modification status of each backup object page through the first bitmap space, recording the modified log information in the backup object page through the snapshot backup space, and recording the modification status of each log information in the backup object page through the second bitmap space further comprises:
when a target object page related to the updating data does not exist, creating the target object page, adding a bitmap space of the target object page in a first bitmap space corresponding to the backup object so as to record the modification state of the target object page through the bitmap space, and allocating a corresponding second bitmap space for the target object page;
updating the update data into target record information associated with the update data in the target object page, setting the modification state of the target object page to be a modified state in an added bitmap space, and setting the modification state of the target record information to be a modified state in the second bitmap space;
and backing up the target recording information into the snapshot backup space.
4. The MPP database management method according to claim 2, wherein the step of recording the modification status of each backup object page through the first bitmap space, recording the modified log information in the backup object page through the snapshot backup space, and recording the modification status of each log information in the backup object page through the second bitmap space further comprises:
when the modification state of the target object page is an unmodified state, setting the modification state of the target object page to be a modified state in the first bitmap space, and modifying target record information associated with the update data in the target object page according to the update data;
setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page;
and backing up the target recording information into the snapshot backup space.
5. The MPP database management method according to claim 2, wherein the step of recording the modification status of each backup object page through the first bitmap space, recording the modified log information in the backup object page through the snapshot backup space, and recording the modification status of each log information in the backup object page through the second bitmap space further comprises:
when the modification state of the target record information is an unmodified state, backing up the target record information into the snapshot backup space;
and setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page, and modifying the target record information according to the update data.
6. The MPP database management method according to any one of claims 1-5, further comprising:
determining a corresponding snapshot backup identifier and at least one recovery object according to a snapshot recovery instruction sent by the main node, wherein the recovery object is stored through at least one recovery object page;
searching a first bitmap space which is allocated for each recovery object in advance and a snapshot backup space and a second bitmap space which correspond to each recovery object page;
and executing recovery operation on each recovery object according to the snapshot backup identifier, the snapshot backup space, the first bitmap space and the second bitmap space corresponding to each recovery object page.
7. The MPP database management method according to claim 6, wherein the step of performing a restore operation on each restore object according to the snapshot backup identification, the snapshot backup space, the first bitmap space, and the second bitmap space corresponding to each restore object page comprises:
for each recovery object, judging whether the modification state of each recovery object page is a modified state or not according to the first bitmap space corresponding to the recovery object;
when the modification state of any recovery object page is the modified state, judging whether each record information corresponding to the recovery object page is the modified state according to the second bitmap space corresponding to the recovery object page;
when the modification state of any one piece of recorded information is the modified state, judging whether a pre-recorded snapshot identifier corresponding to the recorded information is matched with the snapshot backup identifier or not;
and when the snapshot identifier corresponding to the record information is matched with the snapshot backup identifier, searching the record information from the snapshot backup space, and restoring the record information to the restoration object page.
8. An MPP database management apparatus applied to any one of the computing nodes in an MPP database management system, the apparatus comprising:
the first determining module is used for determining a corresponding snapshot backup identifier and at least one backup object according to a snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
the distribution module is used for distributing a corresponding first bitmap space, a snapshot backup space and a second bitmap space corresponding to each backup object page for each backup object, and recording a snapshot identifier of each piece of recorded information in each backup object page corresponding to each backup object as the snapshot backup identifier;
and the recording module is used for recording the modification state of each backup object page through the first bitmap space, recording modified record information in the backup object page through the snapshot backup space, and recording the modification state of each record information in the backup object page through the second bitmap space.
9. The MPP database management apparatus according to claim 8, wherein the recording module is specifically configured to:
when detecting the update data written into the backup object, judging whether the backup object has a target object page related to the update data;
when a target object page associated with the updating data exists, judging whether the modification state of the target object page currently recorded in the first bitmap space is a modified state;
when the modification state of the target object page is a modified state, judging whether the modification state of the target record information associated with the update data in a second bitmap space corresponding to the target object page is the modified state;
and when the modification state of the target record information is a modified state, modifying the target record information according to the updating data, and backing up the modified target record information into the snapshot backup space.
10. The MPP database management apparatus according to claim 9, wherein the recording module is further configured to:
when a target object page related to the updating data does not exist, creating the target object page, adding a bitmap space of the target object page in a first bitmap space corresponding to the backup object so as to record the modification state of the target object page through the bitmap space, and allocating a corresponding second bitmap space for the target object page;
updating the update data into target record information associated with the update data in the target object page, setting the modification state of the target object page to be a modified state in an added bitmap space, and setting the modification state of the target record information to be a modified state in the second bitmap space;
and backing up the target recording information into the snapshot backup space.
11. The MPP database management apparatus according to claim 9, wherein the recording module is further configured to:
when the modification state of the target object page is an unmodified state, setting the modification state of the target object page to be a modified state in the first bitmap space, and modifying target record information associated with the update data in the target object page according to the update data;
setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page;
and backing up the target recording information into the snapshot backup space.
12. The MPP database management apparatus according to claim 9, wherein the recording module is further configured to:
when the modification state of the target record information is an unmodified state, backing up the target record information into the snapshot backup space;
and setting the modification state of the target record information to be a modified state in a second bitmap space corresponding to the target object page, and modifying the target record information according to the update data.
13. The MPP database management apparatus according to any one of claims 8-12, further comprising:
the second determining module is used for determining a corresponding snapshot backup identifier and at least one recovery object according to a snapshot recovery instruction sent by the main node, wherein the recovery object is stored through at least one recovery object page;
the searching module is used for searching a first bitmap space which is allocated for each recovery object in advance and a snapshot backup space and a second bitmap space which correspond to each recovery object page;
and the recovery module is used for executing recovery operation on each recovery object according to the snapshot identifier, the snapshot backup space, the first bitmap space and the second bitmap space corresponding to each recovery object page.
14. The MPP database management apparatus of claim 13, wherein the recovery module performs a recovery operation on each recovery object by:
for each recovery object, judging whether the modification state of each recovery object page is a modified state or not according to the first bitmap space corresponding to the recovery object;
when the modification state of any recovery object page is the modified state, judging whether each record information corresponding to the recovery object page is the modified state according to the second bitmap space corresponding to the recovery object page;
when the modification state of any one piece of recorded information is the modified state, judging whether a pre-recorded snapshot identifier corresponding to the recorded information is matched with the snapshot backup identifier or not;
and when the snapshot identifier corresponding to the record information is matched with the snapshot backup identifier, searching the record information from the snapshot backup space, and restoring the record information to the restoration object page.
15. An MPP database management system, comprising a master node and at least one compute node;
the main node is used for sending a snapshot backup instruction to the computing node;
the computing node is used for determining a corresponding snapshot backup identifier and at least one backup object according to the snapshot backup instruction sent by the main node, wherein the backup object is stored through at least one backup object page;
the computing node is used for allocating a corresponding first bitmap space, a snapshot backup space and a second bitmap space corresponding to each backup object page for each backup object, and recording a snapshot identifier of each piece of recording information in each backup object page corresponding to each backup object as the snapshot backup identifier;
the computing node is configured to record a modification state of each backup object page through the first bitmap space, record modified record information in the backup object page through the snapshot backup space, and record a modification state of each record information in the backup object page through the second bitmap space.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911211383.6A CN111143323B (en) | 2019-12-02 | 2019-12-02 | MPP database management method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911211383.6A CN111143323B (en) | 2019-12-02 | 2019-12-02 | MPP database management method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143323A CN111143323A (en) | 2020-05-12 |
| CN111143323B true CN111143323B (en) | 2022-04-08 |
Family
ID=70517420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911211383.6A Active CN111143323B (en) | 2019-12-02 | 2019-12-02 | MPP database management method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143323B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112256492A (en) * | 2020-12-22 | 2021-01-22 | 深圳市科力锐科技有限公司 | Block device backup method, device and storage medium |
| CN115114359B (en) * | 2022-05-27 | 2023-11-14 | 马上消费金融股份有限公司 | User data processing method and device |
| CN117170942B (en) * | 2023-11-03 | 2024-02-13 | 腾讯科技（深圳）有限公司 | Database backup method based on file system snapshot and related equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567262A (en) * | 2003-06-10 | 2005-01-19 | 联想(北京)有限公司 | On-line data backup method based on data volume snapshot |
| CN102999400A (en) * | 2012-11-22 | 2013-03-27 | 中国电信股份有限公司云计算分公司 | Data backup method and device of cloud storage system |
| CN103262043A (en) * | 2010-09-29 | 2013-08-21 | 赛门铁克公司 | Method and system of performing a granular restore of a database from a differential backup |
| CN106844095A (en) * | 2016-12-27 | 2017-06-13 | 上海爱数信息技术股份有限公司 | File backup method, system and the client with the system |
| CN106874143A (en) * | 2015-12-14 | 2017-06-20 | 财团法人工业技术研究院 | Server backup method and backup system thereof |
| CN110018881A (en) * | 2019-03-28 | 2019-07-16 | 西安交通大学 | A kind of virtual-machine fail quick recovery method and system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7747830B2 (en) * | 2007-01-05 | 2010-06-29 | Hitachi, Ltd. | Backup system with continuous data protection |
| US7917472B2 (en) * | 2008-11-03 | 2011-03-29 | Mats Stefan Persson | Method, system and computer-readable media for backing up information contained in a database |
| US8635187B2 (en) * | 2011-01-07 | 2014-01-21 | Symantec Corporation | Method and system of performing incremental SQL server database backups |
-
2019
- 2019-12-02 CN CN201911211383.6A patent/CN111143323B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567262A (en) * | 2003-06-10 | 2005-01-19 | 联想(北京)有限公司 | On-line data backup method based on data volume snapshot |
| CN103262043A (en) * | 2010-09-29 | 2013-08-21 | 赛门铁克公司 | Method and system of performing a granular restore of a database from a differential backup |
| CN102999400A (en) * | 2012-11-22 | 2013-03-27 | 中国电信股份有限公司云计算分公司 | Data backup method and device of cloud storage system |
| CN106874143A (en) * | 2015-12-14 | 2017-06-20 | 财团法人工业技术研究院 | Server backup method and backup system thereof |
| CN106844095A (en) * | 2016-12-27 | 2017-06-13 | 上海爱数信息技术股份有限公司 | File backup method, system and the client with the system |
| CN110018881A (en) * | 2019-03-28 | 2019-07-16 | 西安交通大学 | A kind of virtual-machine fail quick recovery method and system |
Non-Patent Citations (3)
| Title |
|---|
| Scalable Index Update for Block-Level Continuous Data Protection;Maohua Lu等;《IEEE》;20111030;第372-381页 * |
| 空间实时内存数据库恢复机制研究与实现;杜晔;《计算机工程与设计》;20130228;第734-739页 * |
| 计算机数据库的备份与恢复技术研究;蔡昀峰等;《计算机技术》;20180215;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143323A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111143323B (en) | MPP database management method, device and system | |
| CN109739935B (en) | Data reading method and device, electronic equipment and storage medium | |
| US7386752B1 (en) | Using asset dependencies to identify the recovery set and optionally automate and/or optimize the recovery | |
| US7107294B2 (en) | Method and apparatus for interrupting updates to a database to provide read-only access | |
| CN109542682B (en) | Data backup method, device, equipment and storage medium | |
| US7698319B2 (en) | Database system management method, database system, database device, and backup program | |
| CN102193991B (en) | OLTP(on-line transaction processing)-based data modifying method and system as well as graphic database server | |
| JP2000259456A (en) | File revision management system | |
| EP3895033B1 (en) | Efficient database migration using an intermediary secondary storage system | |
| CN110209527B (en) | Data recovery method, device, server and storage medium | |
| CN110543386B (en) | Data storage method, device, equipment and storage medium | |
| CN112306743B (en) | Data processing method, device, electronic equipment and computer storage medium | |
| CN109063005B (en) | Data migration method and system, storage medium and electronic device | |
| CN109241023A (en) | Distributed memory system date storage method, device, system and storage medium | |
| CN102103642A (en) | OLTP-based data deletion method, system and graphic database sever | |
| CN111753013A (en) | Distributed transaction processing method and device | |
| CN109445928A (en) | A kind of access request processing method, device, equipment and readable storage medium storing program for executing | |
| CN111666266A (en) | Data migration method and related equipment | |
| CN112612775A (en) | Data storage method and device, computer equipment and storage medium | |
| CN109902078B (en) | Method, device, equipment and storage medium for database upgrading compatibility | |
| CN114003569A (en) | Method and device for updating qcow2 mirror image file increment | |
| CN106997305B (en) | Transaction processing method and device | |
| WO2017067397A1 (en) | Data recovery method and device | |
| CN103729301A (en) | Data processing method and device | |
| CN110990145A (en) | Background task processing mechanism and method for distributed system |
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 |