CN115292094B - Data recovery processing method, device, equipment, storage medium and program product - Google Patents
Data recovery processing method, device, equipment, storage medium and program product Download PDFInfo
- Publication number
- CN115292094B CN115292094B CN202210954173.1A CN202210954173A CN115292094B CN 115292094 B CN115292094 B CN 115292094B CN 202210954173 A CN202210954173 A CN 202210954173A CN 115292094 B CN115292094 B CN 115292094B
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- target
- bitmap file
- data block
- 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
- 238000011084 recovery Methods 0.000 title claims abstract description 123
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 230000008859 change Effects 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 28
- 238000004590 computer program Methods 0.000 claims description 36
- 238000004458 analytical method Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 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/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
-
- 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
- G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
Abstract
The present application relates to the field of data processing technologies, and in particular, to a data recovery processing method, apparatus, device, storage medium, and program product. The method comprises the following steps: determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage; determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block; and carrying out data recovery according to the target states of the data blocks. The application can improve the data recovery efficiency.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a data recovery processing method, apparatus, device, storage medium, and program product.
Background
The TDSQL-PG edition (TDSQL for PostgreSQL, hereinafter referred to as TDSQL-PG) integrates the functions of high expansibility, SQL high compatibility, complete distributed transaction support, multi-level disaster recovery, multi-dimensional resource isolation and the like.
The TDSQL-PG implements log level incremental backup by periodically backing up the newly added WAL (Write Ahead Log) log file, how long it takes for WAL log generation, and an equal amount of time may be required to replay the WAL log during data recovery.
Specifically, in the data recovery process, the previous full-volume backup data set and each incremental backup data set associated with the previous full-volume backup data set need to be recovered one by one, and the recovery time objective (Recovery Time Objective, RTO) generated in the process is longer and the data recovery efficiency is lower due to the larger data recovery volume.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a data recovery processing method, apparatus, device, storage medium, and program product that can improve data recovery efficiency.
In a first aspect, the present application provides a data recovery processing method, including:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
And carrying out data recovery according to the target states of the data blocks.
In one embodiment, the method further comprises:
in the backup stage, generating an initial bitmap file according to data blocks in a database, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one;
and for each backup, when the data on the data block changes, updating the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup to obtain the target bitmap file.
In one embodiment, generating an initial bitmap file from a data block in a database includes:
acquiring index files corresponding to all data files of a database;
generating a data block bitmap file of each data file according to each index file;
generating an initial bitmap file according to the bitmap file of each data block.
In one embodiment, for each backup, when data on a data block changes, updating a value of a logical bit corresponding to the changed data block in the initial bitmap file to obtain a target bitmap file, including:
for each backup, when the data on the data block is changed compared with the last backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup as a first value;
Wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks.
In one embodiment, for each target bitmap file, determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup includes:
subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup.
In one of the embodiments of the present invention,
determining a plurality of target bitmap files according to the recovery task, including:
metadata corresponding to each backup in the backup stage is obtained, wherein the metadata are used for describing backup information;
a plurality of target bitmap files are determined according to the recovery tasks and the metadata.
In one of the embodiments of the present invention,
determining a plurality of target bitmap files according to the recovery tasks and the metadata, including:
acquiring a dependency relationship; the dependency relationship comprises an association relationship among the metadata;
and determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relation.
In a second aspect, the application further provides a data recovery processing device. The device comprises:
the query module is used for determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
the analysis module is used for determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and the recovery module is used for recovering the data according to the target state of each data block.
In a third aspect, the present application also provides a computer device comprising a memory storing a computer program and a processor which when executing the computer program performs the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
And carrying out data recovery according to the target states of the data blocks.
In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
In a fifth aspect, the application also provides a computer program product comprising a computer program which, when executed by a processor, performs the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
Determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
The data recovery processing method, the device, the equipment, the storage medium and the program product establish respective corresponding bitmap files for each data set to be recovered, take the bitmap files corresponding to the recovery task as target bitmap files, distinguish which data blocks are unchanged in the follow-up process for the current backup according to the target bitmap files corresponding to the current backup and the target bitmap files corresponding to the next backup for each target bitmap file, and determine the target state of the data blocks from the backup data set of the current backup, traverse each target bitmap file and determine the target state of each data block in the database; when the data is recovered, only the target state of the data block is required to be written once, and for the data block which is changed for many times, the intermediate states of the data block do not need to be repeatedly written, so that the number of times of repeated writing of the data is reduced, the data recovery efficiency is improved, and the quick recovery of the database level is realized.
Drawings
FIG. 1 is an application environment diagram of a data recovery processing method in one embodiment;
FIG. 2 is a flow chart of a data recovery processing method according to an embodiment;
FIG. 3 is a schematic diagram of an initial bitmap file in one embodiment;
FIG. 4 is a flowchart illustrating a step of generating a target bitmap file according to another embodiment;
FIG. 5 is a flowchart illustrating a step of generating a full back-up bitmap file according to another embodiment;
FIG. 6 is a flowchart illustrating a step of generating a first target bitmap file according to another embodiment;
FIG. 7 is a flowchart illustrating a step of generating a second target bitmap file according to another embodiment;
FIG. 8 is a schematic diagram of a bit map file subtraction in another embodiment;
FIG. 9 is a flowchart illustrating a step of generating an initial bitmap file according to another embodiment;
FIG. 10 is a flowchart illustrating a step of determining a target bitmap file according to another embodiment;
FIG. 11 is a flowchart illustrating a step of determining a target bitmap file according to a dependency relationship in another embodiment;
FIG. 12 is a block diagram showing the structure of a data recovery processing device in one embodiment;
fig. 13 is an internal structural view of a computer device in one embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The data recovery processing method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 and the server 104 may execute the data recovery processing method separately or may execute the data recovery processing method together, specifically, taking the example that the terminal 102 and the server 104 execute the data recovery processing method together, the server 104 is taken as a recovery host, the terminal 102 sends a recovery task to the server 104, and the server 104 determines a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage; determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block; and carrying out data recovery according to the target states of the data blocks. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.
The TDSQL-PG implements log level incremental backup by periodically backing up the newly added WAL (Write Ahead Log) log file, how long it takes for WAL log generation, and an equal amount of time may be required to replay the WAL log during data recovery. In the data recovery process, the previous full-volume backup data set and each incremental backup data set related to the previous full-volume backup data set need to be recovered one by one, taking a database with the size of 1TB as an example, assuming that 1TB is backed up for the full volume every day, and 1/2TB is backed up for the incremental backup every day from monday to Saturday, then the total data amount generated from the last monday to Saturday is 4TB; if the data is restored to the time point of Saturday according to the data restoration processing method in the conventional technology, the full backup of the last Saturday needs to be restored first, then all the incremental backups of Saturday to Saturday need to be sequentially restored, that is, when the data is restored, the data amount of 4TB needs to be written, and for the data block with multiple data changes, the intermediate state of the data block is sequentially restored, so that the data re-writing and the data restoration amount are increased, and further, the restoration time targets (Recovery Time Objective, RTO) generated in the process are longer and the data restoration efficiency is lower.
In one embodiment, as shown in fig. 2, a data recovery processing method is provided, and the method is applied to the server 104 in fig. 1 for illustration, and includes the following steps:
step 202, determining a plurality of target bitmap files according to the recovery task.
The recovery task is an instruction for controlling the server 104 (recovery host) to recover the acquired backup resource to the data on the target device, and the recovery task may be a recovery task generated by the server 104 according to the recovery request received from the terminal 102, or may be a recovery task initiated by a timing task module set in the server 104. Specifically, for a database, a backup resource is a data file (datafile) generated from database backup, and the backup mode includes full-volume backup and incremental backup, and data corresponding to each backup is used as a backup data set. Each recovery task corresponds to a plurality of backup data sets, for example, the backup data set corresponding to the recovery task is F1-I2-I3-I7-I4-I5, where Fn represents that the nth backup is a full backup, and In represents that the nth backup is an incremental backup.
The server 104 of the present embodiment includes: a global transaction management node (GTM node), one or more coordinator nodes (CN nodes), a plurality of data nodes (DN nodes). The GTM node is connected to each CN node through multiple connection methods, and may be used to provide global transaction services, for example, to allocate a transaction ID (Identity), which is a recovery task in this embodiment; for any one of the plurality of CN nodes, the CN node may be connected to the plurality of DN nodes through a plurality of connections, respectively, for controlling the DN to process data thereon, and controlling the DN to process data thereon includes performing a backup operation or a restore operation on data stored on the DN node.
Each backup data set corresponds to a target bitmap file, and the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage. Obtaining target bitmap files corresponding to each backup data set; an initial bitmap file corresponding to a database is first created, specifically, one database is mapped into a plurality of different data files (datafiles) which are maintained by an underlying database operating system and stored on a storage medium. Each data file (datafile) is divided into fixed-length storage units (called blocks), which are basic units of storage allocation and data transmission, i.e., each data file (datafile) is divided in units of data blocks. The initial bitmap file is built according to each data block in the database, the initial bitmap file includes a plurality of logic bits, each logic bit corresponds to each data block in the database one by one, the initial bitmap file corresponds to the initial state of the database, the initial state of the database is that no data is written into each data block in the database, the numerical value of each logic bit in the initial bitmap file is configured as an initial value, for example, as shown in fig. 3, the initial bitmap file has 16 logic bits in total, corresponding to 0-16 data blocks in the database, and the initial value can be 0.
Specifically, when the target bitmap file is generated, the numerical value of the logic bit in the initial bitmap file is adjusted according to the change condition of each data block in the database based on the initial bitmap file. For example, when the full-size backup is performed, since each data block in the database is subjected to a write operation, that is, the data block is changed, compared with the initial state of the database, the logical bit of the data block corresponding to the full-size backup in the initial bitmap file is adjusted, and the target bitmap file corresponding to the full-size backup is obtained. For example, in the case of incremental backup, since the incremental backup refers to the data that is added or modified in comparison with the previous backup only for each backup after the full-size backup or the previous incremental backup, the data block backed up by the incremental backup refers to the data block that is changed in comparison with the previous backup, and thus the logical bit adjusted in the target bitmap file corresponding to the incremental backup corresponds to the data block that is changed in comparison with the previous target bitmap file.
Specifically, for example, the values of the 16 logical bits corresponding to the full-size backup are all adjusted compared to the initial bitmap file, and the target bitmap file corresponding to the full-size backup is the zeroth target bitmap file (i.e., the full-size bitmap backup file); in the first incremental backup, when the 5 th to 12 th data blocks are changed compared with the full-size backup, the values of the 5 th to 12 th logical bits in the zeroth target bitmap file (i.e., the full-size bitmap backup file) are adjusted to obtain an updated bitmap file serving as a first target bitmap file; in the second incremental backup, the 6 th, 7 th, 8 th, 10 th, 11 th, 12 th, 14 th, 15 th and 16 th data blocks are changed compared with the first incremental backup, and the values of the logic bits of the 6 th, 7 th, 8 th, 10 th, 11 th, 12 th, 14 th, 15 th and 16 th data blocks in the first target bitmap file are adjusted to obtain an updated bitmap file serving as the second target bitmap file; and so on … ….
Step 204, for each target bitmap file, determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup.
The target state of the data block represents data corresponding to the last change of the data block; specifically, when searching the final state of each data block, in this embodiment, according to the states of each data block represented by the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup, the current state and the next state of each data block are compared, so as to distinguish which data blocks are unchanged in the follow-up process for the current backup, which data blocks are changed in the follow-up process, and for the data blocks which are unchanged in the follow-up process, the target state of the data block can be determined from the backup data set of the current backup. By traversing each target bitmap file, the target state of each data block in the whole database can be obtained.
And 206, performing data recovery according to the target states of the data blocks.
When data recovery is carried out, the operation of recovering the data is realized based on the one-to-one correspondence between each logic bit in the target bitmap file and the data block; in this embodiment, only the target state of each data block needs to be written into, and for the data block with multiple changes, the intermediate states of the data block do not need to be repeatedly recovered, so that the invalidation operation is reduced, the data recovery efficiency is improved, and the quick recovery of the database level is realized.
In the data recovery processing method, a corresponding bitmap file is established for each data set to be recovered, the bitmap file corresponding to the recovery task is used as a target bitmap file, for each target bitmap file, according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup, which data blocks are unchanged in the follow-up process for the current backup and which data blocks are changed in the follow-up process for the follow-up unchanged data blocks, the target state of the data block can be determined from the backup data set of the current backup, and the target state of each data block in the database can be determined by traversing each target bitmap file; when the data is recovered, only the target state of the data block is required to be written once, and for the data block which is changed for many times, the intermediate states of the data block do not need to be repeatedly written, so that the number of times of repeated writing of the data is reduced, the data recovery efficiency is improved, and the quick recovery of the database level is realized.
In one embodiment, the method further comprises: as shown in FIG. 4, at step 302, during a backup phase, an initial bitmap file is generated from data blocks in a database.
Each logical bit in the initial bitmap file corresponds one-to-one to each data block in the database. Specifically, each data block in the database may be a valid data block in the database, i.e. a data block used for storing data, or may be all data blocks in the database. The values of the respective logical bits in the initial bitmap file are configured as initial values, the values of the logical bits are expressed in binary form, and for example, the initial values may be configured as 0.
And step 304, for each backup, when the data on the data block changes, updating the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the previous backup to obtain the target bitmap file.
The method for updating the value of the logic bit can be as follows: mode 1) assigns a value to each logical bit based on a uniform value, or mode 2) updates each logical bit based on a different value.
In order to reduce the calculation amount, in the foregoing manner 1), in one embodiment, for each backup, when the data on the data block changes in step 304, the value of the logical bit corresponding to the changed data block in the bitmap file obtained after the previous backup is updated, so as to obtain the target bitmap file, which includes: for each backup, when the data on the data block is changed compared with the last backup, the numerical value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup is set to be a first value.
Wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks. Specifically, for the full-size backup, the initial bitmap file corresponds to the initial backup, and as the last backup corresponding to the full-size backup, the data block at the time of the full-size backup is changed (i.e., written) compared with the initial state of the database, and at this time, all logic bits in the initial bitmap file are set to a first value, so as to obtain the target bitmap file corresponding to the full-size backup. For each incremental backup, the backup data set corresponding to the incremental backup records the data blocks which are changed compared with the previous backup, so that the logical position corresponding to the changed data blocks in the previous target bitmap file is set to be a first value, and the target bitmap file corresponding to the incremental backup is obtained. Further, the value of the logical bit corresponding to the data block which is unchanged from the previous backup in the target bitmap file is set to the second value. Wherein the first value may be 1 and the second value may be 0. As shown in fig. 5 and 6, a target bitmap file corresponding to the full-back (i.e., a full-back bitmap file, and the full-back bitmap file may also be defined as a zeroth target bitmap file), and a first target bitmap file corresponding to the first incremental back-up, and so forth.
In this embodiment, by setting the logic bit to the first value to mark the data block that changes compared with the previous backup, the target state of each data block can be quickly queried based on the comparison result of the logic bit value when the current target bitmap file is compared with the next target bitmap file.
In one embodiment, for each target bitmap file in step 204, determining the target status of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup includes: and subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block.
The target bitmap file corresponding to the current backup minus the target bitmap file corresponding to the next backup is the same as the matrix subtraction, and each logic bit in the target bitmap file corresponding to the previous backup minus each logic bit in the corresponding position in the target bitmap file corresponding to the next backup.
The target data block is a data block which is unchanged from the current backup to the next backup. As shown in fig. 7, for the second target bitmap file corresponding to the second incremental backup illustrated in step 304, in combination with the above-described examples in step 202 and step 304, it is possible that the 5 th to 16 th logical bits in the first target bitmap file are configured as 1, and the other logical bits are configured as 0; the 6 th, 7 th, 8 th, 10 th, 11 th, 12 th, 14 th, 15 th, 16 th logical bits in the second target bitmap file are configured to be 1, and the other logical bits are configured to be 0; as shown in fig. 8, subtracting the second target bitmap file from the first target bitmap file, and updating the first target bitmap file, wherein only the values of the 5 th, 9 th and 13 th logical bits in the updated first target bitmap file are 1; for the first target bitmap file, the data block corresponding to the logical bit with the value of 1 is the target data block corresponding to the first target bitmap file, which characterizes that the target data block is unchanged in the second incremental backup, because the third incremental backup marks only the data changed on the basis of the second incremental backup data set (i.e. the 6 th, 7 th, 8 th, 10 th, 11, 12, 14, 15 th and 16 th data blocks), and because the fourth incremental backup marks only the third incremental backup data set, the subsequent incremental backups do not involve the 5 th, 9 th and 13 th data blocks any more, the target states of the 5 th, 9 th and 13 th data blocks can be found and determined in the backup data set corresponding to the first target bitmap file, and so on … …, the target data blocks corresponding to each target bitmap file and the target states of each target data block are determined.
In one embodiment, as shown in FIG. 9, generating an initial bitmap file from a data block in a database in step 302 includes:
in step 3021, an index file corresponding to each data file of the database is obtained.
The index file is used for representing the corresponding relation between the logical address space of the data file and the physical address interval of the data file. For example, the index file includes an index item corresponding to each data block in the data file, and the index content includes information such as an offset position of the data block in the corresponding storage medium of the database, a size of the data block, whether encryption and compression storage are performed, and the like.
Step 3022, generating a data block bitmap file for each data file according to each index file.
The database comprises a plurality of data files, each data file corresponds to a respective index file, and a data block bitmap file corresponding to each data file is generated according to each index file.
Step 3023, generating an initial bitmap file according to the bitmap file of each data block.
And merging the bitmap files of the data blocks to generate an initial bitmap file.
In this embodiment, by using the index entry in the index file, when the bitmap file is established, the relationship between the bitmap file and the physical address of each data block is not required to be established again, and only the relationship between the bitmap file and the index file is required to be established, so that the initial bitmap file corresponding to each data block can be obtained.
In one embodiment, as shown in fig. 10, determining a plurality of target bitmap files according to the recovery task in step 206 includes:
in step 2061, metadata corresponding to each backup in the backup stage is obtained.
The metadata is used for describing backup information corresponding to the backup, and the backup information at least comprises a data file of the backup, a storage position of the data file, a storage position of a backup data set, a name of the backup data set and the backup time. After each backup metadata generation, the metadata is updated into the database-established data warehouse catalog (catalog). Specifically, a data warehouse catalog (catalog), for example, F1-F2-I3-F4-I5-I6-I7-F8-I9, wherein F1, F2, I3, F4, I5, I6, I7, F8, I9 are the names of backup data sets contained in the respective metadata, respectively.
Step 2062, determining a plurality of target bitmap files according to the recovery task and the metadata.
And determining a backup data set to be restored according to the restoration task, and searching each target bitmap file according to the backup data set to be restored. Specifically, the restore task may be set by a user, at which time the user may manually select the names of the respective backup data sets to be restored; or, the recovery task may be triggered according to a timing module configured in the recovery host, that is, after reaching a timing time point, each backup data set to be recovered is automatically searched. Further, in order to facilitate quick searching of the backup data set to be restored corresponding to the restore task, each metadata corresponding to the restore task may be searched in a data warehouse directory (catalog) through the restore task, and each backup data set to be restored may be obtained according to each metadata association.
When the recovery task may also be triggered according to a timing module configured in the recovery host, in one embodiment, as shown in fig. 11, determining a plurality of target bitmap files according to the recovery task and metadata in step 2062 includes:
in step 20611, the dependency relationship is acquired.
The dependency relationship comprises an association relationship among the metadata, and specifically, when the metadata is generated, the dependency relationship is determined according to a backup data set corresponding to the metadata; that is, if the current backup data set is modified or added based on the previous backup data set, the current backup data set depends on the previous backup data set.
Step 20612, determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relationship.
When the recovery task is triggered according to a timing module configured in the recovery host, the recovery task comprises a recovery time point, and metadata corresponding to the last full-quantity backup data set before the recovery time point is searched in the dependency chain table according to the recovery time point and is used as starting point metadata; and taking the metadata between the time starting point corresponding to the starting point metadata and the time point to be recovered and the starting point metadata as target metadata, and searching each target bitmap file according to each target metadata. For example: and if the recovery time point is a time point between I7 and F8, F4-I5-I6-I7 and I7 need to be recovered in turn, wherein [ F4, I5, I6 and I7] is a recovery dependent linked list, and each target bitmap file is determined according to each target metadata in the dependent linked list.
Determining a recovery time point according to the recovery task, searching metadata corresponding to the last full-quantity backup data set before the recovery time point in the dependency chain table according to the recovery time point, and taking the metadata as starting point metadata; and taking the metadata between the time starting point corresponding to the starting point metadata and the time point to be recovered and the starting point metadata as target metadata, and searching each target bitmap file according to each target metadata. And for each backup, when the data on the data block is changed compared with the last backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup to be 1, and setting the value of the logic bit corresponding to the unchanged data block in the bitmap file obtained after the last backup to be 0 to obtain the target bitmap file corresponding to the last backup. For each target bitmap file, subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, determining a target data block corresponding to the target bitmap file, determining a target state of the target data block according to a backup data set corresponding to the target bitmap file, determining the target data blocks corresponding to each target bitmap file and the target states of each target data block, and performing data recovery according to the target states of each data block.
It should be understood that, although the steps in the flowcharts related to the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a data recovery processing device for realizing the above related data recovery processing method. The implementation of the solution provided by the apparatus is similar to the implementation described in the above method, so the specific limitation in the embodiments of the data recovery processing apparatus provided in the following may refer to the limitation of the data recovery processing method, which is not described herein.
In one embodiment, as shown in fig. 12, there is provided a data recovery processing apparatus 100, including a query module 110, an analysis module 120, and a recovery module 130, wherein:
a query module 110, configured to determine a plurality of target bitmap files according to a recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
the analysis module 120 is configured to determine, for each target bitmap file, a target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup; the target state of the data block represents data corresponding to the last change of the data block;
and the recovery module 130 is used for recovering the data according to the target state of each data block.
In one embodiment, the recovery device further comprises a generation module comprising:
the initial unit is used for generating an initial bitmap file according to the data blocks in the database in the backup stage, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one;
and the updating unit is used for updating the numerical value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup when the data on the data block changes for each backup, so as to obtain the target bitmap file.
In one embodiment, the initial unit is further configured to obtain an index file corresponding to each data file of the database;
generating a data block bitmap file of each data file according to each index file;
generating an initial bitmap file according to the bitmap file of each data block.
In one embodiment, the updating unit is further configured to, for each backup, set, when the data on the data block changes compared to the previous backup, a value of a logical bit corresponding to the changed data block in the bitmap file obtained after the previous backup to a first value;
wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks.
In one embodiment, the analysis module 120 is further configured to subtract the target bitmap file corresponding to the current backup from the target bitmap file corresponding to the next backup, and determine a target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup.
In one embodiment, the query module 110 includes:
the recording unit is used for acquiring metadata corresponding to each backup in the backup stage, wherein the metadata are used for describing backup information;
And the association unit is used for determining a plurality of target bitmap files according to the recovery task and the metadata.
In an embodiment, the association unit is further configured to obtain a dependency relationship; the dependency relationship comprises an association relationship among the metadata;
and determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relation.
The respective modules in the above-described data recovery processing apparatus may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 13. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a data recovery processing method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in FIG. 13 is merely a block diagram of some of the structures associated with the present inventive arrangements and is not limiting of the computer device to which the present inventive arrangements may be applied, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
In one embodiment, the processor when executing the computer program further performs the steps of: in the backup stage, generating an initial bitmap file according to data blocks in a database, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one; and for each backup, when the data on the data block changes, updating the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup to obtain the target bitmap file.
In one embodiment, the processor when executing the computer program further performs the steps of: acquiring index files corresponding to all data files of a database; generating a data block bitmap file of each data file according to each index file; generating an initial bitmap file according to the bitmap file of each data block.
In one embodiment, the processor when executing the computer program further performs the steps of: for each backup, when the data on the data block is changed compared with the last backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup as a first value; wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks.
In one embodiment, the processor when executing the computer program further performs the steps of: subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup.
In one embodiment, the processor when executing the computer program further performs the steps of: metadata corresponding to each backup in the backup stage is obtained, wherein the metadata are used for describing backup information; a plurality of target bitmap files are determined according to the recovery tasks and the metadata.
In one embodiment, the processor when executing the computer program further performs the steps of: acquiring a dependency relationship; the dependency relationship comprises an association relationship among the metadata; and determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relation.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
In one embodiment, the computer program when executed by the processor further performs the steps of: in the backup stage, generating an initial bitmap file according to data blocks in a database, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one; and for each backup, when the data on the data block changes, updating the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup to obtain the target bitmap file.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring index files corresponding to all data files of a database; generating a data block bitmap file of each data file according to each index file; generating an initial bitmap file according to the bitmap file of each data block.
In one embodiment, the computer program when executed by the processor further performs the steps of: for each backup, when the data on the data block is changed compared with the last backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup as a first value; wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks.
In one embodiment, the computer program when executed by the processor further performs the steps of: subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup.
In one embodiment, the computer program when executed by the processor further performs the steps of: metadata corresponding to each backup in the backup stage is obtained, wherein the metadata are used for describing backup information; a plurality of target bitmap files are determined according to the recovery tasks and the metadata.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a dependency relationship; the dependency relationship comprises an association relationship among the metadata; and determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relation.
In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:
determining a plurality of target bitmap files according to the recovery task; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
determining the target state of each data block according to the target bitmap file corresponding to the current backup and the target bitmap file corresponding to the next backup aiming at each target bitmap file; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
In one embodiment, the computer program when executed by the processor further performs the steps of: in the backup stage, generating an initial bitmap file according to data blocks in a database, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one; and for each backup, when the data on the data block changes, updating the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup to obtain the target bitmap file.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring index files corresponding to all data files of a database; generating a data block bitmap file of each data file according to each index file; generating an initial bitmap file according to the bitmap file of each data block.
In one embodiment, the computer program when executed by the processor further performs the steps of: for each backup, when the data on the data block is changed compared with the last backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the last backup as a first value; wherein the changing of the data on the data block compared with the last backup includes: writing data blocks or making changes to the data on the data blocks.
In one embodiment, the computer program when executed by the processor further performs the steps of: subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup.
In one embodiment, the computer program when executed by the processor further performs the steps of: metadata corresponding to each backup in the backup stage is obtained, wherein the metadata are used for describing backup information; a plurality of target bitmap files are determined according to the recovery tasks and the metadata.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a dependency relationship; the dependency relationship comprises an association relationship among the metadata; and determining a plurality of target bitmap files according to the recovery tasks, the metadata and the association relation.
The user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.
Claims (9)
1. A data recovery processing method, the method comprising:
in a backup stage, generating an initial bitmap file according to data blocks in a database, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one;
for each backup, when the data on the data block is changed compared with the previous backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the previous backup as a first value;
Wherein the changing of the data on the data block compared to the last backup includes: writing data blocks or modifying data on the data blocks; the backup mode comprises full backup and incremental backup;
acquiring metadata corresponding to each backup in the backup stage, wherein the metadata are used for describing backup information;
acquiring a dependency relationship, wherein the dependency relationship comprises an association relationship among the metadata;
determining a plurality of target bitmap files according to the recovery task, each metadata and the association relation;
the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup, and determining the target state of the target data block; the target data block is a data block which is unchanged from the current backup to the next backup; the target state of the data block represents data corresponding to the last change of the data block;
and carrying out data recovery according to the target states of the data blocks.
2. The method of claim 1, wherein a value of each logical bit in the initial bitmap file is configured as an initial value.
3. The method of claim 1, wherein generating an initial bitmap file from data blocks in a database comprises:
acquiring index files corresponding to all data files of the database;
generating a data block bitmap file of each data file according to each index file;
and generating the initial bitmap file according to each data block bitmap file.
4. A method according to claim 3, wherein the index file is used to characterize the correspondence between the logical address space of the data file and the physical address space of the data file.
5. The method of any of claims 1-4, wherein the backup information includes at least a data file of the secondary backup, a storage location of the data file, a storage location of the backup data set, a name of the secondary backup data set, and a time of the secondary backup.
6. The method of claim 2, wherein each data block in the database is a valid data block in the database.
7. A data recovery processing device, the device comprising:
the query module is used for generating an initial bitmap file according to the data blocks in the database in the backup stage, wherein each logic bit in the initial bitmap file corresponds to each data block in the database one by one; for each backup, when the data on the data block is changed compared with the previous backup, setting the value of the logic bit corresponding to the changed data block in the bitmap file obtained after the previous backup as a first value; wherein the changing of the data on the data block compared to the last backup includes: writing data blocks or modifying data on the data blocks; the backup mode comprises full backup and incremental backup; acquiring metadata corresponding to each backup in the backup stage, wherein the metadata are used for describing backup information; acquiring a dependency relationship, wherein the dependency relationship comprises an association relationship among the metadata; determining a plurality of target bitmap files according to the recovery task, each metadata and the association relation; determining the plurality of target bitmap files according to the recovery task, each metadata and the association relation; the target bitmap file is generated according to the initial bitmap file and the change condition of the data blocks in the database in the backup stage;
The analysis module is used for subtracting the target bitmap file corresponding to the next backup from the target bitmap file corresponding to the current backup and determining the target state of the target data block; the target state of the data block represents data corresponding to the last change of the data block;
and the recovery module is used for carrying out data recovery according to the target states of the data blocks.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210954173.1A CN115292094B (en) | 2022-08-10 | 2022-08-10 | Data recovery processing method, device, equipment, storage medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210954173.1A CN115292094B (en) | 2022-08-10 | 2022-08-10 | Data recovery processing method, device, equipment, storage medium and program product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115292094A CN115292094A (en) | 2022-11-04 |
| CN115292094B true CN115292094B (en) | 2023-11-14 |
Family
ID=83828772
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210954173.1A Active CN115292094B (en) | 2022-08-10 | 2022-08-10 | Data recovery processing method, device, equipment, storage medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115292094B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101276300A (en) * | 2007-03-30 | 2008-10-01 | 株式会社日立制作所 | Storage system and storage control method |
| CN102591982A (en) * | 2011-01-07 | 2012-07-18 | 赛门铁克公司 | Method and system of performing incremental sql server database backups |
| CN107135662A (en) * | 2015-12-28 | 2017-09-05 | 华为技术有限公司 | A kind of variance data backup method, storage system and variance data back-up device |
| CN112988473A (en) * | 2021-05-10 | 2021-06-18 | 南京云信达科技有限公司 | Backup data real-time recovery method and system |
| CN113868018A (en) * | 2021-08-25 | 2021-12-31 | 苏州浪潮智能科技有限公司 | Data storage method and device and data recovery method |
| CN114020527A (en) * | 2021-10-28 | 2022-02-08 | 济南浪潮数据技术有限公司 | Snapshot recovery method and device, computer equipment and storage medium |
| CN114442944A (en) * | 2022-01-05 | 2022-05-06 | 杭州宏杉科技股份有限公司 | Data copying method, system and equipment |
-
2022
- 2022-08-10 CN CN202210954173.1A patent/CN115292094B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101276300A (en) * | 2007-03-30 | 2008-10-01 | 株式会社日立制作所 | Storage system and storage control method |
| CN102591982A (en) * | 2011-01-07 | 2012-07-18 | 赛门铁克公司 | Method and system of performing incremental sql server database backups |
| CN107135662A (en) * | 2015-12-28 | 2017-09-05 | 华为技术有限公司 | A kind of variance data backup method, storage system and variance data back-up device |
| CN112988473A (en) * | 2021-05-10 | 2021-06-18 | 南京云信达科技有限公司 | Backup data real-time recovery method and system |
| CN113868018A (en) * | 2021-08-25 | 2021-12-31 | 苏州浪潮智能科技有限公司 | Data storage method and device and data recovery method |
| CN114020527A (en) * | 2021-10-28 | 2022-02-08 | 济南浪潮数据技术有限公司 | Snapshot recovery method and device, computer equipment and storage medium |
| CN114442944A (en) * | 2022-01-05 | 2022-05-06 | 杭州宏杉科技股份有限公司 | Data copying method, system and equipment |
Non-Patent Citations (1)
| Title |
|---|
| 王永全 等.《电子数据取证技术》.西安电子科技大学出版社,2021,第44页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115292094A (en) | 2022-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8965850B2 (en) | Method of and system for merging, storing and retrieving incremental backup data | |
| US10606865B2 (en) | Database scale-out | |
| CN111309720A (en) | Time sequence data storage method, time sequence data reading method, time sequence data storage device, time sequence data reading device, electronic equipment and storage medium | |
| US20210182160A1 (en) | System and method for generating file system and block-based incremental backups using enhanced dependencies and file system information of data blocks | |
| US10642530B2 (en) | Global occupancy aggregator for global garbage collection scheduling | |
| CN112817962B (en) | Data storage method and device based on object storage and computer equipment | |
| CN114924911B (en) | Method, device, equipment and storage medium for backing up effective data of Windows operating system | |
| CN115292094B (en) | Data recovery processing method, device, equipment, storage medium and program product | |
| CN117112941A (en) | Dictionary acquisition method, dictionary acquisition device, computer device, storage medium, and program product | |
| CN115202929B (en) | Database cluster backup system | |
| CN115858471A (en) | Service data change recording method, device, computer equipment and medium | |
| CN115509808A (en) | Data backup method and device, computer equipment and storage medium | |
| CN113515518A (en) | Data storage method and device, computer equipment and storage medium | |
| US11010332B2 (en) | Set-based mutual exclusion using object metadata tags in a storage appliance | |
| CN116257531B (en) | Database space recovery method | |
| CN115269274B (en) | Data recovery method, device, computer equipment and storage medium | |
| CN112835886A (en) | Data table field adding method and device | |
| CN114647630A (en) | File synchronization method, information generation method, file synchronization device, information generation device, computer equipment and storage medium | |
| CN115934750A (en) | Data query method and device based on StarRocks, computer equipment and storage medium | |
| CN109753228B (en) | Snapshot deleting method, device and system | |
| CN117573424A (en) | Data recovery method, device, computer equipment and storage medium | |
| CN114510492A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN114237977A (en) | Transaction rollback method, device, computer equipment and storage medium | |
| CN114385630A (en) | Blood relationship combing method, apparatus, device, storage medium, and program product | |
| CN117075951A (en) | Program maintenance method, program maintenance device, computer equipment and storage medium |
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 |