A data disaster recovery method, apparatus, device, and readable storage medium

Abstract

This invention discloses a data disaster recovery method. Upon receiving a data backup request, the method determines the pre-registered disaster recovery configuration information of the target application to be backed up, and performs data backup processing according to the target application's custom backup requirements. Different data disaster recovery backup mechanisms are employed for different applications, thereby meeting the usage needs of different disaster recovery scenarios and improving versatility. Furthermore, this method utilizes storage devices in multiple regions for data backup and storage. In the event of a large-scale disaster in one location, backup data from other regions can be retrieved to achieve complete recovery. It also meets the needs of long-distance data backup in financial services, ensuring secure data storage. This invention also discloses a data disaster recovery device, equipment, and readable storage medium, which have corresponding technical effects.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a data disaster recovery method, apparatus, device, and readable storage medium. Background Technology

[0002] With the rise of next-generation computing technologies such as cloud computing, big data, and artificial intelligence, data is growing explosively. Data has become a crucial asset for businesses, and consequently, the consequences of data disasters are becoming increasingly severe. For example, in the financial sector, if data cannot be recovered after a disaster, businesses almost always face bankruptcy, and this also generates numerous economic disputes and related compensation claims from users.

[0003] To avoid the aforementioned situations, current data disaster recovery employs a multi-data center approach within the same region, which is a multi-copy disaster recovery method. This approach can maintain normal service operation in some data anomaly scenarios, such as single server failure, localized network failure, or single data center anomaly. However, the current multi-data center backup method within the same region does not meet the specific legal compliance requirements of financial businesses, nor the diverse business needs of support, credit, and funds. Furthermore, in the event of large-scale disasters such as floods or earthquakes, this method cannot ensure the continuity of the company's operations. Additionally, in terms of backup costs, both labor and storage costs are relatively high, there is a lack of platform-based management, and the data backup and recovery metrics, such as RTO (Recovery Time Objective) and RPO (Recovery Point Objective), cannot be guaranteed.

[0004] In conclusion, how to improve the stability and universality of disaster recovery while controlling the cost of data disaster recovery is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this invention is to provide a data disaster recovery method, apparatus, device, and readable storage medium to improve the stability and universality of disaster recovery while controlling the cost of data disaster recovery.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] A data disaster recovery method includes:

[0008] Upon receiving a data backup request, determine the disaster recovery configuration information of the target application;

[0009] Backup rules are extracted from the disaster recovery configuration information, and data backup tasks are generated based on the backup rules.

[0010] Upon receiving the data backup task, the target data to be backed up is extracted from the target application;

[0011] The target data is stored on storage devices in multiple regions, and the storage records are added to the disaster recovery configuration information.

[0012] Optionally, storing the target data in a multi-regional storage device includes:

[0013] Back up the target data to the cache service;

[0014] If the target data backup is completed, the target data in the cached data will be synchronized to the cold backup service; wherein, the cold backup service is defined as having a physical distance from the business system that exceeds the off-site disaster recovery threshold.

[0015] Optionally, after synchronizing the target data in the cached data to the cold backup service, the method further includes:

[0016] If a tape backup request is received, data that has been stored in the cold backup service for a period of time reaching the long-term storage threshold will be synchronized to the tape service.

[0017] Optionally, after synchronizing data whose storage time in the cold backup service has reached the long-term storage threshold to the tape service, the method further includes:

[0018] Determine the storage duration of each data item in the cold backup service;

[0019] Delete the data whose storage duration has reached the cold backup expiration threshold.

[0020] Optionally, after storing the target data in a storage device in multiple regions, the method further includes: performing an integrity check on the data in the storage device.

[0021] Optionally, the data disaster recovery method further includes:

[0022] If a data recovery request is received, determine the disaster recovery configuration information of the application to be recovered, and use it as the specified configuration information;

[0023] Extract the business association information of the application to be restored and the storage record from the specified configuration information;

[0024] The corresponding backup data is extracted from the storage device according to the storage record;

[0025] The backup data is restored to the corresponding business cluster based on the business association information.

[0026] A data disaster recovery device, comprising:

[0027] The management platform is used to trigger the disaster recovery system engine after receiving a data backup request;

[0028] The disaster recovery system engine is used to determine the disaster recovery configuration information of the target application; extract backup rules from the disaster recovery configuration information; and generate data backup tasks according to the backup rules.

