CN105550063B - A kind of disaster recovery method based on continuous data protection and kvm virtualization - Google Patents
A kind of disaster recovery method based on continuous data protection and kvm virtualization Download PDFInfo
- Publication number
- CN105550063B CN105550063B CN201510884272.7A CN201510884272A CN105550063B CN 105550063 B CN105550063 B CN 105550063B CN 201510884272 A CN201510884272 A CN 201510884272A CN 105550063 B CN105550063 B CN 105550063B
- Authority
- CN
- China
- Prior art keywords
- disk
- disaster tolerance
- data
- time point
- virtual disk
- 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.)
- Expired - Fee Related
Links
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/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to a kind of disaster recovery methods virtualized based on continuous data protection and kvm, comprising: A, starting disaster tolerance task；B, emergency recovery has been judged whether to, if so, thening follow the steps C, if not, then the disaster tolerance end continues waiting for the backup end generation time point, and from the backup end acquisition time point, respective virtual disk is written in the data block in each time point；C, snapshot successively is carried out to each piece of kvm virtual disk, disaster tolerance task terminates after the completion；D, it is again started up disaster tolerance task, then first to each piece of kvm virtual disk rollback snapshot, then obtains the data block in unrecovered each time point that at time point, will acquire from the backup end and respective virtual disk is written.Compared with prior art, the present invention has many advantages, such as the permanent loss for improving disaster tolerance efficiency, avoiding user's creation data.
Description
Technical field
The present invention relates to computer information storage technology fields, are based on continuous data protection and kvm more particularly, to one kind
The disaster recovery method of virtualization.
Background technique
With the rapid development of science and technology, the information age has nowadays been entered, the value of information is self-evident, and is counting
In calculation machine field, data are the carriers of information, so being exactly the most important thing to the protection of data.And how will correctly and efficiently count
It is then current more popular research topic according to protecting.Continuous data protection, also referred to as lasting backup, is realization number
According to one of the approach of protection.
Block level backup refers to for anti-locking system operation error occur or the system failure leads to loss of data, and will all or
Partial data set copies to the process of other storage mediums from the hard disk or array of applied host machine.Such as China Patent Publication No.
A kind of Block level backup method based on content address storage is disclosed for CN103365745A, and this method includes two stages: first
Stage carries out piecemeal and initialization backup to data in magnetic disk using full dose state bitmap technology.Second stage, using delta state
Bitmap technology carries out piecemeal and incremental backup to data in magnetic disk.Wherein, full dose state bitmap is refer in particular to obtain from book the
One part bitmap, reflection be in book data block by service condition, physical record is source volume data block use state
0 and 1 sequence, a data block corresponds to one of bitmap, and the 0 expression data block is still not used by, and 1 indicates opposite situation.
The reflection of delta state bitmap be the data block in book since the last time bitmap more new state, according to the spatial and temporal distributions of data
Characteristic, 1 sequence in delta state bitmap are more concentrated usually than 1 sequence much less in full dose state bitmap.The party
The specific step of method are as follows:
1, source book is segmented: being single with data block according to predefined data segment size threshold values and source book full dose state bitmap
, continuous 1 sequence in source book full dose state bitmap is foundation, is segmented to source volume data area, and each single section is known as one
A data segment；
2, all data segments of source book initial transmission (backup): are passed through into network transmission to storage medium；
3, it obtains delta state bitmap: obtaining source volume data more new state in real time, calculate data block and update section, then give birth to
At source book delta state bitmap, the backup of incremental data block is finally carried out；
4, the incremental data section of source book incremental transmission (backup): is passed through into network transmission to storage medium.
Continuous data protection CDP refers to by being implanted into file system filter driver in operating system kernel layer, comes real-time
Capture All Files access operation.For needing CDP to continue the file of backup protection, when CDP Admin module is via file filter
When its rewriting operation is intercepted in driving, then in advance by file data changing unit together with current system timestamp (System
Time Stamp) together automated back-up into storage medium.In theory, any primary file data variation all can be by certainly
Dynamic record, so being called continuous data protection.
On the basis of above-mentioned lasting Block level backup method, how quickly and efficiently to make operating system and upper layer application also
As far as different machine, and allow to operate normally and use be the problem to be solved in the present invention.
Summary of the invention
It is an object of the present invention to overcome the above-mentioned drawbacks of the prior art and provide a kind of raising disaster tolerance efficiency,
Avoid the disaster recovery method based on continuous data protection and kvm virtualization of user's creation data permanently lost.
The purpose of the present invention can be achieved through the following technical solutions:
A kind of disaster recovery method based on continuous data protection and kvm virtualization, which comprises the following steps:
A, start disaster tolerance task, task is related to backing up end and disaster tolerance end；Wherein the backup supports continuous generation time point,
After the backup end generates first time point, in the disaster tolerance end creation kvm virtual machine and virtual disk, and from institute
Respective virtual disk is written in data block in each time point by the backup end acquisition time point stated；
B, emergency recovery has been judged whether to, if so, C is thened follow the steps, if it is not, then the disaster tolerance end continues waiting for
The backup end generation time point, and from the backup end acquisition time point, the data block in each time point is write
Enter respective virtual disk；
C, snapshot successively is carried out to each piece of kvm virtual disk, disaster tolerance task terminates after the completion；
D, it is again started up disaster tolerance task, then first to each piece of kvm virtual disk rollback snapshot, then is obtained from the backup end
Unrecovered time point is taken, respective virtual disk is written in the data block in each time point that will acquire.
The step A specifically:
A1) disaster tolerance task is applied in starting, and the backup end starts copied chunks to media server and continues to generate
Time point, the disaster tolerance end then send recovery request to media server；
A2 the Backup Data in media server traversal various time points described in), and one by one will be in each time point
Data are sent to the disaster tolerance end；
Whether the Backup Data that the disaster tolerance end judgement described in A3) receives is data block object, if so, thening follow the steps
A8), if it is not, thening follow the steps A4)；
A4 the disaster tolerance end described in) judges whether Redundancy Machine has been created according to the data object received, if so, holding
Row step A6), if it is not, thening follow the steps A5)；
A5 the disaster tolerance end described in) creates kvm Redundancy Machine according to the title specified in disaster tolerance task, and executes step A6)；
A6 the disaster tolerance end described in) judges whether disk where monitoring volume has been created according to the data object received, if
It is then to open disk handle, and return step A2), if it is not, thening follow the steps A7)；
A7 it) is run after fame with call number of the hard disk in original production machine, the virtual disk of creation and former hard disk equal sizes, and beat
The disk handle for building completion is started, virtual disk, return step A2 is written into guidance information)；
Virtual disk, return step A2 is written in the data block received by the disaster tolerance end described in A8) one by one).
Call number, former hard disk size and the guidance information is maintained in the metadata of data object.
The step A3) in, the Backup Data type that disaster tolerance termination receives is divided into data object and data block object, backs up
One monitored partition tissue is become a data object by end, and by each attribute record of the monitored partition in the member of data object
In data.
The step A3) in,
The step A8) in, virtual disk is written in the data block received by disaster tolerance end one by one specifically:
801) the disk handle opened is obtained；
802) data block is calculated with respect to disk deviation post, i.e. offset and number of the initial position of monitored partition relative to disk
According to the sum of block own offset, wherein the offset relative to disk is obtained from the metadata of data object, the own offset is
Offset of the initial position of data block relative to monitored partition；
It 803) is write-in length with the length of the data block, the deviation post writing data blocks described in 802).
The disaster tolerance end is kvm virtual platform.
The step C specifically:
C1 the virtual disk on kvm virtual machine) is traversed；
C2) virtual disk for traversing C1) is unloaded from virtual machine；
C3 sub-disk) is created using the virtual disk that C1) is traversed as stamper, and by record stamper sub-disk；
C4) by the sub-disk carry created in C3) to virtual machine, return step C1).
The step D specifically:
D1 the virtual disk on kvm virtual machine) is traversed；
D2) virtual disk for traversing D1) is unloaded from virtual machine；
D3) according to record, D1 is found) traverse the stamper of virtual disk；
D4) by the stamper carry found in D3) to virtual machine, return step D1).
The data object is a kind of model as made of the attribute information tissue of monitored partition, and only with a whole world
One identifier name.
The data block object is the opposite monitored partition start bit of binary data slice, the slice by monitored partition
A kind of model made of the length tissue of the offset set and the slice, and the name of the data object corresponding to corresponding monitored partition
Claim to name, data object corresponding to same monitored partition and data block object are one-to-many relationships.
Compared with prior art, the invention has the following advantages that
1) the application disaster tolerance of traditional file-level is influenced greatly by upper layer factor, is especially reached in topmost paper quantity
Million even millions when, the performance degradation using disaster recovery method of file-level substantially prolongs the disaster recovery time
RTO.Continuous data protection and recovery of the present invention using block rank, there is better performance in performance, without considering that upper layer is grasped
Make system, file system, influence brought by quantity of documents, improve the speed of production environment reduction, accelerates the time of reduction,
Reduce the risk that user data caused by being interrupted due to upper-layer service is permanently lost.
2) present invention using to kvm disk progress snapshot and rollback snapshot by the way of, realize disaster tolerance task again
The data being initiated in rear disk can revert to the state at the end of last task, without because user in disaster tolerance twice
The execution of a disaster tolerance task, can more prevent the behaviour due to user after influencing during task on the modification that data in magnetic disk is made
Make improper the phenomenon that leading to Redundancy Machine delay machine and can not retrieving.
Detailed description of the invention
Fig. 1 is the structure chart of virtualization applications disaster tolerance of the present invention；
Fig. 2 is the flow diagram of virtualization applications disaster tolerance of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiment is a part of the embodiments of the present invention, rather than whole embodiments.Based on this hair
Embodiment in bright, those of ordinary skill in the art's every other reality obtained without making creative work
Example is applied, all should belong to the scope of protection of the invention.
Disaster tolerance system by production server (including backup client), kvm virtual platform (include restore client) and
Console (including media server) composition, console are connected with production server, kvm virtual platform by Ethernet respectively
It connects, the transport protocol of use is TCP/IP.The structure chart of whole system is as shown in Figure 1.
The embodiment of the present invention provides a kind of disaster recovery method based on continuous data protection and KVM virtualization, Concrete workflow
Journey schematic diagram is as shown in Figure 2, comprising the following steps:
As shown in Fig. 2, backup end (end cdp) and disaster tolerance end (end cdr) starts execution simultaneously after disaster tolerance task is initiated:
The step end s001, cdp carries out complete initialization backup, and generates complete initialization time point；
Step s002 judges whether to have generated complete initialization time point, if so, s003 is entered step, if it is not, then returning
Return step s001；
The step end s003, cdp carries out incremental backup, and generates Delta Time point；
Step s004, cdp implement process, and non-this patent emphasis is not specifically described herein；
Step s005, after the end cdp generates complete initialization time point, the end cdr is waken up from wait state, is checked
Kvm disaster tolerance virtual machine whether there is, if so, s007 is entered step, if it is not, then entering step s006；
Step s006 creates kvm disaster tolerance virtual machine, and goes to step s009；
Step s007, checks whether kvm disaster tolerance virtual machine is in open state, if so, s008 is entered step, if it is not,
Then enter step s009；
Step s008 closes kvm disaster tolerance virtual machine, and goes to step s009；
Step s009, data object in recovery time point obtain out from the metadata of the object and need to be resumed
Partition information, information specifically include: partition size, disk size where subregion, rope of the disk in original production machine where subregion
Draw number, deviant of the subregion with respect to place disk, the guidance information of disk where subregion.
Step s010, according to " index number of the disk where subregion in original production machine " got in step s009,
Judge whether disk where subregion is present in kvm disaster tolerance virtual machine, if so, s011 is entered step, if it is not, then entering step
Rapid s012；
Step s011, according to " the guidance letter of disk where disk size, subregion where subregion got in step s009
Breath " creates one piece of new disk for kvm Redundancy Machine and guidance information is written；
Step s012, the data block of data object, that is, get the deviant of data block itself in recovery time point, passes through
The block is calculated relative to the offset that disk will be written, the content of writing data blocks at deviation post；
Step s013, judges whether all data blocks in the data object are all restored to complete, if so, entering step
S014, if it is not, then return step s012；
Step s014, judges whether all data objects in the time point all restore to complete, if so, entering step
S015, if it is not, then return step s009；
Step s015 judges whether to have initiated emergency recovery operation, if so, the disk to kvm Redundancy Machine carries out snapshot
And terminate this disaster tolerance task, if it is not, then entering step s016；
Step s016, judges whether all time points all restore to complete, generates newly if so, continuing waiting for the end cdp
Time point, if it is not, then return step s009.
The above description is merely a specific embodiment, but scope of protection of the present invention is not limited thereto, any
Those familiar with the art in the technical scope disclosed by the present invention, can readily occur in various equivalent modifications or replace
It changes, these modifications or substitutions should be covered by the protection scope of the present invention.Therefore, protection scope of the present invention should be with right
It is required that protection scope subject to.
Claims (7)
1. a kind of disaster recovery method based on continuous data protection and kvm virtualization, which comprises the following steps:
A, start disaster tolerance task, task is related to backing up end and disaster tolerance end；Wherein the backup supports continuous generation time point, to institute
After the backup end stated generates first time point, in the disaster tolerance end creation kvm virtual machine and virtual disk, and from described
End acquisition time point is backed up, respective virtual disk is written into the data block in each time point；
B, emergency recovery has been judged whether to, if so, C is thened follow the steps, if it is not, described in then the disaster tolerance end continues waiting for
Backup end generation time point phase is written into the data block in each time point and from the backup end acquisition time point
Answer virtual disk；
C, snapshot successively is carried out to each piece of kvm virtual disk, disaster tolerance task terminates after the completion；
D, it is again started up disaster tolerance task, then first to each piece of kvm virtual disk rollback snapshot, then not from the backup end acquisition
Respective virtual disk is written in the time point of recovery, the data block in each time point that will acquire；
The step C specifically:
C1 the virtual disk on kvm virtual machine) is traversed；
C2) virtual disk for traversing C1) is unloaded from virtual machine；
C3 sub-disk) is created using the virtual disk that C1) is traversed as stamper, and by record stamper sub-disk；
C4) by the sub-disk carry created in C3) to virtual machine, return step C1)；
The step D specifically:
D1 the virtual disk on kvm virtual machine) is traversed；
D2) virtual disk for traversing D1) is unloaded from virtual machine；
D3) according to record, D1 is found) traverse the stamper of virtual disk；
D4) by the stamper carry found in D3) to virtual machine, return step D1)；
The step A specifically:
A1) disaster tolerance task is applied in starting, and the backup end starts copied chunks to media server and continues generation time
Point, the disaster tolerance end then send recovery request to media server；
A2 the Backup Data in media server traversal various time points described in), and one by one by the data in each time point
It is sent to the disaster tolerance end；
Whether the Backup Data that the disaster tolerance end judgement described in A3) receives is data block object, if so, thening follow the steps A8), if
It is no, then follow the steps A4)；
A4 the disaster tolerance end described in) judges whether Redundancy Machine has been created according to the data object received, if so, executing step
Rapid A6), if it is not, thening follow the steps A5)；
A5 the disaster tolerance end described in) creates kvm Redundancy Machine according to the title specified in disaster tolerance task, and executes step A6)；
A6 the disaster tolerance end described in) judges whether disk where monitoring volume has been created according to the data object received, if so,
Then open disk handle, and return step A2), if it is not, thening follow the steps A7)；
A7 it) is run after fame with call number of the hard disk in original production machine, the virtual disk of creation and former hard disk equal sizes, and open wound
The disk handle for building completion, is written virtual disk, return step A2 for guidance information)；
Virtual disk, return step A2 is written in the data block received by the disaster tolerance end described in A8) one by one).
2. disaster recovery method according to claim 1, which is characterized in that call number, former hard disk size and the guidance letter
Breath is maintained in the metadata of data object.
3. disaster recovery method according to claim 1, which is characterized in that the step A3) in, disaster tolerance terminates the backup received
Data type is divided into data object and data block object, and a monitored partition tissue is become a data object by backup end, and
By each attribute record of the monitored partition in the metadata of data object.
4. disaster recovery method according to claim 1, which is characterized in that the step A8) in, number that disaster tolerance end will receive
Virtual disk is written one by one according to block specifically:
801) the disk handle opened is obtained；
802) data block is calculated with respect to disk deviation post, i.e. offset and data block of the initial position of monitored partition relative to disk
The sum of own offset, wherein the offset relative to disk is obtained from the metadata of data object, the own offset is data
Offset of the initial position of block relative to monitored partition；
It 803) is write-in length with the length of the data block, the deviation post writing data blocks described in 802).
5. disaster recovery method according to claim 1, which is characterized in that the disaster tolerance end is kvm virtual platform.
6. disaster recovery method according to claim 3, which is characterized in that the data object is the attribute by monitored partition
A kind of model made of information tissue, and named with a globally unique identifier.
7. disaster recovery method according to claim 3, which is characterized in that the data block object is by the two of monitored partition
Binary data slice, a kind of slice mould made of the offset of monitored partition initial position and the length tissue of the slice
Type, and the title of the data object corresponding to corresponding monitored partition is named, data object corresponding to same monitored partition
It is one-to-many relationship with data block object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510884272.7A CN105550063B (en) | 2015-12-03 | 2015-12-03 | A kind of disaster recovery method based on continuous data protection and kvm virtualization |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510884272.7A CN105550063B (en) | 2015-12-03 | 2015-12-03 | A kind of disaster recovery method based on continuous data protection and kvm virtualization |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105550063A CN105550063A (en) | 2016-05-04 |
| CN105550063B true CN105550063B (en) | 2019-03-22 |
Family
ID=55829259
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510884272.7A Expired - Fee Related CN105550063B (en) | 2015-12-03 | 2015-12-03 | A kind of disaster recovery method based on continuous data protection and kvm virtualization |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105550063B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106648981A (en) * | 2016-12-13 | 2017-05-10 | 龚平 | Continuous data protection based virtual machine data protection method |
| CN107797888A (en) * | 2017-11-06 | 2018-03-13 | 长沙曙通信息科技有限公司 | A kind of continuous data protection system data rollback implementation method |
| CN108255645A (en) * | 2018-01-08 | 2018-07-06 | 长沙曙通信息科技有限公司 | A kind of continuous data protection system data rollback implementation method |
| CN110972497A (en) * | 2018-11-02 | 2020-04-07 | 深信服科技股份有限公司 | Disaster recovery method and device for virtualization platform |
| CN109582497B (en) * | 2018-11-19 | 2023-05-09 | 杭州信核数据科技股份有限公司 | Rapid emergency starting method based on dynamic data increment |
| CN110362273A (en) * | 2019-06-05 | 2019-10-22 | 黄疆 | Noise-reduction method and system based on hardware intelligence reduction of speed |
| CN112817698A (en) * | 2021-02-20 | 2021-05-18 | 咪咕音乐有限公司 | Virtual machine backup method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103365745A (en) * | 2013-06-07 | 2013-10-23 | 上海爱数软件有限公司 | Block level backup method based on content-addressed storage and system |
| CN103530204A (en) * | 2013-10-15 | 2014-01-22 | 上海爱数软件有限公司 | Method and system for real-time data backup |
| CN104090828A (en) * | 2014-07-24 | 2014-10-08 | 浪潮(北京)电子信息产业有限公司 | Real-time data backup method and system |
| CN104102556A (en) * | 2014-06-13 | 2014-10-15 | 上海爱数软件有限公司 | Disk data backup and recovering method of virtual machine |
| CN104461776A (en) * | 2014-11-26 | 2015-03-25 | 上海爱数软件有限公司 | Application disaster tolerance method based on CDP and iSCSI virtual disk technology |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008046101A2 (en) * | 2006-10-13 | 2008-04-17 | Ariel Silverstone | Client authentication and data management system |
-
2015
- 2015-12-03 CN CN201510884272.7A patent/CN105550063B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103365745A (en) * | 2013-06-07 | 2013-10-23 | 上海爱数软件有限公司 | Block level backup method based on content-addressed storage and system |
| CN103530204A (en) * | 2013-10-15 | 2014-01-22 | 上海爱数软件有限公司 | Method and system for real-time data backup |
| CN104102556A (en) * | 2014-06-13 | 2014-10-15 | 上海爱数软件有限公司 | Disk data backup and recovering method of virtual machine |
| CN104090828A (en) * | 2014-07-24 | 2014-10-08 | 浪潮(北京)电子信息产业有限公司 | Real-time data backup method and system |
| CN104461776A (en) * | 2014-11-26 | 2015-03-25 | 上海爱数软件有限公司 | Application disaster tolerance method based on CDP and iSCSI virtual disk technology |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105550063A (en) | 2016-05-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105550063B (en) | A kind of disaster recovery method based on continuous data protection and kvm virtualization | |
| JP6734866B2 (en) | Resynchronization to the first storage system after failover to the second storage system that mirrors the first storage system | |
| US9400611B1 (en) | Data migration in cluster environment using host copy and changed block tracking | |
| CN104407938B (en) | A kind of a variety of granularity restoration methods after virtual machine image level backup | |
| WO2020224023A1 (en) | Reshard method and system in distributed storage system | |
| US7415488B1 (en) | System and method for redundant storage consistency recovery | |
| US9256605B1 (en) | Reading and writing to an unexposed device | |
| CN105550062B (en) | The data reflow method restored based on continuous data protection and time point browsing | |
| US8612700B1 (en) | Method and system of performing block level duplications of cataloged backup data | |
| CN106354582B (en) | A kind of continuous data protection method | |
| CA3054040A1 (en) | Synchronously replicating datasets and other managed objects to cloud-based storage systems | |
| US10872017B2 (en) | Restoring a file system object | |
| US8793456B2 (en) | Automated migration to a new target volume via merged bitmaps to maintain consistency | |
| US7617259B1 (en) | System and method for managing redundant storage consistency at a file system level | |
| US20120072685A1 (en) | Method and apparatus for backup of virtual machine data | |
| US9983937B1 (en) | Smooth restart of storage clusters in a storage system | |
| EP2318927B1 (en) | Systems and methods for tracking changes to a volume | |
| CN101441582A (en) | Backup and recovery method of computer data object and system and program product for implementing the same | |
| US8438130B2 (en) | Method and system for replicating data | |
| JP2009506399A (en) | System and method for virtualizing backup images | |
| US20150046398A1 (en) | Accessing And Replicating Backup Data Objects | |
| US8019953B2 (en) | Method for providing atomicity for host write input/outputs (I/Os) in a continuous data protection (CDP)-enabled volume using intent log | |
| JP2012074039A (en) | System and method for distributed processing of file on chunk unit basis | |
| CN109558213A (en) | The method and apparatus for managing the virtual machine snapshot of OpenStack platform | |
| US8799596B2 (en) | Switching visibility between virtual data storage entities |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20190322 Termination date: 20191203 |