WO2025001272A1 - Data processing method, apparatus and system - Google Patents

Abstract

The present application relates to the field of cloud computing. Provided are a data processing method, device and system. The data processing method is applied to a data center and a cloud computing platform of a hybrid cloud system, a backup format of the data center is different from a backup format of the cloud computing platform, and a cloud interface module configured to communicate with the cloud computing platform is deployed in the data center. The data processing method comprises: a data center acquiring cloud backup data from a cloud computing platform by means of a cloud interface module, and converting the cloud backup data into raw data; the data center performing local backup on the raw data according to a backup format of the data center, so as to obtain local backup data; and when the data center needs to recover a service of the cloud computing platform, the data center recovering the service of the cloud computing platform on the basis of the local backup data. In this way, when the data center needs to recover the service of the cloud computing platform, the data center can locally recover the service of the cloud computing platform on the basis of the local backup data, so that the recovery efficiency is improved.

Description

Data processing method, device and system

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on June 26, 2023, with application number 202310760054.7, and application name “A method, device and other equipment for data format identification”, and the Chinese patent application filed with the State Intellectual Property Office on September 27, 2023, with application number 202311264924.8, and invention name “Data processing method, device and system”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of cloud computing, and in particular to a data processing method, device and system.

Background Art

As enterprises' information technology (IT) is gradually virtualized, enterprises use virtualized data centers to process data and services locally. In order to improve data security, enterprises usually back up data on data centers and cloud computing platforms. Therefore, data centers and cloud platforms often serve as each other's disaster recovery sites.

Usually, the disaster recovery solution for an enterprise's virtualized data center is provided by a disaster recovery provider, and the disaster recovery solution for the cloud platform is provided by the cloud platform vendor. Due to the different disaster recovery solutions, the data backup formats of the data center and the cloud platform are not unified, and the backup data of the cloud platform and the data center cannot be recognized and converted between each other. In a hybrid cloud scenario, part of the enterprise's business runs in the data center, and the other part runs on the cloud platform. When the cloud platform fails, the data center cannot use the backup data of the cloud platform according to the disaster recovery solution provided by the disaster recovery provider to restore the cloud platform's business, and the recovery efficiency is low.

Summary of the invention

The present application provides a data processing method, device and system, thereby improving the recovery efficiency of data recovery of cloud platform services using backup data of the cloud platform in a data center.

In a first aspect, the present application provides a data processing method, which is applied to a data center in a hybrid cloud system. The hybrid cloud system includes a data center and a cloud platform, the cloud platform and the data center are communicatively connected, and the backup format of the data center is different from the backup format of the cloud platform. The data center is deployed with a cloud interface module for communicating with the cloud platform. The data processing method includes: the data center obtains cloud backup data from the cloud platform through the cloud interface module, and converts the cloud backup data into original data. The data center performs a local back-up of the original data according to the backup format of the data center to obtain local backup data. When it is necessary to restore the business of the cloud platform in the data center, the data center restores the business of the above-mentioned cloud platform in the data center based on the local backup data.

Among them, cloud backup data is the backup of the data of the business running on the cloud platform by the cloud platform, and the cloud backup data conforms to the backup format of the cloud platform. Raw data refers to unprocessed data, which means data that has not been modified, cleaned or filtered, such as data stored by users in the storage (such as disk, etc.) of the data center before local backup.

Based on the above data processing method, the data center can obtain cloud backup data from the cloud platform through the cloud interface module, and can identify the cloud backup data in the backup format of the cloud platform, thereby converting the cloud backup data into original data. When the data center is able to identify the cloud backup data, it converts the cloud backup data into original data that has not been processed and can be identified and processed by any computing device (such as the computing node of the data center, etc.). Based on the original data, even if the data center and the cloud platform use disaster recovery solutions provided by different disaster recovery vendors, the data center can also perform local backup of the cloud platform's business data, that is, the original data converted from the cloud backup data, in accordance with the backup format of the local disaster recovery solution provided to the data center by the disaster recovery vendor used by the data center, to obtain local backup data. Since the local backup data is backup data that can be identified and used by the local disaster recovery solution of the data center, when it is necessary to restore the cloud platform's business in the data center, the data center can restore the above-mentioned cloud platform's business in the data center based on the local backup data, thereby improving the recovery efficiency.

As a possible implementation method, the data center queries the backup format corresponding to the cloud backup data through the cloud interface module, and then converts the cloud backup data into original data based on the backup format corresponding to the cloud backup data. In this way, when the disaster recovery solution used by the data center is different from the disaster recovery solution of the cloud platform, the cloud interface module can also be used to query and convert the backup format of the cloud backup data.

Optionally, the cloud interface module may be a software development kit (SDK) provided by the cloud platform. The software development kit may encapsulate interfaces with codes for implementing different functions, such as a backup query (get) interface. The data center calls the backup query interface to query the backup format corresponding to the cloud backup data, and then calls the backup read interface to convert the cloud backup data into original data based on the backup format corresponding to the cloud backup data.

As a possible implementation method, the backup format of the cloud platform is the backup format corresponding to the disaster recovery solution used by the cloud platform, and may include a backup parsing algorithm corresponding to the backup storage algorithm used by the cloud platform for data backup. The backup parsing algorithm is the inverse algorithm of the backup storage algorithm, that is, after the cloud platform stores the data as cloud backup data based on the backup storage algorithm, the cloud platform or the data center can restore the cloud backup data to the data before the backup based on the backup parsing algorithm. In this way, when the data center uses a disaster recovery solution different from that of the cloud platform, it can also call the interface of the cloud interface module to realize the recognition and conversion of cloud backup data.

Optionally, the data center uses a backup parsing algorithm to convert the cloud backup data into original data through the cloud interface module. For example, the backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm. The data center calls the backup reading interface and processes the cloud backup data according to the deduplication and restoration algorithm, the decompression algorithm, and the decryption algorithm corresponding to the cloud backup data to restore the cloud backup data to original data.

As a possible implementation method, the backup format of the data center is a backup format corresponding to the disaster recovery solution used by the data center, including a backup storage algorithm and a backup storage layout for data backup in the data center.

Optionally, the data center performs a local backup of the original data according to the backup storage algorithm and backup storage layout of the data center, and obtains the local backup data of the cloud backup data in the data center. In this way, the data center performs a local backup of the original data converted from the cloud backup data using the backup storage algorithm and backup storage layout corresponding to the disaster recovery solution used locally in the data center, and the obtained local backup data can be recognized and applied by the disaster recovery solution used locally in the data center, providing a data basis for the data center to directly recover the cloud platform's services locally based on the disaster recovery solution used locally.

As a possible implementation method, the cloud interface module includes a list query interface, a backup query interface, and a backup read interface. The data center calls the list query interface, the backup query interface, and the backup read interface to read the cloud backup data. First, the data center calls the list query interface to query the cloud backup list of the cloud platform, and the cloud backup list includes at least one set of cloud backup data. Then, the data center calls the backup query interface to obtain the backup information of the cloud backup data corresponding to the business in at least one set of cloud backup data, and the backup information includes at least one of the backup storage algorithm, the backup parsing algorithm, and the storage location of the cloud backup data. Secondly, the data center calls the backup read interface to obtain the cloud backup data from the cloud platform based on the backup information. In this way, the disaster recovery solution used locally in the data center can also query and obtain the cloud backup data and backup information of the cloud platform by calling the interfaces with different functions encapsulated by the cloud interface module.

