Data backup system and method, medium and program product

Abstract

The invention relates to the technical field of disaster recovery, and discloses a data backup system and method, a medium and a program product. The system comprises the steps that a snapshot establishment request is sent to a virtual resource management node through a backup control module, a bitmap volume establishment request is sent to a backup module after a current snapshot volume is established, and data backup configuration information is sent to the backup module when a bitmap volume establishment completion response is received; when a backup module receives a bitmap volume establishment request, according to a backup type, a bitmap volume establishment instruction is generated and sent to FusionStorage for storage, after a current bitmap volume is established, a bitmap volume establishment completion response is sent to a backup control module, and when data backup configuration information is received, the current bitmap volume establishment completion response is sent to the backup control module. And performing data backup on the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume. According to the scheme provided by the embodiment of the invention, the backup of the data stored in the FusionStorage can be realized, and effective data protection can be carried out on the virtual machine stored in the FusionStorage.

Description

Technical Field

[0001] The present invention relates to the field of disaster recovery technology, and in particular to a data backup system, method, medium and program product. Background Art

[0002] Under the demand of computer technology, storage technology, computer network technology and software operating environment, in order to meet the environmental needs and reduce the hardware cost as much as possible, virtualization technology has been paid more and more attention and developed. Virtualization technology can run multiple virtual operating systems on a single machine, improve the utilization of hardware, and thus reduce production costs.

[0003] However, if a system does not have backup, recovery and disaster recovery, the business running on it cannot be guaranteed. When disasters such as force majeure occur, the system will crash. Even if the system is restored afterwards, it will still face problems such as data loss. As virtualization technology becomes increasingly important, backup and disaster recovery in virtualized environments are becoming increasingly important.

[0004] FusionCompute is a newly developed virtualization software that can enable a physical server to take on the work of multiple servers through computing virtualization, storage virtualization, network virtualization and other technologies. The storage in FusionCompute supports local hard disks, storage area networks, network attached storage and distributed storage. Traditional non-distributed storage is generally used as virtualized storage. However, for FusionStorage storage, FusionCompute does not provide storage disaster recovery related interfaces, so it is impossible to implement effective data backup for FusionStorage storage, and thus it is impossible to effectively protect virtual machines located in FusionStorage storage. Summary of the invention

[0005] The present invention provides a data backup system, method, medium and program product, which can realize data backup of FusionStorage storage and effectively protect the data of virtual machines stored in FusionStorage.

[0006] According to one aspect of the present invention, a data backup system is provided, including a backup control module and a backup module, wherein the backup module is pre-connected to a FusionStorage environment and is in communication connection with the FusionStorage storage, and the backup control module is in communication connection with a virtual resource management node;

[0007] The backup control module is used to send a snapshot creation request to the virtual resource management node, so that the virtual resource management node creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage according to the snapshot creation request, and after the current snapshot volume is created, send a bitmap volume creation request to the backup module, and upon receiving a bitmap volume creation completion response fed back by the backup module, send data backup configuration information to the backup module, and upon receiving a backup completion response fed back by the backup module, determine that the data backup is completed;

[0008] The backup module is used to generate a bitmap volume creation instruction and send it to FusionStorage storage according to the backup type when receiving a bitmap volume creation request, so that FusionStorage storage creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, send a bitmap volume creation completion response to the backup control module, and when receiving the data backup configuration information, perform data backup on the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, send a backup completion response to the backup control module.

[0009] Optionally, the data backup system further includes a virtual resource management node, a computing node and a FusionStorage storage, wherein the virtual resource management node is communicatively connected to the FusionStorage storage via the computing node;

[0010] The virtual resource management node is used to, upon receiving the snapshot creation request sent by the backup control module, obtain the identifier of the virtual machine to be backed up according to the snapshot creation request, and generate a snapshot creation instruction according to the identifier of the virtual machine to be backed up and send it to the computing node;

[0011] The computing node is used to obtain the identifier of the virtual machine to be backed up according to the snapshot creation instruction, and send the identifier of the virtual machine to be backed up to the FusionStorage storage;

