CN112328427A - Method for designing and implementing True CDP data protection scheme based on reflink - Google Patents
Method for designing and implementing True CDP data protection scheme based on reflink Download PDFInfo
- Publication number
- CN112328427A CN112328427A CN202011085970.8A CN202011085970A CN112328427A CN 112328427 A CN112328427 A CN 112328427A CN 202011085970 A CN202011085970 A CN 202011085970A CN 112328427 A CN112328427 A CN 112328427A
- Authority
- CN
- China
- Prior art keywords
- data
- reflink
- cdp
- file
- true
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000004140 cleaning Methods 0.000 claims description 18
- 230000004048 modification Effects 0.000 claims description 18
- 238000012986 modification Methods 0.000 claims description 18
- 238000004458 analytical method Methods 0.000 claims description 8
- 238000013500 data storage Methods 0.000 claims description 7
- 230000000737 periodic effect Effects 0.000 claims description 5
- 230000009286 beneficial effect Effects 0.000 description 11
- 238000011084 recovery Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 1
- 230000007774 longterm Effects 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5072—Grid computing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, which comprises the following steps: customizing a Blockdriver implementation of QEMU; determining a system disk or a data disk which needs CDP protection; performing CDP related configuration; executing QEMU customized for the Blockdriver to start the virtual machine; the virtual machine tracks the data IO of each user; reflink backup is performed on the tracked data IO of each user. The invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, which is characterized in that a Blockdriver of a QEMU is customized to track each data writing of a virtual machine, and the reflink is called to backup and protect data history, so that the characteristics of high efficiency and low space overhead of the reflink are fully utilized, the requirements of the True CDP scheme are met, and the problems of high cost or low efficiency of the prior art are solved.
Description
Technical Field
The invention relates to the technical field of cloud computing and virtualization, in particular to a method for designing and implementing a True CDP data protection scheme based on reflink.
Background
In a cloud computing and virtualization scene, a traditional data backup scheme mainly performs periodic data backup, including full backup and incremental backup, and the main scheme is a snapshot technology. The main problems of the conventional data backup scheme are as follows: the time granularity of data protection is coarse, generally, the unit of hours or days is used, the data can only be restored to a specified backup point, and the data cannot be restored to any time. However, in some application scenarios with high requirements on data security, the user has higher requirements on the granularity of data recovery, and needs to be able to recover data to any point in time, so the CDP technology is applied. CDP is an abbreviation of Continuous Data Protection, meaning Continuous Data Protection, also called real-time backup (real-time backup), and can automatically backup any modification of user Data, essentially saving any version of user Data modification, thus supporting user to restore Data to any time.
CDP differs from the traditional periodic backup scheme in that the system keeps track of every data write of the user's data and supports playback to a point in time-as we drag the video playback, switching to any time in history. This kind of CDP implementation supporting arbitrary granularity playback is called "True CDP (True CDP, True continuous data protection)", and one problem with True CDP is that its implementation is complicated, and because it needs to record each write IO of data, it introduces extra data write overhead, and has a large impact on performance. Another CDP implementation is "Near CDP" (quasi-CDP, quasi-persistent data protection). Near CDP employs a "snapshot" like scheme, but the frequency with which data is backed up is typically on the order of seconds. The Near CDP does not need to track each data IO (input and output), so the influence on the performance is small, and the second-level data protection basically meets the application scene requirements of most users CDP. However, Near CDP is only a pseudo CDP scheme, and cannot guarantee data recording and recovery of IO granularity, so that some application occasions with higher requirements on data protection granularity cannot be met.
The existing True CDP implementation technology mainly has two implementation modes of hardware-based and log-based. The hardware-based CDP writes data into a dedicated CDP hardware device through a dedicated hardware bypass. The scheme has good performance, but has high realization cost, and is only applied to special occasions which are not sensitive to cost. Another CDP scheme is implemented based on a log, that is, before data is written in each time, the data is recorded in a backup area in the form of a log, and each IO during the protection of system operation data is recorded in the backup area; when data is recovered, each history IO needs to be replayed. The scheme has the advantages of low cost and the defect that the problem of data double writing occurs, namely the data is written into the log firstly and then written into the real file, so that the space efficiency and the time efficiency are low; and when data playback, need traverse past each IO, therefore playback efficiency is lower.
Based on the problems, the invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, which is characterized in that a Blockdriver (closed driver) of a QEMU (Quick indicator, an open-source management program capable of performing hardware virtualization) is customized to track each data writing of a virtual machine, and reflink (reference link) is called to perform backup protection on data history, so that the characteristics of high efficiency and low space overhead of the reflink are fully utilized, and the requirement of the True CDP scheme is met.
Disclosure of Invention
The invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, which is characterized in that a Blockdriver of a QEMU is customized to track each data writing of a virtual machine, and the reflink is called to backup and protect data history, so that the characteristics of high efficiency and low space overhead of the reflink are fully utilized, the CDP data protection scheme based on IO granularity is implemented, and the problems of limited application and low playback efficiency in the prior art are solved.
The invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, which comprises the following steps:
determining a system disk or a data disk which needs CDP protection;
performing CDP related configuration;
executing QEMU customized for the Blockdriver to start the virtual machine;
the virtual machine tracks the data IO of each user;
reflink backup is performed on the tracked data IO of each user.
Further, the performing CDP related configuration comprises: the method ensures that a file system where the data is located supports a reflink characteristic, specifies a reflink data protection backup storage position and makes a historical data backup strategy.
Further, the executing the QEMU customized to the blockadriver to start the virtual machine further includes: modifying the Blockdriver implementation of QEMU;
the modification of the Blockdriver implementation of the QEMU is carried out by adding a hook function, and the data writing method is modified by means of the hook function.
Further, the process of implementing the method modification for data writing by means of the hook function includes:
judging data writing to obtain a judgment result;
calling a reflink interface of a bottom file system according to the judgment result;
and performing reflink backup on the file before data writing through the invoked reflink interface of the bottom layer file system.
Further, when the data writing is judged, if the data writing operation is performed, the reflink needs to be executed to perform backup protection on the data before the data is written into the back-end file, and then the data writing is executed; if it is a data read operation, it is directly ignored.
Further, while reflink backup is performed on the file before data writing, the modification time of the file before data writing is recorded.
Further, still include:
recovering historical data and regularly cleaning a reflink data copy;
when a user wants to obtain the data of the appointed time again, the historical data can be obtained again by recovering;
with the increase of the reflink backup data, the CDP regularly cleans the reflink copy file based on the consideration of space overhead.
Further, the process of recovering the historical data includes:
determining a time point of data desired to be restored;
retrieving a reflink copy corresponding to the time point of the data to be recovered to obtain a retrieval result;
and starting the system or restoring the data disc by taking the retrieval result as a restoring point.
Further, the periodically cleaning the reflink data copy comprises:
setting a periodic cleaning time interval;
analyzing and sorting the reflink backed-up files according to the time interval to obtain an analyzing and sorting result;
determining a file of the reflink backup to be deleted according to the analysis and sorting result;
and cleaning the file to be deleted which is backed up by the reflink.
Further, the analyzing and sorting of the reflink backed-up files comprises judging the time of the reflink backed-up files and judging the data granularity of the reflink backed-up files;
the judgment of the time of the reflink backed file determines whether the reflink backed file is recent or more remote by judging the time of the reflink backed file;
the judgment of the data granularity of the reflink backed file determines whether the reflink backed file is subjected to coarse-granularity data storage or fine-granularity data storage by judging the data granularity of the reflink backed file.
The invention has the beneficial effects that:
(1) the method and the device provided by the invention have the advantages that the Block driver of the QEMU is customized to track each data writing of the virtual machine, and the reflink is called to backup and protect the data history, so that the characteristics of high efficiency and low space overhead of the reflink are fully utilized, and the CDP data protection scheme based on IO granularity is realized.
(2) The CDP scheme can be supported as long as the file system supports the reflink characteristic, and the CDP scheme has a wide application range.
(3) According to the invention, when a user prepares to recover data at a certain moment, a recovery time point is selected; the CDP system will search the reflink copy corresponding to the time point, and start the system or recover the data disk by using the copy as the recovery point, so as to complete the history recovery of the data and avoid the occurrence of the data double-write problem.
(4) The method and the device achieve the purposes of cleaning the historical reflink backup at the bottom layer and reducing the occupation of the disk space by regularly cleaning the reflink data copy, so that the requirement of the whole method on the size of the occupied space is lowered.
(5) The method can be applied to any cloud computing and virtualized CDP data protection requirement scene.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
fig. 1 is a flowchart of a method for designing and implementing a True CDP data protection scheme based on reflink according to the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
As shown in fig. 1, an embodiment of the present invention provides a method for designing and implementing a True CDP data protection scheme based on reflink, including:
determining a system disk or a data disk which needs CDP protection;
performing CDP related configuration;
executing QEMU customized for the Blockdriver to start the virtual machine;
the virtual machine tracks the data IO of each user;
reflink backup is performed on the tracked data IO of each user.
The principle of the technical scheme is as follows: the method for designing and implementing the True CDP data protection scheme based on reflink comprises the following steps: determining a system disk or a data disk which needs CDP protection; performing CDP related configuration; executing QEMU customized for the Blockdriver to start the virtual machine; the virtual machine tracks the data IO of each user; reflink backup is performed on the tracked data IO of each user.
The beneficial effects of the above technical scheme are that: according to the technical scheme, the method for designing and implementing the True CDP data protection scheme based on the reflink is characterized in that a Blockdriver of a QEMU is customized to track each data writing of a virtual machine, and the reflink is called to backup and protect data history, so that the characteristics of high efficiency and low space overhead of the reflink are fully utilized, and the CDP data protection scheme based on IO granularity is implemented; meanwhile, the method does not depend on a specific file system, can support the CDP scheme as long as the file system supports the reflink characteristic, has a wide application range, and is low in cost of the design and implementation method of the True CDP data protection scheme based on the reflink.
In an embodiment of the present invention, the performing CDP related configuration includes: the method ensures that a file system where the data is located supports a reflink characteristic, specifies a reflink data protection backup storage position and makes a historical data backup strategy.
The principle of the technical scheme is as follows: in the above technical solution, when performing CDP related configuration, a file system where data is located should support a reflink characteristic, specify a reflink data protection backup storage location, and determine a historical data backup policy.
The beneficial effects of the above technical scheme are that: through the technical scheme, when carrying out CDP related configuration, at least the fact that a file system where data is located supports a reflink characteristic, setting a reflink data protection backup storage position and setting a historical data backup strategy are required, so that the design and implementation method of the True CDP data protection scheme based on reflink can be implemented.
In an embodiment provided by the present invention, the executing the process of starting the virtual machine by the QEMU customized to the blockadriver further includes: modifying the Blockdriver implementation of QEMU;
the modification of the Blockdriver implementation of the QEMU is carried out by adding a hook function, and the data writing method is modified by means of the hook function.
The principle of the technical scheme is as follows: in the technical scheme, in the process of starting the virtual machine by executing the QEMU customized to the Blockdriver, the Blockdriver implementation of the QEMU is modified by adding a hook function, and a method for writing data is modified.
The beneficial effects of the above technical scheme are that: according to the technical scheme, the method for writing data is modified by means of the hook function, and further modification of the Blockdriver implementation of QEMU is achieved, so that the Blockdriver implementation of QEMU supports tracking of IO granularity.
In an embodiment provided by the present invention, the process of implementing the method modification for data writing by means of a hook function includes:
judging data writing to obtain a judgment result;
calling a reflink interface of a bottom file system according to the judgment result;
and performing reflink backup on the file before data writing through the invoked reflink interface of the bottom layer file system.
The principle of the technical scheme is as follows: in the process of modifying the data writing method through the hook function, firstly, judging the data writing to obtain a judgment result; then, calling a reflink interface of the bottom file system according to the judgment result; and finally, reflink backup is carried out on the file before data writing through the called reflink interface of the bottom layer file system.
The beneficial effects of the above technical scheme are that: the technical scheme realizes the modification of the data writing method, calls the reflink to perform backup protection on the data history, fully utilizes the characteristics of high efficiency and low space overhead of the reflink, and meets the requirements of the True CDP scheme.
In an embodiment provided by the present invention, when determining data writing, if the data writing operation is performed, a reflink needs to be executed to perform backup protection on the data before the data is written into a back-end file, and then data writing is performed; if it is a data read operation, it is directly ignored.
The principle of the technical scheme is as follows: in the technical scheme, in the process of judging data writing, if the data writing operation is carried out, the reflink needs to be executed to carry out backup protection on the data before the data is written into a back-end file, and then the data writing is carried out; if the operation is data reading operation, the reflink does not need to be executed to backup and protect the data and execute data writing.
The beneficial effects of the above technical scheme are that: by the technical scheme, the data writing is judged, so that the reflink is executed to perform backup protection on the data only aiming at the data writing operation before the data is written into the back-end file, and the data writing is performed by means of the re-execution data.
In an embodiment provided by the invention, the modification time of the file before the data is written is recorded while reflink backup is performed on the file before the data is written.
The principle of the technical scheme is as follows: in the technical scheme, the reflink backup is carried out on the file before data writing, and meanwhile, the modification time of the file before data writing is recorded.
The beneficial effects of the above technical scheme are that: by the technical scheme, the historical modification time of the file before data writing is conveniently and clearly known, and matching and correspondence are also facilitated.
In one embodiment, the present invention further includes:
recovering historical data and regularly cleaning a reflink data copy;
when a user wants to obtain the data of the appointed time again, the historical data can be obtained again by recovering;
with the increase of the reflink backup data, the CDP regularly cleans the reflink copy file based on the consideration of space overhead.
The principle of the technical scheme is as follows: in the technical scheme, the method for designing and implementing the True CDP data protection scheme based on reflink is used for customizing the Blockdriver implementation of QEMU; determining a system disk or a data disk which needs CDP protection; performing CDP related configuration; executing QEMU customized for the Blockdriver to start the virtual machine; the virtual machine tracks the data IO of each user; besides the steps of reflink backup of the tracked data IO of each user, historical data recovery and periodical cleaning of reflink data copy are carried out.
The beneficial effects of the above technical scheme are that: by the technical scheme, when a user wants to obtain the data of the appointed time again, the historical data can be obtained again by recovering; as the reflink backup data increases, the CDP regularly cleans the reflink copy files based on the consideration of space overhead; the method for designing and implementing the True CDP data protection scheme based on reflink not only can reduce the occupation of disk space, but also can implement the recovery and the reacquisition of data at any time.
In an embodiment provided by the present invention, the process of recovering the historical data includes:
determining a time point of data desired to be restored;
retrieving a reflink copy corresponding to the time point of the data to be recovered to obtain a retrieval result;
and starting the system or restoring the data disc by taking the retrieval result as a restoring point.
The principle of the technical scheme is as follows: when a user wants to retrieve data of a designated time, first, determining a time point of the data that is desired to be recovered; then finding a reflink copy corresponding to the time point of the data to be recovered through retrieval, and determining a retrieval result; then, the system is started or the data disk is restored with the retrieval result as a restoration point.
The beneficial effects of the above technical scheme are that: when the technical scheme is used for recovering the historical data, each historical IO does not need to be played back (replay), only the time point of the historical data which is required to be recovered or is required to be recovered is determined, then the reflink copy of the corresponding time point is retrieved according to the time point, finally the retrieved reflink copy is used as a recovery point to start a system or recover a data disc, the data at the specified time can be recovered, and the data at the specified time is recovered.
In an embodiment provided by the present invention, the periodically cleaning the reflink data copy includes:
setting a periodic cleaning time interval;
analyzing and sorting the reflink backed-up files according to the time interval to obtain an analyzing and sorting result;
determining a file of the reflink backup to be deleted according to the analysis and sorting result;
and cleaning the file to be deleted which is backed up by the reflink.
The principle of the technical scheme is as follows: in the process of regularly cleaning the reflink data copy, firstly, setting a regular cleaning time interval, and then, analyzing and sorting the reflink backed-up file according to the time interval to obtain an analyzing and sorting result; then, determining a file backed up by the reflink to be deleted according to the analysis and sorting result; and finally, cleaning the file to be deleted which is backed up by the reflink.
The beneficial effects of the above technical scheme are that: through above-mentioned technical scheme according to the user set for the regular clearance time interval historical reflink backup of bottom clear up, reduce the occupation to disk space, it is right still to carry out the in-process of regular clearance moreover the file of reflink backup carries out the analysis arrangement for the probability of making mistakes of clearance process reduces, just before the process of carrying out the analysis arrangement at every turn just to carry out the analysis arrangement apart from the time of clearing up last time in the newly-increased reflink backup's file, and then also make the time that the clearance process was occupied shorten.
In an embodiment provided by the present invention, the analyzing and sorting of the reflink backed-up files includes judging the time of the reflink backed-up files and judging the data granularity of the reflink backed-up files;
the judgment of the time of the reflink backed file determines whether the reflink backed file is recent or more remote by judging the time of the reflink backed file;
the judgment of the data granularity of the reflink backed file determines whether the reflink backed file is subjected to coarse-granularity data storage or fine-granularity data storage by judging the data granularity of the reflink backed file.
The principle of the technical scheme is as follows: in the technical scheme, the reflink backed files are analyzed and sorted by judging the time of the reflink backed files and the data granularity of the reflink backed files, so that the analysis and sorting results of the reflink backed files on the time and the data granularity are obtained.
The beneficial effects of the above technical scheme are that: by the technical scheme, the files backed up by the reflink are analyzed and sorted, so that the files backed up by the reflink are presented neatly and clearly according to the sorted and analyzed attributes, the files backed up by the reflink to be deleted are convenient to determine, fine-grained protection on recent data is facilitated, and only coarse-grained data storage on long-term data is facilitated.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A method for designing and implementing a True CDP data protection scheme based on reflink is characterized by comprising the following steps:
customizing a Blockdriver implementation of QEMU;
determining a system disk or a data disk which needs CDP protection;
performing CDP related configuration;
executing QEMU customized for the Blockdriver to start the virtual machine;
the virtual machine tracks the data IO of each user;
reflink backup is performed on the tracked data IO of each user.
2. The method of claim 1, wherein the design and implementation of the True CDP data protection scheme based on reflink,
the performing CDP-related configuration comprises: the method ensures that a file system where the data is located supports a reflink characteristic, specifies a reflink data protection backup storage position and makes a historical data backup strategy.
3. The method of claim 1, wherein the design and implementation of the True CDP data protection scheme based on reflink,
the process of executing the QEMU customized to the Blockdriver to start the virtual machine further comprises the following steps: modifying the Blockdriver implementation of QEMU;
the modification of the Blockdriver implementation of the QEMU is carried out by adding a hook function, and the data writing method is modified by means of the hook function.
4. The design and implementation method of a True CDP data protection scheme based on reflink as claimed in claim 3,
the process for realizing the modification of the data writing method by means of the hook function comprises the following steps:
judging data writing to obtain a judgment result;
calling a reflink interface of a bottom file system according to the judgment result;
and performing reflink backup on the file before data writing through the invoked reflink interface of the bottom layer file system.
5. The design and implementation method of a True CDP data protection scheme based on reflink of claim 4,
when the data writing is judged, if the data writing operation is carried out, the reflink needs to be executed to carry out backup protection on the data before the data is written into the back-end file, and then the data writing is executed; if it is a data read operation, it is directly ignored.
6. The design and implementation method of a True CDP data protection scheme based on reflink of claim 4,
and recording the modification time of the file before the data is written while reflink backup is carried out on the file before the data is written.
7. The method of claim 1, wherein the method for designing and implementing a True CDP data protection scheme based on reflink further comprises:
recovering historical data and regularly cleaning a reflink data copy;
when a user wants to obtain the data of the appointed time again, the historical data can be obtained again by recovering;
with the increase of the reflink backup data, the CDP regularly cleans the reflink copy file based on the consideration of space overhead.
8. The design and implementation method of a True CDP data protection scheme based on reflink of claim 7,
the process of recovering the historical data comprises the following steps:
determining a time point of data desired to be restored;
retrieving a reflink copy corresponding to the time point of the data to be recovered to obtain a retrieval result;
and starting the system or restoring the data disc by taking the retrieval result as a restoring point.
9. The design and implementation method of a True CDP data protection scheme based on reflink of claim 7,
the periodically cleaning the reflink data copy comprises the following steps:
setting a periodic cleaning time interval;
analyzing and sorting the reflink backed-up files according to the time interval to obtain an analyzing and sorting result;
determining a file of the reflink backup to be deleted according to the analysis and sorting result;
and cleaning the file to be deleted which is backed up by the reflink.
10. The design and implementation method of a True CDP data protection scheme based on reflink of claim 9,
the analyzing and sorting of the reflink backed files comprises judging the time of the reflink backed files and judging the data granularity of the reflink backed files;
the judgment of the time of the reflink backed file determines whether the reflink backed file is recent or more remote by judging the time of the reflink backed file;
the judgment of the data granularity of the reflink backed file determines whether the reflink backed file is subjected to coarse-granularity data storage or fine-granularity data storage by judging the data granularity of the reflink backed file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085970.8A CN112328427A (en) | 2020-10-12 | 2020-10-12 | Method for designing and implementing True CDP data protection scheme based on reflink |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011085970.8A CN112328427A (en) | 2020-10-12 | 2020-10-12 | Method for designing and implementing True CDP data protection scheme based on reflink |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112328427A true CN112328427A (en) | 2021-02-05 |
Family
ID=74314816
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011085970.8A Withdrawn CN112328427A (en) | 2020-10-12 | 2020-10-12 | Method for designing and implementing True CDP data protection scheme based on reflink |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112328427A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114327270A (en) * | 2021-12-23 | 2022-04-12 | 郑州云海信息技术有限公司 | Request processing method, device, equipment and readable storage medium |
| CN114546276A (en) * | 2022-02-23 | 2022-05-27 | 华云数据控股集团有限公司 | High-availability data storage read-write method, system, device and equipment |
-
2020
- 2020-10-12 CN CN202011085970.8A patent/CN112328427A/en not_active Withdrawn
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114327270A (en) * | 2021-12-23 | 2022-04-12 | 郑州云海信息技术有限公司 | Request processing method, device, equipment and readable storage medium |
| CN114327270B (en) * | 2021-12-23 | 2023-09-15 | 郑州云海信息技术有限公司 | Request processing method, device, equipment and readable storage medium |
| CN114546276A (en) * | 2022-02-23 | 2022-05-27 | 华云数据控股集团有限公司 | High-availability data storage read-write method, system, device and equipment |
| CN114546276B (en) * | 2022-02-23 | 2024-04-30 | 华云数据控股集团有限公司 | High-availability data storage read-write method, system, device and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7720817B2 (en) | Method and system for browsing objects on a protected volume in a continuous data protection system | |
| US7325159B2 (en) | Method and system for data recovery in a continuous data protection system | |
| US7284019B2 (en) | Apparatus, system, and method for differential backup using snapshot on-write data | |
| US7650533B1 (en) | Method and system for performing a restoration in a continuous data protection system | |
| US20190370117A1 (en) | File level access to block level incremental backups of a virtual disk | |
| US8868507B2 (en) | Method and apparatus for data recovery using storage based journaling | |
| US7680996B2 (en) | Method and system for shrinking a set of data using a differential snapshot, a watch-list structure along with identifying and retaining updated blocks | |
| US9558072B1 (en) | Block-level incremental recovery of a storage volume | |
| US8732417B1 (en) | Techniques for creating snapshots of a target system | |
| US7873601B1 (en) | Backup of incremental metadata in block based backup systems | |
| AU700681B2 (en) | A method of operating a computer system | |
| US20110022811A1 (en) | Information backup/restoration processing apparatus and information backup/restoration processing system | |
| US20030167380A1 (en) | Persistent Snapshot Management System | |
| US20110246706A1 (en) | Disk array configuration program, computer, and computer system | |
| JPH0823841B2 (en) | Data processing system and method | |
| CN112328427A (en) | Method for designing and implementing True CDP data protection scheme based on reflink | |
| CN102541691B (en) | Log check point recovery method applied to memory data base OLTP (online transaction processing) | |
| CN111338844A (en) | Database backup management method and electronic equipment | |
| CN112269681A (en) | Method, device and equipment for continuously protecting virtual machine data | |
| CN111611108A (en) | Method and device for restoring virtual database | |
| CN112130760A (en) | Data writing method, device and medium based on True CDP | |
| CN110674502A (en) | Data detection method and device | |
| KR101738965B1 (en) | Apparatus and method for journaling based on garbage collection | |
| US20060217952A1 (en) | Backup/recovery system and methods regarding the same | |
| JP2015114750A (en) | Examination program, information processing device, and information processing 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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210205 |
|
| WW01 | Invention patent application withdrawn after publication |