Data processing method, apparatus and system

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

[0001] 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 into this application. Technical Field

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

[0003] With the increasing virtualization of enterprise information technology (IT), enterprises are using virtualized data centers to process data and services locally. To improve data security, enterprises typically back up data in both data centers and cloud computing platforms. Consequently, data centers and cloud platforms often serve as each other's disaster recovery sites.

[0004] Typically, an enterprise's virtualized data center disaster recovery solution is provided by the disaster recovery vendor, while the cloud platform disaster recovery solution is provided by the cloud platform vendor. Due to the different disaster recovery solutions, the data backup formats of the data center and cloud platform are not standardized, making the backup data of the cloud platform and the data center incompatible and inconvertible. In a hybrid cloud scenario, an enterprise runs part of its business in the data center and part on the cloud platform. In the event of a cloud platform failure, the data center cannot use the cloud platform's backup data to restore the cloud platform's business according to the disaster recovery solution provided by the disaster recovery vendor, resulting in low recovery efficiency.

[0005] Summary of the Invention

[0006] 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.

[0007] In a first aspect, the present application provides a data processing method for use in 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 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 in accordance with the backup format of the data center to obtain local backup data. When it is necessary to restore the cloud platform's business in the data center, the data center restores the cloud platform's business in the data center based on the local backup data.

[0008] Cloud backup data is a backup of business data running on the cloud platform, conforming to the cloud platform's backup format. Raw data refers to unprocessed data that has not been modified, cleaned, or filtered, such as data stored by users in data center storage (such as disks) before local backup.

[0009] 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 unprocessed original data that 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 recovery efficiency.

[0010] As one possible implementation, the data center uses the cloud interface module to query the backup format corresponding to the cloud backup data and then converts the cloud backup data into the original data based on the corresponding backup format. This allows the data center to query and convert the backup format of the cloud backup data even if the disaster recovery solution used by the data center differs from that of the cloud platform.

[0011] Alternatively, the cloud interface module may be a software development kit (SDK) provided by the cloud platform. The SDK may encapsulate interfaces containing codes for implementing different functions, such as a backup query (get) interface and a backup read (read) 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 raw data based on the backup format corresponding to the cloud backup data.

[0012] As one possible implementation, the cloud platform's backup format corresponds 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 of the backup storage algorithm. That is, after the cloud platform stores data as cloud backup data based on the backup storage algorithm, the cloud platform or data center can restore the cloud backup data to its original state based on the backup parsing algorithm. This allows the data center, even if using a different disaster recovery solution than the cloud platform, to call upon the cloud interface module's interface to identify and convert cloud backup data.

[0013] Optionally, the data center uses a backup parsing algorithm through the cloud interface module to convert the cloud backup data into original data. For example, the backup parsing algorithm may include at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm. The data center invokes the backup read interface and processes the cloud backup data according to the deduplication and restoration algorithm, decompression algorithm, and decryption algorithm corresponding to the cloud backup data to restore the cloud backup data to original data.

[0014] 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 the backup storage algorithm and backup storage layout used by the data center for data backup.

[0015] Optionally, the data center performs a local backup of the original data according to its backup storage algorithm and backup storage layout, generating 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 data center's local disaster recovery solution. The resulting local backup data can be recognized and applied by the data center's local disaster recovery solution, providing a data foundation for the data center to directly recover cloud platform services locally based on the local disaster recovery solution.

[0016] 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. 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. 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.

[0017] 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 cloud platform's business 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 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 that of the cloud platform, compared to building a 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 platform through the cloud interface module in a backup format that can be recognized and applied by the cloud platform's disaster recovery solution. The software platform corresponding to the disaster recovery solution used by the cloud platform can directly restore the cloud platform's business on the cloud based on the uploaded cloud backup data, thereby improving recovery efficiency and reducing software architecture costs.

[0018] 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, where the local backup data is obtained by the data center performing a local backup of data of services 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 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 services on the cloud platform based on the cloud backup data.

