CN112199162B - Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance - Google Patents
Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance Download PDFInfo
- Publication number
- CN112199162B CN112199162B CN202011111555.5A CN202011111555A CN112199162B CN 112199162 B CN112199162 B CN 112199162B CN 202011111555 A CN202011111555 A CN 202011111555A CN 112199162 B CN112199162 B CN 112199162B
- Authority
- CN
- China
- Prior art keywords
- snapshot
- disk
- child node
- file
- layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/065—Replication mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0656—Data buffering arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0664—Virtualisation aspects at device level, e.g. emulation of a storage device or system
-
- 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/45562—Creating, deleting, cloning virtual machine instances
-
- 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
-
- 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/45583—Memory management, e.g. access or allocation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a virtual disk snapshot method and device based on virtualized disk double-active disaster recovery and a computer readable storage medium. The method is applied to Qemu, the double-active disaster recovery function of the disk is started when the virtual machine is preset to be started, and a snapshot interface is set in an IO copy layer. After the virtual machine is started in a double-active mode, a disk snapshot creating or deleting instruction issued by an upper layer can be received in the normal operation process. When a disk snapshot creating instruction is received, creating a virtual snapshot task in an IO replication layer, issuing the same task to each child node of a block device simulation layer, and simultaneously executing the snapshot task by each child node in the IO replication layer suspension IO state; when a disk snapshot deleting instruction is received, a snapshot deleting task is created in the IO replication layer, snapshot files to be deleted corresponding to all the child nodes in the block device simulation layer are searched, the deleting task is simultaneously issued to each child node, and each child node simultaneously executes deleting operation on the snapshot files to be deleted, so that the snapshot of the IO replication layer is realized.
Description
Technical Field
The present application relates to the field of virtualization technologies, and in particular, to a virtual disk snapshot method and apparatus based on a virtualized disk double-active disaster recovery, and a computer-readable storage medium.
Background
With the rapid development of virtualization technologies, virtualization management platforms such as ICS (internet Sphere, wave virtualization platform) generally utilize Qemu (Quick Emulator) to provide a virtual machine and manage the entire life cycle of the virtual machine. Qemu is used by a user as a user mode simulator or/and a virtual machine supervisor, and the user mode simulator executes codes different from a host machine architecture by utilizing a dynamic code translation mechanism; the hypervisor is used to simulate the whole system, and creates a Virtual machine close to the performance of the host machine using virtualization support provided by other VMMs (Virtual Memory managers) such as Xen and KVM using hardware. Each virtual machine virtualized by Qemu corresponds to a Qemu process on the host, and the execution threads of the virtual machine, such as CPU threads, I/O threads, and the like, correspond to a thread of the Qemu process.
The virtualized disk double-active disaster recovery scheme of the virtualized management platform is to perform double writing on a virtual disk at a virtualized layer, and each IO issued by a virtual machine is copied and written to disk files in two storage pools. When one storage pool is damaged, the disk file in the other storage pool can be used for continuing working, so that the data of a user is not lost, the virtual machine is not suspended, and the user cannot sense the inside of the virtual machine.
Qemu provides a simple disk double-write function for a virtual machine, and an IO (input/output) copy function of Qemu, that is, a qurum function, is used to copy the IO of the virtual machine and write the IO of the virtual machine into different disk files, a conventional process of simulating a disk file by using virtio equipment as an example can be referred to as fig. 1, and a process of implementing a virtualized disk double-active disaster tolerance based on the qurum function can be referred to as fig. 2. In the figure, VM represents a virtual machine, a virtual _ blk is a paravirtualized disk, and is used for implementing event notification and data transfer inside and outside the virtual machine, the device is "embedded" on a PCI (Peripheral Component Interconnect) device board, i.e., a virtual-blk-PCI device, and the interior of the device is connected with a PCI interface and the virtual-blk device through a virtual bus, a disk driven by the VM using the virtual _ blk is shown as/dev/vda, bdrv _ qcow2 is used for implementing block device simulation, which may be called a block device simulation layer, and a file is a disk file for storing virtual machine IO. Qemu simulates the bottom layer disk file into a disk device through internal software modules, namely virtual-blk-pci and bdrv _ qcow2, and the disk device can be identified inside the virtual machine through a virtual machine host driver. Not limited to virtio-blk-pci, qemu can also emulate disk files as ide and scsi devices. After using the quuorum function, that is, adding a bdrv _ quuorum layer into the whole architecture shown in fig. 2, where the bdrv _ quuorum layer is an IO copy layer, and Qemu uses two disk files file1 and file2 to jointly simulate, that is, a virtual-blk-pci and a bdrv _ qcow2 simulate the disk file1 as one disk device, and a virtual-blk-pci and a bdrv _ qcow2 simulate the disk file2 as another disk device, where all contents in the two files, file1 and file2, are the same, and after issuing IO by the virtual machine, the IO is copied on the bdrv _ quuorum layer and written into the file1 and the file2 at the same time, thereby implementing the disk double-write function. However, after using the quorum function, since bdrv _ quorum is a virtual device, it is currently impossible to snapshot the virtual device.
Disclosure of Invention
The application provides a virtual disk snapshot method, a device and a computer readable storage medium based on double-active disaster tolerance of a virtual disk, which realize the snapshot of an IO copy layer.
In order to solve the above technical problems, embodiments of the present invention provide the following technical solutions:
an embodiment of the present invention provides a virtual disk snapshot method based on a virtualized disk double-active disaster recovery, which is applied to Qemu with an IO copy function, and includes:
the method comprises the steps that a double-active disaster recovery function of a disk is started in the starting process of a preset virtual machine, and a snapshot interface is arranged on an IO copy layer;
receiving a disk snapshot creating instruction in the running process of a virtual machine, creating a virtual snapshot task in the IO replication layer, and issuing the same task to each child node of a block device simulation layer so that each child node can execute the snapshot task at the same time when the IO replication layer suspends the IO state;
receiving a disk snapshot deleting instruction in the running process of the virtual machine, creating a snapshot deleting task in the IO copy layer, searching for the snapshot file to be deleted corresponding to all the child nodes in the block device simulation layer, and simultaneously issuing the deleting task to each child node so that each child node simultaneously executes deleting operation on the snapshot file to be deleted.
Optionally, the issuing the same task to each child node of the block device simulation layer to enable each child node to simultaneously execute the snapshot task in the IO replication layer suspended IO state includes:
the same task is issued to each child node of the block device simulation layer, so that each child node simultaneously creates a new disk file as a block device simulation file;
when detecting that the new disk file creating operation of each child node is completed, sending an IO pause instruction of the IO copy layer;
sending a command for executing the cache writing operation to each child node so that each child node writes all caches in the qemu process into corresponding old disk files;
sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO replication layer;
and when detecting that each child node completes the backup file switching operation, sending an IO replication layer recovery IO instruction.
Optionally, the simultaneously executing the deletion operation on the snapshot file to be deleted by each child node includes:
each child node determines data to be copied by comparing the stored data of the new disk file and the stored data of the old disk file, wherein the data to be copied is the data which does not contain the corresponding old disk file in the current new disk file;
and all the corresponding data to be copied are copied to the new disk file from the corresponding old disk file by each child node.
Optionally, after the sending the deletion task to each child node, the method further includes:
when detecting that each child node finishes deleting the snapshot, sending feedback information of finishing deleting the snapshot to an upper-layer virtualization management platform so that the virtualization management platform deletes the old disk file of each child node after receiving the feedback information.
Optionally, after issuing the same task to each child node of the block device simulation layer, the method further includes:
when detecting that each child node completes snapshot creation operation, sending feedback information of successful snapshot creation to an upper-layer virtualization management platform;
and when the fact that the child node snapshot creation fails is detected, reporting an error to the virtual machine.
Optionally, before receiving the instruction of creating the disk snapshot in the running process of the virtual machine, the method further includes:
setting a disk snapshot creating option and a disk snapshot deleting option in a user management interface of a virtualization management platform where the virtual machine is located in advance, so that a user can issue the disk snapshot creating instruction and the disk snapshot deleting instruction through the user management interface.
Another aspect of the embodiments of the present invention provides a virtual disk snapshot apparatus based on a virtualized disk double-active disaster recovery, which is applied to Qemu with an IO copy function, and includes:
the double-active mode starting preset module is used for presetting a function of starting a double-active disaster tolerance of a magnetic disk in the starting process of the virtual machine;
the interface creating module is used for setting a snapshot interface in an IO copy layer in advance;
the snapshot creating module is used for receiving a disk snapshot creating instruction in the running process of the virtual machine, creating a virtual snapshot task in the IO replication layer, and issuing the same task to each child node of the block device simulation layer so that each child node can execute the snapshot task at the same time when the IO replication layer is in an IO suspension state;
and the snapshot deleting module is used for receiving a disk snapshot deleting instruction in the running process of the virtual machine, creating a snapshot deleting task in the IO copying layer, searching for the snapshot file to be deleted corresponding to all the child nodes in the block device simulation layer, and simultaneously issuing the deleting task to each child node so that each child node simultaneously executes deleting operation on the snapshot file to be deleted.
Optionally, the snapshot creating module includes:
the new disk file creating submodule is used for issuing the same task to each child node of the block device simulation layer so that each child node simultaneously and respectively creates a new disk file to serve as a block device simulation file;
the IO suspension sub-module is used for sending an IO suspension instruction of the IO replication layer when detecting that the new disk file creation operation of each child node is completed;
the cache submodule is used for sending a command for executing write cache operation to each child node so that each child node writes all caches in the qemu process into corresponding old disk files;
the backup file switching submodule is used for sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO replication layer;
and the IO recovery submodule is used for sending an IO replication layer recovery IO instruction when detecting that each child node completes the backup file switching operation.
The embodiment of the invention also provides a virtual disk snapshot device based on the double-active disaster recovery of the virtual disk, which comprises a processor, wherein the processor is used for realizing the steps of the virtual disk snapshot method based on the double-active disaster recovery of the virtual disk when executing the computer program stored in the memory.
The embodiment of the present invention finally provides a computer readable storage medium, where a virtual disk snapshot program based on a virtual disk double-active disaster recovery is stored in the computer readable storage medium, and when the virtual disk snapshot program based on the virtual disk double-active disaster recovery is executed by a processor, the step of implementing the virtual disk snapshot method based on the virtual disk double-active disaster recovery as in any of the foregoing is implemented.
The technical scheme provided by the application has the advantages that for the virtual machine supporting the double-active disaster tolerance of the virtual disk, a snapshot interface is added to an IO replication layer for realizing the IO replication function, and a snapshot command including a snapshot creation command and a snapshot deletion command is issued to all child nodes of the IO replication layer, so that the transfer of the snapshot command is realized, all the child nodes execute corresponding snapshot creation tasks or snapshot deletion tasks, the complex operation of the child nodes at the bottom layer is shielded by the IO replication layer, a set of simple snapshot creation and deletion interfaces is provided for an upper platform, the snapshot creation interfaces are compatible with the interfaces of qemu for creating snapshots of simple equipment, the snapshots of the IO replication layer are realized in the normal use process of the virtual machine, the snapshot deletion is simultaneously executed by each child node, the snapshot creation is executed in the suspended IO state, the consistency of the disk files and snapshot chains of the virtual machine on two virtual pools of the virtual platform is guaranteed, the snapshot management function is provided for the virtual disk, and the double-active disaster tolerance and management function of the virtual disk are completed.
In addition, the embodiment of the invention also provides a corresponding implementation device and a computer readable storage medium for the virtual disk snapshot method based on the virtual disk double-active disaster tolerance, so that the method has higher practicability, and the device and the computer readable storage medium have corresponding advantages.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the related arts, the drawings used in the description of the embodiments or the related arts will be briefly described below, it is obvious that the drawings in the description below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a process of simulating a disk file by Qemu in an exemplary application scenario according to an embodiment of the present invention;
fig. 2 is a schematic diagram of an implementation process of virtualized disk dual-active disaster recovery based on a quorum function implementation in an exemplary application scenario according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a virtual disk snapshot method based on a virtualized disk double-active disaster recovery according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a disk snapshot creation flow in an exemplary application scenario according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a system framework after completion of creation of a disk snapshot in an exemplary application scenario according to an embodiment of the present invention;
fig. 6 is a schematic flow chart of deleting a disk snapshot in an exemplary application scenario according to an embodiment of the present invention;
fig. 7 is a schematic diagram of a system framework after completion of deletion of a disk snapshot in an exemplary application scenario according to an embodiment of the present invention;
fig. 8 is a configuration diagram of an embodiment of a virtual disk snapshot apparatus based on a virtualized disk double-active disaster recovery according to an embodiment of the present invention;
fig. 9 is a configuration diagram of another specific embodiment of a virtual disk snapshot apparatus based on a virtualized disk double-active disaster recovery according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It should be apparent that the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Having described the technical solutions of the embodiments of the present invention, various non-limiting embodiments of the present application are described in detail below.
Referring to fig. 3, fig. 3 is a schematic flowchart of a virtual disk snapshot method based on a virtualized disk double-active disaster recovery provided in an embodiment of the present invention, and the method is applied to Qemu having an IO copy function, where the embodiment of the present invention may include the following contents:
s301: the method comprises the steps of starting a double-active disaster recovery function of a disk in the starting and starting process of a preset virtual machine, and setting a snapshot interface in an IO copy layer.
In the application, the virtual machine is started in a double-active mode by setting a virtual machine starting item. The snapshot interface is also an application program interface API, a set of simple snapshot creating and deleting interfaces are provided for an upper platform, namely a virtualization management platform, by setting the snapshot interface in an IO copy layer and realizing the complex operation that the snapshot function comprises a snapshot creating function and a snapshot deleting function to shield the subnodes on the bottom layer, and the snapshot creating and deleting interfaces are compatible with the interfaces of Qemu for creating snapshots of simple equipment.
S302: receiving a disk snapshot creating instruction in the running process of the virtual machine, creating a virtual snapshot task in an IO replication layer, and issuing the same task to each child node of the block device simulation layer so that each child node can execute the snapshot task at the same time when the IO replication layer suspends the IO state.
Because the bottom layer interface calls the relevant instruction to realize under the normal operation state of the virtual machine, the snapshot creating and deleting process of the application is carried out in the normal operation process of the virtual machine, namely the snapshot creating operation and the snapshot deleting operation of the virtual disk of the virtual machine do not influence the normal operation of the virtual machine. The child nodes in the block device simulation layer are used for simulating the files below the node into the block device, and the total number of the child nodes in the layer can also be adjusted according to the actual application scenario, and is usually 2.
S303: receiving a disk snapshot deleting instruction in the running process of the virtual machine, creating a snapshot deleting task in an IO copying layer, searching for a snapshot file to be deleted corresponding to all child nodes in a block device simulation layer, and simultaneously issuing a deleting task to each child node so that each child node simultaneously executes deleting operation on the snapshot file to be deleted.
In this embodiment, the virtualization management platform sends a snapshot command to the Qemu, and the snapshot command carries an IO replication layer as an equipment ID of a simulated virtual block equipment when being issued, where the snapshot command includes two commands, namely, a virtual disk snapshot creation command and a virtual disk snapshot deletion command, the Qemu first establishes a corresponding snapshot task in the IO replication layer, where the snapshot task includes a virtual snapshot task, that is, a task of creating a virtual disk snapshot and a snapshot deletion task, and for the snapshot creation task, after the task creation is completed, the Qemu directly issues the same task to the child nodes, and when issuing the task to each child node, the Qemu needs to carry each child node as an equipment ID of a simulated virtual block equipment. For the snapshot creation task, after the task creation is completed, qemu searches for snapshot files to be deleted under all child nodes, then issues the deletion task to the child nodes, and when the deletion task is issued to each child node, it also needs to carry the device ID of each child node as a simulated virtual block device, and also can carry the name of the file to be deleted, that is, the snapshot file to be deleted.
In the technical scheme provided by the embodiment of the invention, as for the virtual machine supporting the double-live disaster tolerance of the virtual disk, a snapshot interface is added in an IO copying layer for copying the IO function, and a snapshot command including a snapshot creating command and a snapshot deleting command is issued to all the child nodes of the IO copying layer, so that the transfer of the snapshot command is realized, all the child nodes execute corresponding snapshot creating tasks or snapshot deleting tasks, the complex operation of the child nodes at the bottom layer is shielded by the IO copying layer, a set of simple snapshot creating and deleting interfaces are provided for an upper platform, the interfaces are compatible with the interfaces for creating the snapshot by qemu on simple equipment, the snapshot on the IO copying layer is realized in the process of not influencing the normal use of the virtual machine, and the snapshot deleting is simultaneously executed through each child node and the snapshot creating is executed in the state of suspending the IO to ensure that the disk files and snapshot chains of the virtual machine on two virtual pools of the virtual platform are kept consistent, so that the snapshot management function is provided for the virtual disk, and the double-live disaster tolerance and snapshot management function of the virtual disk are completed.
It should be noted that, in the present application, there is no strict sequential execution order among the steps, and as long as a logical order is met, the steps may be executed simultaneously or according to a certain preset order, and fig. 3 is only an exemplary manner, and does not represent that only such an execution order is available.
In the foregoing embodiment, how to execute step S302 is not limited, and a snapshot creation implementation manner provided in this embodiment may include the following steps:
a1: and issuing the same task to each child node of the block device simulation layer, so that each child node simultaneously and respectively creates a new disk file to serve as a block device simulation file.
Before this step, each child node has a disk file, and after this step, each child node has a new disk file and also an old disk file, i.e. the disk file before the new disk file was created. After the new disk file is created, the new disk file is an active file serving as an IO replication layer, i.e., a block device simulation file.
A2: and when detecting that the new disk file creating operation of each child node is completed, sending an IO replication layer IO pause instruction. To ensure snapshot consistency, an IO pause is required before the snapshot function, i.e., the A3 step, is performed.
A3: and sending a command for executing the cache writing operation to each child node, so that each child node writes all caches in the qemu process into corresponding old disk files.
In this step, after each child node receives the write cache operation command, each child node writes all caches in the qemu process into its old disk file.
A4: and sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO replication layer.
And after each child node completes the write cache operation, sending a backup file switching instruction. The backup file is used for dumping files on the hard disk to other external media, when a new disk file is not created, the backup file of the IO copying layer is an old disk file, after the new disk file is created, the backup file of the IO copying layer is a new disk file, and the backup file of the new disk file is the old disk file.
A5: and when detecting that each child node completes the backup file switching operation, sending an IO replication layer recovery IO instruction.
In this embodiment, each child node generates a new disk file at the same time, and switches to a new active file to operate after writing an old disk file into all caches in the qemu process in an IO pause state, so that it is ensured that the disk files and the snapshot chains of the virtual machines in the two storage pools are kept consistent.
In the foregoing embodiment, how to execute step S303 is not limited, and an implementation manner of deleting a snapshot is provided in this embodiment, and may include the following steps:
each child node determines data to be copied by comparing the stored data of the new disk file and the stored data of the old disk file, wherein the data to be copied is the data which does not contain the corresponding old disk file in the current new disk file; and all the corresponding data to be copied are copied to the new disk file from the corresponding old disk file by each child node.
The data to be copied in this embodiment is also the snapshot file to be deleted, and these files refer to data that is not present in the new disk file compared to the old disk file. In other words, since the new disk file is created later than the old disk file, the snapshot file to be deleted is the older data content of the old disk file.
In this embodiment, each child node deletes the snapshot file at the same time, so that the disk files of the virtual machines and the snapshot chains on the two storage pools are guaranteed to be consistent.
As an optional implementation manner of this embodiment, when it is detected that each child node completes snapshot deletion, sending feedback information of completion of snapshot deletion to the upper-layer virtualization management platform, so that the virtualization management platform deletes the old disk file of each child node after receiving the feedback information, so as to recycle the storage space, and efficiently improve the space utilization rate.
As another optional implementation manner of this embodiment, when it is detected that each child node completes the snapshot creation operation, feedback information that the snapshot creation is successful may also be sent to the upper-layer virtualization management platform; and when the condition that at least one child node snapshot creation fails is detected, reporting an error to the virtual machine so as to repair the fault in time.
It can be understood that, in order to make the virtualization management platform more convenient for the user to use and improve the user experience, a disk snapshot creation option and a disk snapshot deletion option may be set in advance in the user management interface of the virtualization management platform where the virtual machine is located, so that the user issues a disk snapshot creation instruction and a disk snapshot deletion instruction through the user management interface, in this embodiment, the whole snapshot implementation technical solution may be:
firstly, when the virtual machine is started, the double-activity disaster recovery function of the disk is started, and the virtual machine is started in a double-activity mode.
Then, the virtual machine runs normally, the user selects an option of creating a disk snapshot through the ICS management interface, and the backend program of Qemu automatically and respectively snapshots two disk files on two storage pools.
Secondly, the virtual machine runs normally, the user selects an option of deleting the disk snapshots through an ICS management interface, and the backend program of Qemu can automatically and respectively delete the snapshots of the two files on the two storage pools.
In order to make it more clear to those skilled in the art to understand the technical solution of the present application, taking ICS as an example in conjunction with fig. 4 to fig. 7, sets a virtual snapshot function at a quorum layer, that is, an IO replication layer, of the ICS, for managing snapshot creation and deletion operations of bottom child nodes. The following describes a process for automatically executing snapshot creation and snapshot deletion by a Qemu backend program based on a virtio device, and may include:
after the ICS sends a snapshot command to the Qemu, the Qemu first establishes a snapshot _ create task at the bdrv _ quorum layer, and issues the same snapshot _ create task to the two child nodes bdrv _ qcow2, and at this time, the two child nodes simultaneously establish new files, that is, newfile1 and newfile2, and prepare to be used as new active files, as shown in fig. 4. After the two child nodes create the newly prepared active files, the bdrv _ quorum layer suspends IO, informs the two child nodes to execute drain _ all operation, and writes all the caches still in the qemu process into file1 and file2; and then informing the two child nodes to execute the operation of changing _ backing _ file switching backup file, wherein after the backup file is switched by the two child nodes, the bdrv _ quorum restores IO, at the moment, the snapshot is completed, and the virtual machine can normally execute the IO. The virtual machine frame after snapshot creation is shown in FIG. 5 below.
The process of deleting a snapshot also requires bdrv _ quorum layer scheduling. Firstly, an ICS sends a command of deleting a snapshot to Qemu, the Qemu firstly establishes a stream _ quorum task at a bdrv _ quorum layer, and searches corresponding snapshot files to be deleted under all child nodes. Then, stream tasks are created in the two child nodes at the same time, and as shown in fig. 6, all the contents of file1 that are older than newfile1 are copied into newfile1, and all the contents of file2 that are older than newfile2 are copied into newfile 2. When the bdrv _ quorum finds that the two child nodes complete the stream operation, the ICS is notified through Qemu that the operation of deleting the snapshot has been completed. After the ICS obtains the command of deleting the snapshot, the original file1 and file2 are deleted to recover the storage space, and a frame diagram of the virtual machine after deleting the snapshot is shown in fig. 7.
In this embodiment, the tasks of creating a snapshot and deleting a snapshot are added at the bdrv _ quorum level, and the snapshot operation of the child node is managed. Complex operation of a bottom-layer child node is shielded through the bdrv _ quorum, a set of simple interfaces for creating and deleting snapshots is provided for an upper layer, and the interfaces are compatible with the interfaces for creating the snapshots of the simple equipment through qemu, so that the ICS is convenient to manage the disk with the disk double-activity disaster recovery function; and simultaneously supports the double-active disaster recovery and snapshot management functions of the virtualized disk.
In the above embodiments, the snapshot function of the virtual disk is executed in the normal operation process of the virtual machine, and for the virtual machine executing the snapshot function in the shutdown state, the disk may be directly copied or deleted, and for the copy disk, the new disk file is directly designated as the old disk file, for example, newfile1 is directly designated as file1, and newfile2 is directly designated as file2. Compared with the disk snapshot in the running process, the method is simpler, more convenient and faster.
The embodiment of the invention also provides a corresponding device for the virtual disk snapshot method based on the virtual disk double-active disaster recovery, so that the method has higher practicability. Wherein the means can be described separately from the functional module point of view and the hardware point of view. In the following, the virtual disk snapshot apparatus based on the virtualized disk double-active disaster recovery provided in the embodiment of the present invention is introduced, and the virtual disk snapshot apparatus based on the virtualized disk double-active disaster recovery described below and the virtual disk snapshot method based on the virtualized disk double-active disaster recovery described above may be referred to in a corresponding manner.
Based on the angle of the functional module, referring to fig. 8, fig. 8 is a structural diagram of a virtual disk snapshot apparatus based on a virtualized disk double-active disaster recovery according to an embodiment of the present invention in a specific implementation, where the apparatus is applied to Qemu having an IO copy function, and the apparatus may include:
the dual active mode startup presetting module 801 is used for presetting a function of starting a disk dual active disaster recovery in a startup process of a virtual machine.
An interface creating module 802, configured to set a snapshot interface in the IO replication layer in advance.
The snapshot creating module 803 is configured to receive a disk snapshot creating instruction in the running process of the virtual machine, create a virtual snapshot task in the IO replication layer, and issue the same task to each child node of the block device simulation layer, so that each child node executes the snapshot task simultaneously in the IO replication layer in the IO suspension state.
The snapshot deleting module 804 is configured to receive a disk snapshot deleting instruction in the running process of the virtual machine, create a snapshot deleting task in the IO replication layer, search for a snapshot file to be deleted corresponding to all child nodes in the block device simulation layer, and simultaneously issue a deleting task to each child node, so that each child node executes a deleting operation on the snapshot file to be deleted at the same time.
As an optional implementation manner, the snapshot creation module 803 may include:
the new disk file creating submodule is used for issuing the same task to each child node of the block device simulation layer so that each child node simultaneously and respectively creates a new disk file to serve as a block device simulation file;
the IO suspension sub-module is used for sending an IO replication layer IO suspension instruction when detecting that the new disk file creation operation of each child node is completed;
the cache submodule is used for sending a command for executing the write cache operation to each child node so that each child node writes all caches in the qemu process into corresponding old disk files;
the backup file switching submodule is used for sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO copy layer;
and the IO recovery submodule is used for sending an IO replication layer recovery IO instruction when detecting that each child node completes the backup file switching operation.
As another optional implementation manner of the embodiment of the present invention, the snapshot deleting module 804 may determine, for example, to-be-copied data for each child node by comparing respective stored data of a new disk file and an old disk file, where the to-be-copied data is data that does not include data in a corresponding old disk file in a current new disk file; and all the child nodes copy the corresponding data to be copied to the module in the new disk file from the corresponding old disk file.
Optionally, in some embodiments of this embodiment, the apparatus may further include, for example, an information feedback module and an error reporting module;
the information feedback module is used for sending feedback information of snapshot deletion completion to the upper-layer virtualization management platform when detecting that each child node completes snapshot deletion operation, so that the virtualization management platform deletes the old disk file of each child node after receiving the feedback information; the system is also used for sending feedback information of successful snapshot creation to the upper-layer virtualization management platform when detecting that each child node completes snapshot creation operation;
and the error reporting module is used for reporting an error to the virtual machine when detecting that the creation of the child node snapshot fails.
Optionally, in other embodiments of this embodiment, the apparatus may further include an interfacing setting module, for example, configured to set a disk snapshot creating option and a disk snapshot deleting option in a user management interface of a virtualization management platform where the virtual machine is located in advance, so that a user issues a disk snapshot creating instruction and a disk snapshot deleting instruction through the user management interface.
The functions of the functional modules of the virtual disk snapshot apparatus based on the virtualized disk double-active disaster recovery according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
As can be seen from the above, the embodiment of the present invention implements snapshot of the IO replication layer.
The virtual disk snapshot device based on the double-active disaster recovery of the virtual disk is described from the perspective of a functional module, and further, the application also provides a virtual disk snapshot device based on the double-active disaster recovery of the virtual disk, which is applied to Qemu with an IO copy function and is described from the perspective of hardware. Fig. 9 is a structural diagram of another virtual disk snapshot apparatus based on a virtualized disk double-active disaster recovery according to an embodiment of the present application. As shown in fig. 9, the apparatus includes a memory 90 for storing a computer program; the processor 91 is configured to implement the steps of the virtual disk snapshot method based on the dual-active disaster recovery of the virtualized disk as mentioned in any of the above embodiments when executing the computer program.
Among other things, the processor 91 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 91 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 91 may also include a main processor and a coprocessor, the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 91 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 91 may further include an AI (Artificial Intelligence) processor for processing a calculation operation related to machine learning.
The memory 90 may include one or more computer-readable storage media, which may be non-transitory. Memory 90 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 90 is at least used for storing a computer program 901, wherein after the computer program is loaded and executed by the processor 91, the relevant steps of the virtual disk snapshot method based on the virtualized disk double-active disaster recovery disclosed in any of the foregoing embodiments can be implemented. In addition, the resources stored by the memory 90 may also include an operating system 902, data 903, and the like, and the storage may be transient storage or permanent storage. The operating system 902 may include Windows, unix, linux, etc. Data 903 may include, but is not limited to, data corresponding to test results, and the like.
In some embodiments, the virtual disk snapshot apparatus based on the double active disaster recovery of the virtualized disk may further include a display screen 92, an input/output interface 93, a communication interface 94, a power supply 95, and a communication bus 96.
Those skilled in the art will appreciate that the configuration shown in fig. 9 does not constitute a limitation of the virtual disk snapshot apparatus based on the virtual disk double active disaster recovery, and may include more or less components than those shown, for example, a sensor 97.
The functions of the functional modules of the virtual disk snapshot apparatus based on the virtualized disk double-active disaster recovery according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
As can be seen from the above, the embodiment of the present invention implements the snapshot of the IO replication layer.
It is understood that, if the virtual disk snapshot method based on the virtual disk double-active disaster recovery in the foregoing embodiments is implemented in the form of a software functional unit and is sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the present application may be substantially or partially implemented in the form of a software product, which is stored in a storage medium and executes all or part of the steps of the methods of the embodiments of the present application, or all or part of the technical solutions. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), an electrically erasable programmable ROM, a register, a hard disk, a removable magnetic disk, a CD-ROM, a magnetic disk, or an optical disk.
Based on this, an embodiment of the present invention further provides a computer readable storage medium, in which a virtual disk snapshot program based on a virtualized disk double-active disaster recovery is stored, and when the virtual disk snapshot program based on a virtualized disk double-active disaster recovery is executed by a processor, steps of the virtual disk snapshot method based on a virtualized disk double-active disaster recovery according to any one of the above embodiments are performed.
The functions of the functional modules of the computer-readable storage medium according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
As can be seen from the above, the embodiment of the present invention implements the snapshot of the IO replication layer.
In the present specification, the embodiments are described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same or similar parts between the embodiments are referred to each other. The device disclosed in the embodiment corresponds to the method disclosed in the embodiment, so that the description is simple, and the relevant points can be referred to the description of the method part.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The method, the device and the computer-readable storage medium for virtual disk snapshot based on the double-active disaster recovery of the virtual disk provided by the present application are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A virtual disk snapshot method based on double-active disaster recovery of a virtual disk is characterized in that the method is applied to Qemu with an IO copy function and comprises the following steps:
the method comprises the steps that a disk double-active disaster recovery function is started in the starting process of a preset virtual machine, a snapshot interface is set in an IO replication layer, and the IO replication layer is specifically a bdrv _ quorum layer;
receiving a disk snapshot creating instruction in the running process of a virtual machine, creating a virtual snapshot task in the IO replication layer, and issuing the same task to each child node of a block device simulation layer so that each child node can simultaneously execute the snapshot task in the IO replication layer suspension IO state;
receiving a disk snapshot deleting instruction in the running process of the virtual machine, creating a snapshot deleting task in the IO replication layer, searching for snapshot files to be deleted corresponding to all child nodes in the block device simulation layer, and simultaneously issuing a deleting task to each child node so that each child node can simultaneously delete the snapshot files to be deleted.
2. The virtual disk snapshot method based on the double-active disaster recovery of the virtualized disk as claimed in claim 1, wherein the issuing the same task to each child node of the block device emulation layer so that each child node executes the snapshot task at the same time in the IO replication layer suspension IO state comprises:
the same task is issued to each child node of the block device simulation layer, so that each child node simultaneously creates a new disk file as a block device simulation file;
when detecting that the new disk file creating operation of each child node is completed, sending an IO pause instruction of the IO copy layer;
sending a command for executing the cache writing operation to each child node so that each child node writes all caches in the qemu process into corresponding old disk files;
sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO replication layer;
and when detecting that each child node completes the backup file switching operation, sending an IO replication layer recovery IO instruction.
3. The virtual disk snapshot method based on the virtualized disk double-active disaster recovery as claimed in claim 2, wherein the step of executing the deletion operation on the snapshot file to be deleted simultaneously by each child node comprises:
each child node determines data to be copied by comparing the stored data of the new disk file and the stored data of the old disk file, wherein the data to be copied is the data which does not contain the corresponding old disk file in the current new disk file;
and all the corresponding data to be copied are copied to the new disk file from the corresponding old disk file by each child node.
4. The virtual disk snapshot method based on double-active disaster recovery of a virtualized disk as defined in claim 3, wherein after issuing the deletion task to each child node, the method further comprises:
when detecting that each child node finishes deleting the snapshot, sending feedback information of finishing deleting the snapshot to an upper-layer virtualization management platform so that the virtualization management platform deletes the old disk file of each child node after receiving the feedback information.
5. The virtual disk snapshot method based on the double-active disaster recovery of the virtualized disk as claimed in claim 3, wherein after issuing the same task to each child node of the block device emulation layer, the method further comprises:
when detecting that each child node completes snapshot creation operation, sending feedback information of successful snapshot creation to an upper layer virtualization management platform;
and when the fact that the child node snapshot creation fails is detected, reporting an error to the virtual machine.
6. The virtual disk snapshot method based on the double-active disaster recovery of the virtualized disk according to any one of claims 1 to 5, wherein before receiving the instruction to create the disk snapshot in the running process of the virtual machine, the method further comprises:
setting a disk snapshot creating option and a disk snapshot deleting option in a user management interface of a virtualization management platform where the virtual machine is located in advance, so that a user can issue the disk snapshot creating instruction and the disk snapshot deleting instruction through the user management interface.
7. A virtual disk snapshot device based on double-active disaster recovery of a virtual disk is characterized in that the device is applied to Qemu with IO copy function, and comprises the following components:
the double-active mode starting preset module is used for presetting a function of starting a double-active disaster tolerance of a magnetic disk in the starting process of the virtual machine;
the interface creating module is used for setting a snapshot interface in an IO replication layer in advance, wherein the IO replication layer is specifically a bdrv _ quorum layer;
the snapshot creating module is used for receiving a disk snapshot creating instruction in the running process of the virtual machine, creating a virtual snapshot task in the IO replication layer, and issuing the same task to each child node of the block device simulation layer so that each child node can execute the snapshot task at the same time in the IO replication layer in the IO suspension state;
and the snapshot deleting module is used for receiving a disk snapshot deleting instruction in the running process of the virtual machine, creating a snapshot deleting task in the IO copying layer, searching for the snapshot file to be deleted corresponding to all the child nodes in the block device simulation layer, and simultaneously issuing the deleting task to each child node so that each child node simultaneously executes deleting operation on the snapshot file to be deleted.
8. The virtual disk snapshot apparatus based on dual-active disaster recovery of virtualized disk as in claim 7, wherein the snapshot creation module comprises:
the new disk file creating submodule is used for issuing the same task to each child node of the block device simulation layer so that each child node simultaneously and respectively creates a new disk file to serve as a block device simulation file;
the IO suspension sub-module is used for sending an IO suspension instruction of the IO replication layer when detecting that the new disk file creation operation of each child node is completed;
the cache submodule is used for sending a command for executing the write cache operation to each child node so that each child node writes all caches in the qemu process into corresponding old disk files;
the backup file switching submodule is used for sending a backup file switching instruction to each child node so that each node replaces the corresponding old disk file with the corresponding new disk file to serve as a backup file of the IO replication layer;
and the IO recovery sub-module is used for sending the IO replication layer recovery IO instruction when detecting that each child node completes the backup file switching operation.
9. A virtual disk snapshot apparatus based on double-active disaster recovery of a virtualized disk, comprising a processor, wherein the processor is configured to implement the steps of the virtual disk snapshot method based on double-active disaster recovery of a virtualized disk according to any one of claims 1 to 6 when executing a computer program stored in a memory.
10. A computer-readable storage medium, wherein a virtual disk snapshot program based on a virtualized disk double-active disaster recovery is stored on the computer-readable storage medium, and when executed by a processor, the virtual disk snapshot program based on a virtualized disk double-active disaster recovery implements the steps of the virtual disk snapshot method based on a virtualized disk double-active disaster recovery method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011111555.5A CN112199162B (en) | 2020-10-16 | 2020-10-16 | Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011111555.5A CN112199162B (en) | 2020-10-16 | 2020-10-16 | Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112199162A CN112199162A (en) | 2021-01-08 |
| CN112199162B true CN112199162B (en) | 2023-02-28 |
Family
ID=74009307
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011111555.5A Active CN112199162B (en) | 2020-10-16 | 2020-10-16 | Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199162B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113608683B (en) * | 2021-06-30 | 2024-05-07 | 山东海量信息技术研究院 | Dual-live-disk cleaning method, system and related device |
| CN113961147A (en) * | 2021-10-26 | 2022-01-21 | 江苏安超云软件有限公司 | Method and application for recycling space from deleted blocks on cloud platform |
| CN114090489B (en) * | 2021-11-15 | 2024-04-12 | 深圳云豹智能有限公司 | IO expansion method and device based on virtio |
| US20230229561A1 (en) * | 2022-01-20 | 2023-07-20 | Pure Storage, Inc. | Container Recovery Layer Prioritization |
| US20230229355A1 (en) * | 2022-01-20 | 2023-07-20 | Pure Storage, Inc. | Immutable Nodes in a Container System |
| US20230229354A1 (en) * | 2022-01-20 | 2023-07-20 | Pure Storage, Inc. | Using Data Volumes to Store Container Images |
| CN115048190B (en) * | 2022-08-16 | 2022-11-01 | 江苏安超云软件有限公司 | Virtual machine snapshot management method, system and computer readable medium |
| CN116775353A (en) * | 2023-05-19 | 2023-09-19 | 北京百度网讯科技有限公司 | Method and device for repairing failed disk, electronic equipment and readable storage medium |
| CN117093332B (en) * | 2023-10-20 | 2024-02-27 | 杭州优云科技有限公司 | Method and device for realizing cloning of virtual machine |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103699459A (en) * | 2013-12-31 | 2014-04-02 | 汉柏科技有限公司 | Method and system for incremental backup of virtual machine data based on Qcow2 snapshots |
| CN105335253A (en) * | 2015-10-28 | 2016-02-17 | 北京百度网讯科技有限公司 | Method and device for creating virtual machine system disk snapshots |
| CN106527972A (en) * | 2016-10-09 | 2017-03-22 | 郑州云海信息技术有限公司 | K1-based multi-path method for realizing dual activity of storages |
| CN109101323A (en) * | 2018-09-10 | 2018-12-28 | 南京铱迅信息技术股份有限公司 | Snapshot implementing method based on qcow2 format under virtual machine operating status |
-
2020
- 2020-10-16 CN CN202011111555.5A patent/CN112199162B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103699459A (en) * | 2013-12-31 | 2014-04-02 | 汉柏科技有限公司 | Method and system for incremental backup of virtual machine data based on Qcow2 snapshots |
| CN105335253A (en) * | 2015-10-28 | 2016-02-17 | 北京百度网讯科技有限公司 | Method and device for creating virtual machine system disk snapshots |
| CN106527972A (en) * | 2016-10-09 | 2017-03-22 | 郑州云海信息技术有限公司 | K1-based multi-path method for realizing dual activity of storages |
| CN109101323A (en) * | 2018-09-10 | 2018-12-28 | 南京铱迅信息技术股份有限公司 | Snapshot implementing method based on qcow2 format under virtual machine operating status |
Non-Patent Citations (3)
| Title |
|---|
| 卫星接收站监控管理系统虚拟化平台设计;郑金秀，王强，王万玉;《机电技术》;20200630;全文 * |
| 基于存储双活技术的调度自动化系统高可靠性架构研究;宋英华，王志勇，李钟玮;《供用电》;20200331;全文 * |
| 虚拟机管理器中面向虚拟块设备的一种通用快照扩展机制;陈彬，蔡志平，肖侬，褚福勇;《计算机工程与科学》;20110531(第197期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112199162A (en) | 2021-01-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112199162B (en) | Disk snapshot method, device and medium based on virtualized disk double-active disaster tolerance | |
| US8635395B2 (en) | Method of suspending and resuming virtual machines | |
| US10503532B2 (en) | Creating a virtual machine clone of the host computing device and handling of virtual machine clone requests via an I/O filter | |
| US9940064B2 (en) | Live migration of virtual disks | |
| US9377963B2 (en) | Online virtual machine disk migration | |
| US9323550B2 (en) | Mechanism for providing virtual machines for use by multiple users | |
| US8464259B2 (en) | Migrating virtual machines configured with direct access device drivers | |
| US9870248B2 (en) | Page table based dirty page tracking | |
| US20160378528A1 (en) | Propagating changes from a virtual machine clone to a physical host device | |
| WO2017092219A1 (en) | Method and device for generating virtual machine snapshot | |
| US10303458B2 (en) | Multi-platform installer | |
| US11487523B2 (en) | Updating machine emulator | |
| CN106569876A (en) | Direct device visiting model-based virtual machine migrating method and apparatus | |
| CN111857966A (en) | Virtual machine snapshot creating method and device and computer readable storage medium | |
| US20210055946A1 (en) | Minimizing downtime when importing virtual machines from other platforms | |
| US20180083729A1 (en) | Packet-aware fault-tolerance method and system of virtual machines applied to cloud service, computer readable record medium and computer program product | |
| CN112328365A (en) | Virtual machine migration method, device, equipment and storage medium | |
| US9557980B2 (en) | Seamless application integration apparatus and method | |
| US11900097B2 (en) | Application downtime reduction using detached mode operation during operating system updates | |
| CN110968392A (en) | Method and device for upgrading virtualization simulator | |
| US20180336085A1 (en) | Crash dump extraction of guest failure | |
| JP2007058813A (en) | Verification device and verification method | |
| CN116775413A (en) | PCIE topology scanning method, device, equipment and readable storage medium | |
| CN109308232B (en) | Method, device and system for rollback after virtual machine live migration fault | |
| CN116540929A (en) | Virtualized reading method and device of disk array, electronic 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 |