CN102306115B - Asynchronous remote copying method, system and equipment - Google Patents
Asynchronous remote copying method, system and equipment Download PDFInfo
- Publication number
- CN102306115B CN102306115B CN201110132517.2A CN201110132517A CN102306115B CN 102306115 B CN102306115 B CN 102306115B CN 201110132517 A CN201110132517 A CN 201110132517A CN 102306115 B CN102306115 B CN 102306115B
- Authority
- CN
- China
- Prior art keywords
- write request
- issues
- write
- group system
- lun
- 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.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an asynchronous remote copying method, an asynchronous remote copying system and asynchronous remote copying equipment. The asynchronous remote copying method comprises the following steps of: after a production center receives a writing request of a host machine, labeling a period number for the writing request according to the period number of the current period; writing the labeled writing request with the period number into a local remote copying master logic unit number (LUN) and labeling a sequence number for the labeled writing request with the period number according to a sequence of the period number written into the remote copying master LUN; and sending the labeled writing request with the period number and the sequence number to a disaster tolerance center. By the method, the system and the equipment, the problem of inconsistency of data stored in the remote copying master LUN of the production center and data stored in a remote copying slave LUN of the disaster tolerance center caused by inconsistency of the sequence of a plurality of writing requests which have conflicted accessing addresses reaching the disaster tolerance center and the sequence of the plurality of writing requests written into the production center within the same period can be avoided.
Description
Technical field
The present invention relates to computer technology, relate in particular to a kind of asynchronous remote copying method, a kind of asynchronous remote copy system, a kind of production center and a kind of disaster recovery center.
Background technology
Disaster tolerance system generally comprises two class data centers: the local production center and long-distance disaster center wherein are provided with remote copy that in the remote copy main logic storage object (referred to as LUN) to the production center, data are backed up in the heart from LUN in long-distance disaster.When disaster tolerance system runs into catastrophic event, data by the disaster recovery center remote copy from LUN are recovered the remote copy master LUN in the local source book production center, thereby guarantee the physical security of significant data, for example can be because of power failure, fire or nature reasons such as (earthquake, tsunamis etc.) cause data degradation.Be called as the remote copy process according to the Data Update remote copy in remote copy master LUN from the process of LUN, according to business event environment (as: available bandwidth, network delay, the quantity of server, the size of copy data amount and the physical distance between main frame), and the user is after disaster occurs, time length (Recovery Point Object to obliterated data, RPO) and recover required maximum duration (the Recovery Time Objectives of application, RTO) difference in requirement, the type of remote copy process can be divided into: synchronous remote copy and asynchronous remote copy.
After synchronous remote copy refers to that the production center receives the write request that the upper layer application in main frame sends, before returning to upper layer application and writing successfully acknowledge message, data corresponding to write request successfully sent in the remote copy master LUN of the production center and the remote copy of disaster recovery center from LUN.Because the remote copy of the remote copy master LUN that sends data to the production center and disaster recovery center can expend certain hour from LUN, therefore the performance of upper layer application had to certain influence.Asynchronous remote copy refers to after as long as data corresponding to write request have successfully been sent in the remote copy master LUN of the production center, can return and write successfully acknowledge message to upper layer application, write successfully acknowledge message and needn't wait until that remote copy that data are sent to disaster recovery center is just returned from LUN, follow-uply upgrade the remote copy of disaster recovery center from LUN according to the remote copy master LUN of the production center again.
Adopt asynchronous remote copy can eliminate the performance issue that synchronous remote copy exists, though disaster recovery center likely lags behind the production center, still real-time copying basically, and can not produce obvious impact to the performance of upper layer application.Technical characterstic according to its realization is classified, and can the asynchronous replication technology be divided into other asynchronous remote copy of piece level based on snapshot and other asynchronous remote copy of write request level of Log-based LUN.Wherein the ultimate principle of other asynchronous remote copy of write request level of Log-based LUN is: when write request is issued to remote copy master LUN from the main frame of the production center, can be written in the daily record LUN of the production center simultaneously and be stamped periodic timestamp (within the same cycle, the timestamp of all write requests is consistent), can be safeguarded by daily record LUN the succession of write request thereby make.The asynchronous remote copy module on backstage, the production center is read the write request write in daily record LUN, and send to be positioned at disaster recovery center remote copy from LUN.This method can reduce release time and the loss of data time of disaster tolerance system.
Yet, owing to rolling up when the write request of reading daily record LUN sends to the remote copy of far-end duplicate volume from LUN the reasons such as network delay that exist from daily record, likely there will be for the write request in same period, write the order situation different from writing the order of far-end duplicate volume remote copy from LUN in local source book remote copy master LUN, if the reference address conflict of these write requests, can cause the inconsistent problem of data that occurs that local source book remote copy master LUN and the remote copy of far-end duplicate volume are stored from LUN.
Summary of the invention
The embodiment of the present invention provides a kind of asynchronous remote copying method, in order to solve the prior art medium-long range, copies main LUN and the remote copy inconsistent defect of data from the LUN storage.
Accordingly, the embodiment of the present invention also provides a kind of production center, a kind of disaster recovery center and a kind of asynchronous remote copy system.
The embodiment of the present invention provides a kind of asynchronous remote copying method, comprising:
After the production center receives the write request of main frame, according to all issues of current period, be all issues of described write request mark;
By the week of mark, the write request of issue writes local remote copy master LUN, the write request flag sequence number that is described week of mark issue according to the order that writes described remote copy master LUN;
By the week of mark issue and the write request of serial number send to disaster recovery center.
The embodiment of the present invention provides a kind of asynchronous remote copying method, comprising:
Disaster recovery center receives the write request that the production center sends, and is marked with all issues and serial number in described write request;
Judge whether to receive all write requests of one-period correspondence,
When judgment result is that all write requests that receive the one-period correspondence, according to all issues and the serial number of mark in write request, the write request received is write to local remote copy from LUN.
The embodiment of the present invention provides a kind of production center, comprise at least one production group system, described production group system comprises first front-end platform and first a rear end platform, and described the first rear end platform comprises the first business processing device and remote copy master LUN, wherein:
Described the first front-end platform, for after receiving the write request of main frame, according to all issues of current period, be described write request mark week issue, and by mark week issue write request send under the first business processing device in the first rear end platform in the production group system;
The first business processing device, for by the week of mark issue write request write remote copy master LUN, the write request flag sequence number that is described mark week issue according to the order that writes described remote copy master LUN, and by mark week issue and the write request of serial number send to disaster recovery center.
The embodiment of the present invention provides a kind of disaster recovery center, comprise: comprise at least one disaster tolerance cluster system, described disaster tolerance cluster system comprises second front-end platform and second a rear end platform, and described the second rear end platform comprises that the second business processing device and remote copy are from LUN, wherein:
Described the second front-end platform, the write request sent for receiving the production center, be marked with all issues and serial number in described write request;
Described the second business processing device, for judging whether described the second front-end platform has received all write requests of one-period correspondence, determining while having received all write requests of one-period correspondence, all issues and serial number according to mark in write request, write remote copy from LUN by the write request received.
The embodiment of the present invention provides a kind of asynchronous remote copy system, comprising:
The production center, after the write request that receives main frame, is all issues of described write request mark according to all issues of current period; By the week of mark, the write request of issue writes local remote copy master LUN, the write request flag sequence number that is described week of mark issue according to the order that writes described remote copy master LUN; By the week of mark issue and the write request of serial number send to disaster recovery center;
Disaster recovery center, the write request sent for receiving the production center, be marked with all issues and serial number in described write request; Judge whether to receive all write requests of one-period correspondence, when judgment result is that all write requests that receive the one-period correspondence, according to all issues and the serial number of mark in write request, the write request received is write to local remote copy from LUN.
When the production group system of the embodiment of the present invention production center receives the write request of main frame, for all issues of this write request mark, and after write request writes remote copy master LUN, for this write request is marked in current period the serial number that is written into remote copy master LUN.After the write request that the production center will be marked with all issues and serial number sends to disaster recovery center, for the write request disaster recovery center of same period, can be in order number write remote copy from LUN.Thereby a plurality of write requests of having avoided the conflict of in same period reference address arrive the order of disaster recovery centers when inconsistent with the write sequence of the heart aborning, the inconsistent problem of data that the data of storing in the remote copy master LUN of the caused production center and the remote copy of disaster recovery center are stored from LUN.
The accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, below will the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain according to these accompanying drawings other accompanying drawing.
The process flow diagram of a kind of asynchronous remote copying method that Fig. 1 provides for the embodiment of the present invention;
A kind of asynchronous remote copying method that Fig. 2 A provides for the embodiment of the present invention is applied to the process flow diagram of distributed memory system;
The structural representation of a kind of production center that Fig. 2 B provides for the embodiment of the present invention;
A kind of asynchronous remote copying method that Fig. 2 C provides for the embodiment of the present invention is applied to the process flow diagram of non-distributed memory system;
The process flow diagram of the another kind of asynchronous remote copying method that Fig. 3 provides for the embodiment of the present invention:
The another kind of asynchronous remote copying method that Fig. 4 A provides for the embodiment of the present invention is applied to the process flow diagram of distributed memory system;
The disaster recovery center example structure schematic diagram that Fig. 4 B provides for the embodiment of the present invention;
The schematic diagram of the write request chained list of preserving in the far-end buffer memory in the disaster tolerance cluster system that Fig. 4 C provides for the embodiment of the present invention;
The structural representation of the second business processing device embodiment in the disaster recovery center that Fig. 5 provides for the embodiment of the present invention;
The structural representation of the asynchronous remote copy system that Fig. 6 provides for the embodiment of the present invention.
Embodiment
For the purpose, technical scheme and the advantage that make the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, rather than whole embodiment.Embodiment based in the present invention, those of ordinary skills, not making under the creative work prerequisite the every other embodiment obtained, belong to the scope of protection of the invention.
Embodiment mono-
The process flow diagram of a kind of asynchronous remote copying method that Fig. 1 provides for the embodiment of the present invention.The present embodiment provides the technical scheme of asynchronous remote copying method to describe from production center angle to the embodiment of the present invention.The storage system that the executive agent of the present embodiment is the production center.As shown in Figure 1, the present embodiment comprises:
Step 11: after the production center receives the write request of main frame, be write request mark week issue according to all issues of current period.
According to all issues of current period, being write request mark week issue, is the residing cycle while for the mark production center, processing this write request.
Step 12: the production center writes local remote copy master LUN by the write request of the week of mark issue, the write request flag sequence number that is described week of mark issue according to the order that writes remote copy master LUN.
The production center, by after the write request of all issues of mark writes local remote copy master LUN, writes the order of remote copy master LUN, for this write request is marked in current period the serial number that is written into remote copy master LUN according to write request.Therefore write request not only has and is marked with all issues corresponding to this write request, also is marked with the serial number of this write request when writing remote copy master LUN.
Step 13: the production center by the week of mark issue and the write request of serial number send to disaster recovery center.
Further, after current period finishes, the production center sends to disaster recovery center by the write request number of the main frame received in current period of all issues of current period and correspondence.Thereby so that disaster recovery center can be according to all issues and corresponding write request number, determine whether to receive all write requests in this week corresponding cycle of issue, and, when determining all write requests that receive this week corresponding cycle of issue, all write requests in this cycle are write to remote copy from LUN.
The embodiment of the present invention, when the storage system of the production center receives the write request of main frame, be all issues of this write request mark, and after write request writes remote copy master LUN, for this write request is marked in current period the serial number that is written into remote copy master LUN.After the write request that the production center will be marked with all issues and serial number sends to disaster recovery center, for the write request disaster recovery center of same period, can be in order number write remote copy from LUN.Thereby a plurality of write requests of having avoided the conflict of in same period reference address arrive the order of disaster recovery centers when inconsistent with the write sequence of the heart aborning, the inconsistent problem of data that the data of storing in the remote copy master LUN of the caused production center and the remote copy of disaster recovery center are stored from LUN.
Embodiment bis-
Provided respectively in the present embodiment the concrete application example of the asynchronous remote copying method shown in Fig. 1 in distributed memory system and non-distributed memory system.
A kind of asynchronous remote copying method that Fig. 2 A provides for the embodiment of the present invention is applied to the process flow diagram of distributed memory system.The structural representation of a kind of production center that Fig. 2 B provides for the embodiment of the present invention.The present embodiment illustrates the technical scheme of above-mentioned asynchronous remote copying method from production center angle.As shown in Fig. 2 B, in the present embodiment, the distributed memory system of the production center comprises at least two production group systems.The write request that the production group system issues for the treatment of the main frame of the production center.Wherein, each production group system comprises the first front-end platform and the first rear end platform, and wherein the first rear end platform comprises the first business processing device and remote copy master LUN.Between the first front-end platform in each production group system, can connect by internal network.As shown in Figure 2 A, the present embodiment comprises:
Step 21: the write request that the main frame of each the production group system reception production center in the production center issues.
Alternatively, in main frame and each production group system, the first front-end platform is by the communication of SCSI agreement, and the first front-end platform of each production group system receives by the SCSI agreement write request that the main frame of the production center issues.
Step 22: each production group system is determined the physical address of this write request according to address mapping table, and whether the physical address space that judges this production group system processing comprises the physical address of this write request, the physical address space that this production group system is processed if judgment result is that comprises the physical address of this write request, enters step 23; Otherwise, ignore this write request or forward this write request to the first front-end platform of other production group system.
After the first front-end platform in each production group system receives the write request that main frame issues, according to the logical address of carrying in write request, determine the physical address of write request by searching address mapping table, preserve the mapping relations of logical address and physical address in distributed memory system in address mapping table.
For example, because the physical address space of the write request that in the production center, each production group system is processed is different (from the physical address space of the write request that in this production center, other production group systems are processed, the first production group system is the write request in 00000000～1FFFFFFF physical address space for the treatment of physical address, and the second production group system is the write request in 20000000～3FFFFFFF physical address space for the treatment of physical address).In the time of in the physical address space that the physical address that the first front-end platform in each production group system is determined write request is not processed in affiliated production group system, ignore this write request or forward this write request to the first front-end platform of other production group system.
Step 23: the physical address space of processing comprises that the production group system of the physical address of this write request obtains all issues of current period, and is write request mark week issue according to all issues of the current period obtained, and enters step 24.
Alternatively, the first front-end platform in described production group system is obtained all issues of current period, and is write request mark week issue according to all issues of the current period obtained.
The scheme that the first front-end platform in wherein production group system is obtained all issues of current period includes but not limited to:
The first front-end platform in scheme one, production group system from the production center one for the setting device that all issues are set, obtain, specifically comprise: when receiving write request, send current period number to described setting device and obtain request, and receive all issues of the current period of described setting device feedback; Perhaps, described setting device periodically sends to all issues of current period the first front-end platform in each production group system in this production center.The first front-end platform periodically receives all issues of the current period of described setting device transmission.
Scheme two selects a production group system as master control production group system in advance from each production group system of the production center, and the first front-end platform in this master control production group system can be referred to as master control the first front-end platform.Wherein master control the first front-end platform is for arranging all issues.
Described be write request mark week the production group system of issue can be master control production group system, can be also non-master control production group system.When the described production group system for all issues of write request mark is master control production group system, all issues of the Set For Current that master control the first front-end platform can arrange self are as all issues of the current period obtained; When the described production group system for all issues of write request mark is non-master control production group system, the mode that non-master control the first front-end platform obtains all issues of current period includes but not limited to following several:
First method, master control the first front-end platform, according to the request of non-master control the first front-end platform in this production center, is handed down to current period number non-master control the first front-end platform sent request.
Second method, master control the first front-end platform periodically sends to all issues of current period each non-master control first front-end platform in this production center.Non-master control the first front-end platform periodically receives all issues of the current period of master control the first front-end platform transmission.Master control the first front-end platform and Ge Fei master control the first front-end platform can adopt internal network to interconnect.
With respect to first method, second method periodically sends all issues by master control the first front-end platform to the first front-end platform in each non-master control production group system, rather than by a plurality of non-master control the first front-end platform frequently to master control the first front-end platform RQ cycle number, thereby alleviated the load of master control the first front-end platform, improved system performance.
Further, master control the first front-end platform is also added up in current period the write request number that receives main frame, after current period finishes, master control production group system sends to disaster recovery center by the write request number of the main frame received in current period of all issues of current period and correspondence.
Alternatively, in described production group system, the first front-end platform is issued to the first business processing device in the first rear end platform in this production group system by the write request of all issues of mark current period, then in this production group system the first business processing device in the first rear end platform by mark week issue write request write remote copy master LUN.
Step 25: described production group system is the write request flag sequence number for the issue of mark week according to the order that writes local remote copy master LUN.
Alternatively, the first business processing device in described production group system, the write request flag sequence number according to the order that writes local remote copy master LUN for the week of mark issue.
Step 26: described production group system by the week of mark issue and the write request of serial number send to disaster recovery center.
Alternatively, the first business processing device in this production group system, by the week of mark issue and the write request of serial number send to disaster recovery center.
Alternatively, above-mentioned the first business processing device can by the week of mark issue and the write request of serial number write buffer memory, by buffer memory, write request is issued to disaster recovery center.
In the embodiment of the present invention, the storage system of the production center is distributed memory system, and wherein each production group system is respectively used to process the write request of different physical address spaces.After receiving write request, when the production group system judges that the physical address space of this production group system processing comprises the physical address of write request, for all issues of this write request mark, and be write request flag sequence number according to the order that this write request is write to remote copy master LUN.The production group system is by after the write request of all issues of mark and serial number sends to disaster recovery center, after disaster recovery center receives the write request that is marked with all issues and serial number, for the write request disaster recovery center of same period, can be in order number write remote copy from LUN.Thereby a plurality of write requests of having avoided the conflict of in same period reference address arrive the order of disaster recovery centers when inconsistent with the write sequence of the heart aborning, the inconsistent problem of data that the data of storing in the remote copy master LUN of the caused production center and the remote copy of disaster recovery center are stored from LUN.
It should be noted that, the asynchronous remote copying method that accompanying drawing 1 provides also can be applied to non-distributed storage system, in the storage system of the production center, only comprises the situation of a production group system in accompanying drawing 2B.Non-distributed memory system also can be regarded as a special case of distributed storage system.A kind of asynchronous remote copying method that Fig. 2 C provides for the embodiment of the present invention is applied to the process flow diagram of non-distributed memory system:
Step 201: the write request that the main frame of the production group system reception production center issues.
The write request that the main frame of the first front-end platform reception production center in production group system alternatively, issues.
Because the storage system of the production center in this example only comprises a production group system, therefore without the determining step of carrying out step 22 in accompanying drawing 2A.
Step 202: the production group system is obtained all issues of current period, and is write request mark week issue according to all issues of the current period obtained.
Alternatively, the first front-end platform in the production group system is obtained all issues of current period, and be write request mark week issue according to all issues of the current period obtained, described all issues can be that the first front-end platform in this production group system arranges, and can be also for the device setting that current period number is set the first front-end platform that periodically is handed down to this production group system in production platform.
Step 203: the production group system writes local remote copy master LUN by the write request of all issues of mark current period.
The first front-end platform in the production group system is issued to the first business processing device in the first rear end platform in the production group system by the write request of all issues of mark current period, then in the production group system the first business processing device in the first rear end platform by mark week issue write request write remote copy master LUN.
Alternatively, the first business processing device in the production group system, the write request flag sequence number according to the order that writes local remote copy master LUN for the week of mark issue.
Alternatively, the first business processing device in the production group system, by the week of mark issue and the write request of serial number send to disaster recovery center.Further, the first business processing device in the production group system can by the week of mark issue and the write request of serial number write buffer memory, regularly write request is issued to disaster recovery center by buffer memory.
Embodiment tri-
Corresponding with embodiment mono-, the present embodiment is from the technical scheme of disaster tolerance central angle degree explanation asynchronous remote copying method of the present invention.The process flow diagram of the another kind of asynchronous remote copying method that Fig. 3 provides for the embodiment of the present invention.The storage system that the executive agent of the present embodiment is disaster recovery center.As shown in Figure 3, the present embodiment comprises:
Step 31: disaster recovery center receives the write request that the production center sends, and is marked with all issues and serial number in this write request.
Step 32: disaster recovery center judges whether to receive all write requests of one-period correspondence.
Step 33: disaster recovery center is determining that while having received all write requests of one-period correspondence, all issues and serial number according to mark in write request, write remote copy from LUN by the write request received.
The mode that disaster recovery center judges whether to receive all write requests of one-period correspondence in step 32 includes but not limited to:
Mode one, for the duration in each cycle of the production center, be isometric and the indefinite situation of the number write request that main frame that receive in each cycle is sent.When one-period finishes, the write request number that the main frame received in the described current period of all issues of current period and correspondence is sent in the production center sends to disaster recovery center; All issues that disaster recovery center sends according to the production center and corresponding write request number, and all issues and the serial number of mark in the write request that receives of step 31, judge whether to receive all write requests of one-period correspondence.
Mode two, the situation that is fixing preset value for the indefinite and number write request that main frame that receive in each cycle is sent of the duration in each cycle of the production center.All issues and the serial number of mark in the write request that disaster recovery center receives according to step 31, can judge whether to have received all write requests of one-period correspondence, for example, when sign has the quantity of the write request of same all issues and different order number to arrive described fixing preset value, all write requests that receive the one-period correspondence are described.
The embodiment of the present invention, the write request that disaster recovery center receives is marked with all issues and serial number, for the write request disaster recovery center of same period, can be in order number writes remote copy from LUN.Thereby a plurality of write requests of having avoided the conflict of in same period reference address arrive the order of disaster recovery centers when inconsistent with the write sequence of the heart aborning, the inconsistent problem of data that the data of storing in the remote copy master LUN of the caused production center and the remote copy of disaster recovery center are stored from LUN.
Embodiment tetra-
Provided respectively in the present embodiment the concrete application example of the asynchronous remote copying method shown in Fig. 3 in distributed memory system and non-distributed memory system.
The another kind of asynchronous remote copying method that Fig. 4 A provides for the embodiment of the present invention is applied to the process flow diagram of distributed memory system.The disaster recovery center example structure schematic diagram that Fig. 4 B provides for the embodiment of the present invention.The present embodiment illustrates the technical scheme of this asynchronous remote copying method from disaster tolerance central angle degree.As shown in Figure 4 B, in the present embodiment, the distributed memory system of disaster recovery center comprises at least two disaster tolerance cluster systems.Each disaster tolerance cluster system comprises the second front-end platform and the second rear end platform, and wherein the second rear end platform comprises that the second business processing device and remote copy are from LUN, and the second rear end platform also comprises the far-end buffer memory alternatively.The mode that disaster recovery center adopts the first in embodiment tri-to judge whether to receive all write requests of one-period correspondence in the present embodiment judges whether to receive all write requests of one-period correspondence.As shown in Figure 4 A, the present embodiment comprises:
Step 41: the disaster tolerance cluster system in disaster recovery center receives the write request that send the production center, is marked with all issues and serial number in this write request.This write request is that the identical production group system of physical address space of processing with this disaster tolerance cluster system in the production center sends.
Alternatively, the second front-end platform in the disaster tolerance cluster system receives the write request that the production group system in the production center sends.
That is to say, receive the handled physical address space of disaster tolerance cluster system of write request in disaster recovery center, the physical address space of processing with the production group system that sends this write request in the production center is identical.
Step 42: all issues and the serial number of mark in the write request number of all issues that described disaster tolerance cluster system sends according to the production center and correspondence and the temporary write request received, judge whether to receive all write requests of one-period correspondence, if while judgment result is that all write requests that receive the one-period correspondence, execution step 43, otherwise return to step 41, continue to receive the write request that the production center sends.
Alternatively, after the write request that the first business processing device of the second front-end platform reception production center of this disaster tolerance cluster system sends, the second business processing device in the second rear end platform of disaster tolerance cluster system under this write request is handed down to, the second business processing device can write the write request received in the far-end buffer memory of the second rear end platform.Particularly, according to all issues in write request, the second business processing device writes write request in the queue that in the far-end buffer memory, all issues are corresponding.For example, in the far-end buffer memory, write request is stored with the chain sheet form, chained list of one-period correspondence, and in chained list, write request sorts with serial number.When the second business processing device writes write request according to all issues of write request to chained list in the far-end buffer memory, according to the serial number of mark in write request, write request is inserted to relevant position in chained list.The schematic diagram of the write request chained list of preserving in the far-end buffer memory in the disaster tolerance cluster system that Fig. 4 C provides for the embodiment of the present invention.As shown in Figure 4 C, each week corresponding chained list of issue, in chained list, write request sorts with serial number.
Further, the second front-end platform of this disaster tolerance cluster system also can receive all issues and this week interior write request number received of cycle corresponding to issue that the production center sends, and all issues and the corresponding write request number that receive are sent to the second business processing device in the second rear end platform in affiliated disaster tolerance cluster system.All issues and the serial number of mark in all issues that described the second business processing device sends according to the second front-end platform and corresponding write request number and the temporary write request received, judge whether to receive all write requests of one-period correspondence.Whether the write request number that this week issue that the number of the write request of the same period that particularly, the second business processing device judgement has received number and different order number is sent with the production center is corresponding is identical; If the write request number that this week issue that the number of the write request of the same period received number and different order number is sent with the production center is corresponding is identical, determines and received this week all write requests corresponding to issue; Otherwise, determine and do not receive this week all write requests corresponding to issue.
Step 43: when described disaster tolerance cluster system has received all write requests of one-period correspondence, judge the write request that whether has the reference address conflict in all write requests that this week issue is corresponding.If judgment result is that to be, perform step 44, otherwise perform step 45.
Step 44: if there is the write request of reference address conflict, this disaster tolerance cluster system writes the remote copy of this disaster tolerance cluster system from LUN according to the serial number in write request successively by this week write request corresponding to issue.
Alternatively, the second business processing device of this disaster tolerance cluster system search write request in the queue of far-end buffer memory in queue corresponding to all issues, according to serial number in write request, the write request in queue is write to remote copy from LUN.
Step 45: if there is not the write request of reference address conflict, this disaster tolerance cluster system write request that this week issue is corresponding is concurrent writes remote copy from LUN.
Alternatively, the second business processing device of this disaster tolerance cluster system search write request in the queue of far-end buffer memory in queue corresponding to all issues, by this week issue, corresponding write request was concurrent writes remote copy from LUN.For example, Host1 and Host2 in T2 production center in the cycle issue the A write request of access logic address LBA1 and the B write request of access logic address LBA1 to the first front-end platform first, and the order that in the local remote copy master LUN of the first rear end platform, write request writes is B after first A.When causing the B write request, the reasons such as network delay arrive disaster recovery center prior to the A write request, and while writing in the far-end buffer memory of the second rear end platform of disaster recovery center prior to the A write request, because A write request and B write request all are marked with all issues and serial number, the second rear end platform is according to all issues and serial number, first the A write request is write to the far-end buffer memory, again the B request is write to the far-end buffer memory, and according in the far-end buffer memory, writing remote copy from LUN, thereby the inconsistent problem of data of having avoided remote copy master LUN and remote copy to store from LUN.
In the embodiment of the present invention, the storage system of disaster recovery center is distributed memory system, and each disaster tolerance cluster system is respectively used to process the write request of different physical address spaces.After the disaster tolerance cluster system receives the write request of production group system transmission identical with the physical address space of this disaster tolerance cluster system processing in the production center, judge whether to receive all write requests of one-period correspondence.Determining while having received all write requests, judge again the write request that whether has the physics address conflict in all write requests that this week issue is corresponding, to determine, the write request of this week issue is write to remote copy from LUN successively according to the serial number of mark wherein, or concurrently write remote copy from LUN.
It should be noted that, the another kind of asynchronous remote copying method that accompanying drawing 3 provides also can be applied to non-distributed storage system, in the disaster recovery center storage system, only comprises the situation of a disaster tolerance cluster system in accompanying drawing 4B.Non-distributed memory system also can be regarded as a special case of distributed storage system, its treatment scheme and accompanying drawing 4A are also substantially similar, only in step 41, owing to only having a disaster tolerance cluster system, thereby the write request received without restriction is the write request that the identical production group system of physical address space processed with this disaster tolerance cluster system in the production center sends, need to be only that the write request that send the production center gets final product.
Embodiment five
The distributed memory system structural representation of the production center that Fig. 2 B provides for the embodiment of the present invention.As shown in Fig. 2 B, the production center comprises at least one production group system, and each production group system comprises that first front-end platform 51 and first rear end platform 52, the first rear end platforms comprise the first business processing device 521 and remote copy master LUN522.
The first front-end platform 51, for after receiving the write request of main frame, according to all issues of current period, be write request mark week issue, and by mark week issue write request send under the first business processing device 521 in the first rear end platform 52 in the production group system.
The first business processing device 521, for by the week of mark issue write request write remote copy master LUN, the write request flag sequence number that is described mark week issue according to the order that writes described remote copy master LUN, and by mark week issue and the write request of serial number send to disaster recovery center.
Further, the production center comprises at least two production group systems, it is the storage system of the production center while being distributed memory system: the first front-end platform 51, for all issues according to current period, be also before described write request mark week issue, according to the logical address in the write request received and preserve logical address and the address mapping table of the mapping relations of physical address, determine the physical address of this write request, and in the physical address space processed in affiliated production group system of the physical address of judging this write request.
Further, to comprise at least two production group systems be a master control production group system and at least one non-master control production group system in the described production center;
The first front-end platform 51 in master control production group system, also for all issues of current period are set, and be handed down to each non-master control production group system by all issues of the current period of setting;
The first front-end platform 51 in described master control production group system, also for the cycle labelled notation of current period that self is arranged in described write request;
The first front-end platform 51 in described master control production group system, also for adding up in current period the write request number that receives described main frame; After current period finishes, described the first front-end platform in current period is received to the write request number of described main frame and all issues of current period send to disaster recovery center;
The first front-end platform 51 in non-master control production group system, all issues of the current period also periodically issued for the first front-end platform of obtaining master control production group system.
The first front-end platform 51 in described non-master control production group system, also for the cycle labelled notation of the current period by obtaining in described write request.
The working mechanism of above-mentioned each device, referring to describing in the corresponding embodiment of Fig. 2 A, does not repeat them here.
While comprising at least two production group systems in the heart aborning, in the embodiment of the present invention, the storage system of the production center is distributed memory system, and each production group system is respectively used to process the write request of different physical address spaces.The physical address space of processing comprises the production group system of the physical address of this write request, and all issues that the first front-end platform wherein issues according to master control the first front-end platform are write request mark week issue.The first business processing device of above-mentioned production group system is write request flag sequence number for the order that writes remote copy master LUN according to write request.Disaster recovery center receives write request and is marked with all issues and serial number, for the write request disaster recovery center of same period, can be in order number writes remote copy from LUN.Thereby a plurality of write requests of having avoided the conflict of in same period reference address arrive the order of disaster recovery centers when inconsistent with the write sequence of the heart aborning, the inconsistent problem of data that the data of storing in the remote copy master LUN of the caused production center and the remote copy of disaster recovery center are stored from LUN.
Embodiment six
The structural representation of the disaster recovery center embodiment that Fig. 4 B provides for the embodiment of the present invention.As shown in Figure 4 B, disaster recovery center comprises at least one disaster tolerance cluster system, and the disaster tolerance cluster system comprises that second front-end platform 61 and second rear end platform 62, the second rear end platforms 62 comprise that the second business processing device 621 and remote copy are from LUN622.Wherein,
The second front-end platform 61, the write request sent for receiving the production center, be marked with all issues and serial number in write request.
Further, when disaster recovery center comprises at least two disaster tolerance cluster systems: the second front-end platform 61, the write request sent specifically for receiving production group system identical with the physical address space of the affiliated disaster tolerance cluster system processing of this second front-end platform 61 in the production center.
The second business processing device 621, for judging whether the second front-end platform 61 has received all write requests of one-period correspondence, determining while having received all write requests of one-period correspondence, all issues and serial number according to mark in write request, write remote copy from LUN622 by the write request received.
Alternatively, described disaster tolerance cluster system also comprises far-end buffer memory 623.
The write request that described far-end buffer memory 623 receives for store the second front-end platform 61 in the chained list mode, each week corresponding chained list of issue particularly, the write request in chained list corresponding to each week issue sorts with serial number,
Described the second business processing device 621 judges according to the chained list of storage in far-end buffer memory 623 whether the second front-end platform 61 has received all write requests of one-period correspondence.
The working mechanism of above-mentioned each device, referring to describing in the corresponding embodiment of Fig. 4 A, does not repeat them here.
While comprising at least two disaster tolerance cluster systems in disaster recovery center, in the embodiment of the present invention, the storage system of disaster recovery center is distributed memory system, each disaster tolerance cluster system for the treatment of write request physical address space and other disaster tolerance cluster systems in this disaster recovery center for the treatment of the physical address space of write request different.Receive the handled physical address space of disaster tolerance cluster system of write request in disaster recovery center, the physical address space of processing with the production group system that sends this write request in the production center is identical.When the second business processing device of above-mentioned disaster tolerance cluster system receives the write request of the second front-end platform forwarding, writing of forwarding according to the second front-end platform please be counted and all issues, judges whether to receive all write requests of one-period correspondence.Determining while having received all write requests, judge again the write request that whether has the physics address conflict in all write requests that this week issue is corresponding, to determine, the write request of this week issue is write to remote copy from LUN successively according to the serial number of mark wherein, or concurrently write remote copy from LUN.
Embodiment seven
The structural representation of the second business processing device embodiment in the disaster recovery center that Fig. 5 provides for the embodiment of the present invention.As shown in Figure 5, the second business processing device 621 comprises: number of request judge module 6211, conflict judge module 6212, serial writing module 6213 and concurrent writing module 6214.
The second front-end platform, also the write request number for receiving all issues that the production center sends and receiving in corresponding cycle at this week issue.
Number of request judge module 6211, all issues and the serial number of all issues that send for the production center that receives according to the second front-end platform and write request number and the temporary write request mark received, judge whether to receive all write requests of one-period correspondence.
Embodiment eight
The structural representation of the asynchronous remote copy system that Fig. 6 provides for the embodiment of the present invention.As shown in Figure 6, the production center comprises at least one production group system, and each production group system comprises that first front-end platform 51 and first rear end platform 52, the first rear end platforms 52 comprise the first business processing device 521 and remote copy master LUN522.Disaster recovery center comprises at least one disaster tolerance cluster system, and the disaster tolerance cluster system comprises that second front-end platform 61 and second rear end platform 62, the second rear end platforms 62 comprise that the second business processing device 621 and remote copy are from LUN622.
The working mechanism of above-mentioned each device, referring to describing in Fig. 2 B and the corresponding embodiment of Fig. 4 B, does not repeat them here.
One of ordinary skill in the art will appreciate that: realize that the hardware that all or part of step of said method embodiment can be relevant by programmed instruction completes, aforesaid program can be stored in a computer read/write memory medium, this program, when carrying out, is carried out the step that comprises said method embodiment; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CDs.
Finally it should be noted that: above embodiment only, in order to technical scheme of the present invention to be described, is not intended to limit; Although with reference to previous embodiment, the present invention is had been described in detail, those of ordinary skill in the art is to be understood that: its technical scheme that still can put down in writing aforementioned each embodiment is modified, or part technical characterictic wherein is equal to replacement; And these modifications or replacement do not make the essence of appropriate technical solution break away from the spirit and scope of various embodiments of the present invention technical scheme.
Claims (16)
1. an asynchronous remote copying method, is characterized in that, comprising:
After the production center receives the write request of main frame, according to all issues of current period, be all issues of described write request mark;
By the week of mark, the write request of issue writes local remote copy master LUN, the write request flag sequence number that is described week of mark issue according to the order that writes described remote copy master LUN;
By the week of mark issue and the write request of serial number send to disaster recovery center so that described disaster recovery center writes remote copy from LUN according to described all issues and serial number by described write request.
2. the method for claim 1, is characterized in that, also comprises:
After current period finishes, the write request number of the described main frame that receives in all issues of described current period and current period is sent to described disaster recovery center.
3. method as claimed in claim 2, is characterized in that, the storage system of the production center comprises at least two production group systems, and described all issues according to current period are all issues of described write request mark, specifically comprise:
Each production group system is according to the logical address in described write request and preserve logical address and the address mapping table of the mapping relations of physical address, determines the physical address of described write request;
Judge whether physical address space that described production group system is processed comprises the physical address of described write request;
If the physical address space that described production group system is processed comprises the physical address of described write request, described production group system is obtained all issues of current period, and by the cycle labelled notation of described current period in described write request; Otherwise, ignore this write request or forward this write request to other production group system;
Described by the week of mark issue write request write remote copy master LUN, be specially:
Described production group system writes the remote copy master LUN of this production group system by the write request of the week of mark issue.
4. method as claimed in claim 3, is characterized in that, described at least two production group systems are a master control production group system and at least one non-master control production group system;
Described production group system is non-master control production group system, and described production group system is obtained all issues of current period, is specially:
Described production group system receives all issues of the current period that described master control production group system issues according to the request of this production group system, or
Described production group system receives the current period number that described master control production group system periodically issues;
Described production group system is master control production group system, and described production group system is obtained all issues of current period, is specially:
All issues of the current period that described production group system arranges self are as all issues of current period;
Described after current period finishes, the write request number of the described main frame that receives in current period and all issues of current period are sent to described disaster recovery center, be specially:
Receive the write request number of described main frame in described master control production group system statistics current period;
After current period finishes, described master control production group system sends to disaster recovery center by the write request number of the described main frame that receives in all issues of current period and current period.
5. an asynchronous remote copying method, is characterized in that, comprising:
Disaster recovery center receives the write request that the production center sends, and is marked with all issues and serial number in described write request; Described all issues are that the described production center is after receiving the write request of main frame, according to all issues of current period, it is described write request mark, described serial number is the described production center in the write request while writing local remote copy master LUN by the issue of mark week, the write request mark that is described week of mark issue according to the order that writes described remote copy master LUN;
Judge whether to receive all write requests of one-period correspondence;
When judgment result is that all write requests that receive the one-period correspondence, according to all issues and the serial number of mark in write request, the write request received is write to local remote copy from LUN.
6. method as claimed in claim 5, is characterized in that, described judge whether to receive all write requests of one-period correspondence before, also comprise:
The write request number that receives all issues that the production center sends and receive in corresponding cycle at this week issue;
The described all write requests that judge whether to receive the one-period correspondence are specially:
All issues and the serial number of mark in all issues that send according to the described production center and the write request number received in corresponding cycle at this week issue and the temporary write request received, judge whether to receive all write requests of one-period correspondence.
7. method as described as claim 5 or 6, it is characterized in that, described when judgment result is that all write requests that receive the one-period correspondence, described all issues and serial number according to mark in write request, the write request received is write to remote copy from LUN, is specially:
Judge in all write requests that described all issues are corresponding the write request that whether has the reference address conflict;
If there is the write request of reference address conflict, according to the serial number of mark in write request, by described all issues, corresponding write request writes remote copy successively from LUN;
If there is not the write request of reference address conflict, by described all issues, corresponding write request is concurrent writes remote copy from LUN.
8. method as described as claim 5 or 6, is characterized in that, when the storage system of described disaster recovery center comprises at least two disaster tolerance cluster systems, described disaster recovery center receives the write request that the production center sends, and is specially:
Disaster tolerance cluster system in disaster recovery center receives the write request that production group system identical with the physical address space of this disaster tolerance cluster system processing in the production center sends;
Described the write request received is write to local remote copy from LUN, is specially:
Disaster tolerance cluster system in disaster recovery center writes the remote copy of this disaster tolerance cluster system from LUN by the write request received.
9. the production center, it is characterized in that, comprise at least one production group system, described production group system comprises first front-end platform and first a rear end platform, described the first rear end platform comprises the first business processing device and remote copy master LUN, wherein:
Described the first front-end platform, for after receiving the write request of main frame, according to all issues of current period, be described write request mark week issue, and by mark week issue write request send under the first business processing device in the first rear end platform in the production group system;
The first business processing device, for by the week of mark issue write request write remote copy master LUN, the write request flag sequence number that is all issues of described mark according to the order that writes described remote copy master LUN, and by the week of mark issue and the write request of serial number send to disaster recovery center so that described disaster recovery center writes remote copy from LUN according to described all issues and serial number by described write request.
10. the production center as claimed in claim 9, is characterized in that, when the described production center comprises at least two production group systems:
Described the first front-end platform, for all issues according to current period, be also before described write request mark week issue, according to the logical address in the write request received and preserve logical address and the address mapping table of the mapping relations of physical address, determine the physical address of this write request; And the physical address space that under judging, the production group system is processed comprises the physical address of this write request.
11. as the production center as described in claim 9 or 10, it is characterized in that, the described production center comprises a master control production group system and at least one non-master control production group system;
The first front-end platform in described master control production group system, also for all issues of current period are set, and periodically be handed down to all issues of the current period of setting each non-master control production group system;
The first front-end platform in described master control production group system, the cycle labelled notation of the current period also arranged for the first front-end platform by described master control production group system is in described write request;
The first front-end platform in described master control production group system, also for adding up in current period the write request number that receives described main frame; After current period finishes, described the first front-end platform in current period is received to the write request number of described main frame and all issues of current period send to disaster recovery center;
The first front-end platform in non-master control production group system, all issues of the current period also periodically issued for the first front-end platform of obtaining master control production group system;
The first front-end platform in described non-master control production group system, the cycle labelled notation of the current period also periodically issued for the first front-end platform by described master control production group system is in described write request.
A 12. disaster recovery center, it is characterized in that, comprise at least one disaster tolerance cluster system, described disaster tolerance cluster system comprises second front-end platform and second a rear end platform, described the second rear end platform comprises that the second business processing device and remote copy are from LUN, wherein:
Described the second front-end platform, the write request sent for receiving the production center, be marked with all issues and serial number in described write request; Described all issues are that the described production center is after receiving the write request of main frame, according to all issues of current period, it is described write request mark, described serial number is the described production center in the write request while writing local remote copy master LUN by the issue of mark week, the write request mark that is described week of mark issue according to the order that writes described remote copy master LUN;
Described the second business processing device, for judging whether described the second front-end platform has received all write requests of one-period correspondence, determining while having received all write requests of one-period correspondence, all issues and serial number according to mark in write request, write remote copy from LUN by the write request received.
13. disaster recovery center as claimed in claim 12 is characterized in that:
Described the second front-end platform, the also number of request for receiving all issues that the production center sends and receiving in corresponding cycle at this week issue;
Described the second business processing device specifically comprises:
The number of request judge module, for all issues and the serial number of all issues of receiving according to described the second front-end platform and write request number and the temporary write request mark received, judge whether to receive all write requests of one-period correspondence;
The conflict judge module, for when the number of request judge module is determined all write requests that receive the one-period correspondence, judge in all write requests that described all issues are corresponding the write request that whether has the reference address conflict;
The serial writing module, if for there being the write request of reference address conflict, according to the serial number in write request, by described all issues, corresponding write request writes remote copy successively from LUN;
Concurrent writing module, if for there not being the write request of reference address conflict, by described all issues, corresponding write request is concurrent writes remote copy from LUN.
14. disaster recovery center as claimed in claim 12, is characterized in that, described disaster tolerance cluster system also comprises:
The far-end buffer memory, the write request received for store the second front-end platform in the chained list mode, be specially each week corresponding chained list of issue, and the write request in chained list corresponding to each week issue sorts according to serial number;
Described the second business processing device, also judge for the chained list of storing according to described far-end buffer memory whether the second front-end platform has received all write requests of one-period correspondence.
15. as disaster recovery center as described in claim 12 or 13, it is characterized in that, when described disaster recovery center comprises at least two disaster tolerance cluster systems:
Described the second front-end platform, also when receiving the write request that the production center sends, determining this write request is that the identical production group system of physical address space of processing with affiliated disaster tolerance cluster system in the production center sends.
16. an asynchronous remote copy system, is characterized in that, comprising:
The production center, after the write request that receives main frame, is all issues of described write request mark according to all issues of current period; By the week of mark, the write request of issue writes local remote copy master LUN, the write request flag sequence number that is described week of mark issue according to the order that writes described remote copy master LUN; By the week of mark issue and the write request of serial number send to disaster recovery center;
Disaster recovery center, the write request sent for receiving the production center, be marked with all issues and serial number in described write request; Judge whether to receive all write requests of one-period correspondence, when judgment result is that all write requests that receive the one-period correspondence, according to all issues and the serial number of mark in write request, the write request received is write to local remote copy from LUN.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110132517.2A CN102306115B (en) | 2011-05-20 | 2011-05-20 | Asynchronous remote copying method, system and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110132517.2A CN102306115B (en) | 2011-05-20 | 2011-05-20 | Asynchronous remote copying method, system and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102306115A CN102306115A (en) | 2012-01-04 |
| CN102306115B true CN102306115B (en) | 2014-01-08 |
Family
ID=45379980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110132517.2A Active CN102306115B (en) | 2011-05-20 | 2011-05-20 | Asynchronous remote copying method, system and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102306115B (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102790801B (en) * | 2012-06-20 | 2015-02-18 | 浪潮(北京)电子信息产业有限公司 | Asynchronous remote copy system and method for maintaining data consistency thereof |
| WO2014071588A1 (en) * | 2012-11-08 | 2014-05-15 | 华为技术有限公司 | Data replication method, storage controller and system |
| CN104520802B (en) * | 2013-07-26 | 2017-04-19 | 华为技术有限公司 | Data sending method, data receiving method and storage device |
| WO2015010327A1 (en) | 2013-07-26 | 2015-01-29 | 华为技术有限公司 | Data sending method, data receiving method and storage device |
| CN103617096A (en) * | 2013-11-04 | 2014-03-05 | 华为技术有限公司 | Storage data copying method, equipment and system |
| WO2015081473A1 (en) * | 2013-12-02 | 2015-06-11 | 华为技术有限公司 | Asynchronous replication method, apparatus and system |
| CN103814360B (en) * | 2013-12-12 | 2016-03-30 | 华为技术有限公司 | Data copy method and storage system |
| US9632973B2 (en) * | 2014-09-02 | 2017-04-25 | Intel Corporation | Supporting RMA API over active message |
| WO2016086342A1 (en) * | 2014-12-01 | 2016-06-09 | 华为技术有限公司 | Data write-in method, apparatus and device, and storage system |
| CN107111530B (en) * | 2014-12-31 | 2019-09-20 | 华为技术有限公司 | A kind of disaster recovery method, system and device |
| CN106502831B (en) * | 2016-10-24 | 2019-08-13 | 深信服科技股份有限公司 | A kind of method and device of image file duplication |
| CN108334561A (en) * | 2018-01-05 | 2018-07-27 | 深圳供电局有限公司 | A kind of cross-site remote copy implementation method |
| CN108762668B (en) * | 2018-05-07 | 2021-03-09 | 杭州宏杉科技股份有限公司 | Method and device for processing write conflict |
| CN108810150B (en) * | 2018-06-15 | 2020-11-27 | 国网上海市电力公司 | Data replication method of application-level disaster recovery backup system of cooperative office system |
| CN113868331B (en) * | 2021-08-20 | 2024-01-19 | 苏州浪潮智能科技有限公司 | Self-adaptive asynchronous replication method, device and equipment |
| CN113986128B (en) * | 2021-10-26 | 2024-05-28 | 杭州宏杉科技股份有限公司 | LUN data copying method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101067796A (en) * | 2007-06-07 | 2007-11-07 | 华为技术有限公司 | Image recovery method, storage equipment and network system |
| CN101635638A (en) * | 2008-07-25 | 2010-01-27 | 中兴通讯股份有限公司 | Disaster tolerance system and disaster tolerance method thereof |
| CN101814042A (en) * | 2010-03-05 | 2010-08-25 | 成都市华为赛门铁克科技有限公司 | Data asynchronous replication method and device thereof |
-
2011
- 2011-05-20 CN CN201110132517.2A patent/CN102306115B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101067796A (en) * | 2007-06-07 | 2007-11-07 | 华为技术有限公司 | Image recovery method, storage equipment and network system |
| CN101635638A (en) * | 2008-07-25 | 2010-01-27 | 中兴通讯股份有限公司 | Disaster tolerance system and disaster tolerance method thereof |
| CN101814042A (en) * | 2010-03-05 | 2010-08-25 | 成都市华为赛门铁克科技有限公司 | Data asynchronous replication method and device thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102306115A (en) | 2012-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102306115B (en) | Asynchronous remote copying method, system and equipment | |
| RU2596585C2 (en) | Method for sending data, data receiving method and data storage device | |
| US8468313B2 (en) | Asynchronous replication with write concurrency grouping | |
| US7647449B1 (en) | Method, system, and computer readable medium for maintaining the order of write-commands issued to a data storage | |
| US6950915B2 (en) | Data storage subsystem | |
| US9009724B2 (en) | Load balancing data access in virtualized storage nodes | |
| US7133982B2 (en) | Method, system, and article of manufacture for consistent copying of storage volumes | |
| CN101755257B (en) | Managing the copying of writes from primary storages to secondary storages across different networks | |
| US8463746B2 (en) | Method and system for replicating data | |
| US20150213100A1 (en) | Data synchronization method and system | |
| US20130024722A1 (en) | Virtual disk replication using log files | |
| US20120191908A1 (en) | Storage writes in a mirrored virtual machine system | |
| US9229970B2 (en) | Methods to minimize communication in a cluster database system | |
| CN102521058A (en) | Disk data pre-migration method of RAID (Redundant Array of Independent Disks) group | |
| CN1653427A (en) | Method and apparatus for creating a virtual data copy | |
| US7979651B1 (en) | Method, system, and computer readable medium for asynchronously processing write operations for a data storage volume having a copy-on-write snapshot | |
| CN102750317A (en) | Method and device for data persistence processing and data base system | |
| CN107291924B (en) | Synchronous log replication control method and system for disaster recovery backup system | |
| CN103034564A (en) | Data disaster tolerance demonstration and practicing method and data disaster tolerance demonstration and practicing device and system | |
| CN105824846A (en) | Data migration method and device | |
| US20050154786A1 (en) | Ordering updates in remote copying of data | |
| CN101794246B (en) | Backup storage system, backup system, data backup method and recovery method | |
| CN107329695B (en) | Distributed storage memory management method, system and computer storage medium | |
| US7676688B1 (en) | Concurrent data broadcast of selected common groups of data blocks | |
| CN107807790B (en) | Solid state disk data writing method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information |
Address after: 611731 Chengdu high tech Zone, Sichuan, West Park, Qingshui River Applicant after: HUAWEI DIGITAL TECHNOLOGIES (CHENG DU) Co.,Ltd. Address before: 611731 Chengdu high tech Zone, Sichuan, West Park, Qingshui River Applicant before: CHENGDU HUAWEI SYMANTEC TECHNOLOGIES Co.,Ltd. |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: APPLICANT; FROM: CHENGDU HUAWEI SYMANTEC TECHNOLOGIES CO., LTD. TO: HUAWEI DIGITAL TECHNOLOGY (CHENGDU) CO., LTD. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220831 Address after: No. 1899 Xiyuan Avenue, high tech Zone (West District), Chengdu, Sichuan 610041 Patentee after: Chengdu Huawei Technologies Co.,Ltd. Address before: 611731 Qingshui River District, Chengdu hi tech Zone, Sichuan, China Patentee before: HUAWEI DIGITAL TECHNOLOGIES (CHENG DU) Co.,Ltd. |