[0012] The FusionStorage storage is used to establish a current snapshot volume corresponding to the virtual machine to be backed up according to the virtual machine identifier to be backed up, and when receiving a bitmap volume establishment instruction sent by the backup module, establish a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume establishment instruction.

[0013] Optionally, the backup control module is further used to send a mount volume request to the backup module after the current bitmap volume is established, and to send an unmount volume request to the backup module after the backup is completed;

[0014] The backup module is further configured to send a mount volume instruction to the FusionStorage storage when receiving a mount volume request, and send an unmount volume instruction to the FusionStorage storage when receiving an unmount volume request;

[0015] The FusionStorage storage is further used to mount the current snapshot volume and the current bitmap volume according to the mount volume instruction, and to unmount the current snapshot volume and the current bitmap volume according to the unmount volume instruction.

[0016] Optionally, the FusionStorage is also used for:

[0017] After the backup is completed, the current snapshot volume is retained, and when the backup type is determined to be an incremental backup, the historical snapshot volume created during the previous data backup is deleted.

[0018] Optionally, the backup module is specifically used to:

[0019] When generating a bitmap volume creation instruction, if the backup type is a full backup, the start snapshot parameter is determined to be empty, and the end snapshot parameter is determined to be the current snapshot volume;

[0020] If the backup type is incremental backup, the starting snapshot parameter is determined to be the historical snapshot volume created during the previous data backup, and the ending snapshot parameter is determined to be the current snapshot volume;

[0021] A bitmap volume creation instruction is generated according to the start snapshot parameter and the end snapshot parameter.

[0022] Optionally, the backup module is specifically used to:

[0023] According to the data backup configuration information, obtaining target bitmap information in the current bitmap volume;

[0024] The backup data corresponding to the virtual machine to be backed up is read from the current snapshot volume according to the target bitmap information, and the backup data is written into the backup storage.

[0025] According to another aspect of the present invention, there is provided a data backup method, which is applied to the data backup system according to any embodiment of the present invention, comprising:

[0026] Sending a snapshot creation request to the virtual resource management node through the backup control module, so that the virtual resource management node creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage according to the snapshot creation request, and after the current snapshot volume is created, sending a bitmap volume creation request to the backup module;

[0027] When receiving a bitmap volume creation request, the backup module generates a bitmap volume creation instruction according to the backup type and sends it to the FusionStorage storage, so that the FusionStorage storage creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, sends a bitmap volume creation completion response to the backup control module;

[0028] When the backup control module receives a bitmap volume establishment completion response fed back by the backup module, the backup control module sends data backup configuration information to the backup module, and the backup module backs up data of the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, sends a backup completion response to the backup control module;

[0029] The backup control module determines that the data backup is completed when receiving the backup completion response fed back by the backup module.

[0030] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a processor to implement the data backup method described in any embodiment of the present invention when executed.

[0031] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the data backup method according to any embodiment of the present invention is implemented.

[0032] The technical solution of the embodiment of the present invention is to send a snapshot creation request to the virtual resource management node through the backup control module, so that the virtual resource management node can create a snapshot in Fusion according to the snapshot creation request. A current snapshot volume corresponding to the virtual machine to be backed up is established in the storage storage, and after the current snapshot volume is established, a bitmap volume establishment request is sent to the backup module, and when a bitmap volume establishment completion response fed back by the backup module is received, data backup configuration information is sent to the backup module, and when a backup completion response fed back by the backup module is received, it is determined that the data backup is completed; through the backup module, when receiving the bitmap volume establishment request, a bitmap volume establishment instruction is generated according to the backup type and sent to the FusionStorage storage, so that the FusionStorage storage establishes the current bitmap volume corresponding to the current snapshot volume according to the bitmap volume establishment instruction, and after the current bitmap volume is established, a bitmap volume establishment completion response is sent to the backup control module, and when the data backup configuration information is received, data backup of the virtual machine to be backed up is performed according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, a backup completion response is sent to the backup control module; by setting the backup module to be pre-connected to the FusionStorage environment, and setting the backup control module to control and schedule the backup module to realize data backup, data backup of the FusionStorage storage can be realized, and effective data protection of the virtual machine located in the FusionStorage storage can be performed.

