CN110399202B - Efficient virtual machine disaster recovery method and device - Google Patents
Efficient virtual machine disaster recovery method and device Download PDFInfo
- Publication number
- CN110399202B CN110399202B CN201910582495.6A CN201910582495A CN110399202B CN 110399202 B CN110399202 B CN 110399202B CN 201910582495 A CN201910582495 A CN 201910582495A CN 110399202 B CN110399202 B CN 110399202B
- Authority
- CN
- China
- Prior art keywords
- disaster recovery
- remote
- volume
- site
- production
- 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
- 238000011084 recovery Methods 0.000 title claims abstract description 244
- 238000000034 method Methods 0.000 title claims abstract description 20
- 238000004519 manufacturing process Methods 0.000 claims abstract description 136
- 238000003860 storage Methods 0.000 claims abstract description 101
- 238000013507 mapping Methods 0.000 claims description 10
- 230000001360 synchronised effect Effects 0.000 abstract description 10
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a device for high-efficiency disaster tolerance of a virtual machine, which comprise the following steps: respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage; synchronizing virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship; operating the vCenter automatically completes the recovery of the virtual machine. By utilizing the storage remote copy feature and the associated API provided by the VMware platform. The virtual machine data can be automatically synchronized in the two places and the three centers, and when a production site fails or has a disaster, a user can conveniently and quickly start the virtual machine backed up by the local disaster recovery site or the remote disaster recovery site through the management system, so that the service is quickly recovered. Manual intervention is reduced, and recovery efficiency is greatly improved.
Description
Technical Field
The invention relates to the technical field of virtualization, in particular to a method and a device for efficient disaster recovery of a virtual machine.
Background
With the advent of the big data age, business data of enterprises grow exponentially, and businesses of the enterprises are more and more complex. Thus, enterprises require more and more servers to deploy core services. Currently, virtualization technology is continuously developed, and enterprises aim to save cost and simplify management. More and more services are deployed in virtual machines. It is particularly important how to guarantee the continuity of the traffic and the security of the data in the virtual machine. If a disaster (including power interruption, hardware failure, natural disaster and the like) occurs in the production site data center to cause service interruption, how to quickly recover the service can be realized, the loss of an enterprise is reduced, and the method is worthy of research.
The conventional disaster preparation methods comprise: one conventional disaster recovery solution, which is to implement service availability at the application level with application specific solutions (e.g., oracle RAC, MS SQL, etc.). Although this approach may provide good usability, the disadvantages are also clear since each set of applications has its own solution: the method is complex and expensive, needs professional management technicians to maintain, has high labor cost, complex scheme and large error risk, and needs a special backup framework; secondly, a VMware virtualization platform: aiming at the VMware virtualization platform, the platform provides a software-defined disaster Recovery solution SRM (VMware Site Recovery manager), and the solution makes full use of the advantages of a virtualization environment and provides simplicity and cost benefits of a basic architecture layer solution. The backup architecture is simplified. With SRM, an enterprise may manage failover from a production site to a disaster recovery site. And rapidly recovering the service. However, the SRM solution also has its drawbacks: SRM can only provide a disaster recovery solution for two locations, and in an SRM system, only a production site and a disaster recovery site can be added, and if the production site and the disaster recovery site fail at the same time, the service cannot be recovered quickly.
Disclosure of Invention
Aiming at the problems of the traditional disaster recovery solution and the VMware virtualization platform disaster recovery solution, the invention provides a high-efficiency virtual machine disaster recovery method and device.
The technical scheme of the invention is as follows:
on one hand, the technical scheme of the invention provides an efficient virtual machine disaster recovery method, which comprises the following steps:
respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage;
synchronizing virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship;
operating the vCenter automatically completes the recovery of the virtual machine.
Further, the establishing of the remote copy relationship between the production volume and the local disaster recovery volume and the remote disaster recovery volume in the storage respectively includes:
and adding storage, namely adding the production site storage, the local disaster recovery site storage and the remote disaster recovery site storage into the system.
Further, the step of adding the production site storage, the local disaster recovery site storage and the remote disaster recovery site storage to the system by adding the storage comprises the following steps:
a vCenter platform is built at a production site, a vCenter platform is built at a local disaster recovery site, and the vCenter platform is built at a remote disaster recovery site;
and logging in the virtual machine backup and recovery system to add the vCenter, and adding the vCenter of the production site, the local disaster recovery site and the remote disaster recovery site to the system.
Further, the step of establishing the remote copy relationship between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in the storage respectively includes:
the production storage and the local disaster recovery storage establish a partnership, and the production storage and the remote disaster recovery storage establish a partnership;
and establishing a remote copying relationship between the production volume and the local disaster recovery volume, and establishing a remote copying relationship between the production volume and the remote disaster recovery volume.
Further, the synchronizing the virtual machine data in the production volume to the local and remote disaster recovery sites using the stored remote copy relationship includes:
data synchronization among the production volume, the local disaster recovery volume and the remote disaster recovery volume when a synchronization task is established;
setting a synchronization strategy in a virtual machine backup and recovery system to automatically trigger a synchronization task at regular time;
and synchronizing the virtual machine data in the production volume to the local and remote disaster recovery sites.
Further, before the step of operating the vCenter to automatically complete the recovery of the virtual machine, the method includes;
configuring a virtual machine strategy, and specifying Esxi hosts used by a production site, a local disaster recovery site and a remote disaster recovery site;
the production volume is mapped to the production site's Esxi host, which is added to the production site's vCenter, and a virtual machine is created by the vCenter.
Further, the step of operating the vCenter to automatically complete the recovery of the virtual machine includes:
when the production site has a fault and the virtual machine needs to be started at the local disaster recovery site or the remote disaster recovery site, the local disaster recovery volume or the remote disaster recovery volume is selected to be started, and the vCenter is operated to automatically complete the recovery of the virtual machine.
Further, the step of starting the remote disaster recovery volume and operating the vCenter to automatically complete the recovery of the virtual machine specifically includes:
step 501: closing all virtual machines in the production volume;
step 502: operating the production storage, and unmapping the production volume from the production storage;
step 503: operating remote storage, and mounting the remote disaster recovery volume to the remote storage;
step 504: operating vCenter of the remote disaster recovery site, and scanning equipment to scan a new vmfs volume;
step 505: operating vCenter of the remote disaster recovery site, and mounting a newly discovered vmfs volume;
step 506: operating a vCenter of the remote disaster recovery site, and registering all virtual machines in the remote disaster recovery volume;
step 507: and operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume, and recovering the service. The method utilizes the storage remote copy feature and the related API provided by the VMware platform. The virtual machine data can be automatically synchronized in the two places and the three centers, and when a production site fails or has a disaster, a user can conveniently and quickly start the virtual machine backed up by the local disaster recovery site or the remote disaster recovery site through the management system, so that the service is quickly recovered.
On the other hand, the technical solution of the present invention provides an efficient virtual machine disaster recovery device, which includes a remote copy relationship establishing module, a synchronization module, and an operation module:
the remote copying relation establishing module is used for respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage; the production storage and the local disaster recovery storage establish a partnership, and the production storage and the remote disaster recovery storage establish a partnership; establishing a remote copying relationship between the production volume and the local disaster recovery volume, and establishing a remote copying relationship between the production volume and the remote disaster recovery volume;
the synchronization module synchronizes the virtual machine data in the production volume to local and allopatric disaster recovery sites by utilizing the stored remote copy relationship; and creating a synchronous task, and respectively designating production storage, a production volume, local disaster recovery storage, a local disaster recovery volume, remote disaster recovery storage and remote disaster recovery volume. Specify the task name for the task, and the synchronization period (how often the data is synchronized);
and the operation module is used for operating the vCenter to automatically complete the recovery of the virtual machine.
Furthermore, the operation module comprises a mapping removing unit, a mounting unit, a scanning unit, a registering unit and a starting recovery unit;
the de-mapping unit is used for operating the production storage and de-mapping the production volume from the production storage;
the mounting unit is used for operating the remote storage and mounting the remote disaster recovery volume to the remote storage;
the scanning unit is used for operating vCenter and scanning equipment of the remote disaster recovery site and scanning a new vmfs volume;
the mounting unit is also used for operating a vCenter of the remote disaster recovery site and mounting a newly discovered vmfs volume;
the registration unit is used for operating the vCenter of the remote disaster recovery site and registering all the virtual machines in the remote disaster recovery volume;
and the starting recovery unit is used for operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume and recovering the service. And synchronizing the virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship, and operating the vCenter to automatically complete the recovery of the virtual machine by utilizing an API (application program interface) provided by VMware. Manual intervention is reduced, and recovery efficiency is greatly improved.
According to the technical scheme, the invention has the following advantages: by utilizing the storage remote copy feature and the associated API provided by the VMware platform. The virtual machine data can be automatically synchronized in the two places and the three centers, and when a production site fails or has a disaster, a user can conveniently and quickly start the virtual machine backed up by the local disaster recovery site or the remote disaster recovery site through the management system, so that the service is quickly recovered. Manual intervention is reduced, and recovery efficiency is greatly improved.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Therefore, compared with the prior art, the invention has prominent substantive features and remarkable progress, and the beneficial effects of the implementation are also obvious.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for efficient disaster recovery of a virtual machine according to an embodiment of the present invention.
Fig. 2 is a schematic flow chart of a recovery method for operating a vCenter auto-completion virtual machine according to an embodiment of the present invention.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and not all 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.
Example one
As shown in fig. 1-2, the technical solution of the present invention provides an efficient method for disaster recovery of a virtual machine, where a partnering relationship is established between production storage and local disaster recovery storage, a partnering relationship is established between production storage and remote disaster recovery storage, a remote copy relationship is established between production volumes and local disaster recovery volumes, a remote copy relationship is established between production volumes and remote disaster recovery volumes, a vCenter platform is established at a production site, a vCenter platform is established at a local disaster recovery site, a vCenter platform is established at a remote disaster recovery site, a production volume is mapped to an esi host of the production site, the esi host is added to the vCenter of the production site, and a virtual machine is established through the vCenter to deploy services.
S1: logging in a virtual machine backup and recovery system, and adding a vCenter; adding vCenter of a production site, a local disaster recovery site and a remote disaster recovery site to the system;
s2: adding storage; adding production site storage, local disaster recovery site storage and remote disaster recovery site storage into the system; in this embodiment, remote copy relationships between production volumes and local disaster recovery volumes and between production volumes and remote disaster recovery volumes are respectively established in storage;
s3: and creating a synchronous task, and respectively designating production storage, a production volume, local disaster recovery storage, a local disaster recovery volume, remote disaster recovery storage and remote disaster recovery volume. Specify the task name for the task, and the synchronization period (how often the data is synchronized); synchronizing virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship; data synchronization among the production volume, the local disaster recovery volume and the remote disaster recovery volume when a synchronization task is established; setting a synchronization strategy in a virtual machine backup and recovery system to automatically trigger a synchronization task at regular time; synchronizing virtual machine data in the production volume to local and remote disaster recovery sites;
s4: configuring a virtual machine strategy, and respectively designating Esxi hosts used by a production site, a local disaster recovery site and a remote disaster recovery site; mapping the production volume to an Esxi host of the production site, adding the Esxi host to a vCenter of the production site, and creating a virtual machine through the vCenter;
s5, operating vCenter to automatically complete the recovery of the virtual machine; when a production site fails and a virtual machine needs to be started at a local disaster recovery site or a remote disaster recovery site, a user selects "start a local disaster recovery volume" or "start a remote disaster recovery volume" through a login system, in this embodiment, taking start of a remote disaster recovery volume as an example, the specific steps are as follows:
step 501: closing all virtual machines in the production volume;
step 502: operating the production storage, and unmapping the production volume from the production storage;
step 503: operating remote storage, and mounting the remote disaster recovery volume to the remote storage;
step 504: operating vCenter of the remote disaster recovery site, and scanning equipment to scan a new vmfs volume;
step 505: operating vCenter of the remote disaster recovery site, and mounting a newly discovered vmfs volume;
step 506: operating a vCenter of the remote disaster recovery site, and registering all virtual machines in the remote disaster recovery volume;
step 507: and operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume, and recovering the service.
The method utilizes the storage remote copy feature and the related API provided by the VMware platform. The virtual machine data can be automatically synchronized in the two places and the three centers, and when a production site fails or has a disaster, a user can conveniently and quickly start the virtual machine backed up by the local disaster recovery site or the remote disaster recovery site through the management system, so that the service is quickly recovered.
Example two
The technical scheme of the invention provides an efficient virtual machine disaster recovery device, wherein a production storage and a local disaster recovery storage establish a partnership, a production storage and a remote disaster recovery storage establish a partnership, a production volume and a local disaster recovery volume establish a remote copy relationship, a production volume and a remote disaster recovery volume establish a remote copy relationship, a production site establishes a vCenter platform, a local disaster recovery site establishes a vCenter platform, a remote disaster recovery site establishes a vCenter platform, a production volume is mapped to an Esxi host of the production site, the Esxi host is added to the vCenter of the production site, a virtual machine is established through the vCenter, and a service is deployed. The device comprises a remote copy relationship establishing module, a synchronization module and an operation module:
the remote copying relation establishing module is used for respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage; the production storage and the local disaster recovery storage establish a partnership, and the production storage and the remote disaster recovery storage establish a partnership; establishing a remote copying relationship between the production volume and the local disaster recovery volume, and establishing a remote copying relationship between the production volume and the remote disaster recovery volume;
the synchronization module synchronizes the virtual machine data in the production volume to local and allopatric disaster recovery sites by utilizing the stored remote copy relationship; and creating a synchronous task, and respectively designating production storage, a production volume, local disaster recovery storage, a local disaster recovery volume, remote disaster recovery storage and remote disaster recovery volume. Specify the task name for the task, and the synchronization period (how often the data is synchronized);
and the operation module is used for operating the vCenter to automatically complete the recovery of the virtual machine.
The operation module comprises a de-mapping unit, a mounting unit, a scanning unit, a registration unit and a starting recovery unit;
the de-mapping unit is used for operating the production storage and de-mapping the production volume from the production storage;
the mounting unit is used for operating the remote storage and mounting the remote disaster recovery volume to the remote storage;
the scanning unit is used for operating vCenter and scanning equipment of the remote disaster recovery site and scanning a new vmfs volume;
the mounting unit is also used for operating a vCenter of the remote disaster recovery site and mounting a newly discovered vmfs volume;
the registration unit is used for operating the vCenter of the remote disaster recovery site and registering all the virtual machines in the remote disaster recovery volume;
and the starting recovery unit is used for operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume and recovering the service. And synchronizing the virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship, and operating the vCenter to automatically complete the recovery of the virtual machine by utilizing an API (application program interface) provided by VMware. Manual intervention is reduced, and recovery efficiency is greatly improved.
Although the present invention has been described in detail by referring to the drawings in connection with the preferred embodiments, the present invention is not limited thereto. Various equivalent modifications or substitutions can be made on the embodiments of the present invention by those skilled in the art without departing from the spirit and scope of the present invention, and these modifications or substitutions are within the scope of the present invention/any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (5)
1. An efficient virtual machine disaster recovery method is characterized by comprising the following steps:
respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage;
synchronizing virtual machine data in the production volume to local and remote disaster recovery sites by utilizing the stored remote copy relationship;
operating the vCenter to automatically complete the recovery of the virtual machine;
the remote copy relationship between the production volume and the local disaster recovery volume and the remote disaster recovery volume is respectively established in the storage, and the method comprises the following steps:
adding storage, namely adding production site storage, local disaster recovery site storage and remote disaster recovery site storage into the system;
the step of adding the production site storage, the local disaster recovery site storage and the remote disaster recovery site storage into the system by adding the storage comprises the following steps:
a vCenter platform is built at a production site, a vCenter platform is built at a local disaster recovery site, and the vCenter platform is built at a remote disaster recovery site;
logging in a virtual machine backup and recovery system to add a vCenter, and adding the vCenter of a production site, a local disaster recovery site and a remote disaster recovery site to the system;
the step of operating vCenter to automatically complete the recovery of the virtual machine comprises the following steps:
when a production site fails and a virtual machine needs to be started at a local disaster recovery site or a remote disaster recovery site, selecting to start a local disaster recovery volume or a remote disaster recovery volume, and operating a vCenter to automatically complete the recovery of the virtual machine;
the method comprises the following steps of starting a remote disaster recovery volume, and operating a vCenter to automatically complete the recovery of a virtual machine:
step 501: closing all virtual machines in the production volume;
step 502: operating the production storage, and unmapping the production volume from the production storage;
step 503: operating remote storage, and mounting the remote disaster recovery volume to the remote storage;
step 504: operating vCenter of the remote disaster recovery site, and scanning equipment to scan a new vmfs volume;
step 505: operating vCenter of the remote disaster recovery site, and mounting a newly discovered vmfs volume;
step 506: operating a vCenter of the remote disaster recovery site, and registering all virtual machines in the remote disaster recovery volume;
step 507: and operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume, and recovering the service.
2. The method according to claim 1, wherein the step of establishing the remote copy relationship between the production volume and the local disaster recovery volume, and between the production volume and the remote disaster recovery volume in the storage respectively comprises:
the production storage and the local disaster recovery storage establish a partnership, and the production storage and the remote disaster recovery storage establish a partnership;
and establishing a remote copying relationship between the production volume and the local disaster recovery volume, and establishing a remote copying relationship between the production volume and the remote disaster recovery volume.
3. The method of claim 2, wherein the synchronizing virtual machine data in the production volume to the local and remote disaster recovery sites using the stored remote copy relationship comprises:
data synchronization among the production volume, the local disaster recovery volume and the remote disaster recovery volume when a synchronization task is established;
setting a synchronization strategy in a virtual machine backup and recovery system to automatically trigger a synchronization task at regular time;
and synchronizing the virtual machine data in the production volume to the local and remote disaster recovery sites.
4. The method according to claim 3, wherein said step of operating the vCenter to automatically complete the recovery of the virtual machine is preceded by the steps of;
configuring a virtual machine strategy, and specifying Esxi hosts used by a production site, a local disaster recovery site and a remote disaster recovery site;
the production volume is mapped to the production site's Esxi host, which is added to the production site's vCenter, and a virtual machine is created by the vCenter.
5. An efficient virtual machine disaster recovery device is characterized by comprising a remote copy relationship establishing module, a synchronization module and an operation module:
the remote copying relation establishing module is used for respectively establishing remote copying relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage;
establishing remote copy relations between the production volume and the local disaster recovery volume and between the production volume and the remote disaster recovery volume in storage respectively, wherein the remote copy relations comprise the following steps: adding storage, namely adding production site storage, local disaster recovery site storage and remote disaster recovery site storage into the system;
the step of adding the production site storage, the local disaster recovery site storage and the remote disaster recovery site storage into the system by adding the storage comprises the following steps: a vCenter platform is built at a production site, a vCenter platform is built at a local disaster recovery site, and the vCenter platform is built at a remote disaster recovery site; logging in a virtual machine backup and recovery system to add a vCenter, and adding the vCenter of a production site, a local disaster recovery site and a remote disaster recovery site to the system;
the synchronization module synchronizes the virtual machine data in the production volume to local and allopatric disaster recovery sites by utilizing the stored remote copy relationship;
the operation module is used for operating the vCenter to automatically complete the recovery of the virtual machine;
the step of operating vCenter to automatically complete the recovery of the virtual machine comprises the following steps:
when a production site fails and a virtual machine needs to be started at a local disaster recovery site or a remote disaster recovery site, selecting to start a local disaster recovery volume or a remote disaster recovery volume, and operating a vCenter to automatically complete the recovery of the virtual machine;
the operation module comprises a de-mapping unit, a mounting unit, a scanning unit, a registration unit and a starting recovery unit;
the de-mapping unit is used for operating the production storage and de-mapping the production volume from the production storage;
the mounting unit is used for operating the remote storage and mounting the remote disaster recovery volume to the remote storage;
the scanning unit is used for operating vCenter and scanning equipment of the remote disaster recovery site and scanning a new vmfs volume;
the mounting unit is also used for operating a vCenter of the remote disaster recovery site and mounting a newly discovered vmfs volume;
the registration unit is used for operating the vCenter of the remote disaster recovery site and registering all the virtual machines in the remote disaster recovery volume;
and the starting recovery unit is used for operating the vCenter of the remote disaster recovery site, starting all the virtual machines in the remote disaster recovery volume and recovering the service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910582495.6A CN110399202B (en) | 2019-06-29 | 2019-06-29 | Efficient virtual machine disaster recovery method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910582495.6A CN110399202B (en) | 2019-06-29 | 2019-06-29 | Efficient virtual machine disaster recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110399202A CN110399202A (en) | 2019-11-01 |
| CN110399202B true CN110399202B (en) | 2022-03-04 |
Family
ID=68323612
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910582495.6A Active CN110399202B (en) | 2019-06-29 | 2019-06-29 | Efficient virtual machine disaster recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110399202B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111858170B (en) * | 2020-07-10 | 2023-07-25 | 苏州浪潮智能科技有限公司 | Configuration management method, system and readable storage medium |
| CN112306762A (en) * | 2020-10-30 | 2021-02-02 | 西安万像电子科技有限公司 | Communication processing method, device and system, and non-volatile storage medium |
| CN115242616A (en) * | 2022-07-22 | 2022-10-25 | 济南浪潮数据技术有限公司 | Remote disaster recovery method, device, equipment and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902407A (en) * | 2012-12-31 | 2014-07-02 | 华为技术有限公司 | Virtual machine recovery method and server |
| CN104407938A (en) * | 2014-11-21 | 2015-03-11 | 上海爱数软件有限公司 | Recovery method for various granularities after mirror-image-level backup of virtual machine |
| CN107391294A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method for building up and device of IPSAN disaster tolerance systems |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8510590B2 (en) * | 2010-03-17 | 2013-08-13 | Vmware, Inc. | Method and system for cluster resource management in a virtualized computing environment |
| US9183097B2 (en) * | 2013-06-05 | 2015-11-10 | Sungard Availability Services, Lp | Virtual infrastructure recovery configurator |
-
2019
- 2019-06-29 CN CN201910582495.6A patent/CN110399202B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902407A (en) * | 2012-12-31 | 2014-07-02 | 华为技术有限公司 | Virtual machine recovery method and server |
| CN104407938A (en) * | 2014-11-21 | 2015-03-11 | 上海爱数软件有限公司 | Recovery method for various granularities after mirror-image-level backup of virtual machine |
| CN107391294A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method for building up and device of IPSAN disaster tolerance systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110399202A (en) | 2019-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110399202B (en) | Efficient virtual machine disaster recovery method and device | |
| CN107526626B (en) | Docker container thermal migration method and system based on CRIU | |
| EP3493471B1 (en) | Data disaster recovery method, apparatus and system | |
| CN103744809B (en) | Vehicle information management system double hot standby method based on VRRP | |
| CN106850260A (en) | A kind of dispositions method and device of virtual resources management platform | |
| US9262212B2 (en) | Systems and methods for migrating virtual machines | |
| CN102214128B (en) | Repurposable recovery environment | |
| CN106776121B (en) | Data disaster recovery device, system and method | |
| WO2012071920A1 (en) | Method, system, token conreoller and memory database for implementing distribute-type main memory database system | |
| CN108920489A (en) | Dispositions method, device and the equipment of database | |
| CN109976952A (en) | The method and apparatus of cross-domain backup in cloud computing system | |
| CN111966467B (en) | Method and device for disaster recovery based on kubernetes container platform | |
| WO2013113220A1 (en) | Method and device for backup and recovery of network management configuration data | |
| CN111078352A (en) | Dual-computer hot standby deployment method and system based on KVM virtualization system | |
| CN105933379A (en) | Business processing method, device and system | |
| CN102045187A (en) | Method and equipment for realizing HA (high-availability) system with checkpoints | |
| CN112367186B (en) | Fault protection method and device based on 0penStack bare computer | |
| CN105591801B (en) | A kind of virtual network function VNF fault handling method and VNF management equipment | |
| CN108984346B (en) | Method, system and storage medium for producing data disaster tolerance | |
| CN116719546A (en) | Remote server code updating system and method | |
| CN111125060A (en) | Database management method, system, device and storage medium | |
| CN110688259B (en) | Private cloud backup recovery system and backup recovery method thereof | |
| CN114584459A (en) | Method for realizing high availability of main and standby container cloud platforms | |
| CN108429813B (en) | Disaster recovery method, system and terminal for cloud storage service | |
| CN110764954A (en) | Cloud site disaster tolerance method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |