Data backup method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a data backup method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of obtaining data information of to-be-backed-up data in a source end cloud platform and source virtual private cloud information used for storing the to-be-backed-up data; determining a source virtual private cloud based on the source virtual private cloud information; a disaster recovery virtual private cloud is configured on the disaster recovery end cloud platform; based on the data information, determining the category of the to-be-backed-up data; if the category is metadata, pulling metadata to be backed up from the source virtual private cloud, and converting a data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; and backing up the backup metadata to the disaster recovery virtual private cloud. By adopting the method, data backup can be carried out across cloud platforms, so that data loss is prevented.

Description

Technical Field

[0001] The present application relates to the field of data protection technology, and in particular to a data backup method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] As enterprises become increasingly dependent on cloud computing technology, more and more core business systems of governments and enterprises are gradually migrating and running stably in the cloud environment. In this context, the security of cloud data and the continuity of business operations have become key issues that need to be solved urgently.

[0003] However, many disaster recovery solutions on the market are generally highly dependent on a single cloud service provider. This situation greatly limits the flexible scheduling and efficient use of data across platforms and regions, and also poses a potential threat to the overall security of data. More seriously, this single-dependency model makes enterprises lack sufficient response capabilities and alternative plans when facing emergencies such as cloud platform failures, data leaks or policy changes, thereby exacerbating the risk of data loss. Summary of the invention

[0004] Based on this, it is necessary to provide a data backup method, apparatus, computer equipment, computer-readable storage medium and computer program product that can perform data backup across cloud platforms in response to the above technical problems.

[0005] In a first aspect, the present application provides a data backup method, comprising:

[0006] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0007] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0008] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0009] In one embodiment, the step of converting the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain the backup metadata includes:

[0010] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0011] In one embodiment, the method further comprises:

[0012] If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0013] In one embodiment, the method further comprises:

[0014] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0015] In one embodiment, obtaining the recovery information includes:

[0016] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0017] In one embodiment, performing metadata recovery based on the recovery information includes:

[0018] Based on the component configuration information of the source cloud platform, a recovery component is created on the recovery virtual private cloud; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in the recovery order.

[0019] In a second aspect, the present application also provides a data backup device, including:

[0020] An acquisition module is used to acquire data information of data to be backed up in a source cloud platform and source virtual private cloud information for storing the data to be backed up; determine a source virtual private cloud based on the source virtual private cloud information; and configure a disaster recovery virtual private cloud on a disaster recovery cloud platform;

[0021] A conversion module is used to determine the category of the data to be backed up based on the data information; if the category is metadata, the metadata to be backed up is pulled from the source virtual private cloud, and the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0022] The backup module is used to back up the backup metadata to the disaster recovery virtual private cloud.

[0023] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0024] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0025] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0026] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0027] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0028] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0029] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0030] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0031] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0032] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0033] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0034] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0035] The above-mentioned data backup method, apparatus, computer equipment, computer-readable storage medium and computer program product obtain data information of the data to be backed up in the source cloud platform and the source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform; determine the category of the data to be backed up based on the data information; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; and back up the backup metadata to the disaster recovery virtual private cloud. By performing data backup across cloud platforms, when enterprises face emergencies such as cloud platform failures, data leaks or policy changes, they are provided with coping capabilities and alternative plans, thereby preventing data loss. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0037] FIG1 is an application environment diagram of a data backup method in one embodiment;

[0038] FIG2 is a schematic diagram of a flow chart of a data backup method in one embodiment;

[0039] FIG3 is a schematic diagram of a metadata backup protocol in one embodiment;

[0040] FIG4 is a detailed schematic diagram of a data backup method in another embodiment;

[0041] FIG5 is a block diagram of a data backup device in one embodiment;

[0042] FIG. 6 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0044] The data backup method provided in the embodiment of the present application can be applied to the application environment shown in Figure 1. Among them, the source cloud platform 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be integrated on the server 104, or it can be placed on the cloud or other network servers. Obtain the data information of the data to be backed up in the source cloud platform and the source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform; based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; back up the backup metadata to the disaster recovery virtual private cloud. Among them, the source cloud platform 102 is a cloud service platform. The server 104 is an independent physical server, or it can be a server cluster or distributed system composed of multiple physical servers, or it can be a cloud server that provides cloud computing services.

[0045] In an exemplary embodiment, as shown in FIG. 2 , a data backup method is provided, which is described by taking the method applied to the server 104 in FIG. 1 as an example, and includes the following steps 202 to 206. Among them:

[0046] Step 202, obtaining data information of the data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determining the source virtual private cloud based on the source virtual private cloud information; and configuring the disaster recovery virtual private cloud on the disaster recovery cloud platform.

[0047] Optionally, the source cloud platform and the disaster recovery cloud platform may be cloud platforms such as Tianyi Cloud, Tencent Cloud, Alibaba Cloud, and Huawei Cloud.

[0048] Among them, the virtual private cloud is a set of logically isolated virtual network environments built for cloud servers, which are configured and managed by users themselves; it allows users to create an isolated, dedicated network space in a public cloud computing environment to deploy their own applications, servers, databases and other resources, and communicate through network connections. The source virtual private cloud is a virtual private cloud that stores the data to be backed up on the source cloud platform, and the disaster recovery virtual private cloud is a virtual private cloud that backs up data. Optionally, the source virtual private cloud and the disaster recovery virtual private cloud can communicate through the network.

[0049] Furthermore, when data backup is required, the source cloud platform and the disaster recovery cloud platform will be configured in advance. Optionally, the configuration includes: data that needs to be backed up in the source cloud platform, authorization information of the source cloud platform and the disaster recovery cloud platform, etc. for data backup configuration.

[0050] The information of the source virtual private cloud is used to determine the source virtual private cloud that needs to be connected and to perform data backup.

[0051] Optionally, the data information includes information such as the category of data to be backed up and the size of data to be backed up.

[0052] Exemplarily, data information of data to be backed up in Tencent Cloud and source virtual private cloud information in Tencent Cloud used to store data to be backed up are obtained; based on the source virtual private cloud information, a source virtual private cloud that needs to be connected and data backed up is determined; and a disaster recovery virtual private cloud is configured in Tianyi Cloud.

[0053] Step 204, based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata.

[0054] The categories of data to be backed up include metadata and business data.

[0055] Among them, the unified metadata backup protocol is pre-designed for multi-cloud protocol compatibility. The metadata structure of cloud platforms such as Tianyi Cloud, Tencent Cloud, Alibaba Cloud and Huawei Cloud is converted into a unified disaster recovery structure.

[0056] Exemplarily, based on data information, the category of data to be backed up is determined; if the category of data to be backed up is metadata, the metadata to be backed up is pulled from the source virtual private cloud, and through a unified metadata backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0057] Step 206: back up the backup metadata to the disaster recovery virtual private cloud.

[0058] Among them, the backup metadata will be stored in the storage medium of the disaster recovery virtual private cloud.

[0059] Exemplarily, the backup metadata is backed up to a virtual private cloud in Tianyi Cloud.

[0060] The above-mentioned data backup method, apparatus, computer equipment, computer-readable storage medium and computer program product obtain data information of the data to be backed up in the source cloud platform and the source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform; determine the category of the data to be backed up based on the data information; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; and back up the backup metadata to the disaster recovery virtual private cloud. By performing data backup across cloud platforms, when enterprises face emergencies such as cloud platform failures, data leaks or policy changes, they are provided with coping capabilities and alternative plans, thereby preventing data loss.

[0061] In an exemplary embodiment, the method of converting the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain the backup metadata includes:

[0062] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0063] As shown in FIG3 , a unified metadata backup protocol (Cloud Service IaaS) is used to achieve multi-cloud protocol compatibility and convert the structure of metadata. The unified metadata backup protocol includes a protocol for converting the structure of metadata in Ctyun Cloud Service IaaS into a disaster recovery structure, a protocol for converting the structure of metadata in Tencent Cloud Service IaaS into a disaster recovery structure, a protocol for converting the structure of metadata in Ali Cloud Service IaaS into a disaster recovery structure, and a protocol for converting the structure of metadata in Huawei Cloud Service IaaS into a disaster recovery structure. The target backup protocol is one of the above protocols determined by the source cloud platform. Among them, IaaS is Infrastructure as a Service; backUp MetaData is backup metadata; create Snapshot is a function provided by the cloud platform to create a snapshot for a specified disk, volume or data set; a snapshot is a static copy of data at a certain point in time, which records the state of the data at that point in time; by creating a snapshot, data backup, recovery and migration operations can be easily implemented; importMetaData is importing metadata.

[0064] In this embodiment, by pre-designing a unified metadata backup protocol for different components in different cloud platforms, it is determined that the target backup protocol corresponding to the metadata to be backed up is a protocol that converts the structure of the metadata in Tencent Cloud into a disaster recovery structure; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0065] In this embodiment, through a unified metadata backup protocol, data on different cloud platforms can be converted into a unified disaster recovery structure to facilitate backup on different cloud platforms.

[0066] In an exemplary embodiment, the method further comprises:

[0067] If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0068] The structure of business data stored on different cloud platforms is the same, so no conversion is required.

[0069] Among them, the data change log is an important part of the database log, which records all insertion, update and deletion operations of the data in the database.

[0070] Exemplarily, if the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of Tencent Cloud, and backed up to the disaster recovery database of Tianyi Cloud; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0071] In this embodiment, when the data to be backed up is business data, the business data to be backed up is directly backed up to the disaster recovery database, and real-time incremental synchronization is performed, so that changes in the business data can be monitored in real time and backed up in time.

[0072] In an exemplary embodiment, the method further comprises:

[0073] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0074] Exemplarily, when the metadata needs to be restored, relevant information of the metadata that needs to be restored is obtained, and the metadata is restored according to the information.

[0075] In this embodiment, by restoring the backed-up metadata, the data can be restored when the data is damaged or missing.

[0076] In an exemplary embodiment, the obtaining of recovery information includes:

[0077] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0078] Optionally, the components may be Remote Dictionary Server (Redis) and Kafka, etc.

[0079] Optionally, the restored data information may include information such as metadata size and the current virtual private cloud.

[0080] Exemplarily, component configuration information of a source cloud platform is obtained; data information of metadata that needs to be restored is obtained as recovery data information; the recovery order of metadata in the backup metadata is obtained; based on the recovery data information, the corresponding backed up metadata in Tianyi Cloud is determined; the computing resources and storage resources required for recovery are determined; a recovery virtual private cloud is generated in Tianyi Cloud, and the recovery virtual private cloud is used to store metadata and components; the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order are used as recovery information.

[0081] In this embodiment, by acquiring the information required for data recovery, relevant data can be accurately recovered.

[0082] In an exemplary embodiment, performing metadata recovery based on the recovery information includes:

[0083] Based on the component configuration information of the source cloud platform, a recovery component is created on the recovery virtual private cloud; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in the recovery order.

[0084] Exemplarily, component configuration information of Tencent Cloud is obtained, and a recovery component is created on the recovery virtual private cloud using the corresponding configuration information; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in a recovery order.

[0085] In this embodiment, by using the same component configuration information as the source end, the required recovery virtual private cloud can be restored relatively intact.