[0033] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0035] Figure 1 is a structural diagram of a data backup system provided according to Embodiment 1 of the present invention;

[0036] Figure 2 is a schematic diagram of the structure of another data backup system provided according to the first embodiment of the present invention;

[0037] Figure 3 is a schematic diagram of the structure of another data backup system provided according to the first embodiment of the present invention;

[0038] Figure 4 It is a flow chart of a data backup method provided according to the second embodiment of the present invention. DETAILED DESCRIPTION

[0039] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0040] It should be noted that the terms "first", "second", "target", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0041] Embodiment 1

[0042] Figure 1 A structural diagram of a data backup system is provided for the first embodiment of the present invention. The data backup system 10 may include a backup control module 11 and a backup module 12, wherein the backup module 12 is pre-connected to the FusionStorage environment and is in communication with the FusionStorage storage 15, and the backup control module 11 is in communication with the virtual resource management (Virtual Resource Management, VRM) node 13.

[0043] It should be noted that the storage of virtual machines in FusionCompute can be divided into two types in terms of usage, namely virtualized and non-virtualized. Virtualized data storage creates ordinary disks more slowly, but supports advanced features, such as creating thin disk technology, which can improve storage resource utilization and system security and reliability. Non-virtualized data storage has higher disk performance, but does not support advanced features of virtualized storage.

[0044] Since the FusionCompute management platform does not implement the relevant interfaces of FusionStorage disaster recovery, this embodiment adopts the method of directly connecting to the underlying FusionStorage storage to perform storage-related operations, and the operations related to virtual machine management are still connected to the FusionCompute management platform.

[0045] Among them, the backup module 12 is equipped with a supporting software package of FusionStorage, and is connected to the FusionStorage environment as a computing node. It can receive requests from the backup control module 11 through remote procedure call (RPC) communication, and can use the supporting software package to send instructions to the FusionStorage storage 15 to read or write data.

[0046] It should be noted that the backup module 12 needs to configure the storage network to access the FusionStorage environment. FusionStorage 8.0.1.SPH13 is taken as an example here. First, obtain the software installation package of the corresponding product, including FusionStorage_Tools_8.0.1.SPH13.tar.gz for installing node dependencies, and FusionStorage_Fsc_Cli_For_Multi_8.0.1.SPH13.tar.gz for installing the FSC_CLI command tool. Then, install the cloud hard disk backup (Volume Backup Service, VBS) node dependencies, including turning off the firewall, decompressing FusionStorage_Tools_8.0.1.SPH13.tar.gz, and entering the decompressed install_lib directory, executing the script according to the corresponding operating system, and installing dependencies. For example, CentOS: sh install_lib_for_centos.sh.

[0047] Finally, add the machine where the backup module 12 is located as a VBS node. Take the CentOS 7.5 machine as a computing node to join the FusionStorage cluster as an example, including (1) logging in to the FusionStorage management platform DeviceManager; (2) Enter the Cluster->Network->Network Topology interface, view the management network and storage network of the storage cluster, and configure the network for the machine to be added according to the network topology (joining the cluster requires access to the storage network and management network); (3) Enter the Service->VBS->Add Node interface, and configure the node according to the guided steps. The backup machine only needs to use the storage of the storage cluster and does not need to provide storage space for the storage cluster, so choose the computing node when selecting the node role; (4) Next, DeviceManager will automatically install the matching software package on the backup machine and wait for the installation to complete. After the installation, the backup machine can mount the FusionStorage storage volume to read and write data. At this point, the backup module 12 has successfully connected to the FusionStorage environment.

[0048] The backup control module 11 is used to send a snapshot creation request to the virtual resource management node 13, so that the virtual resource management node 13 creates a current snapshot volume corresponding to the virtual machine to be backed up in the Fusion Storage 15 according to the snapshot creation request, and after the current snapshot volume is created, sends a bitmap volume creation request to the backup module 12, and upon receiving a bitmap volume creation completion response fed back by the backup module 12, sends data backup configuration information to the backup module 12, and upon receiving a backup completion response fed back by the backup module 12, determines that the data backup is completed.

