CN113238891A - Backup deletion method and system based on backup chain - Google Patents
Backup deletion method and system based on backup chain Download PDFInfo
- Publication number
- CN113238891A CN113238891A CN202110294024.2A CN202110294024A CN113238891A CN 113238891 A CN113238891 A CN 113238891A CN 202110294024 A CN202110294024 A CN 202110294024A CN 113238891 A CN113238891 A CN 113238891A
- Authority
- CN
- China
- Prior art keywords
- backup
- data
- module
- disk
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012217 deletion Methods 0.000 title claims abstract description 29
- 230000037430 deletion Effects 0.000 title claims abstract description 29
- 238000000034 method Methods 0.000 title claims abstract description 18
- 230000000977 initiatory effect Effects 0.000 claims abstract description 14
- 230000000903 blocking effect Effects 0.000 claims description 7
- 238000010367 cloning Methods 0.000 claims description 7
- 230000005540 biological transmission Effects 0.000 claims description 6
- 230000001419 dependent effect Effects 0.000 claims description 6
- 238000005192 partition Methods 0.000 claims description 6
- 238000004364 calculation method Methods 0.000 claims description 5
- 230000001105 regulatory effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000009545 invasion Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0608—Saving storage space on storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0674—Disk device
- G06F3/0676—Magnetic disk device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a backup deleting method and a backup deleting system based on a backup chain, belonging to the field of computers; the method comprises the following specific steps: s1 initiating a backup creation request at the job node; s2, creating a snapshot of the current time point of the disk in use; s3, creating a clone disk for mounting the backup component, and continuously reading the disk data; s4, reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data; s5 recording the dependency relationship and metadata information between the backup and the last backup; s6 initiates a backup deletion request; s7, performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup; s8 deleting the backup and storage object; the problem that the depended backup cannot be deleted is solved, the deletion of any backup on the backup chain is supported, the dependence limitation is avoided, the tail backup can be deleted, and any one backup in the middle can be deleted.
Description
Technical Field
The invention discloses a backup deleting method and system based on a backup chain, and relates to the technical field of computers.
Background
Backup is used as an important means for protecting data on the cloud, and when computer virus invasion, manual misoperation, software upgrading failure and even disk hardware damage happen, data on a disk can be backed up and restored, so that the protection of the data on the cloud is provided;
compared with full backup for storing complete data, incremental backup is used as another backup mode, and only newly increased or modified data parts can be backed up on the basis of the previous backup to form a backup chain, so that the storage space, time and network bandwidth are saved; therefore, the intermediate backup or the depended backup on the backup chain can not be deleted only from the last backup at the tail of the backup chain to the head of the backup chain when the backup chain is deleted; therefore, the present invention provides a backup deletion method and system based on a backup chain to solve the above problems.
Disclosure of Invention
The invention provides a backup deleting method and a system based on a backup chain aiming at the problems of the prior art, and the adopted technical scheme is as follows: a backup deletion method based on a backup chain is disclosed, wherein the creating method comprises the following specific steps:
s1 initiating a backup creation request at the job node;
s2, creating a snapshot of the current time point of the disk in use;
s3, creating a clone disk for mounting the backup component, and continuously reading the disk data;
s4, reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
s5 recording the dependency relationship and metadata information between the backup and the last backup;
s6 initiates a backup deletion request;
s7, performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
s8 deletes the backup and storage object.
The specific step of S1 initiating the backup creation request at the job node includes:
s101, creating a backup request in an incremental mode;
s102, the scheduler is used for selecting the optimal node to be scheduled to the job node.
The specific steps of reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data by the S4 include:
s401, reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
s402, comparing the obtained sha256 value with the last backed-up data;
s403 stores the backup with different sha256 values.
The specific steps of S7 performing incremental data fine-grained identification, data merging, and updating of dependency and metadata for the depended backup include:
s701, judging whether the backup is depended on;
s702, if the data is relied on, carrying out fine-grained identification on the data and merging the data into the next backup;
s703 updates the dependency relationship and metadata information of the next backup that is dependent on the backup.
A backup deletion system based on a backup chain specifically comprises a creation request module, a snapshot creation module, a disk cloning module, a disk reading module, an information analysis module, a deletion request module, a backup judgment module and a data deletion module:
a creation request module: initiating a backup creating request at a job node;
a snapshot creation module: creating a snapshot of the current time point of the disk in use;
a disk cloning module: establishing a clone disk for mounting a backup component, and continuously reading disk data;
a disk reading module: reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
an information analysis module: recording the dependency relationship and the metadata information between the backup and the last backup;
a deletion request module: initiating a backup deletion request;
a backup judgment module: performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
a data deleting module: the backup and storage objects are deleted.
The creation request module specifically comprises a request creation module and a creation adjustment module:
a request creation module: creating a backup request in an incremental manner;
creating a regulating module: and selecting the optimal node to be scheduled to the job node by using the scheduler.
The disk reading module specifically comprises a partition calculation module, a data comparison module and a backup storage module:
a partition calculation module: reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
a data comparison module: comparing the obtained sha256 value with the last backed-up data;
a backup storage module: and storing the backup with different sha256 values.
The backup judging module specifically comprises a backup query module, a data updating module A and a data updating module B:
a backup query module: determining whether the backup is relied upon;
the data updating module A: if the backup data is relied on, carrying out fine-grained identification on the data and merging the data to the next backup;
the data updating module B: the dependency and metadata information of the next backup that is dependent on the backup is updated.
The invention has the beneficial effects that: the backup deleting method and the backup deleting system based on the backup chain solve the dilemma that the depended backup cannot be deleted, support the deletion of any backup on the backup chain, mean that the dependence is not limited any more, not only can delete the tail backup, but also can delete any middle backup, and further save the storage space on the premise of ensuring the completeness of the data and being capable of rolling back correctly.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention; FIG. 2 is a schematic diagram of the system of the present invention; fig. 3 is a schematic diagram of an embodiment of the present invention.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The first embodiment is as follows:
a backup deletion method based on a backup chain is disclosed, wherein the creating method comprises the following specific steps:
s1 initiating a backup creation request at the job node;
s2, creating a snapshot of the current time point of the disk in use;
s3, creating a clone disk for mounting the backup component, and continuously reading the disk data;
s4, reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
s5 recording the dependency relationship and metadata information between the backup and the last backup;
s6 initiates a backup deletion request;
s7, performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
s8 deleting the backup and storage object;
firstly, a backup creating request is initiated at a job node according to S1, then a snapshot at the current time point is created on a disk in use according to S2, the data at the current time of backup is recorded, and meanwhile, the snapshot is protected to prevent the snapshot from being damaged when a clone disk is created in the next step;
then, based on the disk and the snapshot, according to S3, a cloned disk is created for mounting the backup component, and a data transmission channel is established, so that the backup component can read the disk data;
then, the clone data is read according to S4, compared with the data in the last backup in the backup chain, and data transmission is carried out;
the dependency between the backup and the last backup is recorded as per S5. Including depended number, father backup, etc, maintaining backup chain information; initiating a backup deletion request according to S6, checking the state of the backup, if the backup is created or deleted, not allowing the backup to be deleted, then inquiring the number of depended backups, judging whether the backups are depended or not according to S7, and determining the next processing logic; finally, deleting the backup and storage objects according to S8;
further, the specific step of S1 initiating the backup creation request at the job node includes:
s101, creating a backup request in an incremental mode;
s102, selecting the optimal node to be scheduled to a job node by using a scheduler;
when a backup creating request is initiated, a backup disk is selected, a backup storage position is created in an incremental mode according to S101, and a scheduler selects an optimal node to be scheduled to an operation node according to factors such as idle and busy nodes, residual storage space and the like and according to S102;
further, the specific steps of reading the data of the clone disk, comparing the data with the data in the last backup in the backup chain, and performing data transmission in S4 include:
s401, reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
s402, comparing the obtained sha256 value with the last backed-up data;
s403, storing the backup with different sha256 values;
firstly, reading data in a disk in a blocking mode according to S401, calculating the sha256 value of each block of data, recording the information such as the sha256 value, the storage initial position, the length and the like, comparing the obtained sha256 value with the last backup data according to S402, wherein different sha256 values mean that the data contents are different, the backups with different sha256 values need to be stored according to S403, otherwise, the data contents are the same, and repeated storage is not needed;
still further, the step of determining whether the backup is dependent and performing data update in S7 includes:
s701, judging whether the backup is depended on;
s702, updating the dependency relationship of the next backup which is depended on the backup, merging data and increasing data fine-grained identification;
s703 updates the dependency and metadata of the last backup that is not depended on.
If the backup is relied on, updating the dependency relationship of the next backup and merging the data; if not, updating the dependency relationship of the parent backup; deleting the backup and the storage objects, traversing all the stored objects under the backup, and deleting and releasing one by one;
example two:
a backup deletion system based on a backup chain is characterized by specifically comprising a creation request module, a snapshot creation module, a disk cloning module, a disk reading module, an information analysis module, a deletion request module, a backup judgment module and a data deletion module:
a creation request module: initiating a backup creating request at a job node;
a snapshot creation module: creating a snapshot of the current time point of the disk in use;
a disk cloning module: establishing a clone disk for mounting a backup component, and continuously reading disk data;
a disk reading module: reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
an information analysis module: recording the dependency relationship and the metadata information between the backup and the last backup;
a deletion request module: initiating a backup deletion request;
a backup judgment module: performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
a data deleting module: deleting the backup and storage objects;
firstly, an operation node initiates a backup establishing request through an establishing request module, then a snapshot establishing module is utilized to establish a snapshot of a current time point on a disk in use, record data of the current moment of backup, and simultaneously protect the snapshot to prevent the snapshot from being damaged when a clone disk is established in the next step;
then, based on the disk and the snapshot, a cloned disk is created through a disk cloning module for mounting the backup component, and a data transmission channel is established, so that the backup component can read the disk data;
then, the clone data is read through a disk reading module, compared with the data in the last backup in the backup chain, and data transmission is carried out;
and recording the dependency relationship between the backup and the last backup by using the information analysis module. Including depended number, father backup, etc, maintaining backup chain information; then, a backup deletion request is initiated through a deletion request module, the state of the backup is verified, if the backup is created or deleted, the backup is not allowed to be deleted, then the number of depended backups is inquired, whether the backup is depended or not is judged through a backup judgment module, and the next processing logic is determined; finally, deleting the backup and the storage object through a data deleting module;
further, the creation request module specifically includes a request creation module and a creation adjustment module:
a request creation module: creating a backup request in an incremental manner;
creating a regulating module: selecting the optimal node to be scheduled to the operation node by using a scheduler;
when a backup establishing request is initiated, a backup disk is selected, a backup storage position is established in an incremental mode by using a request establishing module, and a scheduler selects an optimal node to be scheduled to an operation node through an establishing adjusting module according to factors such as idle and busy nodes, residual storage space and the like;
further, the disk reading module specifically includes a partition calculating module, a data comparing module, and a backup storage module:
a partition calculation module: reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
a data comparison module: comparing the obtained sha256 value with the last backed-up data;
a backup storage module: storing the backup with different sha256 values;
firstly, reading data in a disk by blocks, calculating the sha256 value of each block of data, recording the information of the sha256 value, the storage initial position, the length and the like, comparing the obtained sha256 value with the last backup data by using a data comparison module, wherein different sha256 values mean that the data contents are different, backups with different sha256 values need to be stored by a backup storage module, and otherwise, the data contents are the same and repeated storage is not needed;
still further, the backup judgment module specifically includes a backup query module, a data update module a, and a data update module B:
a backup query module: determining whether the backup is relied upon;
the data updating module A: updating the dependency relationship of the next backup which is depended on the backup, merging data and increasing the fine-grained identification of the data;
the data updating module B: updating the dependency and metadata of the last backup which is not depended on;
if the backup is relied on, updating the dependency relationship of the next backup and merging the data; if not, updating the dependency relationship of the parent backup; deleting the backup and the storage objects, traversing all the stored objects under the backup, and deleting and releasing one by one;
there are a (full backup), B (incremental backup 1) and C (incremental backup 2) on the backup chain. A comprises initial complete data A0-0, A1-0, A2-0, A3-0 and A4-0, when a first incremental backup B is created, only A0-1 and A2-1 are changed, so that only two objects A0-1 and A2-1 are stored, other objects are not stored repeatedly, the parent backup of B is A, and the number of depended objects is 1. When a second incremental backup C is created, A1-2 and A2-2 are changed, the parent backup of C is B, and the dependent number is 1;
when a delete B request occurs, since B is relied upon and there is data storage, it will proceed with the following logical steps: the data A0-1 and A2-1 stored in B are merged into C at first, and since the A2 backup C at the position has the latest data, the A2-1 does not need to be merged into C, and only the A1-0 is merged. The storage object of C at this time contains A0-1, A1-2 and A2-2; then changing the parent backup of the C from B to A; and finally, deleting all the backup B and the storage objects thereof.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (8)
1. A backup deleting method based on a backup chain is characterized in that the method comprises the following specific steps:
s1 initiating a backup creation request at the job node;
s2, creating a snapshot of the current time point of the disk in use;
s3, creating a clone disk for mounting the backup component, and continuously reading the disk data;
s4, reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
s5 recording the dependency relationship and metadata information between the backup and the last backup;
s6 initiates a backup deletion request;
s7, performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
s8 deletes the backup and storage object.
2. The method as claimed in claim 1, wherein the step of S1 initiating the backup creation request at the job node comprises:
s101, creating a backup request in an incremental mode;
s102, the scheduler is used for selecting the optimal node to be scheduled to the job node.
3. The method as claimed in claim 2, wherein the step of S4 reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and performing data transmission comprises:
s401, reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
s402, comparing the obtained sha256 value with the last backed-up data;
s403 stores the backup with different sha256 values.
4. The method as claimed in claim 3, wherein the step of S7 performing fine-grained identification of incremental data, data merging and updating of dependency and metadata for the depended backup comprises:
s701, judging whether the backup is depended on;
s702, if the data is relied on, carrying out fine-grained identification on the data and merging the data into the next backup;
s703 updates the dependency relationship and metadata information of the next backup that is dependent on the backup.
5. A backup deletion system based on a backup chain is characterized by specifically comprising a creation request module, a snapshot creation module, a disk cloning module, a disk reading module, an information analysis module, a deletion request module, a backup judgment module and a data deletion module:
a creation request module: initiating a backup creating request at a job node;
a snapshot creation module: creating a snapshot of the current time point of the disk in use;
a disk cloning module: establishing a clone disk for mounting a backup component, and continuously reading disk data;
a disk reading module: reading the data of the cloned disk, comparing the data with the data in the last backup in the backup chain, and transmitting the data;
an information analysis module: recording the dependency relationship and the metadata information between the backup and the last backup;
a deletion request module: initiating a backup deletion request;
a backup judgment module: performing incremental data fine-grained identification, data merging and updating of dependency and metadata on the depended backup;
a data deleting module: the backup and storage objects are deleted.
6. The system as claimed in claim 5, wherein said creation request module specifically comprises a request creation module and a creation adjustment module:
a request creation module: creating a backup request in an incremental manner;
creating a regulating module: and selecting the optimal node to be scheduled to the job node by using the scheduler.
7. The system of claim 6, wherein the disk reading module specifically comprises a partition calculation module, a data comparison module, and a backup storage module:
a partition calculation module: reading data in a disk in a blocking mode, and calculating the sha256 value of each block of data;
a data comparison module: comparing the obtained sha256 value with the last backed-up data;
a backup storage module: and storing the backup with different sha256 values.
8. The system according to claim 7, wherein the backup determining module specifically includes a backup query module, a data update module a, and a data update module B:
a backup query module: determining whether the backup is relied upon;
the data updating module A: if the backup data is relied on, carrying out fine-grained identification on the data and merging the data to the next backup;
the data updating module B: the dependency and metadata information of the next backup that is dependent on the backup is updated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110294024.2A CN113238891A (en) | 2021-03-19 | 2021-03-19 | Backup deletion method and system based on backup chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110294024.2A CN113238891A (en) | 2021-03-19 | 2021-03-19 | Backup deletion method and system based on backup chain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113238891A true CN113238891A (en) | 2021-08-10 |
Family
ID=77130368
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110294024.2A Pending CN113238891A (en) | 2021-03-19 | 2021-03-19 | Backup deletion method and system based on backup chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238891A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117349086A (en) * | 2023-12-04 | 2024-01-05 | 四川精容数安科技有限公司 | Permanent incremental backup method for Windows complete machine |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521075A (en) * | 2011-12-01 | 2012-06-27 | 浪潮电子信息产业股份有限公司 | Fast and reliable file incremental backup method |
| CN108255647A (en) * | 2018-01-18 | 2018-07-06 | 湖南麒麟信安科技有限公司 | A kind of high-speed data backup method under samba server clusters |
| CN111078464A (en) * | 2018-10-22 | 2020-04-28 | 华为技术有限公司 | Method, device and system for backing up data |
| CN112463450A (en) * | 2020-11-27 | 2021-03-09 | 北京浪潮数据技术有限公司 | Incremental backup management method, system, electronic equipment and storage medium |
-
2021
- 2021-03-19 CN CN202110294024.2A patent/CN113238891A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521075A (en) * | 2011-12-01 | 2012-06-27 | 浪潮电子信息产业股份有限公司 | Fast and reliable file incremental backup method |
| CN108255647A (en) * | 2018-01-18 | 2018-07-06 | 湖南麒麟信安科技有限公司 | A kind of high-speed data backup method under samba server clusters |
| CN111078464A (en) * | 2018-10-22 | 2020-04-28 | 华为技术有限公司 | Method, device and system for backing up data |
| CN112463450A (en) * | 2020-11-27 | 2021-03-09 | 北京浪潮数据技术有限公司 | Incremental backup management method, system, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117349086A (en) * | 2023-12-04 | 2024-01-05 | 四川精容数安科技有限公司 | Permanent incremental backup method for Windows complete machine |
| CN117349086B (en) * | 2023-12-04 | 2024-02-23 | 四川精容数安科技有限公司 | Permanent incremental backup method for Windows complete machine |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10838826B2 (en) | Backup and restore of linked clone VM | |
| US10671487B2 (en) | Fast and optimized restore using delta information | |
| US8725695B2 (en) | Storage system and object management method | |
| US20030056139A1 (en) | Systems and methods for data backup over a network | |
| US10116764B1 (en) | Method for state based snapshot difference with restart capability | |
| US10628298B1 (en) | Resumable garbage collection | |
| WO2021184996A1 (en) | Data storage method and apparatus for database | |
| CN107943501A (en) | Embedded device upgrade method, device, computer equipment and storage medium | |
| US9594643B2 (en) | Handling restores in an incremental backup storage system | |
| CN113238891A (en) | Backup deletion method and system based on backup chain | |
| CN109753381B (en) | Continuous data protection method based on object storage | |
| EP2372552B1 (en) | Automated relocation of in-use multi-site protected data storage | |
| US20160253247A1 (en) | Method and device for restoring system file indexes | |
| CN113467719A (en) | Data writing method and device | |
| US11449389B2 (en) | Techniques for performing incremental data backups | |
| CN115328696A (en) | Data backup method in database | |
| CN111414271B (en) | Storage method based on self-adaptive storage redundancy strategy | |
| CN112328433A (en) | Processing method and device for restoring archived data, electronic device and storage medium | |
| CN113821176B (en) | Data migration processing method, device and storage medium | |
| US20240095132A1 (en) | Backup recovery from remote storage | |
| CN116795296B (en) | Data storage method, storage device and computer readable storage medium | |
| CN114253472B (en) | Metadata management method, device and storage medium | |
| CN115933981A (en) | Data migration method, device, distributed system and computer readable storage medium | |
| CN116166195A (en) | Data processing method, system, equipment and storage medium | |
| CN116737065A (en) | Bad block table inheritance and management method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210810 |
|
| RJ01 | Rejection of invention patent application after publication |