[0086] In an exemplary embodiment, as shown in FIG4 , a data backup method is applied to the management device in the figure, including: obtaining data information of the data to be backed up in Tencent Cloud (source end-cloud platform A) and source virtual private cloud information for storing the data to be backed up in Tencent Cloud; determining the source virtual private cloud that needs to be connected and data backup based on the source virtual private cloud information; configuring the disaster recovery virtual private cloud in Tianyi Cloud (disaster recovery end-cloud platform A). Based on the data information, the category of the data to be backed up is determined. If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of Tencent Cloud (mysql in the disaster recovery end-cloud platform A) through the backup device, and the business data to be backed up is backed up to the disaster recovery database of Tianyi Cloud; when the backup of the business data to be backed up is completed, real-time incremental synchronization is entered, and the data change log corresponding to the business data to be backed up in the source database is monitored in real time by the central control of the backup device according to the heartbeat mechanism. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database. If the category of the data to be backed up is metadata, the metadata to be backed up is pulled from the components of the source virtual private cloud (such as Redis and Kafka), and the target backup protocol corresponding to the metadata to be backed up is determined to be a protocol for converting the structure of the metadata in Tencent Cloud into a disaster recovery structure through a unified metadata backup protocol designed in advance for different components in different cloud platforms; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain the backup metadata. The backup metadata is backed up to the storage medium of the virtual private cloud in Tianyi Cloud. When the metadata needs to be restored, the component configuration information of the source cloud platform, such as Redis and Kafka information, is obtained; the data information of the metadata to be restored is obtained as the restoration data information; the restoration order of the metadata in the backup metadata is obtained; based on the restoration data information, the corresponding backed up metadata in Tianyi Cloud is determined; the computing resources and storage resources required for restoration are determined; a recovery virtual private cloud is generated in Tianyi Cloud, and the recovery virtual private cloud is used to store metadata and components; the component configuration information of the source cloud platform, the computing resources, the storage resources and the restoration order are used as the restoration information. Obtain component configuration information of Tencent Cloud, and use the corresponding configuration information to create a recovery component on the recovery virtual private cloud; based on the computing resources and the storage resources, import the backed up metadata into the recovery component in the recovery order.

[0087] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0088] In an exemplary embodiment, as shown in FIG5 , a data backup device is provided, including: an acquisition module 501, a conversion module 502 and a backup module 503, wherein:

[0089] The acquisition module is used to obtain data information of the data to be backed up in the source cloud platform and the source virtual private cloud information used to store the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; and configure the disaster recovery virtual private cloud on the disaster recovery cloud platform.

[0090] A conversion module is used to determine the category of the data to be backed up based on the data information; if the category is metadata, the metadata to be backed up is pulled from the source virtual private cloud, and the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata.

[0091] The backup module is used to back up the backup metadata to the disaster recovery virtual private cloud.

[0092] In one embodiment, the conversion module is further configured to:

[0093] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0094] In one embodiment, the conversion module is further configured to:

[0095] If the category is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0096] In one embodiment, it further includes: a recovery module, which is used to:

[0097] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0098] In one embodiment, the recovery module is further configured to:

[0099] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0100] In one embodiment, the recovery module is further configured to:

[0101] Creating a recovery component on the recovery virtual private cloud based on the component configuration information of the source cloud platform;

[0102] Based on the computing resources and the storage resources, the backed-up metadata is imported into the recovery component in the recovery order.

[0103] Each module in the above data backup device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0104] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG6. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store backup data and restore data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a data backup method is implemented.

[0105] Those skilled in the art will understand that the structure shown in FIG. 6 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0106] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0107] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0108] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0109] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0110] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0111] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0112] In one embodiment, the method further comprises:

[0113] If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0114] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0115] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0116] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0117] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0118] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0119] Based on the component configuration information of the source cloud platform, a recovery component is created on the recovery virtual private cloud; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in the recovery order.

[0120] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0121] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0122] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0123] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0124] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0125] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0126] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0127] If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0128] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0129] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0130] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0131] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0132] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0133] Based on the component configuration information of the source cloud platform, a recovery component is created on the recovery virtual private cloud; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in the recovery order.

[0134] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0135] Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform;

[0136] Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata;

[0137] The backup metadata is backed up to the disaster recovery virtual private cloud.

[0138] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0139] By pre-designing a unified metadata backup protocol for different components in different cloud platforms, the target backup protocol corresponding to the metadata to be backed up is determined; the unified metadata backup protocol is used to shield the differences in metadata structures of different cloud platforms and different components; based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