As a possible implementation method, the data center can also migrate the local backup data that has been downloaded to the cloud to the cloud platform when it is necessary to restore the business of the cloud platform on the cloud platform, so that the cloud platform can restore the business on the cloud. First, the data center converts the local backup data into original data. Then, the data center converts the original data into the backup format of the cloud platform to obtain the data to be uploaded to the cloud. Secondly, the data center writes the data to be uploaded to the cloud platform through the cloud interface module to obtain the cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data. In this way, when the data center uses a disaster recovery solution different from the cloud platform, relative to the software platform corresponding to the disaster recovery solution used by the data center on the cloud platform, to identify and apply the local backup data in the backup format corresponding to the disaster recovery solution used by the data center, the data center writes the data to be uploaded to the cloud to the cloud platform through the cloud interface module according to the backup format that can be recognized and applied by the disaster recovery solution of the cloud platform, and the software platform corresponding to the disaster recovery solution used by the cloud platform can directly restore the business of the cloud platform on the cloud based on the cloud backup data uploaded to the cloud, thereby improving the recovery efficiency and reducing the software architecture cost.

In a second aspect, a data processing method is provided, which is applied to a data center in a hybrid cloud system. The hybrid cloud system includes a data center and a cloud platform, the cloud platform and the data center are communicatively connected, and the backup format of the data center is different from that of the cloud platform. The data center is deployed with a cloud interface module for communicating with the cloud platform. The data processing method includes: the data center converts local backup data into original data, and the local backup data is obtained by the data center performing a local backup of data of the business running in the data center according to the backup format of the data center. Then, the data center converts the original data into the backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud. Finally, the data center writes the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data.

As a possible implementation method, the cloud interface module includes a backup write interface, and the data center calls the backup write interface to convert the original data into a backup format of the cloud platform.

As a possible implementation method, the cloud interface module also includes a backup creation interface. The data center calls the backup creation interface to create a cloud backup in the cloud platform, and then calls the backup write interface to write the data to be uploaded to the cloud backup storage location to obtain the cloud backup. data.

As a possible implementation method, the backup format of the data center includes a backup parsing algorithm of the data center. The backup parsing algorithm of the data center is an inverse algorithm of a backup storage algorithm of the data center for local data backup. The data center uses the backup parsing algorithm of the data center to convert the local backup data into the original data. The backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm.

As a possible implementation method, the backup format of the cloud platform includes a backup storage algorithm and a backup storage layout. The data center writes the data to be uploaded to the cloud platform through the cloud interface module according to the backup storage algorithm and backup storage layout of the cloud platform to obtain cloud backup data.

As a possible implementation, the cloud interface module includes a software development kit.

In a third aspect, a data processing method is provided, which is applied to a cloud platform in a hybrid cloud system. The hybrid cloud system includes a data center and a cloud platform, the cloud platform and the data center are connected in communication, and the backup format of the data center is different from the backup format of the cloud platform. The data center is deployed with a cloud interface module for communicating with the cloud platform. The data processing method includes: the cloud platform returns cloud backup data to the data center according to the call of the cloud interface module by the data center. The cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform.

As a possible implementation method, the cloud platform provides a cloud interface module so that the data center can obtain and deploy the cloud interface module.

In a fourth aspect, a data processing method is provided, which is applied to a hybrid cloud system. The hybrid cloud system includes a data center and a cloud platform, the cloud platform and the data center are connected in communication, and the backup format of the data center is different from that of the cloud platform. The data center is deployed with a cloud interface module for communicating with the cloud platform. The data processing method includes: the data center sends a backup read request to the cloud platform through the cloud interface module; the cloud platform sends cloud backup data to the data center according to the backup read request, and the cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform; the data center converts the cloud backup data into original data through the cloud interface module; the data center performs local backup on the original data according to the backup format of the data center to obtain local backup data; the data center restores the business in the data center based on the local backup data.

As a possible implementation, the step of the data center reading and converting the cloud backup data through the cloud interface module can be implemented by the data center calling the same interface of the cloud interface module. For example, the data center calls the backup reading interface to obtain the cloud backup data from the cloud platform and converts the cloud backup data into original data.

As a possible implementation method, the cloud platform provides a cloud interface module, and the data center obtains and deploys the cloud interface module on the software platform corresponding to the disaster recovery solution used by the data center. In this way, the cloud platform exposes the backup format of the cloud backup data corresponding to the disaster recovery solution used by the cloud platform to the data center where the cloud interface module is deployed, by providing the cloud interface module, so that the data center can identify and apply the cloud platform data through the cloud interface module.

In a fifth aspect, a data processing device is provided. The data processing device includes a cloud module, a backup module, and a recovery module. The cloud module is used to obtain cloud backup data from the cloud platform through the cloud interface module, and convert the cloud backup data into original data. The cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform. The backup module is used to perform local backup of the original data according to the backup format of the data center to obtain local backup data. The recovery module is used to restore the business in the data center based on the local backup data.

As a possible implementation method, the down-cloud module is specifically used to: query the backup format corresponding to the cloud backup data through the cloud interface module; and convert the cloud backup data into original data based on the backup format corresponding to the cloud backup data.

As a possible implementation method, the backup format of the cloud platform includes the backup parsing algorithm of the cloud platform, which is the inverse algorithm of the backup storage algorithm of the cloud platform for cloud backup of data. The lower cloud module is specifically used to: convert the cloud backup data into original data using the backup parsing algorithm of the cloud platform through the cloud interface module, and the backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm.

As a possible implementation, the backup format of the data center includes a backup storage algorithm and a backup storage layout. The backup module is specifically used to: perform local backup of the original data according to the backup storage algorithm and the backup storage layout of the data center to obtain local backup data of the cloud backup data in the data center.

As a possible implementation, the cloud interface module includes a list query interface, a backup query interface, and a backup read interface. The cloud module is specifically used to: call the list query interface to query the cloud backup list of the cloud platform, the cloud backup list includes at least one group of cloud backup data; call the backup query interface to obtain the backup information of the cloud backup data corresponding to the business in at least one group of cloud backup data, the backup information includes at least one of the backup storage algorithm, backup parsing algorithm, and storage location of the cloud backup data; call the backup read interface to obtain the backup information of the cloud backup data corresponding to the business in ... corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding to the business in the cloud backup data corresponding口, obtain cloud backup data from the cloud platform based on the backup information.

As a possible implementation method, the data processing device also includes a cloud module. The backup module is specifically used to: convert local backup data into original data, and convert original data into a backup format of the cloud platform to obtain data to be uploaded to the cloud. The cloud module is used to write the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore business on the cloud platform based on the cloud backup data.

As a possible implementation, the cloud interface module includes a software development kit.

In a sixth aspect, a data processing device is provided. The data processing device includes a restoration module, a conversion module and a cloud module. The restoration module is used to convert local backup data into original data, and the local backup data is obtained by the data center performing a local backup of the data of the business running in the data center according to the backup format of the data center. The conversion module is used to convert the original data into the backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud. The cloud module is used to write the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data.

As a possible implementation, the cloud interface module includes a backup write interface. The conversion module is specifically used to: call the backup write interface to convert the original data into a backup format of the cloud platform.

As a possible implementation method, the cloud interface module also includes a backup creation interface, and the cloud module is specifically used to: call the backup creation interface to create a cloud backup in the cloud platform; call the backup write interface to write the data to be uploaded to the cloud backup storage location to obtain the cloud backup data.