[0049] In this embodiment, the backup control module 11 is responsible for API communication with the VRM node 13 and scheduling and task execution related to virtual machine protection, and communicates with the backup module 12 via a remote procedure call (RPC). The backup module 12 can save the backup data in a local hard disk or a separate backup storage, and the number of backup modules 12 can be expanded as needed.

[0050] Specifically, when a virtual machine backup is required, the user can configure a backup strategy in the backup control module 11, such as the backup type, backup object, backup time, etc.; the backup control module 11 can schedule the backup task execution according to the backup strategy. When the task starts to execute, the backup control module 11 can send a snapshot creation request to the VRM node 13 by calling the Rest Api (Representational State Transfer Application Programming Interface). The snapshot creation request may include information such as the virtual machine identifier to be backed up and the request type identifier to control the VRM node 13 to create a snapshot volume of a common type for the virtual machine to be backed up in the computing node 14, and wait for the snapshot volume to be created.

[0051] Secondly, the backup control module 11 can also call the Rest API to obtain the configuration information of the virtual machine to be backed up, such as the processor, memory, disk, network, etc., through the VRM node 13, and can send the obtained configuration information to the backup module 12, and the backup module 12 can store the received configuration information. Among them, the VRM node 13 is the management platform of the Fusion Compute host, which provides a Rest API interface to the outside.

[0052] In this embodiment, after the current snapshot volume is established, the backup control module 11 can generate a bitmap volume establishment request based on information such as the backup type, snapshot volume identifier, and request type identifier, and can send the bitmap volume establishment request to the backup module 12, so that the backup module 12 creates a current bitmap volume corresponding to the current snapshot volume based on the bitmap volume establishment request. When the bitmap volume establishment completion response is received from the backup module 12, it indicates that the bitmap volume establishment is completed. The backup control module 11 can send data backup configuration information to the backup module 12, that is, backup task related information, such as virtual machine disks, etc., and notify the backup module 12 to start the backup task. The backup control module 11 can query the progress of the task at regular intervals, and when the backup completion response is received from the backup module 12, it can be determined that the data backup is completed.

[0053] The backup module 12 is used to generate a bitmap volume creation instruction according to the backup type when receiving a bitmap volume creation request and send it to the FusionStorage storage 15, so that the FusionStorage storage 15 creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, send a bitmap volume creation completion response to the backup control module 11, and when receiving the data backup configuration information, perform data backup on the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, send a backup completion response to the backup control module 11.

[0054] Specifically, when the backup module 12 receives a bitmap volume creation request, it can parse the content to obtain the backup type, which may include incremental backup and full backup. Then, the backup module 12 can generate a bitmap volume creation instruction based on the backup type by executing the installed fsc_cli command line, and can send the bitmap volume creation instruction to the FusionStorage storage 15 to request the FusionStorage storage 15 to create the corresponding bitmap volume. After the bitmap volume is created, the backup module 12 can send a response message to the backup control module 11 to inform the backup control module 11. Afterwards, when the data backup configuration information is received, the backup data can be read from the current snapshot volume according to the data backup configuration information and the bitmap information in the current bitmap volume, and the backup data can be written to the backup storage or the local disk to realize the data backup of the virtual machine to be backed up. After the data backup is completed, the backup module 12 can also send a backup completion response to the backup control module 11 to inform the backup control module 11.

[0055] The technical solution of the embodiment of the present invention is to send a snapshot creation request to the virtual resource management node 13 through the backup control module 11, so that the virtual resource management node 13 can create a snapshot in Fusion according to the snapshot creation request. The current snapshot volume corresponding to the virtual machine to be backed up is established in the Storage storage, and after the current snapshot volume is established, a bitmap volume establishment request is sent to the backup module 12, and upon receiving the bitmap volume establishment completion response fed back by the backup module 12, data backup configuration information is sent to the backup module 12, and upon receiving the backup completion response fed back by the backup module 12, it is determined that the data backup is completed; through the backup module 12, when receiving the bitmap volume establishment request, according to the backup type, a bitmap volume establishment instruction is generated and sent to the FusionStorage storage 15, so that the FusionStorage storage 15 establishes the current bitmap volume corresponding to the current snapshot volume according to the bitmap volume establishment instruction, and after the current bitmap volume is established, a bitmap volume establishment completion response is sent to the backup control module 11, and when the data backup configuration information is received, data of the virtual machine to be backed up is backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, a backup completion response is sent to the backup control module 11; by setting the backup module 12 to pre-connect to the Fusion Storage environment, and set the backup control module 11 to control and schedule the backup module 12 to realize data backup, which can realize data backup of FusionStorage storage 15 and effectively protect the data of the virtual machine stored in Fusion Storage.