[0019] 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.

[0020] 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.

[0021] As one possible implementation, the data center's backup format includes its own backup parsing algorithm. This algorithm is the inverse of the backup storage algorithm used by the data center to perform local data backups. The data center uses this algorithm to convert 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.

[0022] As a possible implementation, 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.

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

[0024] A third aspect provides a data processing method for 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 communicatively connected, and the backup format of the data center and the backup format of the cloud platform differ. 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 in response to the data center's call to the cloud interface module. The cloud backup data is obtained by the cloud platform performing a cloud backup of data of services running on the cloud platform in the cloud platform's backup format.

[0025] 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.

[0026] 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 communicatively connected, and the backup format of the data center and the backup format of the cloud platform are different. 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 via the cloud interface module; the cloud platform sends cloud backup data to the data center in response to the backup read request, the cloud backup data being obtained by the cloud platform performing a cloud backup of data of services running on the cloud platform in accordance with the backup format of the cloud platform; the data center converts the cloud backup data into original data via the cloud interface module; the data center performs a local backup of the original data in accordance with the backup format of the data center to obtain local backup data; and the data center restores services in the data center based on the local backup data.

[0027] As a possible implementation, the steps 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 the original data.

[0028] As one possible implementation, the cloud platform provides a cloud interface module. The data center then obtains and deploys the cloud interface module on the software platform corresponding to the disaster recovery solution used by the data center. This allows the cloud platform to expose 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, enabling the data center to identify and apply the cloud platform data through the cloud interface module.

[0029] In a fifth aspect, a data processing device is provided. The data processing device includes a cloud download module, a backup module, and a recovery module. The cloud download module is configured to obtain cloud backup data from the cloud platform via the cloud interface module and convert the cloud backup data into original data. The cloud backup data is obtained by the cloud platform performing a cloud backup of data of services running on the cloud platform in accordance with the cloud platform's backup format. The backup module is configured to perform a local backup of the original data in accordance with the data center's backup format to obtain local backup data. The recovery module is configured to restore services in the data center based on the local backup data.

[0030] As a possible implementation manner, the 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.

[0031] As one possible implementation, the cloud platform's backup format includes the cloud platform's backup parsing algorithm, which is the inverse of the cloud platform's backup storage algorithm used to back up data. The lower cloud module is specifically configured to convert the cloud backup data into original data using the cloud platform's backup parsing algorithm via the cloud interface module. The backup parsing algorithm includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm.

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

[0033] 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 configured to: call the list query interface to query the cloud platform's cloud backup list, which includes at least one set of cloud backup data; call the backup query interface to obtain backup information for the cloud backup data corresponding to a service in the at least one set of cloud backup data; the backup information includes at least one of the following: a backup storage algorithm, a backup parsing algorithm, and a storage location for the cloud backup data; and call the backup read interface to retrieve the cloud backup data from the cloud platform based on the backup information.

[0034] As one possible implementation, the data processing device further includes a cloud migration module. The backup module is specifically configured to convert local backup data into raw data, and then convert the raw data into a backup format suitable for the cloud platform, thereby obtaining data to be migrated to the cloud. The cloud migration module is configured to write the data to be migrated to the cloud platform via the cloud interface module, thereby obtaining cloud backup data, so that the cloud platform can restore services on the cloud platform based on the cloud backup data.

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

[0036] In a sixth aspect, a data processing device is provided. The data processing device includes a restoration module, a conversion module, and a cloud migration module. The restoration module is used to convert local backup data into original data. 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 data center's backup format. 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 migration 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.

[0037] 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 the backup format of the cloud platform.

[0038] As a possible implementation method, the cloud interface module also includes a backup creation interface. 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 cloud backup data.

[0039] As one possible implementation, the data center's backup format includes the data center's backup parsing algorithm, which is the inverse of the data center's backup storage algorithm used to back up data locally. The restore module is specifically configured to convert the local backup data into the original data using the data center's backup parsing algorithm, which includes at least one of a deduplication and restoration algorithm, a decompression algorithm, and a decryption algorithm.