As a possible implementation method, the backup format of the data center includes a backup parsing algorithm of the data center, which is an inverse algorithm of a backup storage algorithm used by the data center to perform local backup of data. The restore module is specifically used to: use the backup parsing algorithm of the data center to convert the local backup data into original data, and the backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm.

As a possible implementation method, the restoration module is specifically used to: write the data to be uploaded to the cloud platform through the cloud interface module according to the backup storage algorithm and backup storage layout of the cloud platform to obtain cloud backup data.

As a possible implementation, the cloud interface module includes a software development kit.

In a seventh aspect, a data processing device is provided. The data processing device includes an interface processing module. The interface processing module is used to respond to the call of the data center to the cloud interface module. For example, the interface processing module is used to return cloud backup data to the data center according to the call of the data center to the cloud interface module.

As a possible implementation, the data processing device further includes a publishing module. The publishing module is used to provide a cloud interface module so that the data center acquires and deploys the cloud interface module.

In an eighth aspect, a data processing system is provided. The data processing system includes a local backup device and a cloud backup device. The local backup device is used to send a backup read request to the cloud platform through a cloud interface module. The cloud backup device is used to send cloud backup data to the data center according to the backup read request. The cloud backup data is obtained by the cloud platform performing a cloud backup of the data of the business running on the cloud platform according to the backup format of the cloud platform. The local backup device is also used to convert the cloud backup data into original data through the cloud interface module. The local backup device is also used to perform a local backup of the original data according to the backup format of the data center to obtain local backup data. The local backup device is also used to restore the business in the data center based on the local backup data.

As a possible implementation, both the local backup device and the cloud backup device can be implemented by software or hardware. For example, the local backup device is a software platform corresponding to the backup solution used by the data center, and the cloud backup device is a software platform corresponding to the backup solution used by the cloud platform.

Regarding the technical principles and beneficial effects of the second, third, fourth, fifth, sixth, seventh and eighth aspects, reference may be made to the relevant description of the first aspect above and no further details will be given here.

In a ninth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory. The processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the data processing method described in any possible implementation of the first aspect.

In a tenth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory. The processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the data processing method described in any possible implementation of the second aspect.

In an eleventh aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory. The processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that The computing device cluster executes the data processing method described in any possible implementation manner of the third aspect above.

In a twelfth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory. The processor of at least one computing device is used to execute instructions stored in the memory of at least one computing device, so that the computing device cluster executes the data processing method described in any possible implementation of the fourth aspect.

In a thirteenth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer executes the data processing method described in any possible implementation of the first aspect.

In a fourteenth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer executes the data processing method described in any possible implementation of the second aspect.

In a fifteenth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer executes the data processing method described in any possible implementation of the third aspect.

In a sixteenth aspect, a computer program product is provided, which includes a computer program or instructions, and when the computer program or instructions are run on a computer, the computer executes the data processing method described in any possible implementation of the fourth aspect.

In a seventeenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes: a computer program or an instruction; when the computer program or the instruction is executed on a computer, the computer executes the data processing method described in any possible implementation of the first aspect.

In an eighteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes: a computer program or instruction; when the computer program or instruction is executed on a computer, the computer executes the data processing method described in any possible implementation of the second aspect.

In a nineteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes: a computer program or an instruction; when the computer program or the instruction is executed on a computer, the computer executes the data processing method described in any possible implementation of the third aspect.

In a twentieth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes: a computer program or instruction; when the computer program or instruction is executed on a computer, the computer executes the data processing method described in any possible implementation of the fourth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of a hybrid cloud system provided by the present application;

FIG2 is a schematic diagram of a virtualized hierarchical structure of a hybrid cloud system provided by the present application;

FIG3 is a flow chart of a data processing method provided by the present application;

FIG4 is a schematic diagram of a backup storage layout provided by the present application;

FIG5 is a flow chart of another data processing method provided by the present application;

FIG6 is a schematic diagram of the structure of a data processing device provided by the present application;

FIG7 is a schematic diagram of the structure of another data processing device provided by the present application;

FIG8 is a schematic diagram of the structure of a data processing system provided by the present application;

FIG9 is a schematic diagram of the structure of a computing device provided by the present application;

FIG10 is a schematic diagram of the structure of a computing device cluster provided by the present application;

FIG. 11 is a schematic diagram of a network connection of a computing device cluster provided in the present application.

DETAILED DESCRIPTION

The data processing method, device, and system provided in the embodiments of the present application can be applied to hybrid cloud scenarios. The following is a brief introduction to the technologies that may be involved in the present application.

(1) Cloud Platform

Cloud platform, also known as cloud computing platform, is a service based on hardware resources and software resources, providing computing, network and storage capabilities. That is, the platform provider combines cloud (remote hardware resources) and computing (remote software resources) to form a platform to provide various services to users.

The services provided by the cloud platform may include software as a service (SaaS), platform as a service (PaaS) and infrastructure as a service (IaaS). SaaS is a service provider that uniformly deploys application software on the cloud platform's servers, and users order application software services from the service provider through the Internet based on their needs. PaaS is the provision of development environment as a service, that is, the service provider provides services such as development environment, server platform and hardware resources to users, and users develop applications in the development environment provided by the cloud platform and share them with other users through the cloud platform and the Internet. IaaS is a service provider that provides a cloud infrastructure consisting of multiple servers to users as a service, that is, integrates memory, input/output devices, storage and computing resources into a virtual resource pool to provide users with storage resources and virtualized servers.

(2) Hybrid Cloud

As a form of cloud computing, hybrid cloud combines private cloud (such as virtualized data center) and public cloud (such as cloud platform provided by cloud service providers) to work together, thereby improving the resource utilization of users across clouds. Enterprise IT architecture has gradually evolved from centralized mainframe to distributed virtualization architecture, and is evolving to multi-site and multi-cloud architecture. According to the characteristics of the business itself, enterprises deploy different businesses in private clouds and public clouds respectively. For example, for security reasons, enterprises can store private data in their own private clouds. At the same time, those test businesses (frequent changes and upgrades) and businesses frequently accessed by external users are deployed on the public cloud, making full use of the advantages of public cloud reliability, professional operation and maintenance, and rapid resource expansion.

(3) Disaster Recovery

Disaster recovery is the abbreviation of disaster tolerance and backup, which refers to the use of existing scientific and technological means and methods to establish reliable emergency response methods in advance to deal with emergencies. Disaster recovery means switching the system to backup devices and backup systems to achieve system business recovery when a system failure or other catastrophic event occurs. Backup means storing data and business-related programs on another device or system so that business can be restored in the event of a system failure or disaster.

The present application provides a data processing method, and in particular, a data processing method in which "a data center obtains the ability to identify and process backup data of a cloud platform through a cloud interface module provided by a cloud platform." In a hybrid cloud system, the cloud platform and the data center are communicatively connected, and the backup format of the data center is different from that of the cloud platform. The data center is deployed with a cloud interface module for communicating with the cloud platform. The data center obtains cloud backup data from the cloud platform through the cloud interface module and converts the cloud backup data into original data. The cloud backup data is a backup of the data of the business running on the cloud platform by the cloud platform, and the cloud backup data conforms to the backup format of the cloud platform. The data center performs a local back-up of the original data in accordance with the backup format of the data center to obtain local backup data. When it is necessary to restore the business of the cloud platform in the data center, the data center restores the business of the above-mentioned cloud platform locally based on the local backup data.