[0056] Optional, such as Figure 2 As shown, the data backup system 10 may also include a virtual resource management node 13, a computing node 14 and a FusionStorage storage 15. The virtual resource management node 13 is communicated with the FusionStorage storage 15 through the computing node 14; wherein the computing node 14 may be a computing node agent (Compute NodeAgent, CNA) host, which is used to provide virtualization services, is managed by the VRM node 13, and cannot be directly accessed from the outside. The CNA host can be connected to the FusionStorage environment as a computing node 14 or a storage node.

[0057] The virtual resource management node 13 is used to obtain the virtual machine identifier to be backed up according to the snapshot creation request when receiving the snapshot creation request sent by the backup control module 11, and generate a snapshot creation instruction according to the virtual machine identifier to be backed up and send it to the computing node 14.

[0058] The computing node 14 is used to obtain the ID of the virtual machine to be backed up according to the snapshot creation instruction, and send the ID of the virtual machine to be backed up to the FusionStorage storage 15; wherein the computing node 14 may be deployed with multiple virtual machines. Specifically, the computing node 14 may generate a snapshot creation command according to the ID of the virtual machine to be backed up, and send the snapshot creation command to the FusionStorage storage 15.

[0059] The FusionStorage storage 15 is used to establish a current snapshot volume corresponding to the virtual machine to be backed up according to the virtual machine identifier to be backed up, and to establish a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume establishment instruction when receiving the bitmap volume establishment instruction sent by the backup module 12. The FusionStorage storage 15 can achieve the creation of corresponding snapshot volumes and bitmap volumes according to parameters such as the virtual machine identifier to be backed up through pre-configured functional modules.

[0060] Specifically, FusionStorage storage 15 can create a snapshot corresponding to the virtual machine to be backed up, and store the snapshot in an existing snapshot volume to obtain the current snapshot volume; or, it can create a snapshot corresponding to the virtual machine to be backed up, and create a new snapshot volume to store it to obtain the current snapshot volume.

[0061] In a specific example, the structure of the data backup system 10 can be as follows: Figure 3 As shown. The backup control module 11 can access the VRM node 13 through the Rest Api interface, and indirectly access the computing node 14 through the VRM node 13, and can communicate with the backup module 12 through RPC. The backup module 12 is pre-connected to the FusionStorage environment, and can read or write data to the Fusion Storage storage 15 according to the request information of the backup control module 11 to achieve data backup. The backup data can be stored in a separate backup storage.

[0062] Optionally, the backup control module 11 is further configured to send a volume mount request to the backup module 12 after the current bitmap volume is established, and to send a volume unmount request to the backup module 12 after the backup is completed;

[0063] The backup module 12 is further configured to send a volume mount instruction to the FusionStorage storage 15 when receiving a volume mount request, and send a volume unmount instruction to the FusionStorage storage 15 when receiving a volume unmount request;

[0064] The FusionStorage storage 15 is further used to mount the current snapshot volume and the current bitmap volume according to the mount volume instruction, and to unmount the current snapshot volume and the current bitmap volume according to the unmount volume instruction.

[0065] In this embodiment, the backup module 12 can execute the pre-installed fsc_cli command line to send the corresponding instruction to the FusionStorage storage 15. For example, when the backup module 12 receives a volume mount request or a volume unmount request, it can generate a volume mount instruction or a volume unmount instruction by executing the pre-installed corresponding fsc_cli command line. By mounting and unmounting the snapshot volume and the bitmap volume, access control to the backup data can be achieved.

