CN105068892A - Data cloning method and system - Google Patents
Data cloning method and system Download PDFInfo
- Publication number
- CN105068892A CN105068892A CN201510515712.1A CN201510515712A CN105068892A CN 105068892 A CN105068892 A CN 105068892A CN 201510515712 A CN201510515712 A CN 201510515712A CN 105068892 A CN105068892 A CN 105068892A
- Authority
- CN
- China
- Prior art keywords
- cloning
- data
- controller
- instruction
- main controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000010367 cloning Methods 0.000 title claims abstract description 212
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000011084 recovery Methods 0.000 claims abstract description 12
- 230000004913 activation Effects 0.000 claims description 16
- 230000003213 activating effect Effects 0.000 claims description 11
- 238000013377 clone selection method Methods 0.000 claims description 4
- 230000008439 repair process Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The embodiment of the present invention provides a data cloning method and a data cloning system, wherein the method comprises: determining whether a main controller gets out of order or not, if so, sending a cloning stop instruction to the main controller, receiving feedback information fed back by the main controller after stopping cloning, determining the data that are not cloned in a source volume, sending a cloning instruction to a subordinate controller, and cloning the data that are not cloned in the source volume by virtue of the subordinate controller after receiving the cloning instruction. When the main controller gets out of order, a cloning function is switched to and carried out on the subordinate controller, the waiting for the repair of the main controller is not required, and the data are not required to recover from a target volume to ensure that cloning operation can be performed continuously, so that the waiting time of cloning recovery is extremely short, the uninterrupted operation of upper-layer service is ensured, the real-time consistent data backup of user data is ensured, and the reliability of the data is improved.
Description
Technical Field
The invention relates to the technical field of data disaster recovery, in particular to a data cloning method and a data cloning system.
Background
The cloning technology is that a cloning relation is established between a source volume and a target volume in a storage system, when a user triggers a cloning action, data can be backed up from the source volume to the target volume, when an input/output (IO) is issued, a source end completes the cloning action to the target volume firstly, and then processes the received IO, so that the content of the target volume and the content of the source volume are consistent at the cloning time, and the condition that when the data is damaged due to the fault of any volume, the data of one volume is available and is the latest can be ensured. At present, a cloning relationship is established and activated between a source volume and a target volume in a controller, and when a user triggers a cloning action, data in the source volume is backed up to a destination volume through the controller to complete the cloning action. When the controller fails, the ongoing cloning action is terminated, the service of the user is also terminated, the cloning operation can be performed again after the controller is repaired, and even if the controller is recovered, the data can be recovered from the target volume to continue cloning, the service is provided to the outside, the waiting time for recovering cloning is long, the uninterrupted operation of upper-layer services cannot be ensured, the real-time consistent data backup of the user data cannot be ensured, and the reliability of the data is reduced.
Disclosure of Invention
In view of this, embodiments of the present invention provide a data cloning method and system, so as to solve the problems in the prior art that when a controller fails, an ongoing cloning operation is terminated, a service of a user is also terminated, a cloning operation may be performed again after the controller needs to be repaired, and even if the controller is restored, data needs to be restored from a target volume to continue cloning, a service is provided to the outside, a waiting time for restoring cloning is long, uninterrupted operation of an upper layer service cannot be guaranteed, real-time consistent data backup of user data cannot be guaranteed, and reliability of data is reduced.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
a data cloning method is used for a data disaster recovery system, the data disaster recovery system comprises a master controller and a slave controller, and the data cloning method comprises the following steps:
judging whether the main controller fails or not;
if the fault occurs, sending a command of stopping cloning to the main controller, receiving feedback information returned by the main controller after the main controller stops cloning, and determining data which is not cloned in the source volume;
and sending a cloning instruction to the slave controller, and cloning data which is not cloned in the source volume after the slave controller receives the cloning instruction.
Wherein, still include before judging whether main control unit breaks down:
sending a clone instruction to the main controller;
and after receiving the cloning instruction, the main controller clones the data in the source volume.
Wherein before sending the clone instruction to the main controller, the method further comprises:
sending clone preparation instructions to both the master controller and the slave controller;
determining a source volume and a target volume to be cloned, and establishing cloning relations between the source volume and the target volume in the master controller and the slave controller;
and activating the master controller and the slave controllers.
Wherein activating the master controller comprises: sending an activation instruction to the main controller, and registering a main clone plug-in therein by the main controller;
wherein activating the slave controller comprises: and sending an activation instruction to the slave controller, and registering the slave clone plug-in therein by the slave controller.
Wherein the master controller stopping cloning comprises:
the main controller receives a cloning stopping instruction;
and the main controller logs off the registration of the main clone plug-in therein.
Wherein, the cloning, after receiving the cloning instruction from the controller, data that has not been cloned in the source volume includes:
receiving a cloning instruction from the slave controller;
determining data which is not cloned in the source volume according to the cloning instruction;
and copying the data which is not cloned in the source volume into a destination volume corresponding to the source volume.
Wherein the data that has not been cloned in the source volume comprises: the data in the queue to be processed in the main controller, the data being copied in the main controller, and the data which has been cloned by the main controller and is not copied to the destination volume corresponding to the source volume.
A data cloning system is used for a data disaster backup system, the data disaster backup system comprises a main controller and a secondary controller, and the data cloning system comprises: the system comprises a judging module, a cloning stopping module and a first cloning module; wherein,
the judging module is used for judging whether the main controller fails or not;
the cloning stopping module is used for sending a cloning stopping instruction to the main controller when the main controller is judged to have a fault, receiving feedback information returned after the main controller stops cloning, and determining data which are not cloned in the source volume;
the first cloning module is configured to send a cloning instruction to the slave controller, so that the slave controller receives the cloning instruction and then clones data that has not been cloned in the source volume.
Wherein, the data cloning system further comprises: the second cloning module is used for sending a cloning instruction to the main controller; and after the main controller receives the cloning instruction, cloning the data in the source volume.
Wherein the data cloning system further comprises: the system comprises a clone preparation module, a clone selection module and a clone selection module, wherein the clone preparation module comprises an instruction sending unit, a relation establishing unit and an activation unit; wherein,
the instruction sending unit is used for sending clone preparation instructions to the master controller and the slave controller;
the relationship establishing unit is used for determining a source volume and a target volume to be cloned, and establishing the cloning relationship between the source volume and the target volume in the master controller and the slave controller;
and the activation unit is used for activating the master controller and the slave controller.
Based on the technical scheme, the data cloning method and system provided by the embodiment of the invention are used for a data disaster backup system, the data disaster backup system comprises a main controller and a slave controller, whether the main controller in the data disaster backup system fails or not is judged, if the main controller fails, a cloning stopping instruction is sent to the failed main controller, the main controller stops cloning operation after receiving the cloning stopping instruction, feedback information is sent to the main controller to inform the system of which data which are not cloned yet exist in a source volume, and after the data which are not cloned yet exist in the source volume are determined, a cloning instruction is sent to the slave controller, so that the slave controller starts to clone the data which are not cloned yet in the source volume after receiving the cloning instruction. When the master controller fails, the cloning operation of the master controller is stopped, the slave controller is started, the cloning function is switched to the slave controller for proceeding, the cloning operation can be continued without waiting for the repair of the master controller or recovering data from the target volume, the waiting time for recovering the cloning is extremely short, the uninterrupted operation of upper-layer services is ensured, the real-time consistent data backup of user data is ensured, and the reliability of the data is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flow chart of a data cloning method provided by an embodiment of the invention;
fig. 2 is a flowchart of a method for controlling a host controller to clone data in a source volume in a data cloning method according to an embodiment of the present invention;
FIG. 3 is a flowchart of a method for clone preparation in a data cloning method according to an embodiment of the present invention;
FIG. 4 is a flowchart of a method for stopping cloning by a host controller in a data cloning method according to an embodiment of the present invention;
fig. 5 is a flowchart of a method for cloning data that has not been cloned in a source volume after receiving a cloning instruction from a controller in a data cloning method according to an embodiment of the present invention;
FIG. 6 is a system block diagram of a data cloning system provided in an embodiment of the present invention, which is used in a data disaster recovery system;
FIG. 7 is another system block diagram of a data cloning system provided by an embodiment of the present invention;
fig. 8 is a block diagram illustrating a structure of a clone preparation module in the data cloning system according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a flowchart of a data cloning method provided in an embodiment of the present invention, which is used in a data disaster backup system, where the data disaster backup system includes a master controller and a slave controller, and when the master controller fails, a cloning operation of the master controller is stopped, the slave controller is started, and a cloning function is switched to the slave controller for performing, so that the cloning operation can be continued without waiting for repair of the master controller or recovering data from a target volume, and a waiting time for recovering cloning is extremely short, thereby ensuring uninterrupted operation of upper layer services, ensuring real-time consistent data backup of user data, and improving reliability of data; referring to fig. 1, the data cloning method may include:
step S100: judging whether the main controller fails or not;
optionally, each data disaster recovery system may include a master controller and a plurality of slave controllers, where the master controller refers to a controller currently performing a cloning operation, and the slave controller refers to a controller not currently performing a cloning operation.
Optionally, before determining whether the main controller fails, a clone instruction may be sent to the main controller, so that the main controller performs clone operation on the data in the source volume after receiving the clone instruction.
Optionally, before sending the clone instruction to the master controller, both the master controller and the slave controller should be activated.
Optionally, before activating both the master controller and the slave controller, the master controller and the slave controller may be put into clone preparation.
Optionally, the master controller and the slave controller may enter clone preparation by sending a clone preparation instruction to both the master controller and the slave controller, determining a source volume and a destination volume to be cloned, and establishing a clone relationship between the source volume and the destination volume in both the master controller and the slave controller.
Optionally, the activation operation may be performed on the main controller by sending an activation instruction to the main controller, and the main controller registers the main clone plug-in therein. Specifically, the main controller registers a main cloning plug-in therein, and registers the main cloning plug-in the main controller with a main manager therein.
Alternatively, the slave controller may be activated by sending an activation instruction to the slave controller, and registering the slave clone plug-in with the slave controller. Specifically, the slave controller registers the slave cloning plug-in therein, and registers the slave cloning plug-in therein to the slave manager.
Step S110: if the fault occurs, sending a command of stopping cloning to the main controller, receiving feedback information returned by the main controller after the main controller stops cloning, and determining data which is not cloned in the source volume;
if the main controller fails, the main controller can no longer be used for cloning data, a clone stopping instruction should be sent to the main controller, the main controller stops cloning operation, corresponding feedback information is sent to the system after the data which is not cloned is determined, and the main controller is informed of which data in the source volume are not cloned.
Optionally, after receiving the clone stopping instruction, the host controller may log off the registration of the host clone plug-in therein to stop the cloning of the host controller.
Step S120: and sending a cloning instruction to the slave controller, and cloning data which is not cloned in the source volume after the slave controller receives the cloning instruction.
When a clone instruction is sent to the slave controller, the slave controller will clone the data that has not been cloned in the source volume after receiving the clone instruction. At this time, the initial master controller has already been changed to the slave controller, and the initial slave controller is changed to the master controller, so that the master controller that has transmitted the failure at the beginning can perform maintenance.
Cloning the source volume data refers to copying the data in the source volume to the destination volume.
Optionally, after receiving the cloning instruction, the controller may determine, according to the cloning instruction, data that has not been cloned in the source volume, and copy the data that has not been cloned in the source volume to a destination volume corresponding to the source volume, so as to clone the data that has not been cloned in the source volume.
Optionally, the data in the queue to be processed in the master controller may include data being copied in the master controller, and data that has been already cloned by the master controller and has not been copied to the destination volume corresponding to the source volume.
Based on the technical scheme, the data cloning method provided by the embodiment of the invention is used for a data disaster backup system, the data disaster backup system comprises a main controller and a slave controller, whether the main controller in the data disaster backup system fails or not is judged, if the main controller fails, a cloning stopping instruction is sent to the failed main controller, the main controller stops cloning operation after receiving the cloning stopping instruction, feedback information is sent to the main controller to inform the system of which data which are not cloned yet exist in a source volume, and after the data which are not cloned yet exist in the source volume are determined, a cloning instruction is sent to the slave controller, so that the slave controller starts to clone the data which are not cloned yet in the source volume after receiving the cloning instruction. When the master controller fails, the cloning operation of the master controller is stopped, the slave controller is started, the cloning function is switched to the slave controller for proceeding, the cloning operation can be continued without waiting for the repair of the master controller or recovering data from the target volume, the waiting time for recovering the cloning is extremely short, the uninterrupted operation of upper-layer services is ensured, the real-time consistent data backup of user data is ensured, and the reliability of the data is improved.
Optionally, fig. 2 shows a flowchart of a method for controlling a host controller to clone data in a source volume in a data cloning method provided by an embodiment of the present invention, and referring to fig. 2, the method for controlling the host controller to clone data in the source volume may include:
step S200: sending a clone instruction to the main controller;
if the main controller is required to clone the data in the source volume, a clone instruction is sent to the main controller.
Step S210: and after receiving the cloning instruction, the main controller clones the data in the source volume.
And after receiving the cloning instruction, the main controller clones the data in the source volume.
Optionally, fig. 3 shows a flowchart of a method for performing clone preparation in the data cloning method provided in the embodiment of the present invention, and referring to fig. 3, the method for performing clone preparation may include:
step S300: sending clone preparation instructions to both the master controller and the slave controller;
step S310: determining a source volume and a target volume to be cloned, and establishing cloning relations between the source volume and the target volume in the master controller and the slave controller;
step S320: and activating the master controller and the slave controllers.
Optionally, the activation operation may be performed on the main controller by sending an activation instruction to the main controller, and the main controller registers the main clone plug-in therein. Specifically, the main controller registers a main cloning plug-in therein, and registers the main cloning plug-in the main controller with a main manager therein.
Alternatively, the slave controller may be activated by sending an activation instruction to the slave controller, and registering the slave clone plug-in with the slave controller. Specifically, the slave controller registers the slave cloning plug-in therein, and registers the slave cloning plug-in therein to the slave manager.
Optionally, fig. 4 shows a flowchart of a method for stopping cloning by a host controller in a data cloning method provided by an embodiment of the present invention, and referring to fig. 4, the method for stopping cloning by a host controller may include:
step S400: the main controller receives a cloning stopping instruction;
step S410: the slave controller deregisters the registration of the master clone plug-in therein.
Specifically, the slave controller logs off the registration of the master clone plug-in therein, and logs off the registration of the master clone plug-in therein to the management area therein for the host controller.
The method for stopping cloning of the slave controller is the same as the method for stopping cloning of the master controller.
Optionally, fig. 5 is a flowchart illustrating a method for cloning data that has not been cloned in a source volume after receiving a cloning instruction from a controller in the data cloning method according to an embodiment of the present invention, and referring to fig. 5, the method for cloning data that has not been cloned in a source volume after receiving a cloning instruction from a controller may include:
step S500: receiving a cloning instruction from the slave controller;
when the slave controller needs to perform cloning operation, the system generates a cloning instruction to the slave controller, and correspondingly, the slave controller receives the cloning instruction.
Step S510: determining data which is not cloned in the source volume according to the cloning instruction;
the slave controller, upon receiving the clone instruction, will be able to determine the data that the master controller has not cloned in the source volume.
Step S520: and copying the data which is not cloned in the source volume into a destination volume corresponding to the source volume.
And the slave controller clones the data which are not cloned in the source volume by the master controller, and copies the data which are not cloned in the source volume by the master controller into the destination volume corresponding to the source volume.
According to the data cloning method provided by the embodiment of the invention, when the master controller fails, the cloning operation of the master controller is stopped, the slave controller is started, the cloning function is switched to the slave controller for carrying out, the main controller does not need to be repaired, the data can be recovered from the target volume, the cloning operation can be continuously carried out, the waiting time for recovering the cloning is extremely short, the uninterrupted operation of upper-layer services is ensured, the real-time consistent data backup of user data is ensured, and the reliability of the data is improved.
In the following, the data cloning system provided by the embodiment of the present invention is introduced, and the data cloning system described below and the data cloning method described above may be referred to correspondingly.
Fig. 6 is a system block diagram of a data cloning system according to an embodiment of the present invention, where the data cloning system is used in a data disaster recovery system, where the data disaster recovery system includes a master controller and a slave controller, and referring to fig. 6, the data cloning system may include: a decision module 100, a stop cloning module 200 and a first cloning module 300; wherein,
a judging module 100, configured to judge whether the main controller fails;
a clone stopping module 200, configured to send a clone stopping instruction to the main controller when it is determined that the main controller fails, receive feedback information returned after the main controller stops cloning, and determine data that has not been cloned in the source volume;
a first cloning module 300, configured to send a cloning instruction to the slave controller, so that the slave controller receives the cloning instruction and then clones data that has not been cloned in the source volume.
Optionally, fig. 7 shows another system block diagram of the data cloning system provided in the embodiment of the present invention, and referring to fig. 7, the data cloning system may further include: a clone preparation module 400 and a second cloning module 500; wherein,
a second cloning module 500, configured to send a cloning instruction to the main controller; and after the main controller receives the cloning instruction, cloning the data in the source volume.
Optionally, fig. 8 shows a block diagram of a structure of a clone preparation module 400 in the data cloning system according to an embodiment of the present invention, and referring to fig. 8, the clone preparation module 400 may include: an instruction sending unit 410, a relationship establishing unit 410 and an activating unit 420; wherein,
an instruction sending unit 410, configured to send a clone preparation instruction to both the master controller and the slave controller;
a relationship establishing unit 420, configured to determine a source volume and a destination volume to be cloned, and establish a cloning relationship between the source volume and the destination volume in both the master controller and the slave controller;
an activation unit 430, configured to perform an activation operation on both the master controller and the slave controller.
According to the data cloning system provided by the embodiment of the invention, when the master controller fails, the cloning operation of the master controller is stopped, the slave controller is started, the cloning function is switched to the slave controller for carrying out, the main controller does not need to be repaired, the data can be recovered from the target volume, the cloning operation can be continuously carried out, the waiting time for recovering the cloning is extremely short, the uninterrupted operation of upper-layer services is ensured, the real-time consistent data backup of user data is ensured, and the reliability of the data is improved.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A data cloning method is used for a data disaster recovery system, wherein the data disaster recovery system comprises a master controller and a slave controller, and the data cloning method comprises the following steps:
judging whether the main controller fails or not;
if the fault occurs, sending a command of stopping cloning to the main controller, receiving feedback information returned by the main controller after the main controller stops cloning, and determining data which is not cloned in the source volume;
and sending a cloning instruction to the slave controller, and cloning data which is not cloned in the source volume after the slave controller receives the cloning instruction.
2. The data cloning method of claim 1, further comprising, before determining whether the primary controller fails:
sending a clone instruction to the main controller;
and after receiving the cloning instruction, the main controller clones the data in the source volume.
3. The data cloning method of claim 2, wherein before sending the clone instruction to the host controller, further comprising:
sending clone preparation instructions to both the master controller and the slave controller;
determining a source volume and a target volume to be cloned, and establishing cloning relations between the source volume and the target volume in the master controller and the slave controller;
and activating the master controller and the slave controllers.
4. The data cloning method of claim 3,
activating the master controller includes: sending an activation instruction to the main controller, and registering a main clone plug-in therein by the main controller;
activating the slave controller comprises: and sending an activation instruction to the slave controller, and registering the slave clone plug-in therein by the slave controller.
5. The data cloning method of claim 1, wherein the master controller stopping cloning comprises:
the main controller receives a cloning stopping instruction;
and the main controller logs off the registration of the main clone plug-in therein.
6. The data cloning method of claim 1, wherein the cloning of the data that has not been cloned in the source volume after receiving the cloning instruction from the controller comprises:
receiving a cloning instruction from the slave controller;
determining data which is not cloned in the source volume according to the cloning instruction;
and copying the data which is not cloned in the source volume into a destination volume corresponding to the source volume.
7. The data cloning method of claim 1, wherein the data in the source volume that has not been cloned comprises: the data in the queue to be processed in the main controller, the data being copied in the main controller, and the data which has been cloned by the main controller and is not copied to the destination volume corresponding to the source volume.
8. A data cloning system, which is used for a data disaster recovery system, wherein the data disaster recovery system comprises a master controller and a slave controller, and the data cloning system comprises: the system comprises a judging module, a cloning stopping module and a first cloning module; wherein,
the judging module is used for judging whether the main controller fails or not;
the cloning stopping module is used for sending a cloning stopping instruction to the main controller when the main controller is judged to have a fault, receiving feedback information returned after the main controller stops cloning, and determining data which are not cloned in the source volume;
the first cloning module is configured to send a cloning instruction to the slave controller, so that the slave controller receives the cloning instruction and then clones data that has not been cloned in the source volume.
9. The data cloning system of claim 8, further comprising: the second cloning module is used for sending a cloning instruction to the main controller; and after the main controller receives the cloning instruction, cloning the data in the source volume.
10. The data cloning system of claim 9,
the data cloning system further comprises: the system comprises a clone preparation module, a clone selection module and a clone selection module, wherein the clone preparation module comprises an instruction sending unit, a relation establishing unit and an activation unit; wherein,
the instruction sending unit is used for sending clone preparation instructions to the master controller and the slave controller;
the relationship establishing unit is used for determining a source volume and a target volume to be cloned, and establishing the cloning relationship between the source volume and the target volume in the master controller and the slave controller;
and the activation unit is used for activating the master controller and the slave controller.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510515712.1A CN105068892B (en) | 2015-08-20 | 2015-08-20 | A kind of data cloning method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510515712.1A CN105068892B (en) | 2015-08-20 | 2015-08-20 | A kind of data cloning method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105068892A true CN105068892A (en) | 2015-11-18 |
| CN105068892B CN105068892B (en) | 2018-02-09 |
Family
ID=54498269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510515712.1A Active CN105068892B (en) | 2015-08-20 | 2015-08-20 | A kind of data cloning method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105068892B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109460331A (en) * | 2018-10-24 | 2019-03-12 | 郑州云海信息技术有限公司 | A kind of clone's characteristic test method, device, equipment and storage medium |
| WO2020211740A1 (en) * | 2019-04-18 | 2020-10-22 | 华为技术有限公司 | User terminal, debugging apparatus, and data backup method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101237315A (en) * | 2008-02-28 | 2008-08-06 | 浪潮电子信息产业股份有限公司 | A synchronous detection and failure separation method for dual control high-availability system |
| CN103197989A (en) * | 2011-11-30 | 2013-07-10 | 富士通株式会社 | Storage device, controller, and computer-readable recording medium having stored therein program |
| CN104681835A (en) * | 2013-11-28 | 2015-06-03 | 中国科学院沈阳自动化研究所 | Double-unit backup controller of proton exchange membrane fuel cell and control method of double-unit backup controller |
-
2015
- 2015-08-20 CN CN201510515712.1A patent/CN105068892B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101237315A (en) * | 2008-02-28 | 2008-08-06 | 浪潮电子信息产业股份有限公司 | A synchronous detection and failure separation method for dual control high-availability system |
| CN103197989A (en) * | 2011-11-30 | 2013-07-10 | 富士通株式会社 | Storage device, controller, and computer-readable recording medium having stored therein program |
| CN104681835A (en) * | 2013-11-28 | 2015-06-03 | 中国科学院沈阳自动化研究所 | Double-unit backup controller of proton exchange membrane fuel cell and control method of double-unit backup controller |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109460331A (en) * | 2018-10-24 | 2019-03-12 | 郑州云海信息技术有限公司 | A kind of clone's characteristic test method, device, equipment and storage medium |
| CN109460331B (en) * | 2018-10-24 | 2021-10-29 | 郑州云海信息技术有限公司 | Clone characteristic testing method, device, equipment and storage medium |
| WO2020211740A1 (en) * | 2019-04-18 | 2020-10-22 | 华为技术有限公司 | User terminal, debugging apparatus, and data backup method |
| US11966299B2 (en) | 2019-04-18 | 2024-04-23 | Huawei Technologies Co., Ltd. | User terminal, debugging device, and data backup method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105068892B (en) | 2018-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2957749C (en) | Systems and methods for fault tolerant communications | |
| CN106330475B (en) | Method and device for managing main and standby nodes in communication system and high-availability cluster | |
| CN103488498A (en) | Computer booting method and computer | |
| JP6431197B2 (en) | Snapshot processing methods and associated devices | |
| CN104038376A (en) | Method and device for managing real servers and LVS clustering system | |
| TW201843583A (en) | Method and computer system for automatically recovering the BIOS image file | |
| CN103188098B (en) | A kind of disaster tolerance switching method, system and device | |
| CN112380062A (en) | Method and system for rapidly recovering system for multiple times based on system backup point | |
| CN110109772B (en) | CPU restarting method, communication equipment and readable storage medium | |
| CN105068892B (en) | A kind of data cloning method and system | |
| CN113438111A (en) | Method for restoring RabbitMQ network partition based on Raft distribution and application | |
| CN115629785A (en) | Upgrading method, electronic device and storage medium | |
| JP2010067115A (en) | Data storage system and data storage method | |
| JP2007200103A (en) | Client-server system and resource control method | |
| WO2014176969A1 (en) | Automatic disaster recovery switching method and device | |
| JP2008242679A (en) | Server system and patch processing method | |
| JP2007049318A (en) | Managed device, network management system, and information matching method | |
| CN109947593B (en) | Data disaster tolerance method, system, strategy arbitration device and storage medium | |
| CN111142805A (en) | Data center hybrid cloud storage method and device, computer equipment and storage medium | |
| CN104683153A (en) | Cluster-based router host and spare MPU control method and system thereof | |
| JP2008009518A (en) | Dual operation system | |
| JP2006302081A (en) | Service restart device and service restart program | |
| JP2014066664A (en) | System and method for automatic operation changeover upon occurrence of earthquake | |
| KR20090027051A (en) | Method for controlling financial obstacle | |
| JP4819475B2 (en) | Program update device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180817 Address after: 200436 Room 411, No. three, JIANGCHANG Road, Jingan District, Shanghai, 411 Patentee after: Shanghai wave Cloud Computing Service Co., Ltd. Address before: 100085 floor 1, C 2-1, No. 2, Shang Di Road, Haidian District, Beijing. Patentee before: Electronic information industry Co.,Ltd of the tide (Beijing) |