Based on the above data processing method, when the data center is able to identify and obtain cloud backup data through the cloud interface module, it converts the cloud backup data into unprocessed original data that can be identified and processed by any computing device (such as the computing device of the data center, etc.). Therefore, the software platform corresponding to the disaster recovery solution used by the data center can locally back up the original data to obtain local backup data. Since the local backup data is the backup data that can be used by the local disaster recovery solution of the data center, when it is necessary to restore the business of the cloud platform in the data center, the data center can restore the business of the above cloud platform in the data center based on the local backup data. In this way, the data center can use the local disaster recovery solution deployed by the data center to restore the business of the cloud platform in the cloud, thereby improving the recovery efficiency.

The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of the structure of a hybrid cloud system provided by the present application. As shown in Fig. 1, the hybrid cloud system 100 includes a data center 110 and a cloud platform 120. The data center 110 and the cloud platform 120 are connected in communication, and the data center 110 and the cloud platform 120 are remote disaster recovery sites for each other.

The data center 110 includes a production host 111 and a storage device 112 .

The production host 111 is an application server of the data center 110, such as a server, a desktop computer, etc., and is used to generate and allocate resources according to user needs based on virtualization technology. At the hardware level, the production host 111 is provided with a processor and a memory (not shown in FIG. 1 ), and the functions of the production host 111 are realized by the processor running the program in the memory. The production host 111 can also read/write data in the storage device 112 according to the running requirements of the application.

The storage device 112 is a backup resource in the data center 110, such as a server, desktop computer, or storage array controller, hard disk enclosure, etc., and is used to provide logical disk storage, unstructured data storage, and integrated backup services for cloud virtual machines in the data center 110. In terms of hardware, the storage device 112 may only include a memory, such as a network attached storage (NAS), or may be provided with a network card, a processor, and a memory. The processor in the storage device 112 is used to Process data from outside the storage device 112. The network card is used to control the access process of the memory, such as the control of address signals, data signals and various command signals, so that the storage device 112 can provide the memory as a storage resource to the user. The memory is used to store data and may include memory and/or hard disk. Memory refers to the internal memory that directly exchanges data with the processor. The memory can read and write data quickly at any time and serves as a temporary data storage for the operating system or other running programs. Unlike memory, the hard disk reads and writes data slower than memory and is usually used to store data persistently.

The data center 110 is deployed with a disaster recovery software platform 113 provided by a disaster recovery provider, and the disaster recovery software platform 113 is integrated with a cloud interface module 114 provided by the cloud platform 120 .

The disaster recovery software platform 113 is used to perform software backup and data backup in the data center 110 , as well as business recovery.

For the business running in the data center 110, the disaster recovery software platform 113 performs software backup and data backup on the business running in the data center 110 based on the backup format specified by the disaster recovery solution provided by the disaster recovery provider, thereby storing the local backup data in the storage device 112. The backup format specified by the disaster recovery solution provided by the disaster recovery provider can be called the backup format of the data center 110.

In this way, when it is necessary to restore the local business, the disaster recovery software platform 113 restores the business based on the local backup data of the local business of the data center 110 .

For the business running on the cloud platform 120, the disaster recovery software platform 113 obtains the cloud backup data from the cloud platform 120 through the cloud interface module 114, converts the cloud backup data into original data, and then performs local backup of the original data according to the backup format of the data center 110 to obtain the local backup data corresponding to the cloud backup data. The original data may be in the format of data directly read from a storage device such as a disk when the data center 110 runs the business.

In this way, when it is necessary to restore the business running on the cloud platform 120 to the data center 110 , the disaster recovery software platform 113 restores the business running on the cloud platform 120 based on the local backup data corresponding to the cloud backup data of the cloud platform 120 .

As a possible implementation manner, the cloud interface module 114 is a software tool development kit of the disaster recovery software platform 113 published by the cloud platform 120 and deployed in the data center 110 .

Optionally, the cloud interface module 114 includes a list query interface, a backup query interface, a backup open interface, a backup read interface, a backup create interface, a backup write interface, a backup synchronization interface, etc.

The list query interface is used to return the cloud backup list of the cloud platform 120. The cloud backup list includes at least one group of cloud backup data, and each group of cloud backup data can be data of different services or different versions of data of the same service. The cloud backup list can use an identifier corresponding to at least one group of cloud backup data to represent the cloud backup data, for example, backup1, backup2, backup3, etc.

The backup query interface is used to return the backup information of one or more sets of cloud backup data for a specific query. The backup information includes the storage location of the cloud backup data, a universally unique identifier (UUID), resource type, resource size, backup storage algorithm, etc. Among them, the backup storage algorithm is the backup storage algorithm corresponding to the backup format specified by the backup solution provided by the manufacturer of the cloud platform 120.

The backup open interface is used to open the cloud backup data and return the reference handle of the cloud backup data.

The backup read interface is used to read the cloud backup data in the specified storage location through the logical block address (LBA) offset or index after the cloud backup data is opened, and restore the cloud backup data to the original format according to the backup parsing algorithm corresponding to the backup storage algorithm of the cloud backup data.

The backup creation interface is used to create a new set of cloud backup data on the cloud platform 120 .

The backup write interface is used to write cloud backup data according to the input logical block address offset or index. For example, the backup write interface is used to write cloud backup data to a storage location specified by the logical block address offset or index in the cloud platform 120 according to the backup format of the cloud backup data.

The backup synchronization interface is used to synchronize the cloud backup list with the cloud platform data after the cloud backup data is written into the cloud platform 120 .

The cloud platform 120 includes a cloud host 121 and a storage device 122 .

The functions of the cloud host 121 and the storage device 122 in the cloud platform 120 are similar to those of the production host 111 and the storage device 112 in the data center 110 and are not described in detail here.

The cloud platform 120 is deployed with a cloud backup software platform 123 provided by the manufacturer of the cloud platform 120. The cloud backup software platform 123 integrates cloud native backup services such as cloud backup and cloud business recovery. In this application, the cloud backup software platform 123 can be regarded as the server of the cloud platform 120, and the cloud interface module 114 can also be regarded as the client communicating with the server of the cloud platform 120. The client communicates through the Application Programming Interface Gateway (APIG) of the cloud platform 120 to implement the call of the interface integrated by the data center 110 to the cloud interface module 114 .

Optionally, the data center 110 has an account registered on the cloud platform 120, and the disaster recovery software platform 113 and the cloud platform 120 are authenticated through AK/SK (Access Key/Secret Key), and manage each other as a protected environment, thereby establishing a communication connection.

The cloud backup software platform 123 is used to perform software backup and data backup on the cloud platform 120, as well as business recovery.

For the business running on the cloud platform 120, the cloud backup software platform 123 performs software backup and data backup on the business running on the cloud platform 120 based on the backup format specified by the disaster recovery solution provided by the manufacturer of the cloud platform 120, thereby storing the cloud backup data in the storage device 122. Among them, the backup format specified by the disaster recovery solution provided by the manufacturer of the cloud platform 120 can be called the backup format of the cloud platform 120.

In this way, when it is necessary to restore the services of the cloud platform 120 , the cloud backup software platform 123 restores the services based on the cloud backup data of the services of the cloud platform 120 .

For the business running in the data center 110, the cloud backup software platform 123 responds to the call of the cloud interface module 114, stores the data in the backup format of the cloud platform 120 uploaded by the data center 110 into the storage device 122, and obtains cloud backup data.

In this way, when it is necessary to restore the business of the data center 110 on the cloud platform 120 , the cloud backup software platform 123 restores the business of the data center 110 on the cloud platform 120 based on the cloud backup data corresponding to the business data of the data center 110 .

In the embodiment of the present application, the business running in the data center 110 and the business running in the cloud platform 120 may be different businesses, and therefore, the data of the two are also different.

It is worth noting that FIG1 is only a schematic diagram and should not be construed as a limitation of the present application. The hybrid cloud system 100 may also include other devices, which are not shown in FIG1. For example, the hybrid cloud system 100 may also include a network device for supporting communication between the data center 110 and the cloud platform 120. The network device may be one or more switches and routers, or the data center 110 and the cloud platform 120 may be connected via a cloud dedicated line communication. For another example, FIG1 only shows the virtualization architecture of the hybrid cloud system 100. The data center 110 and the cloud platform 120 may also include infrastructure for providing hardware resources, such as a computing server cluster, a storage server cluster, a management server cluster, and/or a network device cluster, which are not shown in FIG1.

Based on the hybrid cloud system 100 shown in FIG1 , the data center 110 and the cloud platform 120 can implement the function of the service node based on IaaS, PssS and SaaS, and provide services (e.g., computing services, storage services and network services) to users through the service node. The service node can be a cloud node (e.g., a management node, a computing node or a storage node, etc.) virtualized using the resources (e.g., computing resources and storage resources) of the data center 110 or the cloud platform 120.

Next, the virtualized hierarchical structure of the data center 110 or the cloud platform 120 is described with reference to FIG. 2 .

As shown in FIG2 , the IaaS platform 210 is used to virtualize all infrastructure resources in the data center 110 or the cloud platform 120, and to provide users with virtual resources (e.g., computing resources, network resources, and storage resources) in a software-defined manner. The infrastructure resources refer to the resources provided by the computing server cluster, storage server cluster, management server cluster, and/or network device cluster in the data center 110 or the cloud platform 120.

The PaaS platform 220 is used to implement the runtime environment and application support functions of the data center 110 or the cloud platform 120, so that users can apply for computing units within the quota instead of virtual resources to run their own services. Optionally, the computing unit can be a container, and the data center 110 or the cloud platform 120 deploys and runs the user's code by scheduling the container. It should be noted that the number of containers in the PaaS platform 220 can be one or more, and only one container is used as an example in Figure 2.

As a possible implementation, the data center 110 or the cloud platform 120 may inject one or more components into the container to implement code deployment and operation. Optionally, the resources (computing resources or storage resources) used by multiple components in the same container may belong to the same hardware device (e.g., computing server, storage server, or management server) in the data center 110 or the cloud platform 120, or may belong to different hardware devices.

Among them, the components may include database components, message queue components, orchestration components, log components, virtualization components, business database components, configuration database components, permission management components, etc.

SaaS application 230 is used to provide services to users by composing user-deployed applications in the form of API responses based on IaaS platform 210 and PaaS platform 220. The application and container of SaaS application 230 can communicate through a network server (Web Server).

It is worth noting that FIG. 2 is only a schematic diagram and should not be construed as a limitation on the present application. The virtualization hierarchical structure may also include other modules that are not shown in FIG. 2 .

The steps of the data processing method provided in the present application are executed by the data center 110 and the cloud platform 120. Next, the data processing method provided in the present application is described in conjunction with FIG. 3 .

Before the data center 110 executes the steps of the data processing method through the cloud interface module 114, the cloud platform 120 provides the cloud interface module 114, and the data center 110 obtains and deploys the cloud interface module 114. For example, the data center 110 deploys the cloud interface module 114 on the disaster recovery software platform 113.

Step 310 : The data center 110 obtains the cloud backup data from the cloud platform 120 through the cloud interface module 114 , and converts the cloud backup data into original data.

As a possible example, the data center 110 sends a backup read request for specified backup data to the cloud platform 120 through the cloud interface module 114 to receive the cloud backup data returned by the cloud platform 120 according to the logical block address offset or index contained in the backup read request, and convert the cloud backup data into original data.

Optionally, the cloud backup data is obtained by the cloud platform 120 backing up the data of the business generated by the cloud host 121 running in the cloud platform 120 according to the configured backup strategy. For example, the cloud platform 120 backs up the data of the business of the cloud platform 120 at 8 am every day according to the backup strategy.

As a possible implementation method, the data center 110 first calls the list query interface to obtain the cloud backup list, then calls the backup query interface to query the backup information of a specified set of cloud backup data, then calls the backup open interface to open the cloud backup data, and calls the backup read interface to read the cloud backup data through the logical block address (logical block address, LBA) offset or index, and restores the cloud backup data to the original format according to the backup parsing algorithm corresponding to the backup storage algorithm of the cloud backup data.

Optionally, the backup storage algorithm of the cloud backup data includes at least one of a deduplication algorithm, a decompression algorithm, and an encryption algorithm. Accordingly, the backup parsing algorithm corresponding to the backup storage algorithm of the cloud backup data is an inverse algorithm of the above-mentioned deduplication algorithm, decompression algorithm, and encryption algorithm, such as at least one of a deduplication restoration algorithm, a decompression algorithm, and a decryption algorithm.

Optionally, considering that for block-stored backup data, the data center 110 and the cloud platform 120 usually have obvious differences in backup storage layouts such as indexing and segmentation. When the data center 110 calls the backup read interface, it needs to read the cloud backup data based on the logical block address offset or index according to the backup storage layout of the cloud backup data of the cloud platform 120.

For example, as shown in FIG. 4 , the backup storage layout of the data center 110 and the backup storage layout of the cloud platform 120 both include index files and block layouts, for example, the index files and block layouts of the storage device 112 and the storage device 122 are different. The index files of the data center 110 and the cloud platform 120 include block identifiers (block id), block names (block name), block paths (block path), cyclic redundancy check (cyclic redundancy check, CRC) and block sizes (size), etc. of multiple blocks. The block layout of the data center 110 includes block 1 (block1), block 2 (block2), block 3 (block3), ..., block N (blockN), etc., and the block layout of the cloud platform 120 includes block '1 (block'1), block '2 (block'2), block 3 (block'3), ..., block 'N (block'N), etc.

The backup storage layout of the cloud backup data can be exposed to the data center 110 by the cloud interface module 114. When the cloud platform 120 targets different virtualized data centers, it can also expose the backup storage layout of the cloud backup data to different virtualized data centers through the cloud interface module 114. In this way, the cloud platform 120 corresponds to different virtualized data centers without providing different versions of clients, thereby covering a wider range of data centers and improving the applicability of the hybrid cloud system 100.

Step 320: The data center 110 performs a local backup of the original data according to the backup format of the data center 110 to obtain local backup data.

As a possible example, the data center 110 performs a local backup of the original data according to the backup storage algorithm and backup storage layout of the data center 110 to obtain local backup data of the cloud backup data in the data center 110 .

As a possible implementation manner, the backup storage algorithm of the data center 110 includes at least one of a deduplication algorithm, a decompression algorithm, and an encryption algorithm, and the backup storage algorithm of the data center 110 is different from the backup storage algorithm of the cloud platform 120.

The backup storage layout of the data center 110 may refer to FIG. 4 , which will not be described in detail here.

Step 330: The data center 110 restores the service in the data center based on the local backup data.

As a possible example, the data center 110 uses the disaster recovery software platform 113 to restore the business originally running on the cloud platform 120 in the data center 110 based on the local backup data corresponding to the cloud backup data of the business on the cloud platform 120.

As a possible implementation method, when the cloud platform 120 fails, such as communication with the cloud platform 120 is disconnected or the cloud platform 120 is shut down, the data center 110 restores the business originally running on the cloud platform 120 based on the local backup data.

In the embodiments of the present application, the execution subject of the data processing method is not limited, and the execution subject may be hardware, software, or a virtualized device obtained by virtualizing the hardware. For example, the execution subject of the above steps 310 to 330 may be the disaster recovery software platform 113 deployed in the data center 110.

Based on the above steps 310 to 330, when the data center 110 uses the disaster recovery software platform 113 provided by the disaster recovery supplier, and the backup format supported by the disaster recovery software platform 113 is different from the backup format supported by the cloud backup software platform 123, the data center 110 can also use the functions encapsulated by the cloud interface module 114 to achieve the acquisition and conversion of the cloud backup data, so that the disaster recovery software platform 113 can restore the business originally running on the cloud platform 120 in the data center 110 based on the converted cloud backup data. In this way, the data center 110 does not need to install the cloud backup software corresponding to the cloud platform 120 locally, and the cloud platform 120 does not need to provide multiple versions of cloud backup software for different versions of disaster recovery software platforms used by different data centers 110. The data center 110 can use the locally installed disaster recovery software platform 113 to directly restore the business of the cloud platform 120 locally, thereby improving the recovery efficiency.

The above describes the process of cloud backup data migration in the data processing method in conjunction with Figures 3 and 4. The data processing method may also include cloud migration of local data of the data center 110. Next, the process of cloud migration of local data of the data center 110 is described in conjunction with Figure 5.

Step 510: The data center 110 performs local backup of the data generated by the production host 111 to obtain local backup data.

As a possible example, the data center 110 performs local backup of data generated by the production host 111 running in the data center 110 according to the configured backup policy to obtain local backup data. For example, the data center 110 performs a backup of the business data of the data center 110 at 9 o'clock every morning according to the backup policy.

As a possible implementation, the data center 110 backs up the data of the services of the data center 110 according to the backup format of the data center 110. The backup format of the data center 110 is a backup format corresponding to the disaster recovery software platform 113 provided by the disaster recovery supplier of the data center 110, which may include a backup storage algorithm and a backup storage layout.

Step 520 : The data center 110 writes the local backup data to the cloud platform 120 through the cloud interface module 114 .

As a possible example, the data center 110 converts the local backup data into original data, and then writes the original data into the cloud platform 120 in the backup format of the cloud platform 120 through the cloud interface module 114 .

As a possible implementation, the data center 110 calls the backup creation interface to create a new set of cloud backups in the cloud platform 120. Then, the data center 110 restores the local backup data to the original data, and calls the backup writing interface to convert the cloud backup data into the backup format of the cloud platform 120 to obtain the data to be uploaded to the cloud. Finally, the data center 110 writes the data to be uploaded to the storage location of the new cloud backup created in the cloud platform 120 according to the backup storage layout of the cloud platform 120.

Optionally, the data center 110 writes the to-be-uploaded-to-the-cloud data into the cloud platform 120 according to the backup storage layout of the cloud platform 120 based on the logical block address offset or index of the newly created cloud backup data.

In a possible embodiment of the present application, the data center 110 writes the local backup data of the cloud platform 120 through the cloud interface module 114 , which may also be obtained based on the above step 320 .

Step 530 : The cloud platform 120 restores the business on the cloud platform 120 based on the cloud backup data.

As a possible example, the cloud platform 120 uses the cloud backup software platform 123 to restore the business originally running on the data center 110 on the cloud platform 120 based on the cloud backup data corresponding to the local backup data of the business of the data center 110 .

As a possible implementation method, when the data center 110 fails, such as communication with the data center 110 is disconnected or the data center 110 is shut down, the cloud platform 120 restores the business originally running on the data center 110 based on the cloud backup data.

In a possible embodiment of the present application, considering that the user may need to migrate the data migrated from the data center 110 to the cloud platform 120 back to the data center 110, after step 520, the data center 110 may further execute: calling the backup synchronization interface to synchronize the cloud backup data to the cloud backup list. In this way, when the user needs to perform a cloud operation on the data migrated from the data center 110 to the cloud platform 120, the user can select a corresponding set of cloud backup data in the cloud backup list.

Based on the above steps 510 to 530, after the cloud platform 120 stores the data of the business of the data center 110 as cloud backup data, the cloud backup software platform 123 can restore the business originally running in the data center 110 on the cloud platform 120 based on the cloud backup data. In this way, there is no need to build the disaster recovery software platform 113 of the data center 110 on the cloud platform 120. The cloud platform 120 can use the cloud native backup and recovery capabilities of the cloud backup software platform 123 to restore the business of the data center 110, thereby improving the recovery efficiency and reducing the software construction cost.

In order to cooperate with the data processing method shown in FIG. 3 provided by the present application, the present application also provides a data processing device 600, as shown in FIG6, includes:

The cloud module 610 is used to obtain cloud backup data from the cloud platform through the cloud interface module and convert the cloud backup data into original data. The cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform.

The backup module 620 is used to locally back up the original data according to the backup format of the data center to obtain local backup data.

The recovery module 630 is used to restore the service in the data center based on the local backup data.

Among them, the cloud module 610, the backup module 620 and the recovery module 630 can all be implemented by software, or can be implemented by hardware. Exemplarily, the implementation of the cloud module 610 is introduced below by taking the cloud module 610 as an example. Similarly, the implementation of the backup module 620 and the recovery module 630 can refer to the implementation of the cloud module 610.

As an example of a software functional unit, the cloud module 610 may include code running on a computing instance. Among them, the computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the above-mentioned computing instance may be one or more. For example, the cloud module 610 may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the code may be distributed in the same region or in different regions. Furthermore, the multiple hosts/virtual machines/containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one data center or multiple data centers with similar geographical locations. Among them, usually a region may include multiple AZs.

Similarly, multiple hosts/virtual machines/containers used to run the code can be distributed in the same virtual private cloud (VPC) or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway needs to be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

As an example of a hardware functional unit, the cloud module 610 may include at least one computing device, such as a server, etc. Alternatively, the cloud module 610 may also be a device implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

The multiple computing devices included in the lower cloud module 610 can be distributed in the same region or in different regions. The multiple computing devices included in the lower cloud module 610 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the lower cloud module 610 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

It should be noted that, in other embodiments, the cloud module 610 can be used to execute any step in the data processing method, the backup module 620 can be used to execute any step in the data processing method, and the recovery module 630 can be used to execute any step in the data processing method. The steps that the cloud module 610, the backup module 620 and the recovery module 630 are responsible for implementing can be specified as needed. The cloud module 610, the backup module 620 and the recovery module 630 respectively implement different steps in the data processing method to realize all the functions of the data processing device 600.

In order to cooperate with the data processing method shown in FIG. 5 provided by the present application, the present application further provides a data processing device 700, as shown in FIG. 7 , comprising:

The restoration module 710 is used to convert the local backup data into the original data, wherein the local backup data is obtained by the data center performing a local backup of the data of the business running in the data center according to the backup format of the data center;

The conversion module 720 is used to convert the original data into the backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud;

The cloud module 730 is used to write the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data.

The restoration module 710, the conversion module 720 and the cloud module 730 can all be implemented by software or by hardware. The configuration is the same as 600 and will not be described again here.

Since the data processing method provided by the present application requires the data center 110 and the cloud platform 120 to communicate with each other in the steps shown in FIG. 3 or FIG. 5 , therefore, the present application also provides a data processing system 800, as shown in FIG. 8 , the data processing system 800 includes:

The local backup device 810 is used to send a backup read request to the cloud platform through the cloud interface module.

The cloud backup device 820 is used to send cloud backup data to the data center according to the backup read request. The cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform.

The local backup device 810 is also used to convert the cloud backup data into original data through the cloud interface module.

The local backup device 810 is also used to restore services in the data center based on the local backup data.

The local backup device 810 and the cloud backup device 820 can be implemented by software or hardware. As an example, the implementation of the local backup device 810 is described below. Similarly, the implementation of the cloud backup device 820 can refer to the implementation of the local backup device 810.

As an example of a software functional unit, the local backup device 810 may include code running on a computing instance. The computing instance may be at least one of a physical host (computing device), a virtual machine, a container, and other computing devices. Furthermore, the computing device may be one or more. For example, the local backup device 810 may include code running on multiple hosts/virtual machines/containers. It should be noted that the multiple hosts/virtual machines/containers used to run the application may be distributed in the same region or in different regions. The multiple hosts/virtual machines/containers used to run the code may be distributed in the same AZ or in different AZs, each AZ including a data center or multiple data centers with close geographical locations. Typically, a region may include multiple AZs.

Similarly, multiple hosts/virtual machines/containers used to run the code can be distributed in the same VPC or in multiple VPCs. Usually, a VPC is set up in a region. For cross-region communication between two VPCs in the same region and between VPCs in different regions, a communication gateway must be set up in each VPC to achieve interconnection between VPCs through the communication gateway.

In an embodiment of the present application, the local backup device 810 can be the disaster recovery software platform 113 of the data center 110 in the hybrid cloud system 100, and the disaster recovery software platform 113 is integrated with the cloud interface module 114. The cloud backup device 820 can be the cloud backup software platform 123 of the cloud platform 120.

As an example of a hardware functional unit, the local backup device 810 may include at least one computing device, such as a server, etc. Alternatively, the local backup device 810 may also be a device implemented using ASIC or PLD, etc. The PLD may be implemented using CPLD, FPGA, GAL or any combination thereof.

The multiple computing devices included in the local backup device 810 can be distributed in the same region or in different regions. The multiple computing devices included in the local backup device 810 can be distributed in the same AZ or in different AZs. Similarly, the multiple computing devices included in the local backup device 810 can be distributed in the same VPC or in multiple VPCs. The multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

In an embodiment of the present application, the local backup device 810 may be an infrastructure of the data center 110 in the hybrid cloud system 100 , and the cloud backup device 820 may be an infrastructure of the cloud platform 120 .

The present application also provides a computing device 900. As shown in FIG9 , the computing device 900 includes: a bus 902, a processor 904, a memory 906, and a communication interface 908. The processor 904, the memory 906, and the communication interface 908 communicate with each other through the bus 902. The computing device 900 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 900.

The bus 902 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, FIG. 9 is represented by only one line, but does not mean that there is only one bus or one type of bus. The bus 902 may include a path for transmitting information between various components of the computing device 900 (e.g., the memory 906, the processor 904, and the communication interface 908).

The processor 904 may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP). processor, DSP) and other processors.