[0040] 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.

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

[0042] In a seventh aspect, a data processing device is provided. The data processing device includes an interface processing module. The interface processing module is configured to respond to a call from a data center to a cloud interface module. For example, the interface processing module is configured to return cloud backup data to the data center based on the call from the data center to the cloud interface module.

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

[0044] 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 based on 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.

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

[0046] Regarding the technical principles and beneficial effects of the second, third, fourth, fifth, sixth, seventh and eighth aspects, please refer to the relevant description of the first aspect above and will not be repeated here.

[0047] In a ninth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device including 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 performs the data processing method described in any possible implementation of the first aspect.

[0048] In a tenth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device including 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 performs the data processing method described in any possible implementation of the second aspect.

[0049] In an eleventh aspect, a computing device cluster is provided, comprising at least one computing device, each computing device including 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 performs the data processing method described in any possible implementation of the third aspect.

[0050] 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 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 performs the data processing method described in any possible implementation of the fourth aspect.

[0051] 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 is caused to execute the data processing method described in any possible implementation of the first aspect.

[0052] 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 executed on a computer, the computer is caused to execute the data processing method described in any possible implementation of the second aspect.

[0053] 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 is caused to execute the data processing method described in any possible implementation of the third aspect.

[0054] 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 is caused to execute the data processing method described in any possible implementation of the fourth aspect.

[0055] In a seventeenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, causes the computer to execute the data processing method described in any possible implementation of the first aspect.

[0056] In an eighteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions, which, when executed on a computer, causes the computer to execute the data processing method described in any possible implementation of the second aspect.

[0057] In a nineteenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, causes the computer to execute the data processing method described in any possible implementation of the third aspect.

[0058] In a twentieth aspect, a computer-readable storage medium is provided. The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, causes the computer to execute the data processing method described in any possible implementation of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] FIG1 is a schematic diagram of the structure of a hybrid cloud system provided by this application;

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

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

[0062] FIG4 is a schematic diagram of a backup storage layout provided by this application;

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

[0064] FIG6 is a schematic structural diagram of a data processing device provided by the present application;

[0065] FIG7 is a schematic structural diagram of another data processing device provided by the present application;

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

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

[0068] FIG10 is a schematic diagram of the structure of a computing device cluster provided by this application;

[0069] FIG11 is a schematic diagram of a network connection of a computing device cluster provided in this application. DETAILED DESCRIPTION

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

[0071] (1) Cloud Platform

[0072] A cloud platform, also known as a cloud computing platform, is a service based on hardware and software resources, providing computing, networking, and storage capabilities. That is, the platform provider combines the cloud (remote hardware resources) and computing (remote software resources) to form a platform that provides various services to users.

[0073] Services provided by cloud platforms can include software as a service (SaaS), platform as a service (PaaS), and infrastructure as a service (IaaS). SaaS involves a service provider deploying application software on the cloud platform's servers, and users subscribe to the application software services from the service provider over the internet based on their needs. PaaS offers a development environment as a service, meaning the service provider provides users with services such as a development environment, server platforms, and hardware resources. Users develop applications within the cloud platform's development environment and share them with other users via the cloud platform and the internet. IaaS involves a service provider providing a cloud infrastructure consisting of multiple servers as a service to users. This integrates memory, input / output devices, storage, and computing resources into a virtual resource pool, providing users with storage resources and virtualized servers.

[0074] (2) Hybrid Cloud

[0075] As a form of cloud computing, hybrid cloud combines private clouds (such as virtualized data centers) and public clouds (such as cloud platforms provided by cloud service providers) to improve cross-cloud resource utilization. Enterprise IT architectures have evolved from centralized mainframes to distributed virtualized architectures and are currently evolving toward multi-site, multi-cloud architectures. Depending on the specific characteristics of each business, enterprises deploy different services in private and public clouds. For example, for security reasons, enterprises can store private data in their own private clouds. At the same time, testing services (which frequently change and upgrade) and services frequently accessed by external users can be deployed on the public cloud, leveraging the public cloud's advantages of reliability, professional operations and maintenance, and rapid resource expansion.