[0066] Optionally, the FusionStorage storage 15 is further used to: after the backup is completed, retain the current snapshot volume, and when it is determined that the backup type is an incremental backup, delete the historical snapshot volume created during the previous data backup.

[0067] It should be noted that in traditional bitmap volume technology, each snapshot point corresponds to a ChangeId. When a snapshot is deleted, the incremental data from the snapshot to the current point can be obtained through the ChangeId of the deleted snapshot. However, FusionStorage's bitmap volume technology is different from traditional methods. The snapshot must be retained to create a bitmap volume of the differential data between snapshots. Therefore, in this embodiment, if it is a full backup, the snapshot volume created during the current data backup is retained for the next incremental backup; if it is an incremental backup, the snapshot volume created during the current data backup is still retained, and the historical snapshot volume created during the last data backup is deleted.

[0068] Optionally, the backup module 12 is specifically used to: when generating a bitmap volume creation instruction, if the backup type is a full backup, determine that the starting snapshot parameter is empty, and determine that the ending snapshot parameter is the current snapshot volume; if the backup type is an incremental backup, determine that the starting snapshot parameter is the historical snapshot volume created during the previous data backup, and determine that the ending snapshot parameter is the current snapshot volume; generate a bitmap volume creation instruction based on the starting snapshot parameter and the ending snapshot parameter.

[0069] Specifically, when generating a bitmap volume creation instruction, if it is a full backup, the start snapshot parameter in the bitmap volume creation parameter can be set to empty, and the end snapshot parameter can be set to the current snapshot volume, thereby creating a full backup bitmap volume. If it is an incremental backup, the start snapshot parameter can be set to the historical snapshot volume created during the previous data backup, and the end snapshot parameter can be set to the current snapshot volume, thereby obtaining the incremental bitmap volume between the two snapshot volumes, that is, the incremental data between the two backups.

[0070] Optionally, the backup module 12 is specifically used to: obtain target bitmap information in the current bitmap volume according to the data backup configuration information; read the backup data corresponding to the virtual machine to be backed up from the current snapshot volume according to the target bitmap information, and write the backup data to the backup storage.

[0071] Specifically, when backing up the data of the virtual machine to be backed up, the backup module 12 can search for matching target bitmap information in the current bitmap volume according to the disk information sent by the backup control module 11, and then read matching snapshot data from the current snapshot volume based on the target bitmap information as the backup data corresponding to the virtual machine to be backed up. Further, the backup module 12 can write the backup data to the backup storage to realize data backup.

[0072] Embodiment 2

[0073] Figure 4 A flowchart of a data backup method is provided for the second embodiment of the present invention. This embodiment is applicable to the case of backing up a virtual machine using FusionStorage storage 15 on a FusionCompute platform. The method can be executed by the data backup system 10 provided in the first embodiment of the present invention. Figure 4 As shown, the method includes:

[0074] S210. Send a snapshot creation request to the virtual resource management node through the backup control module, so that the virtual resource management node creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage according to the snapshot creation request, and after the current snapshot volume is created, sends a bitmap volume creation request to the backup module.

[0075] In this embodiment, the backup module 12 can be connected to the FusionStorage environment by pre-configuring the storage network for the backup module 12. The backup control module 11 can send a snapshot creation request to the VRM node 13 by calling the VRM RestApi. The VRM node 13 is responsible for managing the computing node 14 where the virtual machine is deployed. According to the snapshot creation request of the backup control module 11, a corresponding snapshot creation command can be generated and sent to the computing node 14, so that the computing node 14 can create the current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage 15. Among them, each computing node 14 is pre-connected to the FusionStorage environment.

[0076] S220. When receiving a bitmap volume creation request, the backup module generates a bitmap volume creation instruction according to the backup type and sends it to the FusionStorage storage, so that the FusionStorage storage creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, sends a bitmap volume creation completion response to the backup control module.