[0140] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0141] If the category of the data to be backed up is business data, the business data to be backed up is pulled from the source database of the source cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery cloud platform; when the backup of the business data to be backed up is completed, enter the real-time incremental synchronization, and monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up changes, the changed business data to be backed up is synchronized to the disaster recovery database.

[0142] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0143] When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

[0144] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0145] Obtain component configuration information of the source cloud platform; obtain data information of metadata that needs to be restored as recovery data information; obtain the recovery order of metadata in the backup metadata; based on the recovery data information, determine the corresponding backed up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; generate a recovery virtual private cloud on the disaster recovery cloud platform, the recovery virtual private cloud is used to store metadata and components; use the component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order as recovery information.

[0146] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0147] Based on the component configuration information of the source cloud platform, a recovery component is created on the recovery virtual private cloud; based on the computing resources and the storage resources, the backed up metadata is imported into the recovery component in the recovery order.

[0148] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0150] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A data backup method, characterized in that: The method comprises: Acquire data information of data to be backed up in the source cloud platform and source virtual private cloud information for storing the data to be backed up; determine the source virtual private cloud based on the source virtual private cloud information; configure the disaster recovery virtual private cloud on the disaster recovery cloud platform; Based on the data information, determine the category of the data to be backed up; if the category is metadata, pull the metadata to be backed up from the source virtual private cloud, and convert the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; The backup metadata is backed up to the disaster recovery virtual private cloud.

2. The method according to claim 1, characterized in that The method of converting the data structure of the metadata to be backed up into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata includes: By pre-designing a unified metadata backup protocol for different components in different cloud platforms, determining a target backup protocol corresponding to the metadata to be backed up; the unified metadata backup protocol is used to shield differences in metadata structures of different cloud platforms and different components; Based on the target backup protocol, the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure to obtain backup metadata.

3. The method according to claim 1, characterized in that The method further comprises: If the category is business data, the business data to be backed up is pulled from the source database of the source-end cloud platform, and the business data to be backed up is backed up to the disaster recovery database of the disaster recovery-end cloud platform; When the backup of the business data to be backed up is completed, real-time incremental synchronization is entered to monitor the data change log corresponding to the business data to be backed up in the source database in real time. When the business data to be backed up is changed, the changed business data to be backed up is synchronized to the disaster recovery database.

4. The method according to claim 1, characterized in that The method further comprises: When the metadata needs to be restored, the restoration information is obtained, and the metadata is restored based on the restoration information.

5. The method according to claim 4, characterized in that The obtaining of the recovery information includes: Obtain component configuration information of the source cloud platform; obtain data information of the metadata to be restored as restoration data information; obtain the restoration order of the metadata in the backup metadata; Based on the recovery data information, determine the corresponding backed-up metadata in the disaster recovery cloud platform; determine the computing resources and storage resources required for recovery; Generate a recovery virtual private cloud on the disaster recovery end cloud platform, where the recovery virtual private cloud is used to store metadata and components; The component configuration information of the source cloud platform, the computing resources, the storage resources and the recovery order are used as recovery information.

6. The method according to claim 4, characterized in that The performing metadata recovery based on the recovery information includes: Create recovery components on the recovery VPC based on the component configuration information of the source cloud platform; Based on computing resources and storage resources, the backed-up metadata is imported into the recovery component in a recovery order.

7. A data backup device, characterized in that: The device comprises: An acquisition module is used to acquire data information of data to be backed up in a source cloud platform and source virtual private cloud information for storing the data to be backed up; determine a source virtual private cloud based on the source virtual private cloud information; and configure a disaster recovery virtual private cloud on a disaster recovery cloud platform; A conversion module is used to determine the category of the data to be backed up based on the data information; if the category is metadata, the metadata to be backed up is pulled from the source virtual private cloud, and the data structure of the metadata to be backed up is converted into a pre-designed disaster recovery structure through a unified metadata backup protocol to obtain backup metadata; The backup module is used to back up the backup metadata to the disaster recovery virtual private cloud.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images