The memory 906 may include a volatile memory, such as a random access memory (RAM). The processor 904 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

The memory 906 stores executable program codes, and the processor 904 executes the executable program codes to respectively implement the functions of the aforementioned cloud module 610, the backup module 620, and the recovery module 630, thereby implementing the data processing method. That is, the memory 906 stores instructions for executing the data processing method. FIG. 9 only exemplarily shows that the memory 906 stores program codes for implementing the functions of the aforementioned cloud module 610, the backup module 620, and the recovery module 630 as an example.

Alternatively, the memory 906 stores executable codes, and the processor 904 executes the executable codes to respectively implement the functions of the aforementioned restoration module 710, conversion module 720, and cloud module 730, thereby implementing the data processing method. That is, the memory 906 stores instructions for executing the data processing method.

Alternatively, the memory 906 stores executable codes, and the processor 904 executes the executable codes to respectively implement the functions of the aforementioned local backup device 810 and the cloud backup device 820, thereby implementing the data processing method. That is, the memory 906 stores instructions for executing the data processing method.

The communication interface 908 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement communication between the computing device 900 and other devices or communication networks.

Considering that the data processing method provided in the present application is applied to the hybrid cloud system 100, the infrastructure of the data center 110 and the cloud platform 120 respectively usually includes multiple computing devices. Therefore, the present application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop, a laptop, or a smart phone.

As shown in Fig. 10, the computing device cluster includes at least one computing device 900. The memory 906 in one or more computing devices 900 in the computing device cluster may store the same instructions for executing the data processing method.

In some possible implementations, the memory 906 of one or more computing devices 900 in the computing device cluster may also store partial instructions for executing the data processing method. In other words, the combination of one or more computing devices 900 may jointly execute instructions for executing the data processing method.

It should be noted that the memory 906 in different computing devices 900 in the computing device cluster may store different instructions, which are respectively used to execute part of the functions of the data processing apparatus 600 and the data processing apparatus 700. That is, the instructions stored in the memory 906 in different computing devices 900 may implement the functions of one or more of the cloud download module 610, the backup module 620, and the recovery module 630, or implement the functions of one or more of the restore module 710, the conversion module 720, and the cloud upload module 730.

In some possible implementations, one or more computing devices in the computing device cluster may be connected via a network. The network may be a wide area network or a local area network, etc. FIG. 11 shows a possible implementation. As shown in FIG. 11, two computing devices 900A and 900B are connected via a network. Specifically, the network is connected via a communication interface in each computing device. In this type of possible implementation, the memory 906 in the computing device 900A stores instructions for executing the functions of one or more modules in the cloud module 610, the backup module 620, and the recovery module 630. FIG. 11 takes the memory 906 in the computing device 900A storing instructions for executing the functions of the module of the cloud module 610 as an example. At the same time, the memory 906 in the computing device 900B stores instructions for executing the functions of one or more modules in the cloud module 610, the backup module 620, and the recovery module 630. FIG. 9 takes the memory 906 in the computing device 900B storing instructions for executing the functions of the modules of the backup module 620 and the recovery module 630 as an example.

It should be understood that the functions of the computing device 900A shown in FIG11 may also be completed by multiple computing devices 900. Similarly, the functions of the computing device 900B may also be completed by multiple computing devices 900.

The embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device executes the data processing method shown in FIG3 or the data processing method shown in FIG5.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by the computing device or a data storage device such as a data center containing one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk). The computer-readable storage medium includes instructions that instruct the computing device to execute the data processing method shown in Figure 3, or instruct the computing device to execute the data processing method shown in Figure 5.

The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

In the present application, "at least one" means one or more, and "plurality" means two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b and c can be single or multiple.

It should be noted that, in this application, the words "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being superior to other embodiments or designs. The solution is more preferred or more advantageous. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims (27)