[0076] (3) Disaster recovery

[0077] Disaster recovery, short for disaster tolerance and backup, refers to the use of existing scientific and technological means and methods to establish reliable emergency response methods in advance to cope with emergencies. Disaster recovery involves switching the system to backup devices and systems to restore operations in the event of a system failure or other catastrophic event. Backup involves storing data and business-related programs on another device or system to facilitate business recovery in the event of a system failure or disaster.

[0078] The present application provides a data processing method, in particular, a data processing method in which "a data center obtains the ability to identify and process cloud platform backup data 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.

[0079] 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.

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

[0081] Figure 1 is a schematic diagram of the structure of a hybrid cloud system provided by this application. As shown in Figure 1, hybrid cloud system 100 includes a data center 110 and a cloud platform 120. Data center 110 and cloud platform 120 are communicatively connected, and data center 110 and cloud platform 120 serve as remote disaster recovery sites for each other.

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

[0083] Production host 111, an application server in data center 110, such as a server or desktop computer, is used to generate and allocate resources based on user needs using virtualization technology. At the hardware level, production host 111 is equipped with a processor and memory (not shown in Figure 1). The functions of production host 111 are implemented by the processor running programs in the memory. Production host 111 can also read and write data to storage device 112 based on application requirements.

[0084] The storage device 112 serves as 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 memory, such as network attached storage (NAS), or may be provided with a network card, a processor, and 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 to 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 a hard disk. Memory refers to 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 generally used to store data persistently.

[0085] 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 .

[0086] 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.

[0087] For businesses running in data center 110, disaster recovery software platform 113 performs software and data backups based on the backup format specified by the disaster recovery solution provided by the disaster recovery provider, thereby storing the local backup data in storage device 112. The backup format specified by the disaster recovery solution provided by the disaster recovery provider can be referred to as the backup format of data center 110.

[0088] In this way, when local business needs to be restored, the disaster recovery software platform 113 restores the business based on the local backup data of the local business of the data center 110.

[0089] For services running on cloud platform 120, disaster recovery software platform 113 obtains cloud backup data from cloud platform 120 via cloud interface module 114, converts the cloud backup data into raw data, and then locally backs up the raw data in the backup format of data center 110 to obtain local backup data corresponding to the cloud backup data. The raw data can be in the format of data directly read from a storage device such as a disk when data center 110 runs services.

[0090] 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.

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

[0092] 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.

[0093] The list query interface is used to return the cloud backup list of cloud platform 120. The cloud backup list includes at least one set of cloud backup data. Each set of cloud backup data can be data from different services or different versions of the same service. The cloud backup list can use identifiers that correspond one-to-one with at least one set of cloud backup data to represent the cloud backup data, for example, backup1, backup2, backup3, etc.

[0094] The backup query interface is used to return backup information for one or more sets of cloud backup data for a specific query. This backup information includes the cloud backup data's storage location, universally unique identifier (UUID), resource type, resource size, and backup storage algorithm. The backup storage algorithm is the backup storage algorithm corresponding to the backup format specified by the backup solution provided by the cloud platform 120 vendor.

[0095] The backup open interface is used to open cloud backup data and return a reference handle to the cloud backup data.

[0096] 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.

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

[0098] 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 the 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.

[0099] 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 .

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

[0101] 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.

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

[0103] 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 pass AK / SK (Access Key / Secret Key) authentication, manage each other as a protected environment, and thus establish a communication connection.

[0104] 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.

