Disaster recovery method, platform, system, computer device and storage medium
By recording and matching tenant and cloud platform information, effective backup requests are generated, multi-cloud platform and tenant management problems in the existing technology are solved, intelligent disaster recovery demand identification and diversified backup operations are realized, and the needs of multiple application scenarios are met. .
Patent Information
- Application Number
- CN202210130365.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-02-11
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2042-02-11
AI Technical Summary
The existing technology lacks a unified disaster recovery method to centrally configure, manage and monitor multiple cloud platforms and tenants, which cannot meet diversified backup needs and business scenarios, and lacks automatic identification and intelligence of tenants' disaster recovery needs. deal with.
By pre-recording historical tenant and cloud platform information, obtain disaster recovery requirements, match target tenant and historical tenant information, generate effective backup requests, and send them to the corresponding cloud platform to perform backup operations, realizing unified backup management for multiple types of cloud platforms.
It realizes intelligent identification of disaster recovery needs, unified management of backups of multiple cloud platform resources, meets diverse backup types and planning needs, and is suitable for multi-tenant scenarios, improving the flexibility and efficiency of backup operations.
Smart Images

Figure CN114528155B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data backup, and more specifically, to a disaster recovery method, platform, system, computer equipment and storage medium. Background Art
[0002] Considering the security and high availability of cloud systems, it is necessary to perform disaster recovery backup for key resources such as virtual machines, files, and databases on cloud platforms. Currently, cloud platforms are roughly divided into three types: openstack, vmware, and hyper-v. Due to the hybrid cloud environment of openstack, vmware, and hyper-v and the multi-location, multi-cluster, and multi-tenant distribution of cloud platform systems, disaster recovery work needs to be performed manually between various cloud platform systems. Each cloud platform has its own matching data backup method, and as more and more cloud systems are added, the resource disaster recovery work of many systems becomes increasingly arduous. In this case, a unified and intelligent disaster recovery method is very necessary and important.
[0003] In the existing technology, clusters are widely distributed and there are many tenants. There is no unified disaster recovery method to centrally configure, manage and monitor all clusters and all tenants. In addition, the backup methods of most cloud platforms are relatively simple and cannot meet the various backup needs and business scenarios. For example, virtual machine backup, file backup, and database backup are differentiated by resources; full backup and incremental backup are differentiated by backup content; single backup, hourly backup, daily backup, weekly backup, monthly backup, etc. are differentiated by time. In addition, the existing technology lacks the technology to automatically identify the disaster recovery needs of tenants and perform disaster recovery intelligently. Summary of the invention
[0004] The present invention aims to overcome at least one defect (shortcoming) of the above-mentioned prior art and provide a disaster recovery method, platform, system, computer device and storage medium for intelligently identifying disaster recovery needs and uniformly backing up resources on various types of cloud platforms.
[0005] The technical solution adopted in the first aspect of the present invention is:
[0006] A disaster recovery method, applied to a disaster recovery platform, comprises the following steps:
[0007] Pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information; the historical cloud platform information is information of the cloud platform where the backup data of the historical tenant is located;
[0008] Obtaining disaster recovery requirements, and obtaining target tenant information and target backup information of the target tenant according to the disaster recovery requirements analysis;
[0009] Matching the target tenant information with the historical tenant information to obtain matched historical tenant information and historical cloud platform information corresponding to the matched historical tenant information;
[0010] A valid backup request is generated based on the matched historical cloud platform information and the target backup information, and the valid backup request is sent to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request.
[0011] Furthermore, the cloud platform includes multiple clusters, each cluster includes backup data, and the target tenant information includes the target tenant name and the resource address of the backup data.
[0012] Further, the historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information;
[0013] The target backup information includes at least one of a backup type, a backup plan, and a backup option;
[0014] Generate a valid backup request according to the matched historical cloud platform information and the target backup information, including:
[0015] Based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, a backup request for the cloud platform corresponding to the historical cloud platform information is generated; based on the backup request and the key corresponding to the historical tenant information, a valid backup request is generated.
[0016] Furthermore, obtain disaster recovery requirements, including:
[0017] When performing disaster recovery operations automatically, obtain disaster recovery requirements from the work order platform;
[0018] When performing disaster recovery operations manually, receive disaster recovery requirements sent by users.
[0019] Further, after sending the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0020] Receive the response and backup operation status sent by the cloud platform, and periodically send query requests to the cloud platform to query the backup operation status of the cloud platform.
[0021] Further, after sending the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0022] If the backup operation fails, the failure reason sent by the cloud platform is received and the disaster recovery status is updated.
[0023] The technical solution adopted in the second aspect of the present invention is:
[0024] A disaster recovery platform, comprising:
[0025] A recording module, used to pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information; the historical cloud platform information is information of the cloud platform where the backup data of the historical tenant is located;
[0026] A demand acquisition module is used to acquire disaster recovery requirements and obtain target tenant information and target backup information of the target tenant according to the disaster recovery requirements analysis;
[0027] A matching module, used to match the target tenant information with the historical tenant information, and obtain the matched historical tenant information and the historical cloud platform information corresponding to the matched historical tenant information;
[0028] The request module is used to generate a valid backup request based on the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request.
[0029] The technical solution adopted in the third aspect of the present invention is:
[0030] A disaster recovery system, comprising a disaster recovery platform, a work order platform and a cloud platform;
[0031] The work order platform is used to receive disaster recovery requirements sent by users;
[0032] The disaster recovery platform is used to pre-record historical tenant information and historical cloud platform information corresponding to the historical tenant information; obtain disaster recovery requirements from the work order platform, analyze target tenant information and target backup information according to the disaster recovery requirements, and match the target tenant information with the historical tenant information to obtain matched historical tenant information and historical cloud platform information corresponding to the matched historical tenant information; generate a valid backup request based on the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information;
[0033] The cloud platform is used to perform a backup operation according to the valid backup request.
[0034] The technical solution adopted in the fourth aspect of the present invention is:
[0035] A computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor implements the disaster recovery method when executing the computer program.
[0036] The technical solution adopted in the fifth aspect of the present invention is:
[0037] A computer-readable storage medium stores a computer program, which implements the disaster recovery method when executed by a processor.
[0038] Compared with the prior art, the present invention has the following beneficial effects:
[0039] The disaster recovery method provided by the present invention obtains the disaster recovery requirements intelligently through a unified disaster recovery platform, analyzes the disaster recovery requirements, matches the cloud platform that needs to be backed up after analysis, and sends a valid backup request to the cloud platform to use the cloud platform to perform backup operations. It is applicable to various types of cloud platforms and can centrally configure and manage the backup operations of each tenant. Furthermore, the disaster recovery method can implement diversified backup operations, and can perform backup operations of multiple backup types, backup plans, and backup options to meet the specific backup requirements of various application scenarios and tenants. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 This is a flow chart of the disaster recovery method according to Embodiment 1 of the present invention.
[0041] Figure 2 This is a schematic diagram of a disaster recovery method according to Embodiment 1 of the present invention.
[0042] Figure 3 It is a schematic diagram of each module of Example 2 of the present invention.
[0043] Figure 4 This is a schematic diagram of a disaster recovery system according to Embodiment 3 of the present invention. DETAILED DESCRIPTION
[0044] The drawings of the present invention are only for illustrative purposes and should not be construed as limiting the present invention. In order to better illustrate the following embodiments, some parts of the drawings may be omitted, enlarged or reduced, and do not represent the size of the actual product; it is understandable to those skilled in the art that some well-known structures and their descriptions in the drawings may be omitted.
[0045] Example 1
[0046] like Figure 1 As shown, this embodiment provides a disaster recovery method, which is applied to a disaster recovery platform, so that the disaster recovery platform can match various types of cloud platforms and quickly and conveniently back up the backup data stored on the cloud platform.
[0047] The disaster recovery method includes the following steps:
[0048] S1: pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information.
[0049] Historical tenants are tenants who have stored data on various cloud platforms in advance, and historical tenant information is information about tenants who have stored data on various cloud platforms in advance, such as the tenant name and the resource address of its backup data, etc., which is used for subsequent matching with the target tenant information of the target tenant that needs to be backed up. The historical cloud platform information is information about the cloud platform where the backup data of the historical tenant is located, including information such as the historical cloud platform type, the historical cloud platform address, and the key corresponding to the historical tenant information. Specifically, the type and address of the cloud platform where the backup data of the historical tenant is located can be used as the historical cloud platform type and the historical cloud platform address, respectively. Cloud platform types mainly include VMware, Hyper-v, KVM, etc.
[0050] S21: Obtain disaster recovery requirements.
[0051] Disaster recovery operations for backing up data can be divided into automatic operations and manual operations;
[0052] When the disaster recovery operation is automatically performed, the disaster recovery requirements are obtained in step S21, including:
[0053] Obtain disaster recovery requirements from the work order platform.
[0054] The work order platform receives disaster recovery work orders sent by users and stores them in its own database. The work order platform opens an API interface to the disaster recovery platform so that the disaster recovery platform can automatically obtain disaster recovery work orders through the API interface and use the disaster recovery work orders as disaster recovery requirements to achieve intelligent disaster recovery demand acquisition.
[0055] When the disaster recovery operation is performed manually, obtaining the disaster recovery requirements in step S21 includes:
[0056] Receive disaster recovery requirements sent by users.
[0057] The user manually sends the disaster recovery requirements to the disaster recovery platform so that the disaster recovery platform receives the disaster recovery requirements.
[0058] After the disaster recovery platform obtains the disaster recovery requirements, it analyzes the disaster recovery requirements to obtain the target tenant information and target backup information of the target tenant that needs to be backed up. Specifically, step S22 is executed:
[0059] S22: Obtain target tenant information and target backup information of the target tenant according to the disaster recovery demand analysis.
[0060] like Figure 2 As shown, the cloud platform includes multiple clusters, and each cluster includes backup data.
[0061] Each cluster includes at least one host, each host corresponds to a virtual machine, the virtual machine stores the database and file system, and the backup data includes the database and file system. The database mainly includes MySQL, MongoDB, Oracle, SqlServer, etc. The file system mainly includes configuration files, log files, application files, and media files.
[0062] The target tenant information includes information of the tenant that needs to be backed up, for example, the target tenant name of the target tenant that needs to be backed up and the resource address of the backup data.
[0063] The target backup information is the backup requirement information of the tenant who needs to be backed up, for example, at least one of the backup type, backup plan, and backup options. Among them, the backup type includes but is not limited to at least one of virtual machine backup, file backup, and database backup; the backup plan includes but is not limited to: immediate backup, scheduled backup, backup at a specified interval within a certain period of time, backup at a specified interval of days, backup at a specified interval of weeks and a certain day of the week, and backup at least one of a specified month and a certain day of the month; the backup content can be used as a backup option, and the backup content is not limited to full backup and incremental backup. Further, when the backup type is virtual machine backup, the full backup backs up the entire virtual machine disk, and the incremental backup backs up the changed part of the specified full backup; when the backup type is file backup, the full backup can select the specified file or folder in the backup data for backup, and the incremental backup cannot select the specified file or folder, and can only back up the changed part of the selected file or folder in the specified full backup; when the backup type is database backup, the full backup can select the specified database or specified table for backup, and the incremental backup can only back up the changed part of the specified database or table in the full backup. In the case of a full backup, the backup target pool can be used to store backup data on various cloud platforms. In the case of an incremental backup, the backup data can only be stored in the same target pool as the full backup.
[0064] S3: Match the target tenant information with the historical tenant information to obtain the matched historical tenant information and the historical cloud platform information corresponding to the matched historical tenant information.
[0065] The target tenant name of the target tenant that needs to be backed up and the resource address of the backup data are compared with the historical tenant information pre-recorded on the disaster recovery platform to obtain the historical tenant information that matches the target tenant. Based on the obtained historical tenant information, the historical cloud platform information that also corresponds to the target tenant is obtained, thereby obtaining the information of the cloud platform where the backup data of the target tenant is located, so that subsequent backup can be performed based on the obtained cloud platform information.
[0066] S41: Generate a valid backup request according to the matched historical cloud platform information and the target backup information.
[0067] Specifically, based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, a backup request for the cloud platform corresponding to the historical cloud platform information is generated, and based on the backup request and the key corresponding to the historical tenant information, a valid backup request is generated.
[0068] After executing step S41, continue to execute S42: send the valid backup request to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request.
[0069] The cloud platform sends the key to each tenant in advance so that the target tenant can use the key to pass the authorization authentication of the cloud platform, thereby legally sending HTTP requests to the API interface of the cloud platform to perform disaster recovery operations.
[0070] Based on the backup type, backup plan, at least one of the backup options and the historical cloud platform type and the historical cloud platform address and other information, an effective API request is formed for the cloud platform storing the backup data, and the API request is used as a backup request. At the same time, combined with the key effective backup request, a valid backup request is sent to the cloud platform.
[0071] The disaster recovery method provided in this embodiment, through a unified disaster recovery platform, intelligently obtains disaster recovery requirements, analyzes the disaster recovery requirements, matches the cloud platform that needs to be backed up after analysis, and sends a valid backup request to the cloud platform to use the cloud platform to perform backup operations. It is applicable to various types of cloud platforms and can centrally configure and manage the backup operations of each tenant. Furthermore, the disaster recovery method of this embodiment can implement diversified backup operations, and can perform backup operations of multiple backup types, backup plans, and backup options to meet the specific backup requirements of various application scenarios and tenants.
[0072] Further, after sending the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0073] S5: receiving the response and backup operation status sent by the cloud platform, and regularly sending query requests to the cloud platform to query the backup operation status of the cloud platform.
[0074] If the disaster recovery platform can receive a response from the cloud platform and the backup operation status is successful, it means that the cloud platform has started to back up the backup data. When the backup operation is in progress, the disaster recovery platform can query the backup operation status regularly to understand the progress of the backup operation. The backup operation is displayed in the form of a list on the disaster recovery platform for tenants to query.
[0075] S6: If the backup operation fails, the failure reason sent by the cloud platform is received, and the disaster recovery status is updated.
[0076] When the disaster recovery requirements are obtained from the work order platform, the disaster recovery status will also be updated in the disaster recovery work order on the work order platform, so that the user who sent the disaster recovery work order can promptly understand the reason for the failure of the backup operation and re-execute the backup.
[0077] Example 2
[0078] This embodiment and embodiment 1 are based on the same inventive concept and provide a disaster recovery platform, such as Figure 3 As shown, including:
[0079] Recording module 1, used to pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information; the historical cloud platform information is information of the cloud platform where the backup data of the historical tenant is located;
[0080] Demand acquisition module 2, used to acquire disaster recovery requirements, and obtain target tenant information and target backup information of the target tenant according to the disaster recovery requirements analysis;
[0081] A matching module 3, used for matching the target tenant information with the historical tenant information to obtain the matched historical tenant information and the historical cloud platform information corresponding to the matched historical tenant information;
[0082] The request module 4 is used to generate a valid backup request based on the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request.
[0083] Furthermore, the cloud platform includes multiple clusters, each cluster includes backup data, and the target tenant information includes the target tenant name and the resource address of the backup data.
[0084] Further, the historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information; the target backup information includes at least one of the backup type, the backup plan and the backup option;
[0085] The request module 4 generates a valid backup request according to the matched historical cloud platform information and the target backup information, including:
[0086] The request module 4 generates a backup request for the cloud platform corresponding to the historical cloud platform information based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, and generates a valid backup request based on the backup request and the key corresponding to the historical tenant information.
[0087] Furthermore, the demand acquisition module 2 acquires the disaster recovery demand, including:
[0088] When the disaster recovery operation is automatically performed, the demand acquisition module 2 obtains the disaster recovery demand from the work order platform;
[0089] When the disaster recovery operation is performed manually, the demand acquisition module 2 receives the disaster recovery demand sent by the user.
[0090] Further, after the request module 4 sends the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0091] The request module 4 receives the response and backup operation status sent by the cloud platform, and periodically sends a query request to the cloud platform to query the backup operation status of the cloud platform.
[0092] Further, after the request module 4 sends the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0093] If the backup operation fails, the request module 4 receives the failure reason sent by the cloud platform and updates the disaster recovery status.
[0094] This embodiment uses a unified disaster recovery platform to intelligently obtain disaster recovery requirements and analyze them. After analysis, it matches the cloud platform that needs to be backed up, and sends a valid backup request to the cloud platform to use the cloud platform to perform backup operations. It is applicable to various types of cloud platforms and can centrally configure and manage the backup operations of each tenant. Furthermore, the disaster recovery platform can implement a variety of backup operations, and can perform backup operations of multiple backup types, backup plans, and backup options to meet the specific backup needs of various application scenarios and tenants.
[0095] Example 3
[0096] like Figure 4 As shown, this embodiment and embodiment 1 are based on the same inventive concept and provide a disaster recovery system, including a disaster recovery platform, a work order platform and a cloud platform;
[0097] The work order platform is used to receive disaster recovery requirements sent by users;
[0098] The disaster recovery platform is used to pre-record historical tenant information and historical cloud platform information corresponding to the historical tenant information; obtain disaster recovery requirements from the work order platform, analyze target tenant information and target backup information according to the disaster recovery requirements, and match the target tenant information with the historical tenant information to obtain matched historical tenant information and historical cloud platform information corresponding to the matched historical tenant information; generate a valid backup request based on the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information;
[0099] The cloud platform is used to perform a backup operation according to the valid backup request.
[0100] Furthermore, the cloud platform includes multiple clusters, each cluster includes backup data, and the target tenant information includes the target tenant name and the resource address of the backup data.
[0101] Further, the historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information;
[0102] The target backup information includes at least one of a backup type, a backup plan, and a backup option;
[0103] The disaster recovery platform generates a valid backup request according to the matched historical cloud platform information and the target backup information, including:
[0104] The disaster recovery platform generates a backup request for the cloud platform corresponding to the historical cloud platform information based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, and generates a valid backup request based on the backup request and the key corresponding to the historical tenant information.
[0105] Furthermore, the disaster recovery platform obtains disaster recovery requirements, including:
[0106] When performing disaster recovery operations automatically, the disaster recovery platform obtains disaster recovery requirements from the work order platform;
[0107] When performing disaster recovery operations manually, the disaster recovery platform receives disaster recovery requirements sent by users.
[0108] Further, after the disaster recovery platform sends the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0109] The disaster recovery platform receives the response and backup operation status sent by the cloud platform, and periodically sends a query request to the cloud platform to query the backup operation status of the cloud platform.
[0110] Further, after the disaster recovery platform sends the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes:
[0111] If the backup operation fails, the disaster recovery platform receives the failure reason sent by the cloud platform and updates the disaster recovery status.
[0112] This embodiment uses a unified disaster recovery platform to intelligently obtain disaster recovery requirements and analyze them. After analysis, it matches the cloud platform that needs to be backed up, and sends a valid backup request to the cloud platform to use the cloud platform to perform backup operations. It is applicable to various types of cloud platforms and can centrally configure and manage the backup operations of each tenant. Furthermore, the disaster recovery platform can implement a variety of backup operations, and can perform backup operations of multiple backup types, backup plans, and backup options to meet the specific backup needs of various application scenarios and tenants.
[0113] Example 4
[0114] This embodiment provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the disaster recovery method described in Embodiment 1 when executing the computer program.
[0115] Example 5
[0116] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the disaster recovery method as described in Embodiment 1 is implemented.
[0117] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the technical solution of the present invention, and are not intended to limit the specific implementation methods of the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the claims of the present invention shall be included in the protection scope of the claims of the present invention.
Claims
1. A disaster recovery method, characterized in that: Applied to the disaster recovery platform, including the following steps: Pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information; the historical cloud platform information is information of the cloud platform where the backup data of the historical tenant is located; Obtaining disaster recovery requirements, and obtaining target tenant information and target backup information of the target tenant according to the disaster recovery requirements analysis; Matching the target tenant information with the historical tenant information to obtain matched historical tenant information and historical cloud platform information corresponding to the matched historical tenant information; Generate a valid backup request according to the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request; The historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information; The target backup information includes at least one of a backup type, a backup plan, and a backup option; Generate a valid backup request according to the matched historical cloud platform information and the target backup information, including: Based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, a backup request for the cloud platform corresponding to the historical cloud platform information is generated; based on the backup request and the key corresponding to the historical tenant information, a valid backup request is generated.
2. A disaster recovery method according to claim 1, characterized in that: The cloud platform includes multiple clusters, each cluster includes backup data, and the target tenant information includes the target tenant name and the resource address of the backup data.
3. A disaster recovery method according to claim 1, characterized in that: Obtain disaster recovery requirements, including: When performing disaster recovery operations automatically, obtain disaster recovery requirements from the work order platform; When performing disaster recovery operations manually, receive disaster recovery requirements sent by users.
4. A disaster recovery method according to claim 1, characterized in that: After sending the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes: Receive the response and backup operation status sent by the cloud platform, and periodically send query requests to the cloud platform to query the backup operation status of the cloud platform.
5. A disaster recovery method according to claim 1, characterized in that: After sending the valid backup request to the corresponding cloud platform so that the cloud platform performs the backup operation, the method further includes: If the backup operation fails, the failure reason sent by the cloud platform is received and the disaster recovery status is updated.
6. A disaster recovery platform, characterized in that: include: A recording module, used to pre-record historical tenant information of historical tenants and historical cloud platform information corresponding to the historical tenant information; the historical cloud platform information is information of the cloud platform where the backup data of the historical tenant is located; A demand acquisition module is used to acquire disaster recovery requirements and obtain target tenant information and target backup information of the target tenant according to the disaster recovery requirements analysis; A matching module, used to match the target tenant information with the historical tenant information, and obtain the matched historical tenant information and the historical cloud platform information corresponding to the matched historical tenant information; A request module, used to generate a valid backup request according to the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information, so that the cloud platform performs a backup operation according to the valid backup request; The historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information; The target backup information includes at least one of a backup type, a backup plan, and a backup option; Generate a valid backup request according to the matched historical cloud platform information and the target backup information, including: Based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, a backup request for the cloud platform corresponding to the historical cloud platform information is generated; based on the backup request and the key corresponding to the historical tenant information, a valid backup request is generated.
7. A disaster recovery system, characterized in that: Including disaster recovery platform, work order platform and cloud platform; The work order platform is used to receive disaster recovery requirements sent by users; The disaster recovery platform is used to pre-record historical tenant information and historical cloud platform information corresponding to the historical tenant information; obtain disaster recovery requirements from the work order platform, analyze target tenant information and target backup information according to the disaster recovery requirements, and match the target tenant information with the historical tenant information to obtain matched historical tenant information and historical cloud platform information corresponding to the matched historical tenant information; generate a valid backup request based on the matched historical cloud platform information and the target backup information, and send the valid backup request to the cloud platform corresponding to the historical cloud platform information; The cloud platform is used to perform a backup operation according to the valid backup request; The historical cloud platform information includes the historical cloud platform type, the historical cloud platform address and the key corresponding to the historical tenant information; The target backup information includes at least one of a backup type, a backup plan, and a backup option; Generate a valid backup request according to the matched historical cloud platform information and the target backup information, including: Based on at least one of the backup type, backup plan, backup options, the historical cloud platform type, and the historical cloud platform address, a backup request for the cloud platform corresponding to the historical cloud platform information is generated; based on the backup request and the key corresponding to the historical tenant information, a valid backup request is generated.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the disaster recovery method according to any one of claims 1 to 5 is implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the disaster recovery method according to any one of claims 1 to 5 is implemented.
