CN105550062A - Continuous data protection and time point browse recovery based data backflow method - Google Patents
Continuous data protection and time point browse recovery based data backflow method Download PDFInfo
- Publication number
- CN105550062A CN105550062A CN201510884259.1A CN201510884259A CN105550062A CN 105550062 A CN105550062 A CN 105550062A CN 201510884259 A CN201510884259 A CN 201510884259A CN 105550062 A CN105550062 A CN 105550062A
- Authority
- CN
- China
- Prior art keywords
- disaster tolerance
- task
- data
- volume
- backup
- 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.)
- Granted
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
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 invention relates to a continuous data protection and time point browse recovery based data backflow method. The continuous data protection and time point browse recovery based data backflow method comprises the following steps of A, starting a disaster recovery task which involves a backup end and a disaster recovery end, wherein the backup end provides continuous data protection cdp, and the disaster recovery end provides continuous data recovery cdr; B, after the disaster recovery task is finished, starting a disaster recovery machine to take over an original physical production machine; C, starting reverse cdp of the disaster recovery task in the disaster recovery machine, copying a Hash file in a monitoring volume into a journal volume, and carrying out Hash increment initial copying; and D, after the reverse cdp task is finished, mounting WindowsPE on the original physical production machine so as to carry out browse recovery for all the time points generated by the disaster recovery task in sequence. Compared with the prior art, the continuous data protection and time point browse recovery based data backflow method has the advantages of being convenient, fast, space-saving, time-saving and the like.
Description
Technical field
The present invention relates to computer information storage technology field, especially relate to a kind of data reflow method browsing recovery based on continuous data protection and time point.
Background technology
Along with the arrival of information age; in computer realm, data are as the carrier of information; the growth of its capacity exponentially formula; the value of data highlights; but because various subjectivity or objective reason cause the situation of corrupted data or loss to happen occasionally in daily life; this causes loss greatly and inconvenience to enterprise and user, so how to carry out effective protection to data becoming particularly important and urgent.Namely continuous data protection is current popular, and the scheme of recovery point objectives (RPO) and all higher a kind of real time data protection target release time (RTO).And continuous data protection realizes based on Block level backup.
Block level backup, refers to as anti-locking system occurs that misoperation or the system failure cause loss of data, and all or part of data acquisition is copied to the process of other storage medium from the hard disk of applied host machine or array.As Chinese patent CN103365745A discloses a kind of Block level backup method of content-based address storage, the method comprises two stages: the first stage, adopts full dose mode bit diagram technology to carry out piecemeal and initialization backup to data in magnetic disk.Subordinate phase, adopts increment mode bit diagram technology to carry out piecemeal and incremental backup to data in magnetic disk.Wherein, full dose state bitmap refers in particular to first part bitmap obtained from book, reflection be in book data block by service condition, physical record be 0 and 1 sequence of source volume data block using state, one of the corresponding bitmap of data block, 0 represents that this data block is not yet used, and 1 represents contrary situation.The reflection of increment state bitmap be the more new state of data block in book since last time bitmap, according to the spatial and temporal distributions characteristic of data, 1 sequence in increment state bitmap is usually than 1 sequence much less in full dose state bitmap, and more concentrated.The step that the method is concrete is:
1, source book segmentation: according to predefined data segment size threshold values and source book full dose state bitmap, in units of data block, continuous 1 sequence in source book full dose state bitmap is foundation, carries out segmentation to source volume data district, each single section is called a data segment;
2, initial transmission (backup): by all data segments of source book by Internet Transmission to storage medium;
3, obtain increment state bitmap: Real-time Obtaining source volume data more new state, calculate data block and upgrade interval, then generate source book increment state bitmap, finally carry out the backup of incremental data block;
4, incremental transmission (backup): by the incremental data section of source book by Internet Transmission to storage medium.
Continuous data protection CDP, referring to by implanting file system filter driver in operating system kernel layer, catching All Files accessing operation in real time.For the file needing CDP to continue backup protection; when CDP Admin module intercepts its rewriting operation via filter Driver on FSD, then in advance file data changing unit is passed through block level duplication technology automated back-up in storage medium together with current system timestamp (SystemTimeStamp).In theory, any file data change once all can be automatically recorded, so be called continuous data protection.
On the basis of the above-mentioned continuous data protection method based on block level duplication technology; VDDK (VirtualDiskDevelopmentKit) external member that duration data can be used to copy (CDR) and VMware company to be provided sets up a disaster tolerance virtual machine, commences business for replacing original production machine temporarily.
But consider performance issue, virtual machine can not replace physical machine production business for a long time, so how quick, convenient, effectively the data in original physical production machine and disaster tolerance virtual machine are replaced the data backflow that produces when original production machine is commenced business on original production machine, be the problem to be solved in the present invention.
Summary of the invention
Object of the present invention is exactly provide a kind of convenient and swift and save the data reflow method browsing recovery based on continuous data protection and time point of room and time to overcome defect that above-mentioned prior art exists.
Object of the present invention can be achieved through the following technical solutions:
Browse a data reflow method for recovery based on continuous data protection and time point, it is characterized in that, comprise the following steps:
A, startup disaster tolerance task, task relates to backup end and disaster tolerance end, described backup end provides continuous data protection cdp, described disaster tolerance end provides duration data to recover cdr, the data protection situation of monitoring volume continues to be recorded in Hash file by described backup end, this Hash file is kept on daily record volume, when copying to monitoring volume by being used for the Hash file that the initialization of Hash increment copies from daily record volume after end cdp to be backed up produces point of complete initialization time;
After B, disaster tolerance task complete, Redundancy Machine starts and adapter original physical production machine;
C, in Redundancy Machine, start the reverse cdp of disaster tolerance task, by the Hash file copy in monitoring volume in daily record volume, and carry out the initialization of Hash increment and copy;
After D, reverse cdp task complete, original physical production machine carry WindowsPE, browses recovery successively to all time points that disaster tolerance task produces.
Described steps A is specially:
A1) start disaster tolerance task, described backup end to be run after fame establishment Hash file respectively roll up drive letter to each monitoring volume in daily record volume;
A2) the backup end described in starts copied chunks to media server, and dynamically updates Hash file according to the data protection situation of monitoring volume constantly;
A3) after the backup end described in produces point of complete initialization time, Hash file is copied to monitoring volume from daily record volume;
A4) backup described in supports continuous generation Delta Time point, steps A 3 simultaneously) the middle Hash file copied also can be monitored, and the data block at its place also can be copied to media server, and is stored in Delta Time point;
A5) the disaster tolerance end described in then sends recovery request to media server asynchronously, and backup holds all time points produced to be pushed to disaster tolerance end successively, the data in each time point of disaster tolerance end sustained restoration by media server.
Hash file in described steps A carries out record by the Client Agent in described backup end and generates.
Described step C is specially:
C1) after Redundancy Machine starts, former disaster tolerance task is initiated;
C2) the backup end of current Redundancy Machine as former disaster tolerance task detected, so secondary disaster tolerance task only has backup end and do not have disaster tolerance end, and carry out reverse cdp at backup end;
C3) according to the drive letter of monitoring volume, successively each monitoring is rolled up corresponding Hash file copy in new daily record volume;
C4) disaster tolerance task detects Hash file in the daily record volume of current backup end, directly involves in the initialization of row Hash increment to monitoring and copies, after the initialization of Hash increment has copied, continue to carry out incremental replication until disaster tolerance task is stopped.
Described step D is specially:
D1) WindowsPE of original physical production machine carry built in agent program, and browse recovery request to media server transmission;
D2) all time points of media server traversal disaster tolerance task generation, and be pushed to original physical production machine one by one;
D3) Agent in WindowsPE is successively by the data write original physical production machine in each time point.
Compared with prior art, the present invention has the following advantages:
1) oppositely continuous data protection time, copying without the need to re-starting complete initialization to monitoring volume, saving the media storage space of user, and accelerate the speed that reverse duration data copies, saved the time.
2) the present invention adopts WindowsPE as intermediate medium, solves the problem that data cannot be write physics raw device.
3), during reverse continuous data protection, original physical production machine, without the need to being in starting state, only need starting when time point browses recovery, reduce the consumption of resource.
Accompanying drawing explanation
Fig. 1 is forward disaster tolerance structural representation of the present invention;
Fig. 2 is the reverse replicated architecture schematic diagram of the present invention;
Fig. 3 is that the present invention browses recovery structural representation;
Fig. 4 is forward disaster tolerance schematic flow sheet of the present invention;
Fig. 5 is that the present invention oppositely copies schematic flow sheet;
Fig. 6 is that the present invention browses recovery schematic flow sheet.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is a part of embodiment of the present invention, instead of whole embodiment.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art obtain under the prerequisite not making creative work, all should belong to the scope of protection of the invention.
Data backflow system forms by producing server (built-in backup client agency), virtual disaster recovery platform (built-in recovery Client Agent), control desk (built-in media server) and WindowsPE (built-in recovery Client Agent), all connections are all set up by Ethernet, and the host-host protocol of employing is TCP/IP.Whole data backflow system is divided into forward disaster tolerance, oppositely copies and browse recovery three processes, and its structural drawing respectively as shown in Figure 1, Figure 2, Figure 3 shows.
Forward disaster tolerance workflow as shown in Figure 4, is specially:
Step s101, after task is initiated, according to the driver title of each monitoring volume, creates corresponding Hash file respectively in daily record volume, and this Hash file is for recording the data protection situation of backup agent to monitoring volume;
Step s102, backup agent involves in the complete initialization of row to monitoring and copies, and according to the Hash file in initialized situation constantly Update log volume;
Whether step s103, judge that complete initialization copies and complete, if so, then enter step s104, if not, then return s102;
Step s104, each Hash file copy in daily record being rolled up is in corresponding monitoring volume;
Step s105, involves in row incremental replication to monitoring, and produces Delta Time point constantly, and the Hash file copied in step s104 also can be protected in Delta Time point;
Step s106, cdp specific implementation process, non-this patent emphasis, is not described specifically at this;
Step s107, after cdp end produces point of complete initialization time, cdr end is waken up from waiting status, cdr specific implementation process, and non-this patent emphasis, is not described specifically at this;
Step s108, judges whether to have initiated adapter operation, if so, then terminates disaster tolerance task, if not, then return step s107.
Reverse replication work flow process as shown in Figure 5, is specially:
Step s201, due to the daily record of original production machine volume in data not by disaster tolerance in virtual Redundancy Machine, causing former daily record to twist in current Redundancy Machine is raw form, thus first to daily record involve in formatting lines operation;
Step s202, the Hash file of being come by disaster tolerance in step s105 is copied in daily record volume (rolling up hereinafter referred to as new daily record) of formaing step s201 from the monitoring volume of Redundancy Machine;
Step s203, judges whether there is Hash file in new daily record volume, if so, then enters step s204, if not, then enter step s205;
Step s204, backup agent involves in the initialization of row Hash increment to monitoring and copies, and produces Hash increment initialization time point;
Step s205, backup agent involves in the complete initialization of row to monitoring and copies, and produces point of complete initialization time;
Step s206, judges whether to have initiated shut-down operation, if so, then terminates reverse replication task, if not, then enters step s207;
Step s207, involves in row incremental replication to monitoring, and produces Delta Time point constantly.
Browse and resume work flow process as shown in Figure 6, be specially:
Step s301, media server push time point to carry WindowsPE (WindowsPE is as the intermediate medium browsing recovery, and built-in recovery Client Agent) original physical server, by recovering Client Agent, the data in time point are write in physical disk;
Step s302, judges whether that time point is not resumed in addition, if so, then returns step s301, if not, then terminates to browse recovery tasks.
After completing forward disaster tolerance, oppositely copying and browse rejuvenation, the backflow to data can be realized.
The above; be only the specific embodiment of the present invention; but protection scope of the present invention is not limited thereto; anyly be familiar with those skilled in the art in the technical scope that the present invention discloses; can expect amendment or the replacement of various equivalence easily, these amendments or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection domain of claim.
Claims (5)
1. browse a data reflow method for recovery based on continuous data protection and time point, it is characterized in that, comprise the following steps:
A, startup disaster tolerance task, task relates to backup end and disaster tolerance end, described backup end provides continuous data protection cdp, described disaster tolerance end provides duration data to recover cdr, the data protection situation of monitoring volume continues to be recorded in Hash file by described backup end, this Hash file is kept on daily record volume, when copying to monitoring volume by being used for the Hash file that the initialization of Hash increment copies from daily record volume after end cdp to be backed up produces point of complete initialization time;
After B, disaster tolerance task complete, Redundancy Machine starts and adapter original physical production machine;
C, in Redundancy Machine, start the reverse cdp of disaster tolerance task, by the Hash file copy in monitoring volume in daily record volume, and carry out the initialization of Hash increment and copy;
After D, reverse cdp task complete, original physical production machine carry WindowsPE, browses recovery successively to all time points that disaster tolerance task produces.
2. data reflow method according to claim 1, is characterized in that, described steps A is specially:
A1) start disaster tolerance task, described backup end to be run after fame establishment Hash file respectively roll up drive letter to each monitoring volume in daily record volume;
A2) the backup end described in starts copied chunks to media server, and dynamically updates Hash file according to the data protection situation of monitoring volume constantly;
A3) after the backup end described in produces point of complete initialization time, Hash file is copied to monitoring volume from daily record volume;
A4) backup described in supports continuous generation Delta Time point, steps A 3 simultaneously) the middle Hash file copied also can be monitored, and the data block at its place also can be copied to media server, and is stored in Delta Time point;
A5) the disaster tolerance end described in then sends recovery request to media server asynchronously, and backup holds all time points produced to be pushed to disaster tolerance end successively, the data in each time point of disaster tolerance end sustained restoration by media server.
3. data reflow method according to claim 1, is characterized in that, the Hash file in described steps A carries out record by the Client Agent in described backup end and generates.
4. data reflow method according to claim 1, is characterized in that, described step C is specially:
C1) after Redundancy Machine starts, former disaster tolerance task is initiated;
C2) the backup end of current Redundancy Machine as former disaster tolerance task detected, so secondary disaster tolerance task only has backup end and do not have disaster tolerance end, and carry out reverse cdp at backup end;
C3) according to the drive letter of monitoring volume, successively each monitoring is rolled up corresponding Hash file copy in new daily record volume;
C4) disaster tolerance task detects Hash file in the daily record volume of current backup end, directly involves in the initialization of row Hash increment to monitoring and copies, after the initialization of Hash increment has copied, continue to carry out incremental replication until disaster tolerance task is stopped.
5. data reflow method according to claim 1, is characterized in that, described step D is specially:
D1) WindowsPE of original physical production machine carry built in agent program, and browse recovery request to media server transmission;
D2) all time points of media server traversal disaster tolerance task generation, and be pushed to original physical production machine one by one;
D3) Agent in WindowsPE is successively by the data write original physical production machine in each time point.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510884259.1A CN105550062B (en) | 2015-12-03 | 2015-12-03 | The data reflow method restored based on continuous data protection and time point browsing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510884259.1A CN105550062B (en) | 2015-12-03 | 2015-12-03 | The data reflow method restored based on continuous data protection and time point browsing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105550062A true CN105550062A (en) | 2016-05-04 |
| CN105550062B CN105550062B (en) | 2018-10-12 |
Family
ID=55829258
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510884259.1A Expired - Fee Related CN105550062B (en) | 2015-12-03 | 2015-12-03 | The data reflow method restored based on continuous data protection and time point browsing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105550062B (en) |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106371952A (en) * | 2016-08-30 | 2017-02-01 | 北京中科同向信息技术有限公司 | Emergency management system based on physical machine |
| CN107784016A (en) * | 2016-08-30 | 2018-03-09 | 北京京东尚科信息技术有限公司 | Data syn-chronization control device and data synchronous system and 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 |
| CN109086169A (en) * | 2018-07-19 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of data reconstruction method, device and computer readable storage medium |
| CN109710453A (en) * | 2017-10-26 | 2019-05-03 | 深圳市沃土科技有限公司 | A kind of continuous data store method |
| CN110209530A (en) * | 2019-05-09 | 2019-09-06 | 上海爱数信息技术股份有限公司 | A kind of efficient method and system for restoring CDP system I/O data |
| CN110674502A (en) * | 2019-09-19 | 2020-01-10 | 华为技术有限公司 | Data detection method and device |
| CN112464044A (en) * | 2020-12-09 | 2021-03-09 | 上海爱数信息技术股份有限公司 | File data block change information monitoring and management system and method thereof |
| CN113711188A (en) * | 2019-04-25 | 2021-11-26 | Emc Ip控股有限公司 | Data distribution in continuous replication system |
| CN115328704A (en) * | 2022-09-06 | 2022-11-11 | 安徽鼎甲计算机科技有限公司 | File backup method, file recovery method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101187948A (en) * | 2007-12-20 | 2008-05-28 | 中国科学院计算技术研究所 | A continuous data protection system and its realization method |
| CN101777016A (en) * | 2010-02-08 | 2010-07-14 | 北京同有飞骥科技有限公司 | Snapshot storage and data recovery method of continuous data protection system |
| CN102012851A (en) * | 2010-12-20 | 2011-04-13 | 浪潮(北京)电子信息产业有限公司 | Continuous data protection method and server |
| US8554734B1 (en) * | 2007-07-19 | 2013-10-08 | American Megatrends, Inc. | Continuous data protection journaling in data storage systems |
| CN104090828A (en) * | 2014-07-24 | 2014-10-08 | 浪潮(北京)电子信息产业有限公司 | Real-time data backup method and system |
-
2015
- 2015-12-03 CN CN201510884259.1A patent/CN105550062B/en not_active Expired - Fee Related
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8554734B1 (en) * | 2007-07-19 | 2013-10-08 | American Megatrends, Inc. | Continuous data protection journaling in data storage systems |
| CN101187948A (en) * | 2007-12-20 | 2008-05-28 | 中国科学院计算技术研究所 | A continuous data protection system and its realization method |
| CN101777016A (en) * | 2010-02-08 | 2010-07-14 | 北京同有飞骥科技有限公司 | Snapshot storage and data recovery method of continuous data protection system |
| CN102012851A (en) * | 2010-12-20 | 2011-04-13 | 浪潮(北京)电子信息产业有限公司 | Continuous data protection method and server |
| CN104090828A (en) * | 2014-07-24 | 2014-10-08 | 浪潮(北京)电子信息产业有限公司 | Real-time data backup method and system |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107784016B (en) * | 2016-08-30 | 2019-02-15 | 北京京东尚科信息技术有限公司 | Data sync control device and data synchronous system and method |
| CN107784016A (en) * | 2016-08-30 | 2018-03-09 | 北京京东尚科信息技术有限公司 | Data syn-chronization control device and data synchronous system and method |
| CN106371952A (en) * | 2016-08-30 | 2017-02-01 | 北京中科同向信息技术有限公司 | Emergency management system based on physical machine |
| CN109710453A (en) * | 2017-10-26 | 2019-05-03 | 深圳市沃土科技有限公司 | A kind of continuous data store 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 |
| CN109086169A (en) * | 2018-07-19 | 2018-12-25 | 郑州云海信息技术有限公司 | A kind of data reconstruction method, device and computer readable storage medium |
| CN113711188A (en) * | 2019-04-25 | 2021-11-26 | Emc Ip控股有限公司 | Data distribution in continuous replication system |
| CN113711188B (en) * | 2019-04-25 | 2024-04-05 | Emcip控股有限公司 | Data distribution in a continuous replication system |
| CN110209530A (en) * | 2019-05-09 | 2019-09-06 | 上海爱数信息技术股份有限公司 | A kind of efficient method and system for restoring CDP system I/O data |
| CN110209530B (en) * | 2019-05-09 | 2024-02-09 | 上海爱数信息技术股份有限公司 | Method and system for recovering IO data of CDP system |
| CN110674502A (en) * | 2019-09-19 | 2020-01-10 | 华为技术有限公司 | Data detection method and device |
| CN112464044A (en) * | 2020-12-09 | 2021-03-09 | 上海爱数信息技术股份有限公司 | File data block change information monitoring and management system and method thereof |
| CN115328704A (en) * | 2022-09-06 | 2022-11-11 | 安徽鼎甲计算机科技有限公司 | File backup method, file recovery method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105550062B (en) | 2018-10-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105550062A (en) | Continuous data protection and time point browse recovery based data backflow method | |
| CN105389230B (en) | A kind of continuous data protection system and method for combination snapping technique | |
| US8856080B2 (en) | Backup using metadata virtual hard drive and differential virtual hard drive | |
| US9940205B2 (en) | Virtual point in time access between snapshots | |
| CN104461776A (en) | Application disaster tolerance method based on CDP and iSCSI virtual disk technology | |
| WO2016180160A1 (en) | Data snapshot recovery method and apparatus | |
| CN107256182B (en) | Method and device for restoring database | |
| CN101739313B (en) | Method for protecting and restoring continuous data | |
| CN107122267B (en) | Windows operating system mount recovery method | |
| CN103853837B (en) | Oracle does not stop the table level back-up restoring method of Production database automatically | |
| WO2018098972A1 (en) | Log recovery method, storage device and storage node | |
| CN104407940A (en) | Method for quickly recovering CDP system | |
| CN104375877A (en) | Virtual machine online snapshot generating and deleting method | |
| CN103336728A (en) | Disk data recovery method | |
| CN103810058A (en) | Backup method, equipment and system for virtual machine | |
| US20100115215A1 (en) | Recovering From a Backup Copy of Data in a Multi-Site Storage System | |
| JP2008171387A (en) | Backup system with continuous data protection | |
| CN102594849A (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| WO2020063600A1 (en) | Data disaster recovery method and site | |
| CN108614876B (en) | Redis database-based system and data processing method | |
| CN104461773A (en) | Backup deduplication method of virtual machine | |
| CN105550063A (en) | Continuous data protection and kvm virtualization based disaster recovery method | |
| WO2013170702A1 (en) | File processing method based on snapshot and solid state disk with snapshot function | |
| CN103384266A (en) | Parastor200 management node high availability method based on real-time synchronization at file level | |
| CN102799503A (en) | Recover method applied to large quantity of small files |
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: 20181012 Termination date: 20191203 |