[0105] For businesses running on cloud platform 120, cloud backup software platform 123 performs software and data backups on the businesses running on cloud platform 120 based on the backup format specified by the disaster recovery solution provided by the vendor of cloud platform 120, thereby storing the cloud backup data in storage device 122. The backup format specified by the disaster recovery solution provided by the vendor of cloud platform 120 may be referred to as the backup format of cloud platform 120.

[0106] 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 .

[0107] 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 backup format data of the cloud platform 120 uploaded by the data center 110 into the storage device 122, and obtains cloud backup data.

[0108] 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.

[0109] 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.

[0110] It is worth noting that FIG1 is merely a schematic diagram and should not be construed as limiting 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 network devices for supporting communication between the data center 110 and the cloud platform 120. The network devices may be one or more switches and routers, or the data center 110 and the cloud platform 120 may be connected via a dedicated cloud line. For another example, FIG1 only illustrates 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 .

[0111] Based on the hybrid cloud system 100 shown in FIG1 , the data center 110 and the cloud platform 120 can implement the function of a 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, computing node, or storage node, etc.) virtualized using the resources (e.g., computing resources and storage resources) of the data center 110 or the cloud platform 120.

[0112] Next, the virtualized hierarchical structure of the data center 110 or the cloud platform 120 will be described with reference to FIG. 2 .

[0113] As shown in Figure 2, IaaS platform 210 is used to virtualize all infrastructure resources in data center 110 or cloud platform 120, providing users with virtual resources (e.g., computing resources, network resources, and storage resources) through a software-defined approach. Infrastructure resources refer to the resources provided by the computing server cluster, storage server cluster, management server cluster, and / or network device cluster in data center 110 or cloud platform 120.

[0114] The PaaS platform 220 implements the runtime environment and application support functions of the data center 110 or cloud platform 120. Users can apply for quota-based computing units, rather than virtual resources, to run their services. Alternatively, the computing units can be containers, and the data center 110 or cloud platform 120 schedules the containers to deploy and run the user's code. It should be noted that the PaaS platform 220 can contain one or more containers; Figure 2 shows only one container as an example.

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

[0116] Among them, components may include database components, message queue components, orchestration components, log components, virtualization components, business database components, configuration database components, rights management components, etc.

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

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

[0119] The steps of the data processing method provided in this application are executed by the data center 110 and the cloud platform 120. The data processing method provided in this application is described below with reference to FIG3 .

[0120] 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.

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

[0122] 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 based on the logical block address offset or index contained in the backup read request, and convert the cloud backup data into original data.

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

[0124] 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 (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.

[0125] Optionally, the backup storage algorithm for 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 for the cloud backup data is an inverse algorithm of the aforementioned deduplication algorithm, decompression algorithm, and encryption algorithm, such as at least one of a deduplication restoration algorithm, a decompression algorithm, and a decryption algorithm.

[0126] 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 reading 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.

[0127] For example, as shown in FIG4 , 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 IDs), block names (block names), block paths (block paths), cyclic redundancy checks (CRCs), and block sizes (sizes) 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.

[0128] The backup storage layout of the cloud backup data can be exposed to the data center 110 via the cloud interface module 114. When targeting different virtualized data centers, the cloud platform 120 can also expose the backup storage layout of the cloud backup data to the different virtualized data centers via the cloud interface module 114. In this way, the cloud platform 120 can address different virtualized data centers without having to provide different client versions, thereby covering a wider range of data centers and increasing the applicability of the hybrid cloud system 100.

[0129] 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.

[0130] 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 .

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

[0132] The backup storage layout of the data center 110 may be referred to FIG4 , which will not be described in detail here.

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

[0134] 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.

[0135] 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 local backup data.

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