[0029] The disaster recovery execution layer is used to extract the target data to be backed up from the target application after receiving the data backup task; store the target data in storage devices in multiple regions; and add the storage records to the disaster recovery configuration information.

[0030] A data storage layer is used to store the target data.

[0031] Optionally, the data storage layer includes: a caching service and a cold backup service; wherein the cold backup service is provided when the physical distance between the cold backup service and the business system exceeds the off-site disaster recovery threshold.

[0032] Accordingly, the disaster recovery execution layer is specifically used to: back up the target data to the cache service; and if the target data backup is complete, synchronize the target data in the cache data to the cold backup service.

[0033] A computer device, comprising:

[0034] Memory, used to store computer programs;

[0035] A processor is used to implement the above-described data disaster recovery method when executing the computer program.

[0036] A readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described data disaster recovery method.

[0037] The method provided in this embodiment of the invention, upon receiving a data backup request, determines the pre-registered disaster recovery configuration information of the target application to be backed up, and performs data backup processing according to the custom backup requirements of the target application. For different application objects, this method adopts different data disaster recovery backup mechanisms, thereby meeting the usage requirements under different disaster recovery scenarios and improving universality. In addition, this method uses storage devices in multiple regions for data backup storage, so that when a large-scale disaster occurs in one location, backup data from other regions can be called to achieve complete recovery. At the same time, it can also meet the needs of long-distance data backup for financial business, ensuring the secure storage of data.

[0038] Accordingly, embodiments of the present invention also provide a data disaster recovery device, equipment, and readable storage medium corresponding to the above-described data disaster recovery method, which have the above-described technical effects, and will not be elaborated further here. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 This is a flowchart illustrating the implementation of a data disaster recovery method in an embodiment of the present invention.

[0041] Figure 2 This is an engine operation flow diagram according to an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram of the structure of a data disaster recovery device according to an embodiment of the present invention;

[0043] Figure 4 This is a schematic diagram of a storage hierarchy in an embodiment of the present invention;

[0044] Figure 5 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. Detailed Implementation

[0045] The core of this invention is to provide a data disaster recovery method that can improve the stability and universality of disaster recovery while controlling the cost of data disaster recovery.

[0046] To enable those skilled in the art to better understand the present invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0047] Please refer to Figure 1 , Figure 1 This is a flowchart of a data disaster recovery method according to an embodiment of the present invention. The method includes the following steps:

[0048] S101. After receiving the data backup request, determine the disaster recovery configuration information of the target application;

[0049] All data to be backed up belongs to the application under the service management dimension. Therefore, this method uses the application as the management object for data disaster recovery. The application must first register with the protocol (creating backup rules (configurations) for the data objects to be backed up; the distribution and execution of backup tasks are based on the protocol rules) before the data disaster recovery backup service can be started. Protocol registration involves creating disaster recovery configuration information for a specific application's data types via a web-UI or API. After approval, registration is complete, and only after registration can data backup be performed for that application. The disaster recovery configuration information is customized according to the actual usage needs of the application and may include backup rules, restore rules, application organizational structure information, etc., which are not limited here.

[0050] Upon receiving a data backup request, the pre-registered disaster recovery configuration information of the target application to be backed up is determined so that data backup processing can be performed according to the target application's custom backup requirements, meeting different usage needs and improving universality.

[0051] S102. Extract backup rules from disaster recovery configuration information and generate data backup tasks based on backup rules;

[0052] Backup rules refer to the configuration rules for performing backup storage on data. Specifically, they may include backup frequency, startup time, organization or data to be backed up, etc. There are no restrictions on the information items and specific numerical configurations included in the backup rules. They can be set according to the disaster recovery backup needs of different applications. For example, applications that update frequently can have their backup frequency increased accordingly. This will not be elaborated further here.

[0053] The backup rules are extracted from the disaster recovery configuration information. Data backup tasks are generated according to the backup frequency and start time specified in the backup rules. The data backup tasks are then sent to the execution machine to start the data backup.

[0054] S103. After receiving the data backup task, extract the target data to be backed up from the target application;

[0055] After receiving the data backup task, the data backup execution machine extracts the target data to be backed up from the target application. The target data to be backed up can be extracted from all data in the application as target data; or the data items to be backed up can be configured in the backup rules, and the corresponding data can be extracted from the target application as target data according to the backup rules. In this embodiment, the method of extracting target data is not limited and can be set according to the actual backup needs.

