CN102096615A - Remote incremental backup method and system - Google Patents
Remote incremental backup method and system Download PDFInfo
- Publication number
- CN102096615A CN102096615A CN 201110026734 CN201110026734A CN102096615A CN 102096615 A CN102096615 A CN 102096615A CN 201110026734 CN201110026734 CN 201110026734 CN 201110026734 A CN201110026734 A CN 201110026734A CN 102096615 A CN102096615 A CN 102096615A
- Authority
- CN
- China
- Prior art keywords
- target volume
- source book
- data
- digest value
- range
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a remote incremental backup method, which is used for performing backup on a source volume by a target volume. The method comprises the following steps of: capturing all write requests of the source volume; transmitting a writing position and data needing to be written contained in the write requests of the source volume to the target volume; and writing the data needing to be written into the position, corresponding to the writing position, in the target volume by using the target volume according to the writing position. The invention also discloses a remote incremental backup system. The method and the system can reduce the data volume which needs to be duplicated and realize real-time remote backup with less network bandwidth requirements.
Description
Technical field
The present invention relates to the data backup technical field, particularly a kind of long-range incremental backup method and system.
Background technology
Along with the development of infotech, data become element the most key in the infotech, and the damage of data may mean professional pause, the stopping production of factory, the confusion of traffic, or huge property loss or the like.Therefore for Data Protection, in infotech one of basic task that stands in the breach.
In the time of the data storage technology development, the technology of data security and protection is development at the same time also.But the situation that causes loss of data or damage is varied, as disaster, as artificial damage, as mechanical fault, all may cause the problem of data protection aspect as power fails or the like.The best approach of data protection generates redundancy backup exactly, promptly stores many parts of same data, causes losing the tragedy of all data with regard to having avoided the Single Point of Faliure of storing like this.But many copy storages of data provide a guiding theory just in theory the problem that solves data protection.In the life of reality, prevent the threat that various destructive insidents cause data, then need use different strategies at different situations.
As the redundancy backup at the enterprising line data of disk that separates, the data security problem when having solved one to two disk failure.And deposit the redundancy backup of the enterprising line data of reason memory device at the complete machine physics that separates, then be the data security problem that has solved under the situation that unit damages.If top listed data copy solution is in same position on the geographic position, destructive insident so slightly on a large scale as fire, thunder and lightning, earthquake or flood or the like, will make data protection make great efforts to become ornaments.So still not a kind of data replication strategy physically of our needs, also need on the geographic position, carry out long-range separation to the data duplicate, to reach result, guarantee at any time all have an available copy at least with corrupted data incident localization.
To this, people have proposed the method for teledata backup, and the source data that is about to need protection is transferred to the storage medium (as disk) that is arranged in another geographic position by diverse network (as the internet), thereby realize the teledata backup.
But in existing remote backup method, still continue to use common data copy mode, i.e. employing is duplicated totally or the incremental replication mode is carried out; Wherein, copy mode need be duplicated all data to the backed up data storage medium totally, and causing needs by a large amount of repeating data of Network Transmission when carrying out the teledata backup, and the resource occupying amount is very big; Even and use the incremental replication mode, only in the copy diskette vicissitudinous data block to the backed up data storage medium, but (incremental replication need carry out overall data check according to a certain granule size to be subjected to the restriction of the data block granule size of incremental replication, to find out vicissitudinous data block, the computational resource expense that this process need is a large amount of, for guaranteeing the real-time of incremental replication, what often the data block granularity of incremental replication can not be done is too little, otherwise can only realize asynchronous incremental replication, and can not realize real-time incremental replication), required data volume of duplicating is still very big, under network bandwidth condition of limited, even the process that data are duplicated can be accomplished in real time, still be subjected to the restriction of network transfer speeds, finally still can't accomplish real-time remote backup.
Summary of the invention
The embodiment of the invention provides a kind of long-range incremental backup method, can reduce the data volume that need duplicate, with less network bandwidth requirements, realizes real-time remote backup.
The embodiment of the invention provides a kind of long-range incremental backup system, can reduce the data volume that need duplicate, with less network bandwidth requirements, realizes real-time remote backup.
For achieving the above object, technical scheme of the present invention specifically is achieved in that
A kind of long-range incremental backup method is used for by target volume source book being carried out remote backup, and this method comprises:
Catch all write requests to source book;
Writing position that comprises in will the write request to source book and the data that need write send to target volume;
The data that target volume writes needs according to the said write position write in the position corresponding with this writing position in the target volume.
Preferably, described catching before all write requests to source book, this method further comprises:
Calculate the digest value of all data blocks in the source book memory range, and the digest value of all data blocks in the target volume corresponding with the source book memory range;
The digest value of all data blocks corresponding in the digest value of all data blocks and the target volume in the comparison source book with the source book memory range;
In source book and target volume, the different data block of digest value is carried out data sync.
Preferably, described data sync comprises:
Send to target volume by source book the data block that digest value is different and the positional information of this data block, target volume is written to corresponding position according to the positional information of this data block with the blocks of data that receives.
Preferably, the digest value of all data blocks in the described calculating source book memory range, and in the target volume corresponding with the source book memory range before the digest value of all data blocks, this method further comprises:
To duplicating of having set up to the transmission of the target volume in relation handshake request;
Confirm if in the default time, obtain the answer of target volume, then continue to carry out the digest value of all data blocks in the described calculating source book memory range, and the step of the digest value of all data blocks in the target volume corresponding with the source book memory range, and subsequent step.
Preferably, the digest value of all data blocks in the described calculating source book memory range, and in the target volume corresponding with the source book memory range before the digest value of all data blocks, this method further comprises:
According to the relevant information of source book and target volume, send handshake request to target volume;
If receiving the answer that target volume is returned at handshake request in the default time period confirms, and target volume is more than or equal to source book, then continue to carry out the digest value of all data blocks in the described calculating source book memory range, and the step of the digest value of all data blocks in the target volume corresponding, and subsequent step with the source book memory range.
Preferably, described handshake request comprises: the digest algorithm of synchronous residing stage, employing and the correlation parameter that adopts synchronously the time.
A kind of long-range incremental backup system comprises source book and is used to back up the target volume of source book, and described source book comprises:
The incremental backup module is used to catch all write requests to source book; Writing position that comprises in will the write request to source book and the data that need write send to target volume;
Described target volume comprises:
Communication module is used for writing in the target volume position corresponding with this writing position according to the data that the said write position writes needs.
Preferably, described source book further comprises:
Synchronization module is used to calculate the digest value of all data blocks in the source book memory range, relatively the digest value of all data blocks corresponding with the source book memory range in the digest value of all data blocks and the target volume in the source book; The data block that digest value is different and the positional information of this data block send to target volume,
Described communication module is further used for: calculate the digest value of all data blocks in the target volume corresponding with the source book memory range, and send to source book; Positional information according to described data block is written to corresponding position with the blocks of data that receives.
Preferably, described source book further comprises:
Duplicate starting module, be used for sending handshake request to the target volume of having set up of duplicating to relation;
Confirm if in the default time, obtain the answer of target volume, then enable described synchronization module and incremental backup module.
Preferably, described source book further comprises:
Duplicate starting module, be used for relevant information, send handshake request to target volume according to source book and target volume;
Confirm if in the default time period, receive the answer that target volume is returned at handshake request, and target volume then enables described synchronization module and incremental backup module more than or equal to source book.
As seen from the above technical solutions, this long-range incremental backup method and system of the present invention, owing to need the data of Network Transmission only to comprise the write request that can cause former data variation, than existing incremental replication method after causing former data variation by write data, by larger data piece granularity the data that change in the storage medium are copied to the method for network far-end backup storage medium again, the data of required transmission still less only need the less network bandwidth, can realize real-time teledata backup.
Description of drawings
Fig. 1 duplicates concerning synoptic diagram for the embodiment of the invention;
Fig. 2 is the method for data synchronization process flow diagram of the embodiment of the invention;
Fig. 3 is the incremental backup method flow diagram of the embodiment of the invention;
Fig. 4 duplicates right method flow diagram for the embodiment of the invention starts to have existed;
Fig. 5 is the newly-built right method flow diagram that duplicates for the embodiment of the invention starts;
Fig. 6 is the method for data synchronization particular flow sheet of the embodiment of the invention;
Fig. 7 is the incremental backup method particular flow sheet of the embodiment of the invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in more detail.
The present invention mainly is by intercepting and capturing all carry out write operation to former storage medium write request (write request comprises data that need write and the position that writes), write data into former storage medium in this write request, when causing former data variation, with this write request by Network Transmission in the backup storage medium of network far-end, and write in this backup storage medium, owing to need the data of Network Transmission only to comprise the write request that can cause former data variation, than existing incremental replication method after causing former data variation by write data, by larger data piece granularity the data that change in the storage medium are copied to the method for network far-end backup storage medium again, the data of required transmission still less, only need the less network bandwidth, can realize real-time teledata backup.
In the present invention, will need the backed up data storage medium to be called source book, the backup storage medium that the network far-end is corresponding with the storage medium that needs backup is called target volume; The combination that will have the source book of corresponding relation and target volume be called duplicate right.
Wherein, the corresponding relation between source book and the target volume might not be man-to-man, also can be one-to-many, specifically as shown in Figure 1.In source book and the target volume, source book can corresponding a plurality of target volume, but a target volume can only corresponding source book.The corresponding a plurality of target volume of source book can strengthen the Data Protection ability so that same piece of data is carried out the many places data duplicates.But in the relation of one-to-many, in many ways can not be unrestricted, a plurality of target volume can influence the performance of storage medium, have also increased maintenance cost simultaneously.
If need a plurality of target volume really, also can be in the storage medium of far-end, the write request that will send from source book is transmitted once more, forms as shown in Figure 1 that A arrives the such chain relationship one to one of C again to B, such arrangement can so that performance cost divide equally.But such structure also makes the delay of data protection increase, and the difficulty of data maintenance also increases, and the cost when data sync also can be very high.Therefore the frame mode of chain type should not be provided with long yet.
In addition, duplicating centering, the size of target volume can not be less than the size of source book, otherwise can cause some storage space of source book not protect.
Long-range incremental backup method of the present invention is based on above-mentioned duplicating what carry out, if duplicate being not activated, then before carrying out long-range incremental backup, need duplicate right initialization start-up course, and this process describes in detail later; And duplicating after starting, specifically begin long-range incremental backup before, also need to guarantee to duplicate centering, source book is consistent with data in the target volume, if inconsistent, then needs to carry out data sync, concrete synchronizing process comprises the steps: as shown in Figure 2
Particularly, can be by source book to target volume forward abstract computation requests, the size that comprises the data block (abbreviation piece) of dividing in the source book in this request, with the memory range that with the piece is unit calculating, if duplicate being new the establishment, then block size generally is the sector-size of disk, be typically 512 bytes, if already usedly duplicate rightly, block size is the block size of file system on it so, and typical value has 512,1024,2048 bytes or the like.For example the memory range of source book is 0-3000, and block size is 512 bytes, and target volume is then calculated in the target volume after receiving the digest calculations request that source book sends, the digest value of each piece in the 0-3000 scope; The digest value of all data blocks then can be calculated by source book oneself in the source book memory range.Because when file system is arranged, file system is all carried out read-write operation with the logical block of file system, adopts the purpose of different block sizes to be to be compressed in as far as possible the data volume size of transmission over networks.
If the digest value of the data block of same position is identical in source book and the target volume, illustrate that then the data of this position in source book and the target volume are consistent, otherwise the explanation data are inequality; This step is used for finding out the inconsistent part of data between source book and the target volume.
Particularly, data sync can be carried out in real time with the comparative result of step 202, promptly whenever determine a different data block of digest value and just carry out the operation of a data sync, send to target volume by source book the data block that digest value is different and the positional information of this data block, target volume is written to corresponding position according to the positional information of this data block with the blocks of data that receives; After can waiting for that also all comparative results all obtain, unification is carried out synchronously the different data block of digest value, by source book the data block that digest value is different and the disposable target volume that all sends to of positional information of each data block, target volume is written to corresponding position according to positional information with the blocks of data that receives.Certainly, if there is not the different data block of digest value, then direct process ends.
Through above-mentioned data synchronization process, all carried out then after finishing synchronously, can entering incremental backup flow process of the present invention synchronously up to the source book data block different with all digest value in the target volume.
Incremental backup flow process of the present invention comprises the steps: as shown in Figure 3
Step 301 is caught all write requests to source book;
Owing to have only write request just can cause the data variation of source book, therefore can not catch for the read request of source book, perhaps catch but be left intact.
After writing position and the data that need write were sent to target volume, source book can continue normal data writing process according to this write request.
The data that the extracting data that target volume is sent from source book goes out writing position information and need write, the data that needs are write are written in the target volume and this writing position correspondence position, promptly identical with writing position in source book position.
So far, long-range incremental backup method of the present invention is achieved, and gives a concrete illustration below.
Duplicating when starting,, then generating and duplicated right start-up course, new duplicating rightly, and carrying out start-up course otherwise set up if there be duplicating of having generated right.
Fig. 4 duplicates right start-up course process flow diagram for generating, and as shown in Figure 4, this flow process comprises:
Step 401 reads next duplicating relation of having generated before from configuration file.
Duplicate comprising the identification information etc. of the source book target volume corresponding in the relation with it.
Step 402 judges whether that duplicating of not startup is right, if then enter step 403, otherwise process ends.
Step 403 sends handshake request to duplicating to the target volume in the relation.
Handshake request is that source book and target volume are to carry out negotiation data and the negotiation result that data sync sends, such as these requests comprise the digest algorithm of synchronous residing stage, employing, the correlation parameter that adopts synchronously the time etc.Source book can be by the above-mentioned concrete transmission position of the identification information of the target volume that comprises in the relation being determined handshake request of duplicating.
Step 404 judges whether to receive the answer of target volume to handshake request; Confirm if in the default time, obtain the answer of target volume, then enter step 405,, then can enter step 406 if in the default time, do not obtain replying;
Step 405 starts this and duplicates right data synchronization process, returns step 401.
Step 406 judges whether the number of times that sends handshake request reaches the default number of times upper limit, if, then return step 401, otherwise return step 403, continue to send handshake request.In addition, when reaching the default number of times upper limit and return step 401, can also further send error message, prompting is duplicated starting mistake.This step is also nonessential.
In the present invention, duplicate right data sync and can adopt any method for synchronous, as preferred embodiment, can adopt the asynchronous and synchronous mode, so-called asynchronous, being meant between data synchronization process and source book and target volume other data handling procedure does not separately have dependence, independently of one another operation.Adopting asynchronous system is in order to make full use of the computing power of memory device, and process is carried out as quickly as possible.Concrete data synchronization process will describe in detail later.
More than existing to duplicate right start-up course be at existing a plurality of situations that needs are started of duplicating to carry out, if only current known one is duplicated starting, then can directly begin to carry out from step 403, carries out the back process ends to step 405 and get final product.
Fig. 5 is the newly-built process flow diagram flow chart that starts also that duplicates, and as shown in Figure 5, this flow process comprises:
Step 501 is obtained the identification information of source book and target volume.
This step purpose is that the identification information that makes source book can utilize source book and target volume carries out subsequent operation, here can be by target volume or other third party, as management server etc., the identification information of relevant information such as source book and target volume is sent to source book.
Step 502 sends handshake request to target volume; Need to use the described identification information that obtains in the step 501 in this step.
Step 503 judges whether to receive the answer message that target volume is returned at handshake request in the default time period, if then enter step 504, otherwise enter step 507;
Step 504, whether the size of judging target volume is more than or equal to source book; If then enter step 505, otherwise enter step 506;
The size information of target volume can be extracted from handshake request.
Step 505 starts and duplicates right data synchronization process; Process ends.
Step 507 judges whether the number of times that sends handshake request reaches default maximum times, if then enter step 508, otherwise return step 502; This step is optional.
When duplicating restarting, perhaps newly-built duplicating after also starting all will be carried out data sync to the source book and the target volume of duplicating centering, to guarantee the consistance of data.Duplicate rightly for a plurality of, each duplicates and finishes all starting a new synchronizing process, each other can cross influence.
Concrete data synchronization process comprises the steps: as shown in Figure 6
Step 602 starts an asynchronous summary receiving course and receives the data summarization that sends over from target volume, enters step 603 then, and wherein, concrete asynchronous receiving course describes in detail later.
Step 603 is a unit with described block size, and order reads the data in the source book, and the digest value of computational data piece (abbreviation data summarization).
Whenever read the digest value that a data block just calculates this data block simultaneously.
All data blocks read when finishing, and all data summarizations also calculate and finish accordingly.
Step 606 is judged the data summarization from the data block relevant position that whether exists the data summarization of target volume and read that receives from the summary receiving course of step 602, if do not have, then enters step 607, otherwise enters step 608.
Step 607 is recorded in this data summarization in the untreated summary lists, enters step 612.
Step 609 judges whether the data summarization from target volume that receives is identical with the data summarization of the relevant position that finds.If identical, then enter step 610.If inequality, then enter step 611.
Step 611 sends to target volume with data block and the data block location that reads, and returns step 610.
In this step, data block and data block location information can be carried at and send to target volume in the data synchronization request.
Step 612 judges whether the described tabulation of not finishing data has reached default max cap., if then enter step 613, otherwise return step 603.
Step 613 is extracted the digest value in the described tabulation successively.
Step 614 judges whether to obtain next digest value, if then enter 615, otherwise enter 618.
Step 615 is searched the data summarization of relevant position in the data summarization that receives;
Step 616 is judged the summary whether there is the relevant position in the data summarization that receives, if exist then enter step 617, if there is no then returns step 613.
Step 619 is waited for a default stand-by period, so that step 602 can receive new data summarization.
Step 620 judges whether receive new data summarization in the stand-by period, judges promptly whether finish the new data summarization of reception has surpassed the default stand-by period, if it is overtime, expression does not receive any summary data, then enters step 621, otherwise returns step 613.
Step 622 is checked described untreated summary lists;
Step 623 judges that whether untreated summary lists is empty, if, process ends then, otherwise return step 613.
In fact data summarization receiving course in the above-mentioned steps 602 is exactly a process of not stopping the next data summarization of receiving target curly hair, this process independently continues to carry out, be independent of each other with above-mentioned data synchronization process, up to receiving the ending request that target volume is sent, then finish receiving course, this process is beginning to send synchronization request to target volume.
Target volume can be judged the request that receives duplicating after starting, carry out different processes at different requests.If request is a synchronization request, then at first from request msg, extract the block size and the scope of synchronization request, and start an asynchronous synchronizing process, all data in the scope are read each blocks of data in proper order, with the data computation data summarization, and positional information one gone together deliver to source volume end after the success, after the data summarization of all data blocks and positional information are delivered to source book, send synchronous ending request to source book, finish synchronizing process.
If receive data synchronization request (as step 611), then extract location information and data from request and write data into corresponding position.
After data synchronization process is finished, can enter incremental data backup procedure of the present invention, specifically as shown in Figure 7, comprise the steps:
Step 701 is caught the read that the next one is sent to source book;
Step 702 judges that whether this request is write request, if then enter step 703, otherwise returns step 701.
Step 703 together sends to target volume with the position of write request and the data that need write, and returns step 701.
Above steps, carry out as not indicating target volume especially, then being source book carries out, during concrete the execution, an incremental backup module can be set in source book, be used to carry out above-mentioned incremental backup process, being provided with one duplicates starting module, be used to carry out and above-mentionedly existing duplicate right startup and newly-builtly duplicate right start-up course, and a synchronous module is set, be used to carry out above-mentioned data synchronization process.And in the target volume, a communication module can be set then, and be used to carry out the above-mentioned step that needs target volume to carry out, wherein the concrete steps of each module execution can specifically be exemplified below with reference to said method embodiment:
A kind of long-range incremental backup system comprises source book and is used for the target volume of remote backup source book, and described source book comprises:
The incremental backup module is used to catch all write requests to source book; Writing position that comprises in will the write request to source book and the data that need write send to target volume;
Described target volume comprises:
Communication module is used for writing in the target volume position corresponding with this writing position according to the data that the said write position writes needs.
Wherein, described source book may further include:
Synchronization module is used to calculate the digest value of all data blocks in the source book memory range, relatively the digest value of all data blocks corresponding with the source book memory range in the digest value of all data blocks and the target volume in the source book; The data block that digest value is different and the positional information of this data block send to target volume,
Described communication module is further used for: calculate the digest value of all data blocks in the target volume corresponding with the source book memory range, and send to source book; Positional information according to described data block is written to corresponding position with the blocks of data that receives.
In addition, described source book can further include:
Duplicate starting module, be used for sending handshake request to the target volume of having set up of duplicating to relation;
Confirm if in the default time, obtain the answer of target volume, then enable described synchronization module and incremental backup module.
Perhaps, as another embodiment, described source book can further include:
Duplicate starting module, be used for relevant information, send handshake request to target volume according to source book and target volume;
Confirm if in the default time period, receive the answer that target volume is returned at handshake request, and target volume then enables described synchronization module and incremental backup module more than or equal to source book.
By the above embodiments as seen, this long-range incremental backup method and system of the present invention, owing to need the data of Network Transmission only to comprise the write request that can cause former data variation, than existing incremental replication method after causing former data variation by write data, by larger data piece granularity the data that change in the storage medium are copied to the method for network far-end backup storage medium again, the data of required transmission still less only need the less network bandwidth, can realize real-time teledata backup.
Claims (10)
1. a long-range incremental backup method is used for by target volume source book being carried out remote backup, it is characterized in that this method comprises:
Catch all write requests to source book;
Writing position that comprises in will the write request to source book and the data that need write send to target volume;
The data that target volume writes needs according to the said write position write in the position corresponding with this writing position in the target volume.
2. long-range incremental backup method as claimed in claim 1 is characterized in that, described catching before all write requests to source book, and this method further comprises:
Calculate the digest value of all data blocks in the source book memory range, and the digest value of all data blocks in the target volume corresponding with the source book memory range;
The digest value of all data blocks corresponding in the digest value of all data blocks and the target volume in the comparison source book with the source book memory range;
In source book and target volume, the different data block of digest value is carried out data sync.
3. long-range incremental backup method as claimed in claim 2 is characterized in that described data sync comprises:
Send to target volume by source book the data block that digest value is different and the positional information of this data block, target volume is written to corresponding position according to the positional information of this data block with the blocks of data that receives.
4. long-range incremental backup method as claimed in claim 2, it is characterized in that, the digest value of all data blocks in the described calculating source book memory range, and in the target volume corresponding with the source book memory range before the digest value of all data blocks, this method further comprises:
To duplicating of having set up to the transmission of the target volume in relation handshake request;
Confirm if in the default time, obtain the answer of target volume, then continue to carry out the digest value of all data blocks in the described calculating source book memory range, and the step of the digest value of all data blocks in the target volume corresponding with the source book memory range, and subsequent step.
5. long-range incremental backup method as claimed in claim 2, it is characterized in that, the digest value of all data blocks in the described calculating source book memory range, and in the target volume corresponding with the source book memory range before the digest value of all data blocks, this method further comprises:
According to the relevant information of source book and target volume, send handshake request to target volume;
If receiving the answer that target volume is returned at handshake request in the default time period confirms, and target volume is more than or equal to source book, then continue to carry out the digest value of all data blocks in the described calculating source book memory range, and the step of the digest value of all data blocks in the target volume corresponding, and subsequent step with the source book memory range.
6. as claim 4 or 5 described long-range incremental backup methods, it is characterized in that described handshake request comprises: the digest algorithm of synchronous residing stage, employing and the correlation parameter that adopts synchronously the time.
7. long-range incremental backup system comprises source book and is used for the target volume of remote backup source book, it is characterized in that described source book comprises:
The incremental backup module is used to catch all write requests to source book; Writing position that comprises in will the write request to source book and the data that need write send to target volume;
Described target volume comprises:
Communication module is used for writing in the target volume position corresponding with this writing position according to the data that the said write position writes needs.
8. long-range incremental backup as claimed in claim 7 system is characterized in that described source book further comprises:
Synchronization module is used to calculate the digest value of all data blocks in the source book memory range, relatively the digest value of all data blocks corresponding with the source book memory range in the digest value of all data blocks and the target volume in the source book; The data block that digest value is different and the positional information of this data block send to target volume,
Described communication module is further used for: calculate the digest value of all data blocks in the target volume corresponding with the source book memory range, and send to source book; Positional information according to described data block is written to corresponding position with the blocks of data that receives.
9. long-range incremental backup as claimed in claim 8 system is characterized in that described source book further comprises:
Duplicate starting module, be used for sending handshake request to the target volume of having set up of duplicating to relation;
Confirm if in the default time, obtain the answer of target volume, then enable described synchronization module and incremental backup module.
10. long-range incremental backup as claimed in claim 8 system is characterized in that described source book further comprises:
Duplicate starting module, be used for relevant information, send handshake request to target volume according to source book and target volume;
Confirm if in the default time period, receive the answer that target volume is returned at handshake request, and target volume then enables described synchronization module and incremental backup module more than or equal to source book.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110026734 CN102096615A (en) | 2011-01-25 | 2011-01-25 | Remote incremental backup method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201110026734 CN102096615A (en) | 2011-01-25 | 2011-01-25 | Remote incremental backup method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102096615A true CN102096615A (en) | 2011-06-15 |
Family
ID=44129719
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201110026734 Pending CN102096615A (en) | 2011-01-25 | 2011-01-25 | Remote incremental backup method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102096615A (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102412948A (en) * | 2011-11-17 | 2012-04-11 | 盛科网络（苏州）有限公司 | Method and device for realizing high-reliability backup in data oscillation environment |
| CN102508740A (en) * | 2011-10-26 | 2012-06-20 | 上海文广互动电视有限公司 | Remote replication method of file system |
| CN103092533A (en) * | 2013-01-24 | 2013-05-08 | 上海爱数软件有限公司 | Method and system for data remote synchronization |
| CN103179158A (en) * | 2011-12-22 | 2013-06-26 | ***股份有限公司 | Parameter batch synchronization method and system |
| CN103312743A (en) * | 2012-03-09 | 2013-09-18 | 盛乐信息技术（上海）有限公司 | Data synchronization device and method |
| CN104090729A (en) * | 2014-07-04 | 2014-10-08 | 浙江宇视科技有限公司 | Method and device for repairing mirror image synchronization through service write operation |
| CN104102554A (en) * | 2013-04-07 | 2014-10-15 | 杭州信核数据科技有限公司 | Data backup method and data backup device |
| CN104662521A (en) * | 2012-07-16 | 2015-05-27 | 康佩伦特科技公司 | System and method for replication of data utilizing delta volumes |
| WO2015085840A1 (en) * | 2013-12-13 | 2015-06-18 | Beijing Zhigu Rui Tuo Tech Co., Ltd | Backup and related operations |
| CN104798059A (en) * | 2012-12-20 | 2015-07-22 | 英特尔公司 | Multiple computer system processing write data outside of checkpointing |
| CN106610875A (en) * | 2015-10-23 | 2017-05-03 | 先智云端数据股份有限公司 | Mixed backup restoration management system and backup method and restoration method therefor |
| CN106778305A (en) * | 2016-12-15 | 2017-05-31 | 深圳市中科鼎创科技股份有限公司 | A kind of device and method that unit data are carried out with continuous data protection |
| CN106850842A (en) * | 2012-06-28 | 2017-06-13 | 北京奇虎科技有限公司 | A kind of download of file, method for uploading and device |
| CN107092538A (en) * | 2017-03-14 | 2017-08-25 | 平安科技（深圳）有限公司 | Virtual-machine data backup method and system |
| CN107544865A (en) * | 2016-06-24 | 2018-01-05 | 中兴通讯股份有限公司 | A kind of quick available method and apparatus of Backup Data |
| CN109522160A (en) * | 2018-11-29 | 2019-03-26 | 上海英方软件股份有限公司 | Compare backup method and system by saving the file information abstract progress file directory |
| CN110673797A (en) * | 2019-09-20 | 2020-01-10 | 浪潮电子信息产业股份有限公司 | Logical volume copying method in distributed block storage service |
| CN112346771A (en) * | 2019-08-07 | 2021-02-09 | 杭州海康威视数字技术股份有限公司 | Upgrade file generation method and device |
| CN113535465A (en) * | 2020-04-17 | 2021-10-22 | 广东中兴新支点技术有限公司 | Method and device for establishing base line of disk image and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101436151A (en) * | 2008-12-01 | 2009-05-20 | 成都索贝数码科技股份有限公司 | Data real time backup method and system based on file system |
| CN101441582A (en) * | 2007-11-20 | 2009-05-27 | 北京和力记易科技有限公司 | Backup and recovery method of computer data object and system and program product for implementing the same |
| US7694086B1 (en) * | 2003-06-30 | 2010-04-06 | Symantec Operating Corporation | Method and system for incremental backup of data volumes |
| US7734887B1 (en) * | 2007-05-30 | 2010-06-08 | Symantec Corporation | Relocation tracking during write operation |
-
2011
- 2011-01-25 CN CN 201110026734 patent/CN102096615A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7694086B1 (en) * | 2003-06-30 | 2010-04-06 | Symantec Operating Corporation | Method and system for incremental backup of data volumes |
| US7734887B1 (en) * | 2007-05-30 | 2010-06-08 | Symantec Corporation | Relocation tracking during write operation |
| CN101441582A (en) * | 2007-11-20 | 2009-05-27 | 北京和力记易科技有限公司 | Backup and recovery method of computer data object and system and program product for implementing the same |
| CN101436151A (en) * | 2008-12-01 | 2009-05-20 | 成都索贝数码科技股份有限公司 | Data real time backup method and system based on file system |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102508740A (en) * | 2011-10-26 | 2012-06-20 | 上海文广互动电视有限公司 | Remote replication method of file system |
| CN102412948A (en) * | 2011-11-17 | 2012-04-11 | 盛科网络（苏州）有限公司 | Method and device for realizing high-reliability backup in data oscillation environment |
| CN103179158B (en) * | 2011-12-22 | 2017-03-01 | ***股份有限公司 | A kind of parameter batch synchronization method and system |
| CN103179158A (en) * | 2011-12-22 | 2013-06-26 | ***股份有限公司 | Parameter batch synchronization method and system |
| CN103312743A (en) * | 2012-03-09 | 2013-09-18 | 盛乐信息技术（上海）有限公司 | Data synchronization device and method |
| CN106850842A (en) * | 2012-06-28 | 2017-06-13 | 北京奇虎科技有限公司 | A kind of download of file, method for uploading and device |
| CN104662521A (en) * | 2012-07-16 | 2015-05-27 | 康佩伦特科技公司 | System and method for replication of data utilizing delta volumes |
| CN104662521B (en) * | 2012-07-16 | 2018-11-20 | 康佩伦特科技公司 | Utilize the system and method for delta volumes of replicate data |
| CN104798059A (en) * | 2012-12-20 | 2015-07-22 | 英特尔公司 | Multiple computer system processing write data outside of checkpointing |
| CN103092533A (en) * | 2013-01-24 | 2013-05-08 | 上海爱数软件有限公司 | Method and system for data remote synchronization |
| CN103092533B (en) * | 2013-01-24 | 2016-04-27 | 上海爱数信息技术股份有限公司 | A kind of method and system of data remote synchronization |
| CN104102554B (en) * | 2013-04-07 | 2017-05-03 | 杭州信核数据科技股份有限公司 | Data backup method and data backup device |
| CN104102554A (en) * | 2013-04-07 | 2014-10-15 | 杭州信核数据科技有限公司 | Data backup method and data backup device |
| WO2015085840A1 (en) * | 2013-12-13 | 2015-06-18 | Beijing Zhigu Rui Tuo Tech Co., Ltd | Backup and related operations |
| CN104090729A (en) * | 2014-07-04 | 2014-10-08 | 浙江宇视科技有限公司 | Method and device for repairing mirror image synchronization through service write operation |
| CN104090729B (en) * | 2014-07-04 | 2017-08-15 | 浙江宇视科技有限公司 | The method and device of mirror image synchronization is repaired by business write operation |
| CN106610875A (en) * | 2015-10-23 | 2017-05-03 | 先智云端数据股份有限公司 | Mixed backup restoration management system and backup method and restoration method therefor |
| CN107544865B (en) * | 2016-06-24 | 2022-11-11 | 中兴通讯股份有限公司 | Method and device for quickly making backup data available |
| CN107544865A (en) * | 2016-06-24 | 2018-01-05 | 中兴通讯股份有限公司 | A kind of quick available method and apparatus of Backup Data |
| CN106778305A (en) * | 2016-12-15 | 2017-05-31 | 深圳市中科鼎创科技股份有限公司 | A kind of device and method that unit data are carried out with continuous data protection |
| WO2018166101A1 (en) * | 2017-03-14 | 2018-09-20 | 平安科技（深圳）有限公司 | Virtual machine data backup method, system, storage medium and server |
| CN107092538B (en) * | 2017-03-14 | 2019-12-24 | 平安科技（深圳）有限公司 | Virtual machine data backup method and system |
| CN107092538A (en) * | 2017-03-14 | 2017-08-25 | 平安科技（深圳）有限公司 | Virtual-machine data backup method and system |
| CN109522160A (en) * | 2018-11-29 | 2019-03-26 | 上海英方软件股份有限公司 | Compare backup method and system by saving the file information abstract progress file directory |
| CN112346771A (en) * | 2019-08-07 | 2021-02-09 | 杭州海康威视数字技术股份有限公司 | Upgrade file generation method and device |
| CN112346771B (en) * | 2019-08-07 | 2024-05-31 | 杭州海康威视数字技术股份有限公司 | Upgrade file generation method and device |
| CN110673797A (en) * | 2019-09-20 | 2020-01-10 | 浪潮电子信息产业股份有限公司 | Logical volume copying method in distributed block storage service |
| CN113535465A (en) * | 2020-04-17 | 2021-10-22 | 广东中兴新支点技术有限公司 | Method and device for establishing base line of disk image and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102096615A (en) | Remote incremental backup method and system | |
| CN108255641B (en) | CDP disaster recovery method based on cloud platform | |
| US10895996B2 (en) | Data synchronization method, system, and apparatus using a work log for synchronizing data greater than a threshold value | |
| KR101662212B1 (en) | Database Management System providing partial synchronization and method for partial synchronization thereof | |
| WO2020151323A1 (en) | Data slicing-based data storage method, device, and medium | |
| US7647449B1 (en) | Method, system, and computer readable medium for maintaining the order of write-commands issued to a data storage | |
| WO2014059804A1 (en) | Method and system for data synchronization | |
| JP5594828B2 (en) | Data distributed storage device and method, program, and recording medium | |
| CN104572357A (en) | Backup and recovery method for HDFS (Hadoop distributed filesystem) | |
| CN106156359A (en) | A kind of data synchronization updating method under cloud computing platform | |
| CN104335159A (en) | Interval-controlled replication | |
| CN103530201A (en) | Safety data repetition removing method and system applicable to backup system | |
| CN107124305B (en) | Node device operation method and node device | |
| CN102508740A (en) | Remote replication method of file system | |
| CN101771548A (en) | File synchronizing method and system | |
| CN103593264A (en) | System and method for remote wide area network disaster recovery backup | |
| CN111177257A (en) | Data storage and access method, device and equipment of block chain | |
| CN103294704A (en) | File synchronous system and method | |
| US20160139996A1 (en) | Methods for providing unified storage for backup and disaster recovery and devices thereof | |
| CN104965835A (en) | Method and apparatus for reading and writing files of a distributed file system | |
| CN103984622B (en) | The blog management method and device of GPON ONU equipments based on Linux | |
| CN105550230B (en) | The method for detecting and device of distributed memory system node failure | |
| CN113190620B (en) | Method, device, equipment and storage medium for synchronizing data between Redis clusters | |
| CN105471616A (en) | Cache system management method and system | |
| CN108415951B (en) | Database control method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110615 |