[0137] Based on the above steps 310-330, when data center 110 uses the disaster recovery software platform 113 provided by the disaster recovery vendor, and the backup format supported by disaster recovery software platform 113 is different from the backup format supported by cloud backup software platform 123, it can also use the functions encapsulated by cloud interface module 114 to obtain and convert cloud backup data, thereby enabling disaster recovery software platform 113 to restore the services originally running on cloud platform 120 in data center 110 based on the converted cloud backup data. In this way, data center 110 does not need to install the cloud backup software corresponding to cloud platform 120 locally, nor does cloud platform 120 need to provide multiple versions of cloud backup software for different versions of disaster recovery software platforms used by different data centers 110. Data center 110 can directly restore the services of cloud platform 120 locally using the locally installed disaster recovery software platform 113, thereby improving recovery efficiency.

[0138] 3 and 4, the process of cloud backup data migration in the data processing method is described above. The data processing method may also include cloud migration of local data from the data center 110. Next, the process of cloud migration of local data from the data center 110 is described in conjunction with FIG5.

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

[0140] As a possible example, data center 110 performs a local backup of data generated by production host 111 running in data center 110 according to a configured backup policy to obtain local backup data. For example, data center 110 performs a backup of data center 110 service data at 9:00 am every day according to the backup policy.

[0141] As one possible implementation, data center 110 backs up service data of data center 110 according to a backup format of data center 110. The backup format of data center 110 corresponds to the backup format of disaster recovery software platform 113 provided by the disaster recovery vendor of data center 110, and may include a backup storage algorithm and a backup storage layout.

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

[0143] 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 .

[0144] As one possible implementation, data center 110 calls a backup creation interface to create a new set of cloud backups on cloud platform 120. Data center 110 then restores the local backup data to its original form and calls a backup write interface to convert the cloud backup data to the backup format of cloud platform 120, obtaining the data to be uploaded to the cloud. Finally, data center 110 writes the data to be uploaded to the storage location of the new cloud backup created on cloud platform 120 according to the backup storage layout of cloud platform 120.

[0145] Optionally, the data center 110 writes the data to be uploaded to 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.

[0146] 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 .

[0147] Step 530 : The cloud platform 120 restores the service on the cloud platform 120 based on the cloud backup data.

[0148] 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.

[0149] 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.

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

[0151] Based on steps 510-530 above, after cloud platform 120 stores data from data center 110's services as cloud backup data, cloud backup software platform 123 can restore services originally running in data center 110 on cloud platform 120 based on the cloud backup data. This eliminates the need to build data center 110's disaster recovery software platform 113 on cloud platform 120. Instead, cloud platform 120 can use the cloud-native backup and recovery capabilities of cloud backup software platform 123 to restore services in data center 110, improving recovery efficiency and reducing software development costs.

[0152] In order to cooperate with the data processing method shown in FIG3 provided by the present application, the present application further provides a data processing device 600, as shown in FIG6 , comprising:

[0153] 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 by backing up the data of the business running on the cloud platform in accordance with the backup format of the cloud platform.

[0154] The backup module 620 is configured to perform a local backup of the original data according to the backup format of the data center to obtain local backup data.

[0155] The recovery module 630 is used to restore services in the data center based on the local backup data.

[0156] The cloud module 610, backup module 620, and recovery module 630 can all be implemented via software or hardware. For example, the implementation of the cloud module 610 will be described below using 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.

[0157] As an example of a software functional unit, the cloud module 610 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Furthermore, the 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 geographically close data centers. Typically, a region may include multiple AZs.

[0158] Similarly, multiple hosts / virtual machines / containers running the code can be distributed within the same virtual private cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

[0159] As an example of a hardware functional unit, the cloud module 610 may include at least one computing device, such as a server. Alternatively, the cloud module 610 may be implemented using 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.

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

[0161] 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 full functions of the data processing device 600 are realized by respectively implementing different steps in the data processing method through the cloud module 610, the backup module 620 and the recovery module 630.

[0162] In order to cooperate with the data processing method shown in FIG5 provided by the present application, the present application further provides a data processing device 700, as shown in FIG7 , comprising:

[0163] Restoring module 710, configured to convert local backup data into original data, wherein the local backup data is obtained by a data center performing a local backup of data of services running in the data center according to the data center's backup format;