[0056] S104. Store the target data in storage devices in multiple regions and add the storage records to the disaster recovery configuration information.

[0057] To achieve off-site disaster recovery capabilities, this method establishes an off-site disaster recovery data center and utilizes storage devices distributed across multiple regions to perform hierarchical storage of target data. The distance between each storage device exceeds the off-site disaster recovery threshold (e.g., 2000km), thereby enabling off-site disaster recovery capabilities in large-scale disaster scenarios and ensuring the continuous operation of the company's business. At the same time, it can also meet the special requirements of legal compliance for financial businesses and achieve data backup over long distances.

[0058] After storing the target data on storage devices in multiple regions, the storage records are added to the disaster recovery configuration information. For example, data backup A is stored in file D on device C in location B to facilitate rapid recovery of the backup data.

[0059] Based on the above description, the technical solution provided by the embodiments of the present invention, upon receiving a data backup request, determines the pre-registered disaster recovery configuration information of the target application to be backed up, and performs data backup processing according to the custom backup requirements of the target application. For different application objects, this method adopts different data disaster recovery backup mechanisms, thereby meeting the usage requirements under different disaster recovery scenarios and improving universality. In addition, this method calls storage devices in multiple regions for data backup storage, so that when a large-scale disaster occurs in one place, backup data from other regions can be called to achieve complete recovery. At the same time, it can also meet the needs of long-distance data backup for financial business and ensure the secure storage of data.

[0060] It should be noted that, based on the above embodiments, the present invention also provides corresponding improvements. In the preferred / improved embodiments, steps that are the same as or corresponding to those in the above embodiments can be referred to each other, and the corresponding beneficial effects can also be referred to each other; however, these will not be elaborated upon in the preferred / improved embodiments herein.

[0061] The above embodiments do not limit the backup storage mechanism for the target data. However, considering the stability, efficiency, and cost of data backup, this embodiment proposes a multi-level storage scheme.

[0062] Specifically, step S104, storing the target data in a multi-regional storage device, may include the following sub-steps:

[0063] (1) Back up the target data to the cache service;

[0064] The caching service is a distributed storage service located in the same region as the business system (with a physical distance less than the disaster recovery threshold). Specifically, it can be implemented by calling Baidu Object Storage (BOS), and there are no restrictions on this.

[0065] Using caching for data backup allows for efficient collection of various types of data and rapid retrieval of backup data. Due to limited cache space, it's recommended to store only backup data from the past month; specific settings can be configured according to actual usage needs.

[0066] (2) If the target data backup is complete, synchronize the target data in the cached data to the cold backup service;

[0067] Among them, cold backup service is a distributed storage service in a remote data center where the physical distance from the business system exceeds the disaster recovery threshold. It uses a larger single storage block of storage medium, has a lower overall cost, and can store backup data for a longer period of time, such as up to 6 months of backup data.

[0068] The storage solution provided in this embodiment proposes to use multiple types of storage devices for tiered storage, provide a distributed storage system in the same region as the business service for hot data backup to ensure the RPO of data backup, and at the same time synchronize hot data to a remote location for cold storage to provide a certain degree of fault tolerance and control costs.

[0069] Furthermore, based on the above storage mechanism, in order to further reduce storage costs, after synchronizing the target data in the cached data to the cold backup service, (3) can be executed;

[0070] (3) If a tape backup request is received, data that has been stored in the cold backup service for a period of time that has reached the long-term storage threshold can be synchronized to the tape service.

[0071] Important data that needs to be stored for a longer period of time (such as data that needs to be stored for more than 6 months) can be synchronized to tape storage devices for longer retention. Tape has better storage reliability (lifespan) and lower storage costs, thereby further reducing implementation costs and improving the reliability of data storage.

[0072] Furthermore, based on the above storage mechanism, in order to ensure the successful writing of the latest data and reduce storage costs, the cache duration of each data in the cache service can be determined after the target data in the cache data is synchronized to the cold backup service; and data whose cache duration has reached the cache expiration threshold can be deleted.

[0073] This method cleans up expired data in the cache layer, which can prevent expired data from occupying too much cache space and enable fast recycling of cached data.

[0074] Similarly, after synchronizing data that has reached the long-term storage threshold in the cold backup service to the tape service, the storage duration of each data in the cold backup service can be further determined; and data whose storage duration has reached the cold backup expiration threshold can be deleted, which will not be elaborated here.

