WO2020233311A1 - 一种基于云平台数据中心的虚拟机备份方法及装置 - Google Patents

一种基于云平台数据中心的虚拟机备份方法及装置 Download PDF

Info

Publication number
WO2020233311A1
WO2020233311A1 PCT/CN2020/085588 CN2020085588W WO2020233311A1 WO 2020233311 A1 WO2020233311 A1 WO 2020233311A1 CN 2020085588 W CN2020085588 W CN 2020085588W WO 2020233311 A1 WO2020233311 A1 WO 2020233311A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
cloud platform
disk
backup
data center
Prior art date
Application number
PCT/CN2020/085588
Other languages
English (en)
French (fr)
Inventor
张翼
俞义方
赵培
戚晨
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20810430.7A priority Critical patent/EP3974973A4/en
Priority to US17/612,652 priority patent/US20220237089A1/en
Publication of WO2020233311A1 publication Critical patent/WO2020233311A1/zh

Links

Images

Classifications

    • 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/1458—Management of the backup or restore process
    • 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/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
    • 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
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • 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/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments
    • 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/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
    • 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
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/815—Virtual
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • the present disclosure relates to, but is not limited to, the field of computer technology, and in particular relates to a method and device for virtual machine backup based on a cloud platform data center.
  • the embodiments of the present disclosure provide a virtual machine backup method and device based on a cloud platform data center, which can support rapid recovery of virtual machines in various failure scenarios of the cloud platform data center.
  • an embodiment of the present disclosure provides a virtual machine backup method based on a cloud platform data center, including: creating an internal snapshot based on a disk image of a virtual machine in the cloud platform data center; and obtaining the internal snapshot based on the internal snapshot Disk backup data of the virtual machine.
  • an embodiment of the present disclosure provides a virtual machine backup device based on a cloud platform data center, including: an internal snapshot creation module configured to create an internal snapshot based on a disk image of a virtual machine in the cloud platform data center;
  • the first backup module is configured to obtain disk backup data of the virtual machine based on the internal snapshot.
  • an embodiment of the present disclosure provides a computer-readable storage medium storing a computer program that, when executed, realizes the steps of the above-mentioned virtual machine backup method based on a cloud platform data center.
  • Figure 1 is an example diagram of a schematic architecture of a cloud platform data center
  • Figure 2 is a schematic diagram of the process of performing full backups of virtual machines in the cloud platform data center through external snapshots
  • Figure 3 is a flow chart of performing full backup of virtual machines in the cloud platform data center through external snapshots
  • Figure 4 is a schematic diagram of the process of incremental backup of virtual machines in the cloud platform data center through external snapshots
  • Figure 5 is a flowchart of incremental backup of virtual machines in the cloud platform data center through external snapshots
  • FIG. 6 is a flowchart of a virtual machine backup method based on a cloud platform data center provided by an embodiment of the disclosure
  • FIG. 7 is a schematic diagram of a process of performing full and incremental backups of virtual machines in a cloud platform data center through internal snapshots in an exemplary embodiment of the present disclosure
  • FIG. 8 is a flowchart of performing full and incremental backups of virtual machines in the cloud platform data center through internal snapshots in an exemplary embodiment of the present disclosure
  • FIG. 9 is a schematic diagram of a process of creating an internal snapshot in an exemplary embodiment of the present disclosure.
  • FIG. 10 is an application example diagram of a virtual machine backup method based on a cloud platform data center provided by an exemplary embodiment of the present disclosure
  • Fig. 11 is a schematic diagram of a virtual machine backup device based on a cloud platform data center provided by an embodiment of the disclosure.
  • Fig. 1 is a schematic diagram of a schematic architecture of a cloud platform data center.
  • VMs virtual machines
  • KVM Kernel-based Virtual Machine
  • FIG. 1 a schematic diagram of a schematic architecture of a cloud platform data center.
  • VMs virtual machines
  • KVM Kernel-based Virtual Machine
  • FIG. 1 a schematic diagram of a schematic architecture of a cloud platform data center.
  • VMs virtual machines
  • KVM Kernel-based Virtual Machine
  • one or more virtual machines can be deployed on one server, and multiple servers can share storage resources provided by storage devices.
  • the present disclosure does not limit the architecture and deployment mode of the cloud platform data center. It should be noted that the present disclosure takes the backup of a virtual machine in a KVM virtualization scenario as an example for description.
  • the node represents the physical storage file where the disk data of the virtual machine is located.
  • the internal snapshot created based on the disk image of the virtual machine in the cloud platform data center is used to obtain the disk backup data of the virtual machine, so as to support the rapid recovery of the virtual machine in various failure scenarios of the cloud platform data center. Disaster recovery purpose.
  • Figure 2 is a schematic diagram of the process of performing full backup of virtual machines in the cloud platform data center through external snapshots
  • Figure 3 is a flowchart of performing full backups of virtual machines in the cloud platform data center through external snapshots.
  • FIGS. 2 and 3 only a virtual machine in a KVM virtualization scenario is used as an example for description.
  • the differential disk scenario multiple virtual machines can share a parent node, and each virtual machine corresponds to its own child node, and the child nodes point to the parent node.
  • the process of performing a full backup of a virtual machine in a cloud platform data center through an external snapshot includes the following operations:
  • Figure 4 is a schematic diagram of the process of incremental backup of virtual machines in the cloud platform data center through external snapshots
  • Figure 5 is a flowchart of incremental backup of virtual machines in the cloud platform data center through external snapshots.
  • FIGS. 4 and 5 only one virtual machine in the KVM virtualization scenario is used as an example for description.
  • the process of incremental backup of virtual machines in the cloud platform data center through external snapshots includes the following operations:
  • the disk incremental data of the virtual machine will be stored on the grandchild node where the virtual machine is currently running. It can be seen that the process of using external snapshots for incremental backup uses the virtual machine disk file itself as a storage container for incremental data, which makes the coupling between incremental backup data and the virtual machine's original disk file higher, which will increase The operability of remote disaster recovery backup. Moreover, the use of external snapshots for incremental backup also requires changes to the disk file chain structure of the virtual machine, which changes the file chain structure of the virtual machine.
  • the snapshot is saved in a single qcow2 file, and the data after the snapshot creation time point is recorded in a new qcow2 file, and the original image file becomes the backup file of the new qcow2 file. That is, the parent node (read-only). After multiple snapshots are created, these files form a file chain.
  • the embodiments of the present disclosure provide a virtual machine backup method and device based on a cloud platform data center.
  • a virtualized cloud platform data center for example, a virtual machine is damaged, etc.
  • a disk image based on a virtual machine The created internal snapshot is used for disaster recovery backup, which supports the rapid recovery of virtual machines under various failure scenarios in the cloud platform data center to achieve disaster recovery purposes.
  • the embodiments of the present disclosure implement virtual machine backup based on internal snapshots, which can maintain the relatively stable structure of the original virtual machine without changing the disk file chain structure of the original virtual machine, and the data exported by the backup is independent of the virtual machine disk image itself, which is convenient Export to achieve disaster tolerance.
  • FIG. 6 is a flowchart of a virtual machine backup method based on a cloud platform data center provided by an embodiment of the disclosure. As shown in Figure 6, the virtual machine backup method provided in this embodiment includes:
  • the snapshot and subsequent changes can be saved in the original qcow2 file (e.g., equivalent to the child nodes in Figure 2 and Figure 4, It can be a file node in qcow2 format).
  • S602 may include at least one of the following:
  • the snapshot points are used to obtain the corresponding disk full backup data and the disk incremental backup between any two snapshot points. Data, so as to realize the full backup and incremental backup of the disk data of the virtual machine on the cloud platform data center. Moreover, by backing up the disk data of the virtual machine on the cloud platform data center, it can be supported to restore the virtual machine to a state of normal operation time through the backup disk data when the virtual machine encounters an unrecoverable failure.
  • the method of this embodiment may further include: exporting the disk backup data to at least one of the following: a storage device outside the cloud platform data center where the virtual machine is located, and a remote cloud platform data center.
  • the disk backup data by exporting the disk backup data to a storage device outside the cloud platform data center, it can be supported to fetch from an external storage device when the storage device in the cloud platform data center is damaged and the virtual machine fails. Back to the corresponding disk backup data to restore the virtual machine.
  • exporting the disk backup data to the remote cloud platform data center it can support the recovery of virtual machines in the remote cloud platform data center to continue running when the local cloud platform data center is damaged by a disaster.
  • the method of this embodiment may further include at least one of the following:
  • the management data of the virtual machine may include the specification parameters of the virtual machine, for example, the name of the virtual machine, the number of CPU cores, the memory size, and the configuration of the graphics card.
  • the management data of the virtual machine can be stored by the management device of the cloud platform data center.
  • the physical host (for example, server) in the cloud platform data center can generate a virtual machine configuration file according to the management data of the virtual machine, and then start or rebuild the corresponding virtual machine based on the virtual machine configuration file.
  • the virtual machine recovery operation in various failure scenarios in the cloud platform data center can be supported.
  • FIG. 7 is a schematic diagram of a process of performing full and incremental backups of virtual machines in a cloud platform data center through internal snapshots in an exemplary embodiment of the present disclosure
  • FIG. 8 is a process diagram of performing internal snapshots on the cloud through internal snapshots in an exemplary embodiment of the present disclosure
  • a flowchart of full and incremental backup of virtual machines in the platform data center In FIGS. 7 and 8, only a virtual machine in the KVM virtualization scenario is taken as an example for description, and the node represents the physical storage file (qcow2 file) where the disk data of the virtual machine is located.
  • qcow2 file can use L1 table, L2 table and cluster table to manage data.
  • Each entry in the cluster table stores data
  • each entry in the L2 table stores the address of the cluster
  • each entry in the L1 table stores the starting address of the L2 table.
  • the process of performing full and incremental backups of virtual machines in the cloud platform data center through internal snapshots includes the following operations:
  • the snapshot information includes header, extradata, identification (id) and name (name); Yes, the information of multiple snapshots is stored in a continuous cluster;
  • the full disk backup data at the time corresponding to the internal snapshot can be obtained; based on any two internal snapshots, the disk between the time points corresponding to the two internal snapshots can be obtained Incremental backup data.
  • FIG. 10 is a diagram of an application example of a virtual machine backup method provided by an exemplary embodiment of the present disclosure.
  • the application scenario of this embodiment is in a virtualized cloud platform environment of a large data center.
  • the virtual machine backup method provided by this exemplary embodiment includes:
  • S44 to S46 can be triggered periodically according to requirements, that is, disk incremental backup data can be periodically obtained and exported, or S44 to S46 can be manually triggered, that is, at a set time Click to get disk incremental backup data and export it.
  • this disclosure is not limited to this.
  • the virtual machine after the backup of the disk backup data and management data of the virtual machine, the virtual machine can be restored in the following scenarios: When the virtual machine in the local cloud platform data center is abnormal, the local Disk backup data and management data backed up by the local cloud platform data center to restore the virtual machine; when the local cloud platform data center encounters a disaster or damage, you can use the disk backup data and virtual machine management data exported to the remote cloud platform data center , Restore the virtual machine to the remote cloud platform data center.
  • the embodiments of the present disclosure can support disaster recovery backup of business virtual machines in the cloud platform data center.
  • By performing full backup and incremental backup based on the internal disk snapshots of the virtual machine the original disk file chain structure of the virtual machine is not changed.
  • Realize full backup and incremental backup of virtual machine disk image data which can greatly reduce the operational complexity of remote disaster recovery backup, and greatly reduce the impact on the original virtual machine.
  • FIG. 11 is a schematic diagram of a virtual machine backup device based on a cloud platform data center provided by an embodiment of the disclosure.
  • the virtual machine backup device provided in this embodiment may include: an internal snapshot creation module 501, configured to create an internal snapshot based on a disk image of a virtual machine in a cloud platform data center; a first backup module 502, It is constructed to obtain disk backup data of the virtual machine based on the internal snapshot.
  • the first backup module 502 may be configured to obtain disk backup data of the virtual machine based on the internal snapshot in at least one of the following ways: Based on any internal snapshot, obtain the time corresponding to the internal snapshot of the virtual machine The full disk backup data at a point; based on any two internal snapshots, obtain the disk incremental backup data of the virtual machine between the two internal snapshots corresponding to the time points.
  • the device of this embodiment may further include: an export module configured to export the disk backup data after the first backup module obtains the disk backup data of the virtual machine Back up data to at least one of the following: storage devices outside the cloud platform data center where the virtual machine is located, and remote cloud platform data centers.
  • the device of this embodiment may further include: a second backup module configured to execute at least one of the following: in the cloud platform data center where the virtual machine is located Back up the management data of the virtual machine; back up the management data of the virtual machine in the remote cloud platform data center.
  • a second backup module configured to execute at least one of the following: in the cloud platform data center where the virtual machine is located Back up the management data of the virtual machine; back up the management data of the virtual machine in the remote cloud platform data center.
  • embodiments of the present disclosure also provide a computer-readable storage medium that stores a computer program that implements the aforementioned virtual machine backup method when the computer program is executed, such as the steps shown in FIG. 6, FIG. 8, or FIG. 10.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种基于云平台数据中心的虚拟机备份方法，包括：基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；以及基于内部快照，获取虚拟机的磁盘备份数据。本公开可以支持在云平台数据中心的各种故障场景下实现快速恢复虚拟机。