[0077] Among them, the backup type may include full backup and incremental backup. Specifically, the backup module 12 can read the relevant information of the current snapshot volume from the FusionStorage storage 15, and can determine the parameters for creating a bitmap volume based on the backup type and the relevant information of the current snapshot volume. Typically, if it is a full backup, the start snapshot parameter in the parameters for creating a bitmap volume can be set to empty, and the end snapshot parameter can be set to the current snapshot volume; if it is an incremental backup, the start snapshot parameter can be set to the historical snapshot volume created during the previous data backup, and the end snapshot parameter can be set to the current snapshot volume. Then, based on the parameters for creating a bitmap volume, a bitmap volume creation instruction can be generated.

[0078] S230. When the backup control module receives a bitmap volume establishment completion response fed back by the backup module, the backup control module sends data backup configuration information to the backup module, and the backup module backs up data of the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, sends a backup completion response to the backup control module.

[0079] The data backup configuration information may be the virtual machine disk information to be backed up, etc. The backup module 12 may first search for bitmap information matching the data backup configuration information from the current bitmap volume, and then search for backup data matching the bitmap information from the current snapshot volume. Further, the backup data may be written to a local disk or a separate backup storage to implement data backup.

[0080] S240: When receiving a backup completion response fed back by the backup module, the backup control module determines that the data backup is completed.

[0081] The technical solution provided by the embodiment of the present invention is to send a snapshot creation request to the virtual resource management node 13 through the backup control module 11, so that the virtual resource management node 13 creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage 15 according to the snapshot creation request, and after the current snapshot volume is created, send a bitmap volume creation request to the backup module 12; when the backup module 12 receives the bitmap volume creation request, it generates a bitmap volume creation instruction according to the backup type and sends it to the FusionStorage storage 15, so that the FusionStorage storage 15 creates the current snapshot volume corresponding to the FusionStorage storage 15 according to the bitmap volume creation instruction. The current bitmap volume is established, and after the current bitmap volume is established, a bitmap volume establishment completion response is sent to the backup control module 11; when the backup control module 11 receives the bitmap volume establishment completion response fed back by the backup module 12, the data backup configuration information is sent to the backup module 12, and the backup module 12 backs up the data of the backup virtual machine according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, a backup completion response is sent to the backup control module 11; when the backup control module 11 receives the backup completion response fed back by the backup module 12, it is determined that the data backup is completed; by setting the backup module 12 to pre-connect to the Fusion Storage environment, and setting the backup control module 11 to control and schedule the backup module 12 to realize data backup, data backup of the FusionStorage storage 15 can be realized, and effective data protection can be performed on the virtual machines stored in the Fusion Storage.

[0082] In the technical solution of the present disclosure, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0083] Embodiment 3

[0084] The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein. In some embodiments, the data backup method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit. In some embodiments, part or all of the computer program may be loaded and / or installed on an electronic device via a read-only memory (ROM) and / or a communication unit. When the computer program is loaded into a random access memory (RAM) and executed by a processor, one or more steps of the data backup method described above may be performed. Alternatively, in other embodiments, the processor may be configured to perform the data backup method by any other appropriate means (e.g., by means of firmware).

[0085] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays, application specific integrated circuits, application specific standard products, systems on a chip, load programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0086] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0087] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical fiber, a portable compact disk read-only memory, an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0088] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a cathode ray tube or a liquid crystal display) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0089] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area networks, wide area networks, blockchain networks, and the Internet.

[0090] A computing system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship to each other. The server may be a cloud server.

[0091] This embodiment may also include a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the data backup method provided by any embodiment of the present invention.

[0092] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0093] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data backup system, characterized in that: It includes a backup control module and a backup module, wherein the backup module is pre-connected to the FusionStorage environment and is connected to the FusionStorage storage communication, and the backup control module is connected to the virtual resource management node communication; The backup control module is used to send a snapshot creation request to the virtual resource management node, so that the virtual resource management node creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage according to the snapshot creation request, and after the current snapshot volume is created, send a bitmap volume creation request to the backup module, and upon receiving a bitmap volume creation completion response fed back by the backup module, send data backup configuration information to the backup module, and upon receiving a backup completion response fed back by the backup module, determine that the data backup is completed; The backup module is used to generate a bitmap volume creation instruction and send it to FusionStorage storage according to the backup type when receiving a bitmap volume creation request, so that FusionStorage storage creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, send a bitmap volume creation completion response to the backup control module, and when receiving the data backup configuration information, perform data backup on the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, send a backup completion response to the backup control module.