[0075] It should be noted that, considering the cost issues under normal circumstances, the off-site data center does not need to be in a permanent state. It can only maintain the operating system, underlying software, network access, and upper-layer application relationships required for service recovery. For example, cold backup storage services and tape storage services are both applicable and are not limited here.

[0076] The storage solution provided in this embodiment uses different data storage media and defines corresponding data backup levels and expiration mechanisms. First, the data is backed up to the cache, then backed up from the cache to cold backup storage and tape storage, and then expired storage devices except for the last level are deleted. This can ensure data security and control implementation costs.

[0077] In addition, after storing the target data in storage devices in multiple regions in step S104 of the above embodiment, the following steps can be performed to further ensure the integrity of disaster recovery data:

[0078] Step S105: Perform an integrity check on the data in the storage device.

[0079] Perform integrity checks on the backed-up data to ensure its integrity.

[0080] It should be noted that data verification can be performed on only a portion of the data, such as sampling data of different storage levels according to different verification strategies; or all data can be verified. In addition, the specific data integrity verification methods used are not limited in this embodiment, and can be referred to the introduction of relevant technologies, which will not be elaborated here.

[0081] This embodiment provides a data verification mechanism for disaster recovery data, which can ensure the integrity and reliability of backup data.

[0082] To deepen the understanding of data backup, data synchronization, and rolling deletion proposed in the above embodiments, this embodiment introduces a complete data backup scheduling process. In the entire architecture, data backup, data synchronization, and rolling deletion can be considered as a continuous action. However, if the upstream and downstream are in a call chain manner, the link becomes longer. Therefore, all actions are made independent and can be uniformly initiated by the scheduler, such as... Figure 2 The diagram shown is a flowchart of engine operation.

[0083] Once an application registration is complete, if the application's registration agreement is a periodic task, the following actions will occur:

[0084] 1) Data backup interface call: If the target application's registration protocol meets the backup conditions, start the backup.

[0085] 2) No action was taken when calling the data synchronization interface if no backup of the data was completed;

[0086] 3) When the data deletion API is called, no action is taken for data that has not been backed up and synchronized.

[0087] 4) Routine data validation call, validation time strategy not met, no action taken;

[0088] 5) Once the data backup is successful, the above step 2) determines that the data backup is complete and initiates a task to synchronize to the remote cold standby BOS.

[0089] 6) Once the data synchronization and cold backup are complete, and the conditions for cached data rollover are met as determined in step 3 above, the cached data will be deleted.

[0090] 7) After the data synchronization cold backup is completed, the data synchronization will determine the tape backup requirement. If there is no requirement, no action will be taken; if there is a requirement and the tape backup conditions are met (i.e., tape backup is required and the data has been saved in the cold backup BOS for more than 6 months), then the tape backup will be initiated.

[0091] 8) When the cold backup data also expires, the cold backup data will be deleted in a rolling manner after 6 months or the user-defined expiration time (less than 6 months).

[0092] 9) Routine data verification: For data in each storage medium, determine if it meets the verification policy and if the data exists in a certain storage layer, and initiate integrity verification and recovery (cache and cold backup BOS are sampled once a week, tape backup is sampled once a quarter).

[0093] The above is a complete scheduling process of a scheduler running tasks provided by the engine. Each type of task has a certain degree of reentrancy, that is, if the execution fails, it can be executed again, thereby ensuring that the system is in a normal operating state.

[0094] This embodiment only uses the above backup steps as an example for introduction. Other implementation methods can refer to the introduction of this embodiment, and will not be described in detail here.

[0095] While cloud backup services can currently store data that needs to be backed up, a robust data recovery mechanism is lacking as data volume grows. To address this, this embodiment proposes a script-based recovery scheme based on the aforementioned embodiments, enabling regular drills to ensure the reliability of the disaster recovery plan.

[0096] Specifically, in addition to the steps mentioned above, the following steps may be performed:

[0097] Step S106: If a data recovery request is received, determine the disaster recovery configuration information of the application to be recovered, and use it as the specified configuration information;

[0098] Step S107: Extract business association information and storage records from the specified configuration information;

