CN111309433A - Virtualization system and virtual machine data copying method - Google Patents
Virtualization system and virtual machine data copying method Download PDFInfo
- Publication number
- CN111309433A CN111309433A CN201811518182.6A CN201811518182A CN111309433A CN 111309433 A CN111309433 A CN 111309433A CN 201811518182 A CN201811518182 A CN 201811518182A CN 111309433 A CN111309433 A CN 111309433A
- Authority
- CN
- China
- Prior art keywords
- data stream
- virtualization system
- data
- copied
- integrated
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000011084 recovery Methods 0.000 claims abstract description 63
- 230000010076 replication Effects 0.000 claims abstract description 52
- 238000004519 manufacturing process Methods 0.000 claims description 34
- 230000010354 integration Effects 0.000 claims description 20
- 238000012423 maintenance Methods 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000003786 synthesis reaction Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer 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/45579—I/O management, e.g. providing access to device drivers or storage
-
- 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/45595—Network integration; Enabling network access in 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 discloses a virtualization system and a virtual machine data replication method, wherein the virtualization system comprises: the system comprises a virtualization management layer, a background engine and an IO transceiver, wherein the IO funnel, the background engine and the IO transceiver are deployed on the virtualization management layer; the IO funnel is used for capturing IO data streams of the virtual machine and acquiring a plurality of IO data streams to be copied from the captured IO data streams; the background engine is used for integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied; and the IO transceiver is used for sending the IO data stream integrated by the background engine to another virtualization system. According to the embodiment of the invention, disaster recovery and replication of data among different brands of storage can be realized, and the replication relationship is not required to be deployed, so that the maintenance workload is reduced.
Description
Technical Field
The invention belongs to the field of computers, and particularly relates to a virtualization system and a virtual machine data copying method.
Background
For disaster recovery replication of a virtual machine, including replication disaster recovery of configuration information in an internal operating system of the virtual machine and an installed program and a database, the disaster recovery replication is generally divided into two modes:
1. disaster recovery based replication: the replication is performed based on replication software at the bottom of the storage, and the storage of the same brand is needed. And if the storage of the virtual machine at the production end is damaged, the data stored at the disaster recovery end can be used for recovery.
2. Data replication based on operating system level: and installing data copying software in the virtual machine, and realizing disaster recovery copying of the data by configuring the copying relation of the virtual machines of the production end and the disaster recovery end. And if the data of the production end is damaged, the data of the disaster recovery end can be adopted for recovery.
However, the existing virtual machine data replication has the following disadvantages:
1. disaster recovery based replication: the data disaster recovery method needs storage of the same brand, which is high-end storage, needs additional storage authorization to be realized, and simultaneously needs high-end centralized storage of the same brand at both a production end and a disaster recovery end, so that data disaster recovery copying cannot be realized by spanning storage of different brands. And storage-based replication must rely on fiber optic networks. And long-distance data disaster recovery and replication cannot be carried out.
2. Data replication based on operating system level: compared with disaster recovery replication based on storage, the method can realize the disaster recovery replication of data among different brands of storage, does not depend on an optical fiber network, and can realize long-distance disaster recovery replication of the data through the network. However, in this way, replication software must be installed on each virtual machine, replication relationships are configured, and a large number of replication relationships need to be deployed in the face of a large-scale virtualization environment, which results in a large maintenance workload and a complex scale maintenance.
Disclosure of Invention
The embodiment of the invention provides a virtualization system and a virtual machine data replication method, which can realize disaster recovery replication of data among different brands of storage, do not need to deploy replication relationship, and reduce maintenance workload.
In one aspect, an embodiment of the present invention provides a virtualization system, including a virtualization management layer, where an IO funnel, a background engine, and an IO transceiver are deployed on the virtualization management layer;
the IO funnel is used for capturing IO data streams of the virtual machine and acquiring a plurality of IO data streams to be copied from the captured IO data streams;
the background engine is used for integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied;
and the IO transceiver is used for sending the IO data stream integrated by the background engine to another virtualization system.
In another aspect, an embodiment of the present invention provides a virtual machine data replication method, used in a first virtualization system, where the method includes:
capturing an IO data stream of a virtual machine through an input/output (IO) funnel, wherein the IO funnel is deployed in a virtualization management layer of the first virtualization system;
acquiring a plurality of IO data streams to be copied from the captured IO data streams;
integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied;
and sending the integrated IO data stream to a second virtualization system.
According to the virtualization system and the virtual machine data copying method provided by the embodiment of the invention, the IO data stream to be copied is captured through the IO funnel deployed on the virtualization management layer so as to copy the IO data stream. Because disaster recovery replication is on a virtualization management layer, dependence on bottom storage is eliminated, data disaster recovery replication between different brands of storage is realized, and meanwhile, the method is independent of an optical fiber network and can realize long-distance data disaster recovery replication through the network. In addition, the IO data stream of the virtual machine is captured in an agent-free mode, any agent does not need to be installed in the virtual machine, shutdown is not needed, and the production system is not affected. And moreover, the copy relationship does not need to be configured in a large-scale virtualization environment, so that the maintenance workload is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 illustrates a framework diagram of a dual virtualization system provided by one embodiment of the present invention;
FIG. 2 is a flow diagram illustrating an IO funnel capturing IO data streams provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating the integration of IO data streams according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating a bitmap log for recording consolidated information provided by an embodiment of the invention;
fig. 5 is a schematic diagram illustrating an operation principle of a dual virtualization system after disaster recovery switching according to an embodiment of the present invention;
fig. 6 is a flowchart illustrating a virtual machine data replication method according to an embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
In order to solve the problem of the prior art, embodiments of the present invention provide a virtualization system and a virtual machine data replication method. First, a data replication method of a virtual machine according to an embodiment of the present invention is described below.
FIG. 1 illustrates a framework diagram of a double virtualization system provided by one embodiment of the present invention. As shown in fig. 1, the double virtualization system includes: a virtualization system of a production end and a virtualization system of a disaster recovery end. The virtualization system of the production end and the virtualization system of the disaster recovery end both comprise virtualization management layers. An input/output (In-Out) funnel, a background engine and an IO transceiver are deployed on a virtualization management layer of each virtualization system.
It should be noted that, the virtualization system at the production end and the virtualization system at the disaster recovery end may be replaced, that is, the virtualization system at the production end is used as the virtualization system at the disaster recovery end, and the original virtualization system at the disaster recovery end is used as the virtualization system at the production end.
Since the composition and the working principle of the virtualization system at the production end and the virtualization system at the disaster recovery end are the same, the virtualization system at the production end is taken as an example for description, and the IO funnel, the background engine and the IO transceiver of the virtualization system at the production end have the following functions respectively.
The IO funnel is configured to capture an IO data stream of a Virtual Machine (VM), and acquire a plurality of IO data streams to be copied from the captured IO data stream.
The capturing process of the IO funnel is shown in fig. 2, and as can be seen from fig. 2, the capturing of the IO data stream by the IO funnel includes:
1) the IO data stream is written from the VM.
2) The IO data stream enters a virtual Small Computer system interface (vsscsi) device layer, that is, the file system identified by the virtual machine is written into the virtual machine, and a vsscsi back-end channel in a system kernel of the physical host bearing the VM is opened by a vsscsi driver of the virtual machine.
3) And the IO data stream enters the file system layer through the vSCSI back-end channel and is processed and executed by the file system layer.
4) And the IO data stream enters the file device layer identified by the physical host from the file system layer of the physical host and is ready to be written into the physical device of the back-end physical storage.
5) The IO funnel captures IO data streams that are ready to be written into the physical device.
6) The IO funnel selects IO data streams to be copied from the captured IO data and sends the IO data streams to be copied to the background engine; and normally writing the IO data streams except the IO data stream to be copied in the captured IO data into the physical equipment.
In this process, the IO data flow passes from the VM to the system kernel, where it passes through the file system layer and the file device layer.
The background engine is used for integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied.
The background engine integrates the content of the IO data streams occurring at the same time point into one IO data stream.
The integration of multiple IO data streams is described below by way of an example.
As shown in fig. 3, there is a copy policy of VM1, VM2, and VM3 that needs to copy the IO data streams of VM1, VM2, and VM 3.
VM1 executes IO data flows at time 00:00: 01: a01-0101, the IO data flow is VM1 writing content 0101 to A01 location.
VM2 executes IO data flows at time 00:00: 01: b03-1010, the IO data flow is VM2 writing content 1010 to B03 location.
VM1 executes IO data flows at time 00:00: 02: a02-0001, the IO data flow is VM1 writing content 0001 to the A02 location.
VM3 executes IO data flows at time 00:00: 02: c03-0001, the IO data flow is VM3 writing content 0001 to the C03 location.
The IO data streams of VM1, VM2, and VM3 are sent to the background engine by the IO funnel, and the background engine performs the nearby integration, that is, the IO data streams occurring at the same time point are integrated, and it is not possible to distinguish which VMs write the IO data streams during the integration, and only the content of the IO data streams is integrated, and in fig. 3, the integrated IO data streams are as follows:
the IO data streams executed at 00:00:01 are integrated into one IO data stream: z01-01011010, the integrated IO data stream representing the writing of content 01011010 to the Z01 location.
The IO data streams executed at 00:00:02 are integrated into one IO data stream: z02-00010001 this consolidated IO data stream represents writing content 01011010 to Z02 location.
The integrated IO data flow is transmitted to the IO transceiver through the background engine.
The IO transceiver is used for sending the IO data stream integrated by the background engine to another virtualization system.
Therefore, the background engine integrates the discrete IO data streams into IO data streams arranged according to the time sequence, and integrates the IO data streams with the granularity into IO data streams with a large content. And integrating the discrete IO data streams into continuous density IO data streams by adopting a principle of near integration, sending the continuous density IO data streams to an IO receiver, continuously storing the continuous density IO data streams in storage, and sequentially reading the density IO data streams.
According to the virtualization system provided by the embodiment of the invention, the IO data stream to be copied is captured through the IO funnel deployed on the virtualization management layer so as to copy the IO data stream. Because disaster recovery replication is on a virtualization management layer, dependence on bottom storage is eliminated, data disaster recovery replication between different brands of storage is realized, and meanwhile, the method is independent of an optical fiber network and can realize long-distance data disaster recovery replication through the network. In addition, the IO data stream of the virtual machine is captured in an agent-free mode, any agent does not need to be installed in the virtual machine, shutdown is not needed, and the production system is not affected. And moreover, the copy relationship does not need to be configured in a large-scale virtualization environment, so that the maintenance workload is reduced.
In an embodiment of the present invention, bitmap logs are deployed on the virtualization management layers of the virtualization systems of the production side and the disaster recovery side.
The bitmap log is used for recording the integration information of each IO data stream to be copied.
The IO transceiver is further configured to send the integrated information of each IO data stream to be copied recorded in the bitmap log to another virtualization system, where the another virtualization system is referred to as a virtualization system of the disaster recovery end in fig. 1, that is, the IO transceiver of the production end sends the integrated information of each IO data stream to be copied to the IO transceiver of the disaster recovery end.
The background engine does not distinguish the source of the IO data stream when the IO data stream integration is carried out, the source of the IO data stream is recorded by a bitmap log, the playable log is adopted, the bitmap is used for recording the information of each captured IO data stream, and a time point view of each IO data stream can be generated.
FIG. 4 shows the following consolidated information for the IO data flow of bitmap log records:
(1) at time 00:00:01, the IO data stream from VM1 writing to the A01 location is integrated into the 1 st sequence position of the Z01 location.
(2) At time 00:00:01, the IO data stream from VM2 writing to the B03 location is integrated into the 2 nd sequence position of the Z01 location.
(3) At time 00:00:02, the IO data stream from VM1 writing to the A02 location is integrated into the 1 st sequence position of the Z02 location.
(3) At time 00:00:02, the IO data stream from VM3 writing to the C03 location is integrated into the 2 nd sequence position of the Z02 location.
And after the IO data streams are integrated by the background engine, the production end IO transceiver is controlled by the production end scheduler, and the integrated IO data streams are sent to the IO transceiver of the disaster recovery end through the IO transceiver. And updating records related to the bitmap log of the production end into the bitmap log of the disaster recovery end, wherein the integrated information of the integrated IO data stream is updated in the bitmap log of the disaster recovery end.
And the IO transceiver of the disaster tolerance end is controlled by a background engine of the disaster tolerance end, the disaster tolerance end decomposes the integrated IO data stream according to the bitmap log of the disaster tolerance end to obtain the IO data stream before integration, namely discrete IO data streams, and the discrete IO data streams are delivered to an IO funnel of the disaster tolerance end and finally written into the disaster tolerance storage.
According to the virtualization system provided by the embodiment of the invention, the bitmap log records the occurrence time, the source and the integrated position of each IO data stream, the IO data streams can be played back according to the bitmap record, and the view traceability function and the instant use of massive data time points and strong data consistency protection are realized. And the IO data stream integration information is sent to the IO transceiver of the disaster recovery end through the IO transceiver of the production end, so that the background engine of the disaster recovery end can disassemble the integrated IO data stream according to the integration information to obtain each discrete IO data stream, and the IO data stream can be subjected to disaster recovery and replication.
In an embodiment of the present invention, the IO transceiver of the production end is further configured to receive the integrated IO data stream sent from the disaster recovery end after the disaster recovery switching.
And the background engine of the production end is also used for implementing IO data stream disaster tolerance replication according to the integrated IO data stream.
It should be noted that, when the virtualization system at the production end fails to operate normally due to a problem, the virtualization system at the disaster recovery end takes over the virtualization system at the production end, i.e., performs disaster recovery switching, and the IO funnel forcibly stores and starts the VM at the disaster recovery end, thereby ensuring the service sustainability. As shown in fig. 5, after performing disaster recovery switching, an IO data stream is captured by an IO funnel of a disaster recovery end, and the IO data stream is integrated, and an IO transceiver of the disaster recovery end sends the integrated IO data stream to an IO transceiver of a production end.
In one embodiment of the invention, the virtualization system further comprises a storage.
The virtualization system of the production end comprises production storage, and the virtualization system of the disaster recovery end comprises disaster recovery storage.
And the IO transceiver is also used for receiving the integration information of the integrated IO data stream from another virtualization system.
The background engine is used for decomposing the integrated IO data stream according to the integration information of the integrated IO data stream to obtain a discrete IO data stream; and storing the discrete IO data stream in a storage to implement the disaster tolerant replication of the IO data stream.
It should be noted that, the VM at the disaster recovery end takes over the IO data stream and performs reverse forwarding transmission, that is, the IO funnel at the disaster recovery end captures the IO data stream to be copied, and the background engine at the disaster recovery end integrates the IO data stream to be copied; and the IO transceiver of the disaster recovery end sends the integrated IO data stream to the IO transceiver of the production end. And the IO transceiver of the production end receives the integrated IO data stream from the disaster tolerance end, and the background engine of the production end implements the disaster tolerance replication of the IO data stream according to the integrated IO data stream.
In an embodiment of the present invention, the IO funnel is configured to obtain a plurality of IO data streams to be copied from the captured IO data streams according to a predetermined IO data stream copying policy, and is further configured to write IO data streams, other than the plurality of IO data streams to be copied, in the captured IO data streams into the corresponding physical storage device.
It should be noted that the IO funnel is deployed in the virtualization management layer, opens the discovery interface, discovers the VM in the virtualization platform through the interface, and receives the copy policy of the virtualization management layer at the same time, where the copy policy includes the virtual machines that need to perform data copying, that is, the copy policy includes which virtual machines whose data need to be copied. And the IO funnel distinguishes the captured IO data stream according to the copy strategy so as to distinguish the IO data stream to be copied and the IO data stream which does not need to be copied.
The IO data stream is in the file device layer, and before the IO data stream is sent to the physical device, the IO funnel can see the IO data stream, and can check whether the IO data stream is attached with a data copy policy.
If there is no copy policy, the IO data stream will be submitted normally with no overhead.
If the copy strategy for the IO data stream exists, the IO data stream is sent to the background engine, the background engine executes synthesis operation on the IO, and the synthesis operation can be executed quickly due to the fact that context switching does not exist.
Fig. 6 is a flowchart illustrating a virtual machine data replication method according to an embodiment of the present invention. The virtual machine data replication method is used for a first virtualization system, and as shown in fig. 6, the virtual machine data replication method includes:
s201, capturing IO data flow of the virtual machine through an input/output IO funnel, wherein the IO funnel is deployed on a virtualization management layer of the first virtualization system.
S202, a plurality of IO data streams to be copied are obtained from the captured IO data streams.
S203, integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied.
And S204, sending the integrated IO data stream to a second virtualization system.
In an embodiment of the present invention, the virtual machine data replication method further includes:
recording the integrated information of each IO data stream to be copied in a bitmap log of a first virtualization system; and sending the integrated information of each IO data stream to be copied to a second virtualization system.
In an embodiment of the present invention, the virtual machine data replication method further includes:
after disaster recovery switching, receiving an integrated IO data stream sent from a second virtualization system; and performing disaster tolerant replication of the IO data stream according to the integrated IO data stream.
In an embodiment of the present invention, the virtual machine data replication method further includes:
receiving integration information of the integrated IO data stream from the second virtualization system; and decomposing the integrated IO data stream according to the integration information of the integrated IO data stream to obtain the discrete IO data stream.
Implementing IO data stream disaster tolerant replication, comprising:
the discrete IO data streams are stored in storage of the first virtualization system.
In an embodiment of the present invention, a plurality of IO data streams to be copied are obtained from a captured IO data stream according to a predetermined IO data stream copying policy.
The virtual machine data replication method further comprises the following steps:
and writing the IO data streams except the plurality of IO data streams to be copied in the captured IO data streams into the corresponding physical storage equipment.
In one embodiment of the present invention, the first virtualization system is a virtualization system of a production side, and the second virtualization system is a virtualization system of a disaster recovery side; or the first virtualization system is a virtualization system of a disaster recovery end, and the second virtualization system is a virtualization system of a production end.
It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.
The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
It should also be noted that the exemplary embodiments mentioned in this patent describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.
As described above, only the specific embodiments of the present invention are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.
Claims (11)
1. A virtualization system is characterized by comprising a virtualization management layer, wherein an IO funnel, a background engine and an IO transceiver are deployed on the virtualization management layer;
the IO funnel is used for capturing IO data streams of the virtual machine and acquiring a plurality of IO data streams to be copied from the captured IO data streams;
the background engine is used for integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied;
and the IO transceiver is used for sending the IO data stream integrated by the background engine to another virtualization system.
2. The virtualization system of claim 1 wherein said virtualization management layer further deploys a bitmap log;
the bitmap log is used for recording the integrated information of each IO data stream to be copied;
the IO transceiver is further configured to send the integration information of each IO data stream to be copied, recorded by the bitmap log, to the other virtualization system.
3. The virtualization system of claim 1,
the IO transceiver is further configured to receive an integrated IO data stream sent from the another virtualization system after the disaster recovery switching;
and the background engine is also used for implementing IO data stream disaster tolerance replication according to the integrated IO data stream.
4. The virtualization system of claim 3 wherein said virtualization system further comprises a storage;
the IO transceiver is further configured to receive integration information of the integrated IO data stream from the another virtualization system;
the background engine is used for decomposing the integrated IO data stream according to the integration information of the integrated IO data stream to obtain a discrete IO data stream; and storing the discrete IO data stream in the storage to implement the IO data stream disaster tolerant replication.
5. The virtualization system of claim 1,
the IO funnel is used for acquiring the plurality of IO data streams to be copied from the captured IO data streams according to a preset IO data stream copying strategy, and is also used for writing the IO data streams except the plurality of IO data streams to be copied in the captured IO data streams into corresponding physical storage equipment.
6. The virtualization system of claim 1,
the virtualization system is a virtualization system of a production end, and the other virtualization system is a virtualization system of a disaster recovery end;
alternatively, the first and second electrodes may be,
the virtualization system is a virtualization system of a disaster recovery end, and the other virtualization system is a virtualization system of a production end.
7. A virtual machine data replication method is used for a first virtualization system, and is characterized by comprising the following steps:
capturing an IO data stream of a virtual machine through an input/output (IO) funnel, wherein the IO funnel is deployed in a virtualization management layer of the first virtualization system;
acquiring a plurality of IO data streams to be copied from the captured IO data streams;
integrating the plurality of IO data streams to be copied according to the occurrence time of each IO data stream to be copied;
and sending the integrated IO data stream to a second virtualization system.
8. The method of claim 7, further comprising:
recording the integrated information of each IO data stream to be copied in a bitmap log of the first virtualization system;
and sending the integration information of each IO data stream to be copied to the second virtualization system.
9. The method of claim 7, further comprising:
after disaster recovery switching, receiving an integrated IO data stream sent by the second virtualization system;
and performing disaster tolerant replication of the IO data stream according to the integrated IO data stream.
10. The method of claim 9, further comprising:
receiving integration information for the integrated IO data stream from the second virtualization system;
decomposing the integrated IO data stream according to the integration information of the integrated IO data stream to obtain a discrete IO data stream;
the implementing of the IO data stream disaster tolerant replication comprises the following steps:
storing the discrete IO data stream in storage of the first virtualization system.
11. The method of claim 7,
acquiring the plurality of IO data streams to be copied from the captured IO data streams according to a preset IO data stream copying strategy;
the method further comprises the following steps:
and writing the IO data streams except the plurality of IO data streams to be copied in the captured IO data streams into corresponding physical storage equipment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811518182.6A CN111309433A (en) | 2018-12-12 | 2018-12-12 | Virtualization system and virtual machine data copying method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811518182.6A CN111309433A (en) | 2018-12-12 | 2018-12-12 | Virtualization system and virtual machine data copying method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111309433A true CN111309433A (en) | 2020-06-19 |
Family
ID=71150483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811518182.6A Pending CN111309433A (en) | 2018-12-12 | 2018-12-12 | Virtualization system and virtual machine data copying method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309433A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817698A (en) * | 2021-02-20 | 2021-05-18 | 咪咕音乐有限公司 | Virtual machine backup method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102207951A (en) * | 2010-03-29 | 2011-10-05 | 软件Ag公司 | Systems and/or methods for distributed data archiving |
| CN104102556A (en) * | 2014-06-13 | 2014-10-15 | 上海爱数软件有限公司 | Disk data backup and recovering method of virtual machine |
| CN104866372A (en) * | 2015-05-13 | 2015-08-26 | 华中科技大学 | Server integration oriented high efficiency physical machine to virtual machine conversion method |
| WO2016045428A1 (en) * | 2014-09-24 | 2016-03-31 | 华为技术有限公司 | Method for creating virtual machine and apparatus for creating virtual machine |
| WO2016106756A1 (en) * | 2014-12-31 | 2016-07-07 | 华为技术有限公司 | Disaster recovery method, system and apparatus |
-
2018
- 2018-12-12 CN CN201811518182.6A patent/CN111309433A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102207951A (en) * | 2010-03-29 | 2011-10-05 | 软件Ag公司 | Systems and/or methods for distributed data archiving |
| CN104102556A (en) * | 2014-06-13 | 2014-10-15 | 上海爱数软件有限公司 | Disk data backup and recovering method of virtual machine |
| WO2016045428A1 (en) * | 2014-09-24 | 2016-03-31 | 华为技术有限公司 | Method for creating virtual machine and apparatus for creating virtual machine |
| WO2016106756A1 (en) * | 2014-12-31 | 2016-07-07 | 华为技术有限公司 | Disaster recovery method, system and apparatus |
| CN104866372A (en) * | 2015-05-13 | 2015-08-26 | 华中科技大学 | Server integration oriented high efficiency physical machine to virtual machine conversion method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817698A (en) * | 2021-02-20 | 2021-05-18 | 咪咕音乐有限公司 | Virtual machine backup method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10250479B2 (en) | Detecting patterns of events in information systems | |
| CN100504873C (en) | Method and system for managing an archived file system | |
| US20170344433A1 (en) | Apparatus and method for data migration | |
| CN109582443A (en) | Virtual machine standby system based on distributed storage technology | |
| CN105653582A (en) | File management method of electronic equipment and electronic equipment | |
| CN107710215A (en) | The method and apparatus of mobile computing device safety in test facilities | |
| CN105407117A (en) | Distributed data backup method, device and system | |
| CN106446159A (en) | Method for storing files, first virtual machine and name node | |
| CN107943501A (en) | Embedded device upgrade method, device, computer equipment and storage medium | |
| CN113938321B (en) | Extensible operation and maintenance management system, method, electronic equipment and readable storage medium | |
| CN103152390A (en) | Method and device and nodes and system for node configuration of distributed storage system | |
| CN103268183A (en) | Processing method and device for information report | |
| CN103973470A (en) | Cluster management method and equipment for shared-nothing cluster | |
| CN105867962A (en) | System upgrading method and device | |
| US20080115127A1 (en) | Apparatus and method for carrying out information processing by virtualization | |
| CN101937378B (en) | Method for carrying out back-up protection on data of storage equipment and computer system | |
| KR20200000245A (en) | Application hot deploy method to guarentee application version consistency and computer program stored in computer readable medium therfor | |
| CN104239091A (en) | File cleaning method and device and terminal | |
| US9916220B2 (en) | Smart logging of trace data for storage systems | |
| CN111309433A (en) | Virtualization system and virtual machine data copying method | |
| CN104182296A (en) | Data processing system, data processing apparatus, and storage medium | |
| CN109784051A (en) | Protecting information safety method, device and equipment | |
| US9176974B1 (en) | Low priority, multi-pass, server file discovery and management | |
| US20150370649A1 (en) | Sending a Request to a Management Service | |
| CN115543225B (en) | Data processing method, system, device, computer storage medium and electronic equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200619 |
|
| RJ01 | Rejection of invention patent application after publication |