CN103729280A - High availability mechanism for virtual machine - Google Patents
High availability mechanism for virtual machine Download PDFInfo
- Publication number
- CN103729280A CN103729280A CN201310719697.3A CN201310719697A CN103729280A CN 103729280 A CN103729280 A CN 103729280A CN 201310719697 A CN201310719697 A CN 201310719697A CN 103729280 A CN103729280 A CN 103729280A
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- realization
- abnormal
- management
- high available
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Hardware Redundancy (AREA)
Abstract
The invention relates to the technical field of cloud computing, in particular to a high availability mechanism for a virtual machine. The high availability mechanism is realized according to the following steps: 1, configuring a shared memory on each realizing end; 2, creating the virtual machine and a cloud disk in the shared memory by a user, and configuring high availability for the virtual machine; 3, acquiring communication information of each realizing end by a monitoring module; 4, collecting abnormal information and timely forwarding the same to a management end by the monitoring module; 5, performing abnormality analysis by the management end, selecting a target realizing end to move and record the virtual machine and the cloud disk thereof if a circumstance that a source realizing end is abnormal is determined, and ignoring the abnormal information if no abnormality exists; 6, when the source realizing end which is abnormal return to normal, automatically connecting with the management end to perform corresponding synchronous processing on the virtual machine thereon. The high availability mechanism guarantees that the virtual machine still can provide services outwards when a host machine to which the virtual machine belongs is in a failure, and can be used on a cloud platform of cloud computing Iaas.
Description
Technical field
The present invention relates to cloud computing technology field, refer to especially the high available mechanism of a kind of virtual machine.
Background technology
In cloud computing, virtual machine is used to replace the carrier of physics as application deployment by a large amount of, based on the advantage of virtual use as required and rapid deployment, the master-slave redundancy mode that virtual machine can replace conventional physical machine in the mode of dynamic migration is as the available a kind of implementation method of height, so-called dynamic migration refers to that system detects when physical machine breaks down that the virtual machine Autonomic Migration Framework on it, to the technology in other physical machine, general dynamic migration technology is such:
1, system detects physical machine generation network failure, does not connect;
2, system is according to selection algorithm, for each virtual machine in physical machine is chosen target virtual machine;
3, one one of system is walked virtual machine (vm) migration.
There is following problem in this method:
1, non-complete height is available, this method is only comprehensive not from the angle handling failure of virtual machine, the set that virtual machine is high availablely should be " operating system height available+data height is available ", this method is the loss of data on logical volume after processing the situation that is mounted with logical volume on virtual machine and can causing moving;
2, fault-tolerance is not high, this method detect physical machine network failure be exactly conventionally carry out ping do not have later return data bag or ping value too high, can this situation sometimes can not continue to occur, LAN (Local Area Network) is because burst data amount causes greatly transience to be stopped up or physical machine causes the situation that network failure appears in low-response to occur commonplace because temporary load is high, in this case, this method there will be erroneous judgement, virtual machine is all moved, cause unnecessary virtual machine applied business to pause and extra offered load, affect the service quality of whole system.
Summary of the invention
The technical matters that the present invention solves is to provide a kind of virtual machine high available mechanism, has solved the problems such as the fault-tolerance existing in current virtual machine dynamic migration is not strong, offered load is high, loss of data.
The technical scheme that the present invention solves the problems of the technologies described above is:
Comprise the steps:
Step 1: storage is shared in configuration on each realizes end, for depositing the shared resources such as virtual machine image file and cloud dish;
Step 2: user creates virtual machine and cloud dish in the shared storage that realizes end, and it is available to configure this virtual machine height;
Step 3: monitoring module is monitored in real time to realizing end, connects extremely once find to realize end, sends alarm;
Step 4; Monitoring module is collected abnormal information and is transmitted in time management end;
Step 5: management end receives monitoring abnormal information and carries out anomaly analysis: abnormal if analysis result determines that end is realized in source, according to collocation strategy, choose realization of goal end, to disposing high available virtual machine and cloud dish thereof, move and record preservation; If end is realized without abnormal in analysis result demonstration source, ignore this abnormal information;
Step 6: after occurring that end recovery is normally realized in abnormal source, will automatically synchronize with management end, the virtual machine on it is carried out to respective synchronization processing.
Described monitoring module supervisory control action specifically comprises the steps:
Step 1: monitoring module carries out gt communication connection with realization end;
Step 2: abnormal if gt connects, monitoring module produces and realizes end fault warning information, and obtains the IP list that realizes end node; Otherwise proceed step 1;
Step 3: monitoring module successively ping alarm is realized the IP holding: if all IP cannot lead to by ping, realization end corresponding information is handed to management end processing; Otherwise proceed step 1;
Described gt refers to the means of communication that communicates connection on cloud platform between modules, based on Socket, realizes;
Described realization end corresponding information specifically has the title, IP etc. that realize end.
Described management end anomaly analysis flow process is as follows:
Step 1: what receive that monitoring module sends over realizes client information, these abnormal all IP that realize end of ping successively extremely;
Step 2: realize all IP of end if abnormal and all cannot lead to by ping, determine that this realization end is abnormal; Otherwise ignore this abnormality processing, continue execution step 1;
Step 3: to determining abnormal realization end, select successively to dispose above this realization end high available virtual machine and choose realization of goal end according to collocation strategy and carry out virtual machine (vm) migration;
Step 4: virtual machine (vm) migration success, continue judge whether this virtual machine comprises highly reliable cloud dish, if having, continue migration cloud dish extremely with the same realization of goal end of virtual machine;
Step 5: record above-mentioned migration results and preserve;
Described collocation strategy refers to that management end is in the method for choosing realization of goal end and taking, and can be that order is chosen, chosen at random with least resource and choose etc.
After described abnormal realization end recovers, synchronize and comprise with the management end information of carrying out:
Step 1: realize end and recover normal, initiatively gt connection management end;
Step 2: the status information that report realizes end itself is to management end;
Step 3: record to close the original high available virtual machine of deletion and cloud dish thereof according to the virtual machine (vm) migration in management end;
Step 4: carry out synchronously to management end realizing the non-high available virtual machine status report not moved on end.
Described high available virtual machine refers to that virtual machine itself can not be subject to the impact of its host fault, at host, occurs still can normally providing under abnormal conditions service;
Described host refers to that virtual machine moves the physical server of depositing;
Described realization end and management end refer to two the independently processes that operate on physical server; Realize the physical resources such as all CPU above end management of process physical server, internal memory, carry out and create virtual machine, create the processes such as cloud dish and VLAN; Management end process is responsible for the United Dispatching of cloud platform, with the process communication of all realization ends and manage the resource informations such as all virtual machines on it, cloud dish;
Described cloud dish refers to the memory device that is similar to USB flash disk or portable hard drive;
Described shared storage is a storage space that can make all realization ends use by configuration, can be used for the associated documents such as storage virtual machine mirror image, configuration; Described configuration can be used the diverse ways such as NFS, Ceph FS.
Beneficial effect of the present invention has:
1, mechanism of the present invention has considered that the height height available and data of operating system is available comprehensively, when carrying out migration, by different two parts migrations, can guarantee the normal operation of application after migration completes; Virtual machine does not rely on specific host, and, in the situation that host breaks down, virtual machine can normally effectively externally provide service;
2, mechanism of the present invention adopts the mode that continues monitors physical machine, has very high fault-tolerance, can obviously reduce the virtual machine (vm) migration number of times causing because of erroneous judgement, saves the bandwidth of LAN (Local Area Network), reduces offered load.
3, the present invention can be applied on other IaaS cloud platforms fast.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further described:
Fig. 1 is the inventive method process flow diagram;
Fig. 2 is modular structure figure of the present invention.
embodiment
As shown in Figure 1, 2, mechanism of the present invention comprises the steps:
Step 1: storage is shared in configuration on each realizes end, for depositing the shared resources such as virtual machine image file and cloud dish;
Step 2: user creates virtual machine and cloud dish in the shared storage that realizes end, and it is available to configure this virtual machine height;
Step 3: monitoring module is monitored in real time to realizing end, connects extremely once find to realize end, sends alarm;
Step 4: monitoring module is collected abnormal information and is transmitted in time management end;
Step 5: management end receives monitoring abnormal information and carries out anomaly analysis: abnormal if analysis result determines that end is realized in source, according to collocation strategy, choose realization of goal end, to disposing high available virtual machine and cloud dish thereof, move and record preservation; If end is realized without abnormal in analysis result demonstration source, ignore this abnormal information;
Step 6: after occurring that end recovery is normally realized in abnormal source, will automatically synchronize with management end, the virtual machine on it is carried out to respective synchronization processing.
Monitoring module supervisory control action specifically comprises the steps:
Step 1: monitoring module carries out gt communication connection with realization end;
Step 2: abnormal if gt connects, monitoring module produces and realizes end fault warning information, and obtains the IP list that realizes end node; Otherwise proceed step 1;
Step 3: monitoring module successively ping alarm is realized the IP holding: if all IP cannot lead to by ping, realization end corresponding information is handed to management end processing; Otherwise proceed step 1;
Described gt refers to the means of communication that communicates connection on cloud platform between modules, based on Socket, realizes;
Described realization end corresponding information specifically has the title, IP etc. that realize end.
Management end anomaly analysis flow process is as follows:
Step 1: what receive that monitoring module sends over realizes client information, these abnormal all IP that realize end of ping successively extremely;
Step 2: realize all IP of end if abnormal and all cannot lead to by ping, determine that this realization end is abnormal; Otherwise ignore this abnormality processing, continue execution step 1;
Step 3: to determining abnormal realization end, select successively to dispose above this realization end high available virtual machine and choose realization of goal end according to collocation strategy and carry out virtual machine (vm) migration;
Step 4: virtual machine (vm) migration success, continue judge whether this virtual machine comprises highly reliable cloud dish, if having, continue migration cloud dish extremely with the same realization of goal end of virtual machine;
Step 5: record above-mentioned migration results and preserve;
Described collocation strategy refers to that management end is in the method for choosing realization of goal end and taking, and can be that order is chosen, chosen at random with least resource and choose etc.
Abnormal realization after end recovers synchronizeed and comprised with the management end information of carrying out:
Step 1: realize end and recover normal, initiatively gt connection management end;
Step 2: the status information that report realizes end itself is to management end;
Step 3: record to close the original high available virtual machine of deletion and cloud dish thereof according to the virtual machine (vm) migration in management end;
Step 4: carry out synchronously to management end realizing the non-high available virtual machine status report not moved on end.
High available virtual machine of the present invention refers to that virtual machine itself can not be subject to the impact of its host fault, at host, occurs still can normally providing under abnormal conditions service;
Described host refers to that virtual machine moves the physical server of depositing;
Described realization end and management end refer to two the independently processes that operate on physical server; Realize the physical resources such as all CPU above end management of process physical server, internal memory, carry out and create virtual machine, create the processes such as cloud dish and VLAN; Management end process is responsible for the United Dispatching of cloud platform, with the process communication of all realization ends and manage the resource informations such as all virtual machines on it, cloud dish;
Described cloud dish refers to the memory device that is similar to USB flash disk or portable hard drive;
Described shared storage is a storage space that can make all realization ends use by configuration, can be used for the associated documents such as storage virtual machine mirror image, configuration; Described configuration can be used the diverse ways such as NFS, Ceph FS.
Shared storage in the present invention can be diversified, and we are take NFS as example here.
On all realization ends, carry out as ordered, the NFS putting up be mounted to this locality/sharfiles catalogue realize shared storage on 20.251.32.19 node:
#showmount-e20.251.32.19
#mount-t?nfs-o?vers=320.251.32.19:/sdb/sharefiles
#echo"mount-t?nfs-o?vers=3,nolock20.251.32.19:/sdb/sharefiles">>/etc/rc.local
Whether in virtual machine entity class, increase high data available item: isHa data item;
At NFS, share in storage and create high available virtual machine, it is TRUE that isHa is set, and represents that this virtual machine has been set to high available, has high available characteristic.
Monitoring module is according to realizing the end IP all clients of monitoring in real time, and abnormal in order to judge whether realization end occurs, code is as follows:
Realize end node and determine that appearance is abnormal, the method for carrying out is below chosen object realization end, in order to receive abnormal realization end, moves the high available virtual machine of coming, and code is as follows:
Select object and realize after end node, carry out highly reliable virtual machine (vm) migration, migration code is as follows:
For moving successful virtual machine above, management end continues object information to be recorded to database preservation, for recovering rear synchronous effect at the abnormal end of realizing:
// highly reliable and high performance Mail Contents combination
mail+=highPerfMail;
// end of record (EOR) the time
VmHaInfo?endRecord=new?VmHaInfo();
endRecord.setComment(hypervisorType);//KVM、XEN
EndRecord.setCores (core); // statistics check figure
EndRecord.setDisk (disk); // statistics disk
endRecord.setMemory(memory);
EndRecord.setDstIp (" "); // destination ip
endRecord.setEndTime(new?Date());
endRecord.setInstanceId("");
endRecord.setName(name);
endRecord.setNode(name);
EndRecord.setNodeType (" physical "); //physical: physical machine; Virtual: virtual machine
endRecord.setSrcIp("");
endRecord.setStartTime(taskStartDate);
EndRecord.setState (" carrying out HA function finishes ");
endRecord.setParentId(0);
try
When occur abnormal realization end recover normal after, automatically communicate and be connected with management end, first by the status information reporting of oneself to management end, then synchronous all virtual machine states on it, partial code is as follows:
Claims (7)
1. the high available mechanism of virtual machine, is characterized in that: comprise the steps:
Step 1: storage is shared in configuration on each realizes end, for depositing the shared resources such as virtual machine image file and cloud dish;
Step 2: user creates virtual machine and cloud dish in the shared storage that realizes end, and it is available to configure this virtual machine height;
Step 3: monitoring module is monitored in real time to realizing end, connects extremely once find to realize end, sends alarm;
Step 4: monitoring module is collected abnormal information and is transmitted in time management end;
Step 5: management end receives monitoring abnormal information and carries out anomaly analysis: abnormal if analysis result determines that end is realized in source, according to collocation strategy, choose realization of goal end, to disposing high available virtual machine and cloud dish thereof, move and record preservation; If end is realized without abnormal in analysis result demonstration source, ignore this abnormal information;
Step 6: after occurring that end recovery is normally realized in abnormal source, will automatically synchronize with management end, the virtual machine on it is carried out to respective synchronization processing.
2. the high available mechanism of virtual machine according to claim 1, is characterized in that: described monitoring module supervisory control action specifically comprises the steps:
Step 1: monitoring module carries out gt communication connection with realization end;
Step 2: abnormal if gt connects, monitoring module produces and realizes end fault warning information, and obtains the IP list that realizes end node; Otherwise proceed step 1;
Step 3: monitoring module successively ping alarm is realized the IP holding: if all IP cannot lead to by ping, realization end corresponding information is handed to management end processing; Otherwise proceed step 1;
Described gt refers to the means of communication that communicates connection on cloud platform between modules, based on Socket, realizes;
Described realization end corresponding information specifically has the title, IP etc. that realize end.
3. the high available mechanism of virtual machine according to claim 1, is characterized in that: described management end anomaly analysis flow process is as follows:
Step 1: what receive that monitoring module sends over realizes client information, these abnormal all IP that realize end of ping successively extremely;
Step 2: realize all IP of end if abnormal and all cannot lead to by ping, determine that this realization end is abnormal; Otherwise ignore this abnormality processing, continue execution step 1;
Step 3: to determining abnormal realization end, select successively to dispose above this realization end high available virtual machine and choose realization of goal end according to collocation strategy and carry out virtual machine (vm) migration;
Step 4: virtual machine (vm) migration success, continue judge whether this virtual machine comprises highly reliable cloud dish, if having, continue migration cloud dish extremely with the same realization of goal end of virtual machine;
Step 5: record above-mentioned migration results and preserve;
Described collocation strategy refers to that management end is in the method for choosing realization of goal end and taking, and can be that order is chosen, chosen at random with least resource and choose etc.
4. the high available mechanism of virtual machine according to claim 2, is characterized in that: described management end anomaly analysis flow process is as follows:
Step 1: what receive that monitoring module sends over realizes client information, these abnormal all IP that realize end of ping successively extremely;
Step 2: realize all IP of end if abnormal and all cannot lead to by ping, determine that this realization end is abnormal; Otherwise ignore this abnormality processing, continue execution step 1;
Step 3: to determining abnormal realization end, select successively to dispose above this realization end high available virtual machine and choose realization of goal end according to collocation strategy and carry out virtual machine (vm) migration;
Step 4: virtual machine (vm) migration success, continue judge whether this virtual machine comprises highly reliable cloud dish, if having, continue migration cloud dish extremely with the same realization of goal end of virtual machine;
Step 5: record above-mentioned migration results and preserve;
Described collocation strategy refers to that management end is in the method for choosing realization of goal end and taking, and can be that order is chosen, chosen at random with least resource and choose etc.
5. according to the high available mechanism of virtual machine described in claim 1 to 4 any one, it is characterized in that: after described abnormal realization end recovers, synchronize and comprise with the management end information of carrying out:
Step 1: realize end and recover normal, initiatively gt connection management end;
Step 2: the status information that report realizes end itself is to management end;
Step 3: record to close the original high available virtual machine of deletion and cloud dish thereof according to the virtual machine (vm) migration in management end;
Step 4: carry out synchronously to management end realizing the non-high available virtual machine status report not moved on end.
6. according to the high available mechanism of virtual machine described in claim 1 to 4 any one, it is characterized in that:
Described high available virtual machine refers to that virtual machine itself can not be subject to the impact of its host fault, at host, occurs still can normally providing under abnormal conditions service;
Described host refers to that virtual machine moves the physical server of depositing;
Described realization end and management end refer to two the independently processes that operate on physical server; Realize the physical resources such as all CPU above end management of process physical server, internal memory, carry out and create virtual machine, create the processes such as cloud dish and VLAN; Management end process is responsible for the United Dispatching of cloud platform, with the process communication of all realization ends and manage the resource informations such as all virtual machines on it, cloud dish;
Described cloud dish refers to the memory device that is similar to USB flash disk or portable hard drive;
Described shared storage is a storage space that can make all realization ends use by configuration, can be used for the associated documents such as storage virtual machine mirror image, configuration; Described configuration can be used the diverse ways such as NFS, Ceph FS.
7. the high available mechanism of virtual machine according to claim 5, is characterized in that:
Described high available virtual machine refers to that virtual machine itself can not be subject to the impact of its host fault, at host, occurs still can normally providing under abnormal conditions service;
Described host refers to that virtual machine moves the physical server of depositing;
Described realization end and management end refer to two the independently processes that operate on physical server; Realize the physical resources such as all CPU above end management of process physical server, internal memory, carry out and create virtual machine, create the processes such as cloud dish and VLAN; Management end process is responsible for the United Dispatching of cloud platform, with the process communication of all realization ends and manage the resource informations such as all virtual machines on it, cloud dish;
Described cloud dish refers to the memory device that is similar to USB flash disk or portable hard drive;
Described shared storage is a storage space that can make all realization ends use by configuration, can be used for the associated documents such as storage virtual machine mirror image, configuration; Described configuration can be used the diverse ways such as NFS, Ceph FS.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310719697.3A CN103729280A (en) | 2013-12-23 | 2013-12-23 | High availability mechanism for virtual machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310719697.3A CN103729280A (en) | 2013-12-23 | 2013-12-23 | High availability mechanism for virtual machine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103729280A true CN103729280A (en) | 2014-04-16 |
Family
ID=50453362
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310719697.3A Pending CN103729280A (en) | 2013-12-23 | 2013-12-23 | High availability mechanism for virtual machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103729280A (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104268061A (en) * | 2014-09-12 | 2015-01-07 | 国云科技股份有限公司 | Storage state monitoring mechanism for virtual machine |
| WO2015169199A1 (en) * | 2014-05-08 | 2015-11-12 | 中国银联股份有限公司 | Anomaly recovery method for virtual machine in distributed environment |
| CN105281949A (en) * | 2015-09-09 | 2016-01-27 | 浪潮(北京)电子信息产业有限公司 | Host fence method and fence device in mixed storage mode |
| CN105450754A (en) * | 2015-11-30 | 2016-03-30 | 国云科技股份有限公司 | Method of physical machine and virtual machine for mutually sharing cloud disk |
| CN105550013A (en) * | 2015-12-08 | 2016-05-04 | 国云科技股份有限公司 | Method for monitoring internal process of Windows virtual machine |
| CN105550015A (en) * | 2015-12-08 | 2016-05-04 | 国云科技股份有限公司 | Method for monitoring internal process of Linux virtual machine |
| CN105808381A (en) * | 2016-03-05 | 2016-07-27 | 成都云祺科技有限公司 | Instant recovery method of virtual machine |
| CN106034037A (en) * | 2015-03-13 | 2016-10-19 | 腾讯科技（深圳）有限公司 | Disaster recovery switching method and device based on virtual machine |
| CN106209887A (en) * | 2016-07-22 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of composite services high availability implementation method based on virtual machine and device |
| CN106959885A (en) * | 2017-03-31 | 2017-07-18 | 山东超越数控电子有限公司 | A kind of virtual machine High Availabitity realizes system and its implementation |
| CN107329805A (en) * | 2017-07-13 | 2017-11-07 | 郑州云海信息技术有限公司 | The implementation method and device of a kind of virtual platform high availability |
| CN107547273A (en) * | 2017-08-18 | 2018-01-05 | 国网山东省电力公司信息通信公司 | A kind of support method and system of power system virtual instance High Availabitity |
| CN107544839A (en) * | 2016-06-27 | 2018-01-05 | 腾讯科技（深圳）有限公司 | Virtual machine (vm) migration system, method and device |
| CN107608766A (en) * | 2017-10-20 | 2018-01-19 | 北京易思捷信息技术有限公司 | One kind virtualizes cross-platform HA systems |
| CN107870801A (en) * | 2016-09-26 | 2018-04-03 | 中国电信股份有限公司 | The automatic activating method of virtual machine High Availabitity function, device and system |
| CN111090491A (en) * | 2019-07-03 | 2020-05-01 | 杭州海康威视系统技术有限公司 | Method and device for recovering task state of virtual machine and electronic equipment |
| CN112003902A (en) * | 2020-07-29 | 2020-11-27 | 苏州浪潮智能科技有限公司 | Cloud host service rapid recovery method and device based on cloud platform |
| CN112752353A (en) * | 2019-10-31 | 2021-05-04 | 中移物联网有限公司 | Connection method and terminal equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102394791A (en) * | 2011-10-26 | 2012-03-28 | 浪潮(北京)电子信息产业有限公司 | Downtime recovery method and system |
| CN102480396A (en) * | 2010-11-30 | 2012-05-30 | 英业达股份有限公司 | Server system and connection method thereof |
| CN102662751A (en) * | 2012-03-30 | 2012-09-12 | 浪潮电子信息产业股份有限公司 | Method for improving availability of virtual machine system based on thermomigration |
| CN102819465A (en) * | 2012-06-29 | 2012-12-12 | 华中科技大学 | Failure recovery method in virtualization environment |
| CN103152419A (en) * | 2013-03-08 | 2013-06-12 | 中标软件有限公司 | High availability cluster management method for cloud computing platform |
| CN103440160A (en) * | 2013-08-15 | 2013-12-11 | 华为技术有限公司 | Virtual machine recovering method and virtual machine migration method , device and system |
-
2013
- 2013-12-23 CN CN201310719697.3A patent/CN103729280A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102480396A (en) * | 2010-11-30 | 2012-05-30 | 英业达股份有限公司 | Server system and connection method thereof |
| CN102394791A (en) * | 2011-10-26 | 2012-03-28 | 浪潮(北京)电子信息产业有限公司 | Downtime recovery method and system |
| CN102662751A (en) * | 2012-03-30 | 2012-09-12 | 浪潮电子信息产业股份有限公司 | Method for improving availability of virtual machine system based on thermomigration |
| CN102819465A (en) * | 2012-06-29 | 2012-12-12 | 华中科技大学 | Failure recovery method in virtualization environment |
| CN103152419A (en) * | 2013-03-08 | 2013-06-12 | 中标软件有限公司 | High availability cluster management method for cloud computing platform |
| CN103440160A (en) * | 2013-08-15 | 2013-12-11 | 华为技术有限公司 | Virtual machine recovering method and virtual machine migration method , device and system |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015169199A1 (en) * | 2014-05-08 | 2015-11-12 | 中国银联股份有限公司 | Anomaly recovery method for virtual machine in distributed environment |
| US10095576B2 (en) | 2014-05-08 | 2018-10-09 | China Unionpay Co., Ltd. | Anomaly recovery method for virtual machine in distributed environment |
| CN104268061A (en) * | 2014-09-12 | 2015-01-07 | 国云科技股份有限公司 | Storage state monitoring mechanism for virtual machine |
| CN104268061B (en) * | 2014-09-12 | 2017-03-15 | 国云科技股份有限公司 | A kind of storage state monitoring method suitable for virtual machine |
| CN106034037A (en) * | 2015-03-13 | 2016-10-19 | 腾讯科技（深圳）有限公司 | Disaster recovery switching method and device based on virtual machine |
| CN106034037B (en) * | 2015-03-13 | 2019-04-16 | 腾讯科技（深圳）有限公司 | A kind of disaster tolerance switching method and device based on virtual machine |
| CN105281949B (en) * | 2015-09-09 | 2018-06-15 | 浪潮(北京)电子信息产业有限公司 | Mix the partition method and isolating device of host in memory module |
| CN105281949A (en) * | 2015-09-09 | 2016-01-27 | 浪潮(北京)电子信息产业有限公司 | Host fence method and fence device in mixed storage mode |
| CN105450754A (en) * | 2015-11-30 | 2016-03-30 | 国云科技股份有限公司 | Method of physical machine and virtual machine for mutually sharing cloud disk |
| CN105450754B (en) * | 2015-11-30 | 2019-04-26 | 国云科技股份有限公司 | A kind of method of physical machine and the mutually shared cloud disk of virtual machine |
| CN105550013A (en) * | 2015-12-08 | 2016-05-04 | 国云科技股份有限公司 | Method for monitoring internal process of Windows virtual machine |
| CN105550015A (en) * | 2015-12-08 | 2016-05-04 | 国云科技股份有限公司 | Method for monitoring internal process of Linux virtual machine |
| CN105808381B (en) * | 2016-03-05 | 2018-11-02 | 成都云祺科技有限公司 | A kind of virtual machine instantaneous recovery method |
| CN105808381A (en) * | 2016-03-05 | 2016-07-27 | 成都云祺科技有限公司 | Instant recovery method of virtual machine |
| CN107544839A (en) * | 2016-06-27 | 2018-01-05 | 腾讯科技（深圳）有限公司 | Virtual machine (vm) migration system, method and device |
| CN106209887A (en) * | 2016-07-22 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of composite services high availability implementation method based on virtual machine and device |
| CN107870801A (en) * | 2016-09-26 | 2018-04-03 | 中国电信股份有限公司 | The automatic activating method of virtual machine High Availabitity function, device and system |
| CN107870801B (en) * | 2016-09-26 | 2020-05-26 | 中国电信股份有限公司 | Method, device and system for automatically opening high-availability function of virtual machine |
| CN106959885A (en) * | 2017-03-31 | 2017-07-18 | 山东超越数控电子有限公司 | A kind of virtual machine High Availabitity realizes system and its implementation |
| CN107329805A (en) * | 2017-07-13 | 2017-11-07 | 郑州云海信息技术有限公司 | The implementation method and device of a kind of virtual platform high availability |
| CN107547273A (en) * | 2017-08-18 | 2018-01-05 | 国网山东省电力公司信息通信公司 | A kind of support method and system of power system virtual instance High Availabitity |
| CN107547273B (en) * | 2017-08-18 | 2020-06-23 | 国网山东省电力公司信息通信公司 | Method and system for guaranteeing high availability of virtual instance of power system |
| CN107608766A (en) * | 2017-10-20 | 2018-01-19 | 北京易思捷信息技术有限公司 | One kind virtualizes cross-platform HA systems |
| CN111090491A (en) * | 2019-07-03 | 2020-05-01 | 杭州海康威视系统技术有限公司 | Method and device for recovering task state of virtual machine and electronic equipment |
| CN111090491B (en) * | 2019-07-03 | 2023-10-10 | 杭州海康威视系统技术有限公司 | Virtual machine task state recovery method and device and electronic equipment |
| CN112752353A (en) * | 2019-10-31 | 2021-05-04 | 中移物联网有限公司 | Connection method and terminal equipment |
| CN112752353B (en) * | 2019-10-31 | 2022-06-10 | 中移物联网有限公司 | Connection method and terminal equipment |
| CN112003902A (en) * | 2020-07-29 | 2020-11-27 | 苏州浪潮智能科技有限公司 | Cloud host service rapid recovery method and device based on cloud platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103729280A (en) | High availability mechanism for virtual machine | |
| USRE47852E1 (en) | Snapshot and replication of a multi-stream application on multiple hosts at near-sync frequency | |
| CN106713487B (en) | Data synchronization method and device | |
| CN106528327B (en) | A kind of data processing method and backup server | |
| US10565071B2 (en) | Smart data replication recoverer | |
| CN104170323B (en) | Fault handling method and device, system based on network function virtualization | |
| CN102880475B (en) | Based on the real-time event disposal system of cloud computing and method in computer software | |
| CN104243205B (en) | Message processing method and equipment when a kind of virtual switch failure | |
| CN104036043B (en) | High availability method of MYSQL and managing node | |
| CN107733726A (en) | A kind of processing method and processing device of service request | |
| CN104506357B (en) | A kind of high-availability cluster node administration method | |
| CN102857371B (en) | A kind of dynamic allocation management method towards group system | |
| CN102629224A (en) | Method and device of integrated data disaster recovery based on cloud platform | |
| CN107547273B (en) | Method and system for guaranteeing high availability of virtual instance of power system | |
| CN111949444A (en) | Data backup and recovery system and method based on distributed service cluster | |
| CN109828867A (en) | A kind of cloud host disaster recovery method and system across data center | |
| US20050283636A1 (en) | System and method for failure recovery in a cluster network | |
| CN103473328A (en) | MYSQL (my structured query language)-based database cloud and construction method for same | |
| WO2015154525A1 (en) | Method and device for protecting hqos using multiple board cards | |
| CN107357800A (en) | A kind of database High Availabitity zero loses solution method | |
| CN103902401B (en) | Virtual machine fault-tolerance approach and device based on monitoring | |
| CN111193643A (en) | Cloud server state monitoring system and method | |
| CN104391762A (en) | Backup method for realizing multi-machine multi-application with one machine | |
| CN103810038A (en) | Method and device for transferring virtual machine storage files in HA cluster | |
| CN107291589A (en) | Method for improving system reliability in robot operating system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140416 |
|
| RJ01 | Rejection of invention patent application after publication |