Description

一种基于云平台数据中心的虚拟机备份方法及装置 技术领域
本公开涉及但不限于计算机技术领域，尤指涉及一种基于云平台数据中心的虚拟机备份方法及装置。
背景技术
目前，较多的数据中心采用统一的云平台部署各类业务虚拟机，达到资源聚集、建设集中、节约资源、部署快捷、维护方便的目的。各类业务虚拟机可以运行在集中的云平台数据中心上。在这种场景下，如果云平台数据中心遭受到灾难或者云平台数据中心上运行的虚拟机遭到破坏，需要通过恢复虚拟机来恢复中断的业务。
发明内容
本公开的实施例提供了一种基于云平台数据中心的虚拟机备份方法及装置，可以支持在云平台数据中心的各种故障场景下实现快速恢复虚拟机。
一方面，本公开的一个实施例提供一种基于云平台数据中心的虚拟机备份方法，包括：基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；基于所述内部快照，获取所述虚拟机的磁盘备份数据。
另一方面，本公开的一个实施例提供一种基于云平台数据中心的虚拟机备份装置，包括：内部快照创建模块，被构造成基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；第一备份模块，被构造成基于所述内部快照，获取所述虚拟机的磁盘备份数据。
另一方面，本公开的一个实施例提供一种计算机可读存储介质，存储有计算机程序，所述计算机程序被执行时实现上述基于云平台数据中心的虚拟机备份方法的步骤。
本公开的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本公开而了解。本公开的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1为一种云平台数据中心的示意性架构示例图；
图2为通过外部快照对云平台数据中心的虚拟机进行全量备份的过程示意图；
图3为通过外部快照对云平台数据中心的虚拟机进行全量备份的流程图；
图4为通过外部快照对云平台数据中心的虚拟机进行增量备份的过程示意图；
图5为通过外部快照对云平台数据中心的虚拟机进行增量备份的流程图；
图6为本公开实施例提供的基于云平台数据中心的虚拟机备份方法的流程图；
图7为本公开一示例性实施例中通过内部快照对云平台数据中心的虚拟机进行全量和增量备份的过程示意图；
图8为本公开一示例性实施例中通过内部快照对云平台数据中心的虚拟机进行全量和增量备份的流程图；
图9为本公开示例性实施例中内部快照的创建过程示意图；
图10为本公开一示例性实施例提供的基于云平台数据中心的虚拟机备份方法的应用示例图；
图11为本公开实施例提供的基于云平台数据中心的虚拟机备份 装置的示意图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白，下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本公开中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图1为一种云平台数据中心的示意性架构示例图。如图1所示，在云平台数据中心，可以基于服务器集群部署多个虚拟机(VM，Virtual Machine)，比如，采用KVM(Kernel-based Virtual Machine)虚拟化技术部署虚拟机。在本文中，可以在一台服务器上部署一个或多个虚拟机，且多台服务器可以共享存储设备提供的存储资源。本公开对于云平台数据中心的架构和部署方式并不限定。需要说明的是，本公开以对KVM虚拟化场景下的虚拟机进行备份为例进行说明。
目前，针对云平台数据中心的虚拟机，大多采用差分磁盘镜像的外部快照方式来实现对虚拟机某一时刻磁盘数据的全量和增量备份。下面基于图2至图5说明通过外部快照方式对云平台数据中心的虚拟机进行全量备份和增量备份的过程。在本文中，节点表示虚拟机的磁盘数据所在的物理存储文件。在本公开中，利用基于云平台数据中心的虚拟机的磁盘镜像创建的内部快照，获取虚拟机的磁盘备份数据，从而在云平台数据中心的各种故障场景下，支持快速恢复虚拟机，达到容灾目的。
图2为通过外部快照对云平台数据中心的虚拟机进行全量备份的过程示意图；图3为通过外部快照对云平台数据中心的虚拟机进行全量备份的流程图。在图2和图3中仅以KVM虚拟化场景下的一个虚拟机为例进行说明。在差分磁盘场景下，多个虚拟机可以共享一个父节 点，且每个虚拟机对应各自的子节点，子节点均指向该父节点。
如图2和图3所示，通过外部快照对云平台数据中心的虚拟机进行全量备份的过程包括以下操作：
S11、创建虚拟机的全量备份文件节点；此时，该全量备份文件节点与虚拟机原磁盘之间没有关联；
S12、创建虚拟机现在运行的叶子节点(即孙子节点)；此时，该孙子节点与虚拟机原磁盘之间没有关联；
S13、修改孙子节点的父节点为虚拟机原运行的节点(即子节点)；此时，孙子节点与子节点之间建立关联；
S14、创建快照使得虚拟机运行在孙子节点上；
S15、将虚拟机原磁盘数据(对应父节点和子节点)合并备份至全量备份文件节点中。
由此可见，在使用差分磁盘的外部快照方式进行全量备份时，需要对虚机的磁盘文件链结构进行改动，改变了虚拟机的文件链结构。
图4为通过外部快照对云平台数据中心的虚拟机进行增量备份的过程示意图；图5为通过外部快照对云平台数据中心的虚拟机进行增量备份的流程图。在图4和图5中仅以KVM虚拟化场景下的一个虚拟机为例进行说明。
如图4和图5所示，通过外部快照对云平台数据中心的虚拟机进行增量备份的过程包括以下操作：
S21、创建虚拟机备份使用的快照节点；此时，该快照节点与虚拟机原磁盘之间没有关联；
S22、创建虚拟机现在运行的叶子节点(即孙子节点)；此时，该孙子节点与虚拟机原磁盘之间没有关联；
S23、修改孙子节点的父节点为虚拟机原运行的节点(即子节点)；此时，该孙子节点与子节点之间建立关联；
S24、修改虚拟机备份使用的快照节点的父节点为虚拟机原运行的节点(即子节点)；此时，该快照节点与子节点之间建立关联；
S25、创建快照使得虚拟机运行于孙子节点上。此时，父节点、子节点以及虚拟机现在运行的孙子节点对应于虚拟机的新磁盘，父节点、子节点以及该快照节点对应于虚拟机在该快照节点对应时间点的备份磁盘。
在快照节点对应时间点之后的一段时长内，虚拟机的磁盘增量数据会存储在虚拟机现在运行的孙子节点上。由此可见，采用外部快照进行增量备份的过程利用了虚拟机磁盘文件本身作为增量数据的存储容器，使得增量备份数据与虚拟机原磁盘文件之间的耦合度较高，会加大异地容灾备份的可操作性难度。而且，采用外部快照方式进行增量备份同样需要对虚拟机的磁盘文件链结构进行改动，改变了虚拟机的文件链结构。
在创建外部快照时，快照被保存在单独一个qcow2文件中，且创建快照时间点之后的数据被记录到一个新的qcow2文件中，原镜像文件成为新的qcow2文件的备份文件(backing file)，也就是父节点(只读)，在创建多个快照后，这些文件形成一个文件链。
本公开实施例提供一种基于云平台数据中心的虚拟机备份方法及装置，在虚拟化的云平台数据中心的各种故障场景下(比如，虚拟机遭受破坏等)，基于虚拟机的磁盘镜像创建的内部快照进行容灾备份，从而支持在云平台数据中心的各种故障场景下快速恢复虚拟机，达到容灾目的。而且，本公开实施例基于内部快照实现虚拟机备份，可以不改变原虚拟机的磁盘文件链结构，保持原虚拟机的相对稳定的结构，且备份导出的数据独立于虚拟机磁盘镜像本身，便于导出从而实现容灾。
图6为本公开实施例提供的基于云平台数据中心的虚拟机备份方法的流程图。如图6所示，本实施例提供的虚拟机备份方法，包括：
S601、基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；
S602、基于内部快照，获取虚拟机的磁盘备份数据。
在本公开实施例中，针对KVM虚拟化场景下的虚拟机，通过创 建内部快照，可以将快照及后续变动都保存在原来的qcow2文件(例如，相当于图2和图4中的子节点，其可以为qcow2格式的文件节点)内。
在一示例性实施例中，S602可以包括以下至少一项：
基于任一个内部快照，获取虚拟机在该内部快照对应时间点的磁盘全量备份数据；以及
基于任两个内部快照，获取虚拟机在这两个内部快照分别对应的时间点之间的磁盘增量备份数据。
本示例性实施例中，可以通过在虚拟机磁盘内部设置不同的快照点(快照对应的时间点)，利用快照点获取对应的磁盘全量备份数据以及任两个快照点之间的磁盘增量备份数据，从而实现对于云平台数据中心上的虚拟机的磁盘数据的全量备份以及增量备份。而且，通过在云平台数据中心上备份虚拟机的磁盘数据，可以支持在虚拟机遇到不可修复的故障时，通过备份的磁盘数据将虚拟机恢复到某一正常运行时刻的状态。
在一示例性实施例中，在S602之后，本实施例的方法还可以包括：导出磁盘备份数据至以下至少一项：虚拟机所在云平台数据中心之外的存储设备、异地云平台数据中心。
在本示例性实施例中，通过将磁盘备份数据导出到云平台数据中心之外的存储设备，可以支持在云平台数据中心内的存储设备受损导致虚拟机故障时，从外部的存储设备取回相应的磁盘备份数据，进行虚拟机恢复。通过将磁盘备份数据导出至异地云平台数据中心，可以支持在本地云平台数据中心遇到灾难受损时，在异地云平台数据中心恢复虚拟机继续运行。
在一示例性实施例中，本实施例的方法还可以包括以下至少一项：
在虚拟机所在云平台数据中心备份虚拟机的管理数据；以及
在异地云平台数据中心备份虚拟机的管理数据。
在本文中，虚拟机的管理数据可以包括虚拟机的规格参数，比如， 虚拟机的名称、CPU核数、内存大小、显卡配置等信息。虚拟机的管理数据可以由云平台数据中心的管理设备进行存储。云平台数据中心内的物理主机(比如，服务器)可以根据虚拟机的管理数据，生成虚拟机配置文件，进而基于虚拟机配置文件，启动或重建相应的虚拟机。
本示例性实施例中，基于备份的虚拟机的管理数据，可以支持在云平台数据中心的各种故障场景下的虚拟机恢复操作。
图7为本公开一示例性实施例中的通过内部快照对云平台数据中心的虚拟机进行全量和增量备份的过程示意图；图8为本公开一示例性实施例中的通过内部快照对云平台数据中心的虚拟机进行全量和增量备份的流程图。在图7和图8中仅以KVM虚拟化场景下的一个虚拟机为例进行说明，且节点表示虚拟机的磁盘数据所在的物理存储文件(qcow2文件)。
在本文中，qcow2文件可以使用L1表、L2表和簇(cluster)表来管理数据。cluster表中每个条目存放数据，L2表的每个条目存放cluster的地址，L1表的每个条目存放L2表的起始地址。
如图7和图8所示，本实施例提供的通过内部快照对云平台数据中心的虚拟机进行全量和增量备份的过程包括以下操作：
S31、基于虚拟机的差分磁盘镜像，创建内部快照1；
在本文中，如图9所示，内部快照的创建过程如下：
一、申请新的cluster并拷贝原L1表(old L1 table)，需要注意的是，如图9所示的拷贝得到L1’表保存原L1表的内容；
二、在L1表内修改L2表偏移(offset)值，其中，快照后将使用新的L2表进行写入时复制(cow，copy on write)，原L2表不会被修改；
三、在L2表内修改数据偏移(data offset)值，其中，快照后将使用新的cluster进行写入时复制，原数据簇不会被修改；
四、更新所有已经分配簇的再计数(refcount)值，即原簇的再计数值全部加1；
五、新分配连续n个簇，将所有快照(snapshot)信息一起写入，其中，快照信息包括头部(header)、额外数据(extradata)、标识(id)及名称(name)；需要注意的是，多个snapshot的信息是保存在连续的cluster中的；
六、更新新的snapshot offset地址到qcow2文件头(header)中，以便于找到所有的快照。
S32、基于内部快照1获取虚拟机在内部快照1对应时间点的磁盘全量备份数据；
在本文中，可以通过寻找原来的L1表(比如图9中的L1’表)，获取原来快照时刻原来存储数据的地址空间，然后，获取相应的磁盘数据。
S33、基于虚拟机的差分磁盘镜像，创建内部快照2；其中，关于内部快照2的创建过程可以参照图9所示，故于此不再赘述。
S34、基于内部快照1和内部快照2，获取内部快照2与内部快照1之间的磁盘增量备份数据(即内部快照2对应的时间点与内部快照1对应的时间点之间虚拟机的磁盘增量备份数据)。
在本文中，可以根据内部快照1获取内部快照1对应时间点的L1表，从而获取内部快照1对应时间点的存储数据的地址空间，然后提取该地址空间中的数据即可获取内部快照2与内部快照1之间的增量数据，因为一旦内部快照2建立之后，内部快照1对应的存储数据空间中的数据将不会被改动，新的数据将被写入内部快照2对应的L1表对应的存储数据的地址空间中。
在本示例性实施例中，基于任一个内部快照，可以获取该内部快照对应时间点的磁盘全量备份数据；基于任两个内部快照，可以获取这两个内部快照对应的时间点之间的磁盘增量备份数据。
通过图2至图5与图7和图8的对比可知，在本示例性实施例中，虚拟机的磁盘数据进行全量以及增量备份的操作不需要改变原虚拟机的磁盘文件链的结构；而且，虚拟机的全量以及增量的磁盘备份数据 直接独立于构建虚拟机本身的磁盘镜像文件而存在，方便进行磁盘备份数据的导出。
图10为本公开一示例性实施例提供的虚拟机备份方法的应用示例图。本实施例的应用场景为大型数据中心的虚拟化云平台环境中。如图10所示，本示例性实施例提供的虚拟机备份方法包括：
S41、针对云平台数据中心的虚拟机的磁盘镜像文件进行内部快照操作，创建第一内部快照；
S42、基于虚拟机的第一内部快照，获取虚拟机的磁盘全量备份数据；
S43、将磁盘全量备份数据的数据镜像以及虚拟机的管理数据导出至异地云平台数据中心的存储库中进行备份，并在本地云平台数据中心创建虚拟机的管理数据的备份；
S44、针对虚拟机的磁盘镜像文件进行内部快照操作，创建第二内部快照；
S45、针对虚拟机的第一内部快照和第二内部快照，获取虚拟机的磁盘增量备份数据；
S46、将磁盘增量备份数据的数据镜像以及虚拟机的管理数据导出至异地云平台数据中心的存储库中进行备份，并在本地云平台数据中心创建虚拟机的管理数据的备份。
需要说明的是，在实际应用中，可以根据需求，定期触发执行S44至S46，即周期性获取磁盘增量备份数据并进行导出，或者，可以人为触发执行S44至S46，即可以在设定时间点获取磁盘增量备份数据并进行导出。然而，本公开对此并不限定。
在本示例性实施例中，具备虚拟机的磁盘备份数据和管理数据的备份后可以在遇到如下场景时进行虚拟机的恢复：当本地云平台数据中心的虚拟机出现异常，可以使用本地的磁盘备份数据和本地云平台数据中心备份的管理数据对虚拟机进行恢复；当本地云平台数据中心遇到灾难和破坏，可以使用导出到异地云平台数据中心的磁盘备份数 据和虚拟机的管理数据，将虚拟机恢复至异地云平台数据中心。
本公开实施例可以支持在云平台数据中心对业务虚拟机进行容灾备份，通过对虚拟机进行基于磁盘内部快照的全量备份以及增量备份，在不改变虚拟机原本磁盘文件链结构的基础上实现对于虚拟机磁盘镜像数据的全量备份以及增量备份，从而能够大大降低异地容灾备份的操作复杂性，对原虚拟机的影响也大大降低。
图11为本公开实施例提供的基于云平台数据中心的虚拟机备份装置的示意图。如图11所示，本实施例提供的虚拟机备份装置可以包括：内部快照创建模块501，被构造成基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；第一备份模块502，被构造成基于内部快照，获取虚拟机的磁盘备份数据。
在一示例性实施例中，第一备份模块502可以被构造成通过以下至少之一方式基于内部快照，获取虚拟机的磁盘备份数据：基于任一个内部快照，获取虚拟机在该内部快照对应时间点的磁盘全量备份数据；基于任两个内部快照，获取虚拟机在这两个内部快照分别对应的时间点之间的磁盘增量备份数据。
在一示例性实施例中，基于图11所示的虚拟机备份装置，本实施例的装置还可以包括：导出模块，被构造成在第一备份模块获取虚拟机的磁盘备份数据之后，导出磁盘备份数据至以下至少一项：虚拟机所在云平台数据中心之外的存储设备、异地云平台数据中心。
在一示例性实施例中，基于图11所述的虚拟机备份装置，本实施例的装置还可以包括：第二备份模块，被构造成执行以下至少之一：在虚拟机所在云平台数据中心备份虚拟机的管理数据；在异地云平台数据中心备份虚拟机的管理数据。
关于本实施例提供的装置的相关说明可以参照上述方法实施例的描述，故于此不再赘述。
此外，本公开实施例还提供一种计算机可读存储介质，存储有计算机程序，该计算机程序被执行时实现上述的虚拟机备份方法，比如， 图6、图8或图10所示的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (10)

  1. 一种基于云平台数据中心的虚拟机备份方法，包括：
    基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；以及
    基于所述内部快照，获取所述虚拟机的磁盘备份数据。
  2. 根据权利要求1所述的方法，其中，所述基于所述内部快照，获取所述虚拟机的磁盘备份数据的步骤，包括以下至少一个步骤：
    基于任一个所述内部快照，获取所述虚拟机在所述内部快照对应时间点的磁盘全量备份数据；以及
    基于任两个所述内部快照，获取所述虚拟机在所述两个内部快照分别对应的时间点之间的磁盘增量备份数据。
  3. 根据权利要求1所述的方法，其中，所述基于所述内部快照，获取所述虚拟机的磁盘备份数据的步骤之后，所述方法还包括：导出所述磁盘备份数据至以下至少一项：所述虚拟机所在云平台数据中心之外的存储设备、异地云平台数据中心。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述方法还包括以下至少一个步骤：
    在所述虚拟机所在云平台数据中心备份所述虚拟机的管理数据；以及
    在异地云平台数据中心备份所述虚拟机的管理数据。
  5. 根据权利要求1所述的方法，其中，所述虚拟机的磁盘镜像为差分磁盘镜像。
  6. 一种基于云平台数据中心的虚拟机备份装置，其中，包括：
    内部快照创建模块，被构造成基于云平台数据中心的虚拟机的磁盘镜像，创建内部快照；
    第一备份模块，被构造成基于所述内部快照，获取所述虚拟机的磁盘备份数据。
  7. 根据权利要求6所述的装置，其中，所述第一备份模块被构造成通过以下至少之一方式基于所述内部快照，获取所述虚拟机的磁盘备份数据：
    基于任一个所述内部快照，获取所述虚拟机在所述内部快照对应时间点的磁盘全量备份数据；以及
    基于任两个所述内部快照，获取所述虚拟机在所述两个内部快照分别对应的时间点之间的磁盘增量备份数据。
  8. 根据权利要求6所述的装置，其中，所述装置还包括：导出模块，被构造成在所述第一备份模块获取所述虚拟机的磁盘备份数据之后，导出所述磁盘备份数据至以下至少一项：所述虚拟机所在云平台数据中心之外的存储设备、异地云平台数据中心。
  9. 根据权利要求6至8中任一项所述的装置，其中，所述装置还包括：第二备份模块，被构造成执行以下至少之一：
    在所述虚拟机所在云平台数据中心备份所述虚拟机的管理数据；以及
    在异地云平台数据中心备份所述虚拟机的管理数据。
  10. 一种计算机可读存储介质，其中，存储有计算机程序，所述计算机程序被执行时实现如权利要求1至5中任一项所述的虚拟机备份方法的步骤。