[0099] A business function is provided jointly by multiple applications. Their relationship is not isolated, but it is unrelated to storage and is determined by the service access chain. Users can perform corresponding data recovery according to different needs, and can restore the data to a specific machine or a specific service of a certain application. The data recovery method provided in this embodiment supports script-based (i.e., pre-deduced service dependency relationships) data recovery plans. According to the plan configuration, a series of data are restored to a preset service, which may belong to different applications.

[0100] Data recovery itself involves backup, data processing, and application integration. The complete system recovery proposed in this embodiment is managed by service relationships. These service relationships act like a script for the recovery plan. For example, if a business subsystem consists of three modules and their dependent database cluster, the process of restoring this subsystem is as follows: during backup, the connection relationships between the three modules and the corresponding database cluster information are determined. When a recovery request for this subsystem is issued, the data of these three modules is automatically restored to the corresponding servers, and the services are started to restore the database cluster data and services. This allows for a relatively complete one-click recovery of the system.

[0101] Step S108: Extract the corresponding backup data from the storage device based on the storage record;

[0102] The storage record contains the specific backup storage location of each sub-data part of the backup data. It is necessary to find each sub-data part according to the storage record and reassemble it to obtain the complete backup data.

[0103] Step S109: Restore the backup data to the corresponding business cluster based on the business association information.

[0104] To deepen the understanding of the data recovery method proposed in this embodiment, a specific application step is presented here. Upon receiving a user's data recovery request, after the user initiates a zero-based recovery of a business subsystem, the following steps can be executed:

[0105] 1) Preliminary preparations: The application modules and databases of the business subsystems are complete (including database cluster construction, service startup methods, etc.);

[0106] 2) Obtain information on all application modules, database clusters, and database data contained in this subsystem as business-related information;

[0107] 3) Distribute recovery tasks with a certain concurrency level (default is 10, configurable);

[0108] 4) After receiving the task, the backup client restores the data;

[0109] 5) After data recovery, restore the database cluster according to the description in the configuration information;

[0110] 6) Start the service according to the module startup information configured in the configuration information;

[0111] 7) Once all modules have completed execution, use the test interface to verify and return the expected results.

[0112] Corresponding to the above method embodiments, this invention also provides a data disaster recovery device. The data disaster recovery device described below can be referred to in correspondence with the data disaster recovery method described above.

[0113] See Figure 3 As shown, the device includes the following modules: management platform 110, disaster recovery system engine 120, disaster recovery execution layer 130, and data storage layer 140.

[0114] Among them, the management platform 110 is mainly used to trigger the disaster recovery system engine after receiving a data backup request.

[0115] The management platform is open to users and can be accessed through two methods: a management page and a RESTful API. Users can perform operations on the disaster recovery platform, such as creating backup protocols, initiating backup tasks, initiating recovery tasks, and viewing backup progress.

[0116] The disaster recovery system engine 120 is mainly used to determine the disaster recovery configuration information of the target application; extract backup rules from the disaster recovery configuration information, and generate data backup tasks according to the backup rules.

[0117] The disaster recovery system engine is the core module of the disaster recovery system. It includes a scheduling module, which, in addition to receiving relevant requests from users and executing corresponding actions, is more responsible for the metadata management of the entire disaster recovery system and scheduling backup or recovery tasks according to the configuration information of the protocol, so that the entire system can operate.

[0118] The disaster recovery execution layer 130 is mainly used to extract the target data to be backed up from the target application after receiving the data backup task; store the target data in storage devices in multiple regions; and add the storage records to the disaster recovery configuration information.

[0119] The disaster recovery execution layer is a module that performs specific backup and recovery tasks. It runs on the server where the data is located or on a server that can obtain the relevant data. It receives requests from the engine layer, processes the corresponding actions (including data backup, recovery, integrity verification, rolling deletion, etc.), and returns the execution results.

[0120] Data storage layer 140 is mainly used to store target data.

[0121] In one specific embodiment of the present invention, the data storage layer includes: a caching service and a cold backup service; wherein, the cold backup service is provided when the physical distance between the data storage layer and the business system exceeds the off-site disaster recovery threshold.

[0122] Accordingly, the disaster recovery execution layer is specifically used to: back up the target data to the cache service; and if the target data backup is complete, synchronize the target data in the cache to the cold backup service.

[0123] Optionally, in addition to caching and cold backup services, the data storage layer may further include tape storage, such as... Figure 4 As shown.

[0124] Corresponding to the above method embodiments, this invention also provides a computer device. The computer device described below and the data disaster recovery method described above can be referred to each other.