[0164] A conversion module 720 is configured 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;

[0165] The cloud migration module 730 is used to write the data to be migrated 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.

[0166] The restoration module 710, the conversion module 720, and the cloud module 730 can all be implemented by software or hardware. For example, the implementation of the data processing device 700 and each module of the data processing device 700 is the same as that of the data processing device 600 and will not be repeated here.

[0167] Since the data processing method provided in this application requires the data center 110 and the cloud platform 120 to communicate with each other in the steps shown in Figure 3 or Figure 5, the application also provides a data processing system 800, as shown in Figure 8, which includes:

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

[0169] 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 by backing up the data of the business running on the cloud platform according to the backup format of the cloud platform.

[0170] The local backup device 810 is further configured to convert the cloud backup data into original data through the cloud interface module.

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

[0172] The local backup device 810 and the cloud backup device 820 can be implemented by software or hardware. For 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.

[0173] As an example of a software functional unit, the local backup device 810 may include a 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 above-mentioned 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, and each AZ includes one data center or multiple data centers with close geographical locations. Generally, a region may include multiple AZs.

[0174] Similarly, the multiple hosts / virtual machines / containers running the code can be distributed within the same VPC or across multiple VPCs. Typically, a VPC is located within a region. Cross-region communication between two VPCs within the same region, or between VPCs in different regions, requires a communication gateway within each VPC to interconnect the VPCs.

[0175] 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.

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

[0177] 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 servers, ASICs, PLDs, CPLDs, FPGAs, GALs, and other computing devices.

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

[0179] This application also provides a computing device 900. As shown in Figure 9, computing device 900 includes a bus 902, a processor 904, a memory 906, and a communication interface 908. Processor 904, memory 906, and communication interface 908 communicate with each other via bus 902. Computing device 900 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in computing device 900.

[0180] Bus 902 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. Buses may be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG9 illustrates a single bus line, but this does not imply a single bus or type of bus. Bus 902 may include a path for transmitting information between various components of computing device 900 (e.g., memory 906, processor 904, and communication interface 908).

[0181] The processor 904 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

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

[0183] Memory 906 stores executable program code, which processor 904 executes to implement the functions of the aforementioned cloud module 610, backup module 620, and recovery module 630, thereby implementing the data processing method. In other words, memory 906 stores instructions for executing the data processing method. FIG9 merely illustrates the example of memory 906 storing program code that implements the functions of the aforementioned cloud module 610, backup module 620, and recovery module 630.

[0184] Alternatively, the memory 906 stores executable code, and the processor 904 executes the executable code to respectively implement the functions of the aforementioned restoration module 710, conversion module 720, and cloud migration module 730, thereby implementing the data processing method. In other words, the memory 906 stores instructions for executing the data processing method.

[0185] Alternatively, the memory 906 stores executable code, and the processor 904 executes the executable code to respectively implement the functions of the local backup device 810 and the cloud backup device 820, thereby implementing the data processing method. In other words, the memory 906 stores instructions for executing the data processing method.

[0186] 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 a communication network.

[0187] Considering that the data processing method provided in this application is applied to the hybrid cloud system 100, the infrastructure of the data center 110 and the cloud platform 120 each typically includes multiple computing devices. Therefore, this 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 computer, a laptop computer, or a smartphone.

[0188] As shown in Figure 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.

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

[0190] It should be noted that the memory 906 in different computing devices 900 in the computing device cluster can store different instructions, which are respectively used to execute part of the functions of the data processing device 600 and the data processing device 700. In other words, the instructions stored in the memory 906 in different computing devices 900 can 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.

[0191] In some possible implementations, one or more computing devices in a computing device cluster may be connected via a network. The network may be a wide area network (WAN) or a local area network (LAN), among others. FIG. 11 illustrates one 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 of the cloud module 610, the backup module 620, and the recovery module 630. FIG. 11 takes the example of the memory 906 in the computing device 900A storing instructions for executing the functions of the cloud module 610. At the same time, the memory 906 in the computing device 900B stores instructions for executing the functions of one or more of the cloud module 610, the backup module 620, and the recovery module 630. FIG. 9 takes the example of the memory 906 in the computing device 900B storing instructions for executing the functions of the backup module 620 and the recovery module 630.