PCT/CN2020/085588 2019-05-20 2020-04-20 一种基于云平台数据中心的虚拟机备份方法及装置 WO2020233311A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20810430.7A EP3974973A4 (en) 2019-05-20 2020-04-20 METHOD AND DEVICE FOR BACKING UP A VIRTUAL MACHINE BASED ON A CLOUD PLATFORM DATA CENTER
US17/612,652 US20220237089A1 (en) 2019-05-20 2020-04-20 Virtual machine backup method and apparatus based on cloud platform data center

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910417508.4 2019-05-20
CN201910417508.4A CN111966526A (zh) 2019-05-20 2019-05-20 一种基于云平台数据中心的虚拟机备份方法及装置

Publications (1)

Publication Number Publication Date
WO2020233311A1 true WO2020233311A1 (zh) 2020-11-26

Family

ID=73357949

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/085588 WO2020233311A1 (zh) 2019-05-20 2020-04-20 一种基于云平台数据中心的虚拟机备份方法及装置

Country Status (4)

Country Link
US (1) US20220237089A1 (zh)
EP (1) EP3974973A4 (zh)
CN (1) CN111966526A (zh)
WO (1) WO2020233311A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112965857A (zh) * 2021-03-03 2021-06-15 上海英方软件股份有限公司 一种基于块备份快速恢复数据的方法及系统
CN113467887B (zh) * 2021-06-25 2024-02-23 深信服科技股份有限公司 故障修复方法、宿主机以及可读存储介质
CN113535476A (zh) * 2021-07-14 2021-10-22 中盈优创资讯科技有限公司 一种云资产快速恢复的方法及装置
CN115098299B (zh) * 2022-06-28 2024-02-06 江苏安超云软件有限公司 一种虚拟机的备份方法、容灾方法、装置及设备
CN116521452B (zh) * 2023-06-30 2023-09-22 建信金融科技有限责任公司 灾备系统以及基于灾备系统的业务处理方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110252208A1 (en) * 2010-04-12 2011-10-13 Microsoft Corporation Express-full backup of a cluster shared virtual machine
CN105068856A (zh) * 2015-07-16 2015-11-18 武汉噢易云计算有限公司 基于镜像快照的虚拟机备份系统及备份方法
CN105094948A (zh) * 2015-07-31 2015-11-25 杭州华为数字技术有限公司 一种虚拟机的系统镜像文件更新方法、云数据中心及系统
CN107092538A (zh) * 2017-03-14 2017-08-25 平安科技（深圳）有限公司 虚拟机数据备份方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9785523B2 (en) * 2011-06-20 2017-10-10 Microsoft Technology Licensing, Llc Managing replicated virtual storage at recovery sites
CN106919477B (zh) * 2017-03-03 2020-05-22 上海爱数信息技术股份有限公司 一种虚拟磁盘的解析方法及系统
US10802747B2 (en) * 2017-11-30 2020-10-13 Veritas Technologies Llc Performing backup operations using replicas

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110252208A1 (en) * 2010-04-12 2011-10-13 Microsoft Corporation Express-full backup of a cluster shared virtual machine
CN105068856A (zh) * 2015-07-16 2015-11-18 武汉噢易云计算有限公司 基于镜像快照的虚拟机备份系统及备份方法
CN105094948A (zh) * 2015-07-31 2015-11-25 杭州华为数字技术有限公司 一种虚拟机的系统镜像文件更新方法、云数据中心及系统
CN107092538A (zh) * 2017-03-14 2017-08-25 平安科技（深圳）有限公司 虚拟机数据备份方法及系统