[0125] The computer device includes:

[0126] Memory, used to store computer programs;

[0127] A processor is used to implement the steps of the data disaster recovery method in the above method embodiments when executing a computer program.

[0128] For details, please refer to Figure 5 This is a schematic diagram illustrating the specific structure of a computer device provided in this embodiment. The computer device can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 322 (e.g., one or more processors) and a memory 332. The memory 332 stores one or more computer application programs 342 or data 344. The memory 332 can be temporary or persistent storage. The program stored in the memory 332 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the data processing device. Furthermore, the central processing unit 322 may be configured to communicate with the memory 332 and execute the series of instruction operations stored in the memory 332 on the computer device 301.

[0129] Computer device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341.

[0130] The steps in the data disaster recovery method described above can be implemented by the structure of computer equipment.

[0131] Corresponding to the above method embodiments, this invention also provides a readable storage medium. The readable storage medium described below and the data disaster recovery method described above can be referred to in correspondence.

[0132] A readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the data disaster recovery method described in the above method embodiments.

[0133] Specifically, the readable storage medium can be a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, or any other readable storage medium capable of storing program code.

[0134] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the invention.

Claims

1. A data disaster recovery method, characterized in that, include: Upon receiving a data backup request, determine the disaster recovery configuration information of the target application; Backup rules are extracted from the disaster recovery configuration information, and data backup tasks are generated based on the backup rules. Upon receiving the data backup task, the target data to be backed up is extracted from the target application; The target data is backed up to a cache service, and the physical distance between the cache service and the business system is less than the off-site disaster recovery threshold. If the target data backup is completed, the data in the cache service will be synchronized to the cold backup service, and the physical distance between the cold backup service and the business system will exceed the off-site disaster recovery threshold; if a tape backup request is received, the data that has been stored in the cold backup service for a long time and has reached the long-term storage threshold will be synchronized to the tape service, and the storage record will be added to the disaster recovery configuration information. If a data recovery request is received, determine the disaster recovery configuration information of the application to be recovered, and use it as the specified configuration information; Extract the business association information of the application to be restored and the storage record from the specified configuration information; extract the corresponding backup data from the storage device based on the storage record; Based on the business association information, restore the backup data and its corresponding complete system to the corresponding business cluster; The business association information is determined during backup and includes information on all application modules, database clusters, and database data contained in the system to be restored.

2. The data disaster recovery method according to claim 1, characterized in that, After synchronizing data that has reached a long-term storage threshold in the cold backup service to the tape service, the method further includes: Determine the storage duration of each data item in the cold backup service; Delete the data whose storage duration has reached the cold backup expiration threshold.

3. The data disaster recovery method according to claim 1, characterized in that, After storing the target data in storage devices in multiple regions, the method further includes: performing integrity verification on the data in the storage devices.

4. A data disaster recovery device, characterized in that, include: The management platform is used to trigger the disaster recovery system engine after receiving a data backup request; The disaster recovery system engine is used to determine the disaster recovery configuration information of the target application; Backup rules are extracted from the disaster recovery configuration information, and data backup tasks are generated based on the backup rules. The disaster recovery execution layer is used to extract the target data to be backed up from the target application after receiving the data backup task. The target data is backed up to a cache service, and the physical distance between the cache service and the business system is less than the off-site disaster recovery threshold. If the target data backup is completed, the data in the cache service will be synchronized to the cold backup service, and the physical distance between the cold backup service and the business system will exceed the off-site disaster recovery threshold; if a tape backup request is received, the data that has been stored in the cold backup service for a long time and has reached the long-term storage threshold will be synchronized to the tape service, and the storage record will be added to the disaster recovery configuration information. If a data recovery request is received, determine the disaster recovery configuration information of the application to be recovered, and use it as the specified configuration information; Extract the business association information of the application to be restored and the storage record from the specified configuration information; The corresponding backup data is extracted from the storage device based on the storage records; Based on the business association information, restore the backup data and its corresponding complete system to the corresponding business cluster; A data storage layer is used to store the target data; The business association information is determined during backup and includes information on all application modules, database clusters, and database data contained in the system to be restored.

5. A computer device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the data disaster recovery method as described in any one of claims 1 to 3 when executing the computer program.

6. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the data disaster recovery method as described in any one of claims 1 to 3.

Images