[0192] It should be understood that the functionality of the computing device 900A shown in FIG11 may also be implemented by multiple computing devices 900. Similarly, the functionality of the computing device 900B may also be implemented by multiple computing devices 900.

[0193] The present application also provides a computer program product comprising instructions. The computer program product may be software or a program product comprising 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.

[0194] 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 a 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 (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state drive). 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.

[0195] 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 program 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, computer, server or data center to another website, computer, server or data center via a wired (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer 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 drive.

[0196] Those skilled 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 beyond the scope of this application.

[0197] Those skilled in the art will 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.

[0198] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0200] 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.

[0201] 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, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment 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.

[0202] In this application, "at least one" means one or more, and "more" 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 items" or similar expressions refers to any combination of these items, including any combination of single items 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.

[0203] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0204] 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 deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A data processing method, characterized in that: A data center applied to a hybrid cloud system, the hybrid cloud system further comprising a cloud platform connected to the data center, the backup format of the data center being different from the backup format of the cloud platform, the data center comprising 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.

2. The method according to claim 1, characterized in that: The converting the cloud backup data into original data through the cloud interface module includes: 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.

3. The method according to claim 1 or 2, characterized in that: The backup format of the cloud platform includes a backup parsing algorithm of the cloud platform, which is an inverse algorithm of a backup storage algorithm of the cloud platform for cloud backup of data. The step of converting the cloud backup data into the original data based on the backup format of the cloud backup data includes: 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.

4. 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.

5. 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 reading interface. The cloud backup data is obtained from the cloud platform through the cloud interface module, including: 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.

6. The method according to any one of claims 1 to 5, characterized in that The cloud interface module includes a software development kit.

7. A data processing method, characterized in that: A data center applied to a hybrid cloud system, the hybrid cloud system further comprising a cloud platform connected to the data center, the backup format of the data center being different from the backup format of the cloud platform, the data center comprising 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.

8. The method according to claim 7, characterized in that The cloud interface module includes a backup write interface, and the original data is converted into a backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud, including: The backup writing interface is called to convert the original data into a backup format of the cloud platform.

9. The method according to claim 8, characterized in that The cloud interface module also includes a backup creation interface, and the cloud interface module is used to write the data to be uploaded to the cloud platform to obtain cloud backup data, including: 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.

10. 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 of the data center for local backup of data. 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.

11. 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. The cloud interface module is used to write the data to be uploaded to the cloud platform to obtain cloud backup data, including: 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.

12. The method according to any one of claims 7 to 11, characterized in that: The cloud interface module includes a software development kit.

13. A data processing method, characterized in that: 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.

14. 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.

15. 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.

16. 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.

17. 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.

18. The system according to claim 17, characterized in that The local backup device is further used to: convert local backup data into original data, wherein the local backup data is obtained by the data center performing local backup on data of the business running in the data center according to the backup format of the data center; The original data is converted into the backup format of the cloud platform through the cloud interface module to obtain the data to be uploaded to the cloud; the data to be uploaded to the cloud platform is written into the cloud platform through the cloud interface module to obtain the cloud backup data; The cloud backup device is also used to restore the business on the cloud platform based on the cloud backup data.

19. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising 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.

20. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising 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.

21. A computing device cluster, characterized in that: comprising at least one computing device, each computing device comprising 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.

22. 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.

23. 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 7 to 12.

24. 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.

25. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 1 to 6.

26. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to any one of claims 7 to 12.

27. A computer-readable storage medium, characterized in that: The method comprises computer program instructions, and when the computer program instructions are executed by a computing device cluster, the computing device cluster performs the method according to claim 13 or 14.

Images