2. The data backup system according to claim 1, characterized in that: It also includes a virtual resource management node, a computing node and a FusionStorage storage, wherein the virtual resource management node is connected to the FusionStorage storage through the computing node; The virtual resource management node is used to, upon receiving the snapshot creation request sent by the backup control module, obtain the identifier of the virtual machine to be backed up according to the snapshot creation request, and generate a snapshot creation instruction according to the identifier of the virtual machine to be backed up and send it to the computing node; The computing node is used to obtain the identifier of the virtual machine to be backed up according to the snapshot creation instruction, and send the identifier of the virtual machine to be backed up to the FusionStorage storage; The FusionStorage storage is used to establish a current snapshot volume corresponding to the virtual machine to be backed up according to the virtual machine identifier to be backed up, and when receiving a bitmap volume establishment instruction sent by the backup module, establish a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume establishment instruction.

3. The data backup system according to claim 2, characterized in that: The backup control module is further used to send a mount volume request to the backup module after the current bitmap volume is established, and to send an unmount volume request to the backup module after the backup is completed; The backup module is further configured to send a mount volume instruction to the FusionStorage storage when receiving a mount volume request, and send an unmount volume instruction to the FusionStorage storage when receiving an unmount volume request; The FusionStorage storage is further used to mount the current snapshot volume and the current bitmap volume according to the mount volume instruction, and to unmount the current snapshot volume and the current bitmap volume according to the unmount volume instruction.

4. The data backup system according to claim 3, characterized in that: The FusionStorage storage is also used for: After the backup is completed, the current snapshot volume is retained, and when the backup type is determined to be an incremental backup, the historical snapshot volume created during the previous data backup is deleted.

5. The data backup system according to claim 1, characterized in that: The backup module is specifically used for: When generating a bitmap volume creation instruction, if the backup type is a full backup, the start snapshot parameter is determined to be empty, and the end snapshot parameter is determined to be the current snapshot volume; If the backup type is incremental backup, the starting snapshot parameter is determined to be the historical snapshot volume created during the previous data backup, and the ending snapshot parameter is determined to be the current snapshot volume; A bitmap volume creation instruction is generated according to the start snapshot parameter and the end snapshot parameter.

6. The data backup system according to claim 1, characterized in that: The backup module is specifically used for: According to the data backup configuration information, obtaining target bitmap information in the current bitmap volume; The backup data corresponding to the virtual machine to be backed up is read from the current snapshot volume according to the target bitmap information, and the backup data is written into the backup storage.

7. A data backup method, characterized in that: The data backup system applied to any one of claims 1 to 6 comprises: Sending a snapshot creation request to the virtual resource management node through the backup control module, so that the virtual resource management node creates a current snapshot volume corresponding to the virtual machine to be backed up in the FusionStorage storage according to the snapshot creation request, and after the current snapshot volume is created, sending a bitmap volume creation request to the backup module; When receiving a bitmap volume creation request, the backup module generates a bitmap volume creation instruction according to the backup type and sends it to the FusionStorage storage, so that the FusionStorage storage creates a current bitmap volume corresponding to the current snapshot volume according to the bitmap volume creation instruction, and after the current bitmap volume is created, sends a bitmap volume creation completion response to the backup control module; When the backup control module receives a bitmap volume establishment completion response fed back by the backup module, the backup control module sends data backup configuration information to the backup module, and the backup module backs up data of the virtual machine to be backed up according to the data backup configuration information, the current snapshot volume and the current bitmap volume, and after the backup is completed, sends a backup completion response to the backup control module; The backup control module determines that the data backup is completed when receiving the backup completion response fed back by the backup module.

8. The method according to claim 7, characterized in that Backup types include full backup and incremental backup.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to enable a processor to implement the data backup method according to any one of claims 7 to 8 when executed.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the data backup method according to any one of claims 7 to 8 when executed by a processor.

Images