Also Published As

Publication number Publication date
EP3974973A4 (en) 2023-06-14
EP3974973A1 (en) 2022-03-30
US20220237089A1 (en) 2022-07-28
CN111966526A (zh) 2020-11-20

Similar Documents

Publication Publication Date Title
WO2020233311A1 (zh) 一种基于云平台数据中心的虚拟机备份方法及装置
US11467755B2 (en) Method and system for enabling agentless backup and restore operations on a container orchestration platform
US9250824B2 (en) Backing up method, device, and system for virtual machine
US20190163591A1 (en) Remote Data Replication Method and System
US8738883B2 (en) Snapshot creation from block lists
US9275060B1 (en) Method and system for using high availability attributes to define data protection plans
US10146630B1 (en) Block changes framework for delta file incremental backup
US9165012B2 (en) Periodic file system checkpoint manager
US20150286432A1 (en) Efficient flashcopy backup target volume allocation from a shared resource pool
US9817724B2 (en) Efficient FlashCopy backup target volume allocation with reuse and a shared resource pool
CN104216801B (zh) 一种面向虚拟化环境的数据复制方法及系统
JP2009506399A (ja) バックアップイメージを仮想化するシステム及び方法
US9454315B2 (en) Efficient flashcopy backup target volume allocation from a shared resource pool while ingesting a flashcopy backup in a repository
CN106357703B (zh) 集群切换方法与设备
US11307934B1 (en) Virtual backup and restore of virtual machines
EP3731099B1 (en) System and method for accelerating application service restoration
CN112256400A (zh) 一种虚拟机快照管理方法及装置
US10976952B2 (en) System and method for orchestrated application protection
US9690500B2 (en) Efficient flashcopy backup target volume allocation
US9672118B2 (en) Collision avoidance using dynamic target volume allocation
US11429492B2 (en) Protecting and identifying virtual machines that have the same name in a multi-tenant distributed environment
CN112148532A (zh) 硬盘数据的批量恢复方法、装置、存储介质及电子设备
CN111949441A (zh) 用于可扩展备份搜索的系统和方法
US20240143454A1 (en) System and techniques for backing up scalable computing objects
CN103838639A (zh) 一种恢复虚拟磁盘元数据的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20810430

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020810430

Country of ref document: EP

Effective date: 20211220