A data processing method, characterized in that it is applied to a data center of a hybrid cloud system, the hybrid cloud system also includes a cloud platform connected to the data center, the backup format of the data center is different from the backup format of the cloud platform, and the data center includes a cloud interface module for communicating with the cloud platform, the method comprising: Acquiring cloud backup data from the cloud platform through the cloud interface module and converting the cloud backup data into original data, wherein the cloud backup data is obtained by the cloud platform performing cloud backup on data of the business running on the cloud platform according to the backup format of the cloud platform; Performing a local backup of the original data according to the backup format of the data center to obtain local backup data; The service is restored in the data center based on the local backup data. The method according to claim 1, characterized in that the converting the cloud backup data into original data through the cloud interface module comprises: Querying the backup format of the cloud backup data through the cloud interface module; The cloud backup data is converted into the original data based on a backup format of the cloud backup data. The method according to claim 1 or 2 is characterized in that the backup format of the cloud platform includes a backup parsing algorithm of the cloud platform, the backup parsing algorithm of the cloud platform is an inverse algorithm of a backup storage algorithm of the cloud platform for cloud backup of data, and the converting of the cloud backup data into the original data based on the backup format of the cloud backup data comprises: The cloud interface module converts the cloud backup data into the original data using the backup parsing algorithm of the cloud platform, wherein the backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm. The method according to any one of claims 1 to 3, characterized in that the backup format of the data center includes a backup storage algorithm and a backup storage layout, and the locally backing up the original data according to the backup format of the data center to obtain the local backup data includes: According to the backup storage algorithm and backup storage layout of the data center, the original data is locally backed up to obtain the local backup data of the cloud backup data in the data center. The method according to any one of claims 1 to 4, characterized in that the cloud interface module includes a list query interface, a backup query interface and a backup read interface, and the obtaining of cloud backup data from the cloud platform through the cloud interface module comprises: Calling the list query interface to query the cloud backup list of the cloud platform, the cloud backup list including at least one set of cloud backup data; Calling the backup query interface to obtain backup information of the cloud backup data corresponding to the business in the at least one group of cloud backup data, the backup information including at least one of a backup storage algorithm, a backup parsing algorithm, and a storage location of the cloud backup data; The backup reading interface is called to obtain the cloud backup data from the cloud platform based on the backup information. The method according to any one of claims 1-5 is characterized in that the cloud interface module includes a software development kit. A data processing method, characterized in that it is applied to a data center of a hybrid cloud system, the hybrid cloud system also includes a cloud platform connected to the data center, the backup format of the data center is different from the backup format of the cloud platform, and the data center includes a cloud interface module for communicating with the cloud platform, the method comprising: Converting local backup data into original data, wherein the local backup data is obtained by the data center performing local backup of data of a business running in the data center according to a backup format of the data center; The original data is converted into a backup format of the cloud platform through the cloud interface module to obtain data to be uploaded to the cloud; The data to be uploaded to the cloud is written into the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data. The method according to claim 7, characterized in that the cloud interface module includes a backup write interface, and the converting of the original data into a backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud comprises: The backup writing interface is called to convert the original data into a backup format of the cloud platform. The method according to claim 8, characterized in that the cloud interface module further includes a backup creation interface, and the step of writing the to-be-uploaded data to the cloud platform through the cloud interface module to obtain cloud backup data comprises: Calling the backup creation interface to create a cloud backup in the cloud platform; The backup writing interface is called to write the data to be uploaded to the cloud into the storage location of the cloud backup to obtain the cloud backup data. The method according to any one of claims 7 to 9, characterized in that the backup format of the data center includes a backup parsing algorithm of the data center, the backup parsing algorithm of the data center is an inverse algorithm of a backup storage algorithm for locally backing up data in the data center, and the converting of the local backup data into the original data includes: The local backup data is converted into the original data using a backup parsing algorithm of the data center, wherein the backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm. The method according to any one of claims 7 to 10, characterized in that the backup format of the cloud platform includes a backup storage algorithm and a backup storage layout, and the writing of the to-be-uploaded data to the cloud platform through the cloud interface module to obtain the cloud backup data comprises: Through the cloud interface module, the data to be uploaded to the cloud is written into the cloud platform according to the backup storage algorithm and backup storage layout of the cloud platform to obtain the cloud backup data. The method according to any one of claims 7-11 is characterized in that the cloud interface module includes a software development kit. A data processing method, characterized in that it is applied to a hybrid cloud system, the hybrid cloud system includes a data center and a cloud platform, the data center is connected to the cloud platform, the backup format of the data center is different from the backup format of the cloud platform, the data center includes a cloud interface module, and the method includes: The data center sends a backup read request to the cloud platform through the cloud interface module; The cloud platform sends cloud backup data to the data center according to the backup read request, where the cloud backup data is obtained by the cloud platform performing cloud backup on data of the business running on the cloud platform according to the backup format of the cloud platform; The data center converts the cloud backup data into original data through the cloud interface module; The data center locally backs up the original data according to the backup format of the data center to obtain local backup data; The data center restores the service at the data center based on the local backup data. The method according to claim 13, characterized in that the method further comprises: The cloud platform provides the cloud interface module; The data center acquires and deploys the cloud interface module. A data processing device, characterized in that the device comprises: A cloud module, used to obtain cloud backup data from the cloud platform through the cloud interface module, and convert the cloud backup data into original data, wherein the cloud backup data is obtained by the cloud platform performing cloud backup on the data of the business running on the cloud platform according to the backup format of the cloud platform; A backup module, used to locally back up the original data according to the backup format of the data center to obtain local backup data; A recovery module is used to restore the business in the data center based on the local backup data. A data processing device, characterized in that the device comprises: A restoration module, used to convert local backup data into original data, wherein the local backup data is obtained by the data center performing local backup of data of the business running in the data center according to the backup format of the data center; A conversion module, used to convert the original data into a backup format of the cloud platform through the cloud interface module to obtain data to be uploaded to the cloud; The cloud module is used to write the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data, so that the cloud platform can restore the business on the cloud platform based on the cloud backup data. A data processing system, characterized in that the system comprises: A local backup device, used to send a backup read request to the cloud platform through a cloud interface module; A cloud backup device, used for sending cloud backup data to the data center according to the backup read request, wherein the cloud backup data is obtained by the cloud platform performing cloud backup on data of the business running on the cloud platform according to the backup format of the cloud platform; The local backup device is further used to convert the cloud backup data into original data through the cloud interface module; The local backup device is further used to locally back up the original data according to the backup format of the data center to obtain local backup data; The local backup device is further used to restore the business in the data center based on the local backup data. The system according to claim 17 is characterized in that the local backup device is further used to: convert local backup data into original data, the local backup data being obtained by the data center performing local backup of data of the business running in the data center according to the backup format of the data center; converting the original data into the backup format of the cloud platform through the cloud interface module to obtain data to be uploaded to the cloud; writing the data to be uploaded to the cloud platform through the cloud interface module to obtain cloud backup data; The cloud backup device is also used to restore the business on the cloud platform based on the cloud backup data. A computing device cluster, characterized in that it includes at least one computing device, each computing device includes a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 1 to 6. A computing device cluster, characterized in that it includes at least one computing device, each computing device includes a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to any one of claims 7 to 12. A computing device cluster, characterized in that it includes at least one computing device, each computing device includes a processor and a memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method according to claim 13 or 14. A computer program product comprising instructions, characterized in that when the instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 6. A computer program product comprising instructions, characterized in that when the instructions are executed by a computing device cluster, the computing device cluster executes the method as claimed in any one of claims 7 to 12. A computer program product comprising instructions, characterized in that when the instructions are executed by a computing device cluster, the computing device cluster executes the method according to claim 13 or 14. A computer-readable storage medium, characterized in that it includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method according to any one of claims 1 to 6. A computer-readable storage medium, characterized in that it includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method as described in any one of claims 7 to 12. A computer-readable storage medium, characterized in that it includes computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster executes the method according to claim 13 or 14.