Disaster recovery backup method and device, equipment, medium and program product

Abstract

The invention discloses a disaster recovery backup method, device and equipment, a medium and a program product, and relates to the field of data protection. The method comprises the following steps: acquiring a disaster recovery backup task; in response to a received content configuration operation on the disaster recovery backup task, obtaining a content configuration result corresponding to the disaster recovery backup task; in response to a received trigger condition configuration operation for the disaster recovery backup task, obtaining a condition configuration result corresponding to the disaster recovery backup task; and executing the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result. By receiving the content configuration operation and the trigger condition configuration operation on the disaster recovery backup task, the backup content requirement and the trigger condition of the disaster recovery backup task are configured, so that the operation difficulty is reduced by visually configuring the backup task, and the disaster recovery backup efficiency is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data protection, and in particular to a disaster recovery backup method, apparatus, device, medium, and program product. Background Art

[0002] With the advancement of information technology, network services are being handled through the construction of data centers. Furthermore, to ensure business continuity, data centers are often equipped with disaster recovery backups. Disaster recovery involves setting up separate data centers in different geographic regions and backing up data from one data center to another. If a data center fails and ceases operations, services can be switched to the other data center to continue processing.

[0003] In the related technology, taking the first data center and the second data center as an example, during the disaster recovery backup process of the first data center, the user compiles the code content corresponding to the backup instruction on the terminal, and backs up the data in the first data center to the second data center with the same file path by executing the backup instruction to ensure that the location of the data in the first data center is the same as that in the second data center.

[0004] However, in the related art, the process of compiling backup instruction code content to perform disaster recovery backup is relatively cumbersome and requires high instruction compilation conditions from the user, which results in low backup accuracy and efficiency of disaster recovery backup. Summary of the Invention

[0005] The present invention provides a disaster recovery backup method, apparatus, device, medium, and program product that can configure parameters for a disaster recovery backup task in a visual manner, so that the configured disaster recovery backup task can be automatically executed on schedule, thereby reducing the difficulty of disaster recovery backup task configuration and improving the efficiency and accuracy of disaster recovery backup. The technical solution is as follows:

[0006] In one aspect, a disaster recovery backup method is provided, the method comprising:

[0007] Obtain a disaster recovery backup task, where the disaster recovery backup task is used to instruct data in a first data center to be backed up to a second data center. The first data center and the second data center have a disaster recovery association relationship, where the disaster recovery association relationship is used to instruct that if the first data center stops running while executing a first service, the first service is switched to the second data center for continued execution.

[0008] In response to receiving a content configuration operation for the disaster recovery backup task, obtaining a content configuration result corresponding to the disaster recovery backup task, the content configuration result being used to indicate a backup content requirement corresponding to backing up the data in the first data center to the second data center;

[0009] In response to receiving a trigger condition configuration operation for the disaster recovery backup task, obtaining a condition configuration result corresponding to the disaster recovery backup task, the condition configuration result being used to indicate a trigger condition corresponding to starting to back up data in the first data center to the second data center;

[0010] The disaster recovery backup task is executed based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result, which is used to indicate that when the trigger condition is met, the data in the first data center will be backed up to the second data center according to the backup content requirements.

[0011] In another aspect, a disaster recovery backup device is provided, comprising:

[0012] an acquisition module, configured to acquire a disaster recovery backup task, wherein the disaster recovery backup task is configured to instruct data in a first data center to be backed up to a second data center, wherein the first data center and the second data center have a disaster recovery association relationship, and wherein the disaster recovery association relationship is configured to instruct that if the first data center stops running while executing a first business, the first application program is switched to the second data center for continued execution;

[0013] a configuration module configured to obtain, in response to receiving a content configuration operation for the disaster recovery backup task, a content configuration result corresponding to the disaster recovery backup task, wherein the content configuration result is used to indicate a backup content requirement corresponding to backing up the data in the first data center to the second data center;

[0014] The configuration module is further configured to, in response to receiving a trigger condition configuration operation for the disaster recovery backup task, obtain a condition configuration result corresponding to the disaster recovery backup task, wherein the condition configuration result is used to indicate a trigger condition corresponding to starting to back up data in the first data center to the second data center;

[0015] An execution module is used to execute the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result. The disaster recovery backup result is used to indicate that when the trigger condition is met, the data in the first data center will be backed up to the second data center according to the backup content requirements.

[0016] On the other hand, a computer device is provided, which includes a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the disaster recovery backup method as described in any of the above embodiments.

[0017] On the other hand, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored. The at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the disaster recovery backup method as described in any of the above embodiments.

[0018] In another aspect, a computer program product or computer program is provided. The computer program product or computer program includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the disaster recovery and backup method described in any of the above embodiments.

[0019] The beneficial effects of the technical solutions provided in the embodiments of the present application include at least:

[0020] Obtain a disaster recovery backup task for backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery relationship. By receiving content configuration operations and trigger condition configuration operations for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center in accordance with the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when backup commands need to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can only be achieved after the user manually executes the backup instruction. The disaster recovery backup process is optimized, which not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 This is a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application;

[0022] Figure 2 This is a flow chart of a disaster recovery backup method provided by an exemplary embodiment of the present application;

[0023] Figure 3 is a flow chart of a disaster recovery backup method provided by another exemplary embodiment of the present application;

[0024] Figure 4 is a schematic diagram of a task configuration interface provided by another exemplary embodiment of the present application;

[0025] Figure 5 is a flowchart of a disaster recovery backup method provided by another exemplary embodiment of the present application;

[0026] Figure 6 This is a schematic diagram of a disaster recovery object creation interface provided by another exemplary embodiment of the present application;

[0027] Figure 7 This is a schematic diagram of a disaster recovery backup object creation process provided by an exemplary embodiment of the present application;

[0028] Figure 8 This is a schematic diagram of a disaster recovery backup task execution process provided by an exemplary embodiment of the present application;

[0029] Figure 9 This is a flow chart of a backup task backend provided by an exemplary embodiment of the present application;

[0030] Figure 10 is a flowchart of a data backup process execution process provided by an exemplary embodiment of the present application;

[0031] Figure 11 This is a structural block diagram of a disaster recovery backup device provided by an exemplary embodiment of the present application;

[0032] Figure 12 It is a structural block diagram of a computer device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0033] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0034] In this application, the terms "first", "second", etc. are used to distinguish identical or similar items with substantially the same effects and functions. It should be understood that there is no logical or temporal dependency between "first" and "second", nor is there any limitation on the quantity and execution order.

[0035] Figure 1 This is a schematic diagram of an implementation environment provided by an exemplary embodiment of the present application. Figure 1As shown, the implementation environment includes a terminal 110, a first data center 120, a second data center 130, and a communication network 140. The terminal 110, the first data center 120, and the second data center 130 are connected via the communication network 140. Optionally, the communication network 140 can be a wired network or a wireless network, which is not limited here.

[0036] In an embodiment of the present application, taking the application in a disaster recovery backup scenario as an example, a disaster recovery backup client is installed in the terminal 110, and the disaster recovery backup client is used to configure parameters for the disaster recovery backup task. The task configuration interface 111 of the disaster recovery backup task is currently displayed in the terminal 110.

[0037] In some embodiments, when the terminal 110 receives a task creation operation, it obtains a disaster recovery backup task based on the task creation operation, and displays the content configuration area and trigger condition configuration area corresponding to the disaster recovery backup task in the task configuration interface 111, wherein the content configuration area is used to configure the backup content requirements of the disaster recovery backup task, and the trigger condition configuration area is used to configure the trigger conditions of the disaster recovery backup task.

[0038] In some embodiments, after receiving the content configuration operation, the terminal 110 obtains the content configuration result corresponding to the disaster recovery backup task and displays it in the content configuration area.

[0039] In some embodiments, after receiving the trigger condition configuration operation, the terminal 110 obtains the condition configuration result corresponding to the disaster recovery backup task and displays it in the trigger condition configuration area.

[0040] In some embodiments, terminal 110 sends the content configuration results, condition configuration results, and disaster recovery backup task as task configuration results to the scheduling system, where the scheduling system is configured to execute the disaster recovery backup task based on the content configuration results and condition configuration results. Optionally, the scheduling system is a system installed in terminal 110 or another terminal, or the scheduling system is a system installed in first data center 120, second data center 130, or another data center, without limitation.

[0041] In some embodiments, when a trigger condition is met, the scheduling system sends a data backup instruction to the first data center 120, for backing up the first data in the first data center 120 to the second data center 130 (for example, data A and data B in drive C / folder a / file 1). After receiving the data backup instruction, the first data center 120 sends the first data (data A and data B) to the designated location of the second data center 130 (for example, drive C / folder a / file 1).

[0042] In other embodiments, when a trigger condition is met, the scheduling system sends a data backup instruction to the first data center 120, for backing up the first data in the first data center 120 to the second data center 130 (for example, data A and data B in drive C / folder a / file 1). After receiving the data backup instruction, the first data center 120 sends the first data (data A and data B) to the scheduling system, which forwards the data to a designated location in the second data center 130 (for example, drive C / folder a / file 1).

[0043] In some optional embodiments, the terminal 110 is a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart home appliance, a smart car terminal, a smart speaker, an intelligent voice interaction device, an aircraft, etc., but is not limited thereto.

[0044] It is worth noting that a data center can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0045] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to enable data computing, storage, processing, and sharing. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, and application technology, all based on the cloud computing business model. It can form a resource pool for on-demand, flexible, and convenient use. Cloud computing technology will become a crucial support. Backend services in technical network systems, such as those for video websites, image websites, and more portals, require significant computing and storage resources. With the rapid development and application of the internet industry, every item will likely have its own unique identifier, requiring transmission to backend systems for logical processing. Data of varying levels will be processed separately, requiring robust system support for all types of industry data, which can only be achieved through cloud computing. Alternatively, server 120 can also be implemented as a node in a blockchain system.

[0046] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions.

[0047] Combined with the above introduction and implementation environment, Figure 2 This is a flow chart of a disaster recovery backup method provided in an embodiment of the present application. The method can be applied to a terminal, a server, or both. The embodiment of the present application takes the application of the method to a terminal as an example for explanation. The method may include:

[0048] Step 210: Obtain a disaster recovery backup task.

[0049] Among them, the disaster recovery backup task is used to indicate that the data in the first data center is backed up to the second data center. The first data center and the second data center have a disaster recovery relationship. The disaster recovery relationship is used to indicate that if the first data center stops running during the execution of the first business, the first business sequence will be switched to the second data center for continued execution.

[0050] Schematically, a disaster recovery backup task refers to a task of performing data backup between at least two data centers.

[0051] Optionally, the at least two data centers include two data centers or multiple data centers. When the disaster recovery backup task refers to data backup between two data centers, taking data center 1 and data center 2 as an example, the data in data center 1 is backed up to data center 2, or the data in data center 2 is backed up to data center 1, or, while the data in data center 1 is backed up to data center 2, the data in data center 2 is also backed up to data center 1. When the disaster recovery backup task refers to data backup between three or more data centers, taking data center 1, data center 2, and data center 3 as an example, the data in data center 1 is synchronously backed up to data center 2 and data center 3, or, part of the data in data center 1 is backed up to data center 2, and another part of the data in data center 1 is backed up to data center 3, or, after backing up the data in data center 1 to data center 2, the data is backed up again from data center 2 to data center 3. In other words, a variety of different backup methods can meet the data backup requirements corresponding to different data centers in the disaster recovery system, avoiding data loss while ensuring that the same business can be executed coherently across data centers, thereby ensuring the integrity of business execution.

[0052] In some embodiments, backup refers to copying specified data in a first data center to a second data center, and the first storage path of the specified data in the first data center and the second storage path of the specified data in the second data center belong to the same path. For example, the path information of data A in the first data center is C drive / folder a. In the process of copying data A from the first data center to the second data center, first query the C drive in the second data center, and search for folder a in the C drive. If folder a exists, store data A in folder a. If folder a does not exist, create a new folder a in the C drive, and then store data A in folder a.

[0053] Optionally, a data center refers to an independent server; or, a data center refers to all servers or designated servers in a server cluster; or, a data center refers to a designated node in a server cluster.

[0054] Schematically, a disaster recovery relationship means that for the same business, two independent data centers can both execute the business, and if the first data center ceases to operate, the second data center can continue to operate the business based on the operation of the first data center, so that the business can operate continuously and coherently. For example, the first business is to analyze multiple data in a data packet. When the first data center stops operating while executing the first business analysis data a in the data packet, the second data center starts executing the first business, and the first business continues to analyze data a. There is a buffer period between the time when the first data center stops operating and the time when the second data center starts operating, which is used to represent the time it takes for the second data center to respond and start operating.

[0055] In this embodiment, since the first data center and the second data center have a disaster recovery association relationship, the first data center and the second data center are both data centers in the disaster recovery backup system.

[0056] The following is a detailed description of the operation process of the disaster recovery backup system.

[0057] First, under normal circumstances, the first data center operates normally, and the second data center backs up the data in the first data center. The specific backup method will be described in detail in the subsequent embodiments. It is worth noting that the disaster recovery backup system needs to monitor the operating status of each data center in the system in real time. Taking the execution of the first business in the first data center as an example, when a failure occurs during the operation of the first business in the first data center and the operation stops, the disaster recovery backup system detects that the operation of the first data center is abnormal and triggers the alarm mechanism. At this time, the disaster recovery backup system sends a backup operation instruction to the second data center, wherein the backup operation instruction includes the operating status of the first data center when it stops operating. After receiving the backup operation instruction, the second data center performs data recovery on the data obtained through the backup. When the data recovery is completed, the second data center uses the recovered data to take over the first data center to continue to execute the first business, so as to ensure that the first business will not be interrupted during the processing.

[0058] Optionally, the first data center and the second data center are data centers located in different geographical areas, for example: data center 1 is located in city a, and data center 2 is located in city b; or, the first data center and the second data center are data centers located in different locations in the same geographical area, for example: data center 1 and data center 2 are both located in city c, but data center 1 is located in area a of city c, and data center 2 is located in area b of city c. There is no limitation on this.

[0059] Optionally, the disaster recovery backup task may be obtained in at least one of the following ways:

[0060] 1. Display the task creation interface. After receiving the task creation operation in the task creation interface, a disaster recovery backup task is obtained based on the input task parameters, where the task parameters include the task name, task identification number, and the name of the account that created the task;

[0061] 2. A plurality of candidate backup tasks are pre-stored, and upon receiving a selection operation for a designated backup task from the plurality of candidate backup tasks, the designated backup task is used as a disaster recovery backup task.

[0062] It is worth noting that the above-mentioned method for obtaining disaster recovery backup tasks is only an illustrative example and is not limited to this embodiment of the present application.

[0063] Optionally, the disaster recovery backup task only represents the data backup task between the first data center and the second data center; or, the disaster recovery backup task includes multiple data backup tasks, different data backup tasks indicate different data centers, wherein there is at least one data backup task that is a data backup task between the first data center and the second data center.

[0064] Optionally, there is only one disaster recovery backup task between the first data center and the second data center; alternatively, there are multiple disaster recovery backup tasks between the first data center and the second data center, with different disaster recovery backup tasks representing different types of data backup. For example, Task 1 and Task 2 exist between the first data center and the second data center. Task 1 backs up system data, and Task 2 backs up the running status data of Application 1.

[0065] Step 220 : In response to receiving the content configuration operation for the disaster recovery backup task, a content configuration result corresponding to the disaster recovery backup task is obtained.

[0066] The content configuration result is used to indicate the backup content requirement corresponding to backing up the data in the first data center to the second data center.

[0067] Schematically, the content configuration operation refers to an operation in which a user manually configures the backup content requirements of a disaster recovery backup task.

[0068] Optionally, the content configuration operation is performed by manual input; or, the content configuration operation is performed by voice input; or, the content configuration operation is performed by moving the terminal, for example: the terminal is equipped with an operating handle, and the backup content requirements are configured by waving the operating handle to the left or right.

[0069] In some embodiments, the backup content requirement refers to the backup conditions that the data backup process complies with when backing up data in the first data center to the second data center.

[0070] Optionally, the backup content requirements include at least one of the following requirement types: a first storage path for data in a first data center, a second storage path for data in a second data center, resource load parameters corresponding to the data, data type, memory load parameters corresponding to the data, data quantity, and data backup speed.

[0071] The first storage path refers to the data's storage location in the first data center. For example, if the first storage path is: drive D / folder A / folder B, the data is stored in folder B in folder A on drive D in the first data center. The second storage path refers to the data's storage location in the second data center after it is backed up to the second data center. Optionally, the second storage path is the same as the first storage path, that is, if the first storage path is: drive D / folder A / folder B, the second storage path is also: drive D / folder A / folder B. Alternatively, the second storage path is different from the first storage path, that is, if the first storage path is: drive D / folder A / folder B, the second storage path is: drive C / folder A / folder B. Although stored on different hard drives, when data is backed up to drive C in the second storage path, a hard drive change indicator is added to the data. For example, "DC" indicates that the data was stored on drive D in the first data center but is stored on drive C after being backed up to the second data center. This approach prevents data from being found or data read errors that occur when the data is stored in different locations in the two data centers, thereby improving data backup accuracy.

[0072] The resource load parameter refers to the computing resources (eg, central processing unit (CPU) or graphics processing unit (GPU)) consumed by the first data center in the process of processing data.

[0073] The data type refers to the file type of data stored in the first data center, for example, distributed file data refers to file data in a distributed file system (Hadoop Distributed File System, HDFS).

[0074] The memory load parameter corresponding to the data refers to the memory capacity occupied by the data stored in the first data center.

[0075] The data quantity refers to the quantity of data in the first data center that is backed up to the second data center.

[0076] The data backup speed refers to the backup speed of backing up data from the first data center to the second data center. For example, if 15,000 data items are backed up from the first data center to the second data center, the backup speed is 500 items / millisecond, which means that 500 data items are backed up every millisecond.

[0077] Step 230 : In response to receiving the trigger condition configuration operation for the disaster recovery backup task, a condition configuration result corresponding to the disaster recovery backup task is obtained.

[0078] The condition configuration result is used to indicate the triggering condition corresponding to starting to back up the data in the first data center to the second data center.

[0079] Schematically, the trigger condition configuration operation refers to the operation of configuring the trigger condition of the disaster recovery backup task.

[0080] In some embodiments, the first data center backs up data to the second data center only when a trigger condition is met.

[0081] Optionally, the trigger condition includes at least one of the following condition types:

[0082] 1. Periodic conditions: This means that the first data center backs up data to the second data center at specified intervals. For example, the first data center backs up data to the second data center every 5 seconds.

[0083] 2. Time range condition: The primary data center will back up data to the secondary data center within a specified time range. If the specified time range is exceeded or not reached, data backup will not be performed between the primary and secondary data centers.

[0084] 3. Resource consumption condition, which means that when the computing resource consumption in the first data center reaches a specified consumption, the data in the first data center will be backed up to the second data center;

[0085] 4. Memory usage condition: When the memory resources occupied by the data stored in the first data center reaches the specified resource threshold, the data in the first data center will be backed up to the second data center.

[0086] It is worth noting that the above-mentioned trigger condition types are merely illustrative examples and are not limited to these in the embodiments of the present application.

[0087] Step 240: Execute the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result.

[0088] The disaster recovery backup result is used to indicate that the data in the first data center will be backed up to the second data center according to the backup content requirements when the triggering conditions are met.

[0089] Illustratively, the disaster recovery backup result refers to the result of backing up the data in the first data center to the corresponding result of the second data center based on the content configuration result and the condition configuration result. In other words, the disaster recovery backup result refers to the data backed up from the second data center.

[0090] Optionally, after obtaining the content configuration results and the condition configuration results, the terminal stores the content configuration results, the condition configuration results, and the disaster recovery backup task in a database, sends the stored results to the scheduling system, and uses the scheduling system to pull the data backup process to complete the data backup between the first data center and the second data center. During the execution of the data backup process, the scheduling system passes the parameters corresponding to the content configuration results and the condition configuration results to the data backup process to ensure that the operation of the data backup process meets the backup content requirements and trigger conditions. The data backup process and scheduling system are described in detail in subsequent embodiments.

[0091] Optionally, after the terminal obtains the content configuration results and the condition configuration results, it reads the configuration parameters corresponding to the trigger conditions in the condition configuration results. When the trigger conditions are met, the terminal generates a data backup instruction based on the content configuration results and the disaster recovery backup task, and sends it to the first data center and the second data center to instruct the first data center to back up the data to the second data center.

[0092] Optionally, after the terminal obtains the content configuration results and the condition configuration results, it reads the configuration parameters corresponding to the trigger conditions in the condition configuration results. When the trigger conditions are met, the condition configuration results and the disaster recovery backup task are forwarded to the cloud server. The cloud server pulls the data backup process based on the received condition configuration results and disaster recovery backup task to complete the data backup between the first data center and the second data center.

[0093] The above methods use different methods to perform data backup tasks, which can adapt to various disaster recovery and backup needs while meeting the trigger conditions and backup content requirements, thereby improving the feasibility and applicability of disaster recovery and backup.

[0094] In summary, the disaster recovery backup method provided in the embodiment of the present application obtains a disaster recovery backup task of backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery association relationship. By receiving the content configuration operation and the trigger condition configuration operation for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center according to the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when the backup command needs to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can be achieved only after the user manually executes the backup instruction. The disaster recovery backup process is optimized, which not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup.

[0095] In an optional embodiment, the configuration process of the trigger conditions and backup content requirements is described in detail. For example, please refer to Figure 3 , which shows a flow chart of a disaster recovery backup method provided by an exemplary embodiment of the present application, that is, step 220 includes step 2201 before step 220, and step 230 also includes steps 231 to 232. For example, Figure 3 As shown, the method can also be implemented as the following steps.

[0096] Step 2201: Display the task configuration interface.

[0097] The task configuration interface includes a trigger condition configuration area and a content configuration area.

[0098] Schematically, the user configures the disaster recovery backup task through a visual interface, and therefore, a task configuration interface is displayed on the terminal, wherein the task configuration interface includes a content configuration area and a trigger condition configuration area.

[0099] In some embodiments, the content configuration area is used to configure the backup content requirements of the disaster recovery backup task, and the trigger condition configuration area is used to configure the trigger conditions of the disaster recovery backup task.

[0100] Optionally, the trigger condition configuration area and the content configuration area are displayed synchronously in the task configuration interface; or, the task configuration interface includes a condition configuration control and a content configuration control. When a selection operation of the condition configuration control is received, the trigger condition configuration area is displayed in the task configuration interface; when a selection operation of the content configuration control is received, the content configuration area is displayed in the task configuration interface.

[0101] For illustration, please refer to Figure 4 , which shows a schematic diagram of a task configuration interface provided by an exemplary embodiment of the present application, including a content configuration area 410 and a trigger condition configuration area 420.

[0102] The content configuration area 410 can configure multiple backup content requirements in the disaster recovery backup task, including: task name, task identification code, creator, task creation time, data type, and synchronization object.

[0103] Among them, the task name refers to the name corresponding to the disaster recovery backup task, the task identification code is used to indicate the identity identification code (Identity Document, ID) unique to the disaster recovery backup task, the creator refers to the user account that creates the disaster recovery backup task, that is, the account of the user who logs in to the disaster recovery backup system in the current terminal, the task creation time refers to the moment when the disaster recovery backup task is created, the data type refers to the corresponding type of data to be backed up, and the synchronization object is used to indicate the objects that need to be synchronized in the first data center and the second data center, for example: the storage path corresponding to the data needs to be synchronized, and for example: the memory percentage corresponding to the data needs to be synchronized.

[0104] The trigger condition configuration area 420 can be used to configure the trigger conditions corresponding to the disaster recovery backup task. Optionally, one or more trigger conditions can be configured.

[0105] In this embodiment, the start time of the disaster recovery backup task and the execution time interval are set in the trigger condition configuration area 420 as the trigger conditions of the disaster recovery backup task. Therefore, during the execution process, when the execution start time is reached, the disaster recovery backup task starts to be executed, and thereafter, the disaster recovery backup task is periodically executed at specified time intervals.

[0106] Step 220 : In response to receiving the content configuration operation for the disaster recovery backup task, a content configuration result corresponding to the disaster recovery backup task is obtained.

[0107] The content configuration result is used to indicate the backup content requirement corresponding to backing up the data in the first data center to the second data center.

[0108] In this embodiment, the terminal displays a task configuration interface, which includes a content configuration area. The configuration operation required for the backup content is received in the content configuration area as a content configuration operation, and the content configuration result corresponding to the disaster recovery backup task is determined based on the configuration parameters input corresponding to the configuration operation.

[0109] Optionally, the configuration operation is implemented as the user manually inputting configuration parameters; or, the content configuration area includes a parameter selection area, and multiple candidate configuration parameters are displayed in the parameter selection area. When a selection operation for a specified parameter from the multiple candidate configuration parameters is received, the specified parameter is used as the content configuration result.

[0110] In some embodiments, the backup content requirements include at least one of a first storage path, a second storage path, a resource load parameter, a memory load parameter, a data type, a data quantity, or a data backup speed; wherein the first storage path is used to indicate the storage location of the data backed up in the first data center in the first data center, the second storage path is used to indicate the storage location of the backed up data in the second data center, the resource load parameter is used to indicate the amount of computing resources occupied by the data in the first data center, and the memory load parameter is used to indicate the amount of memory occupied by the data in the first data center.

[0111] The first storage path refers to the storage location of the data in the first data center. For example, the first storage path is: disk D / folder A / folder B, that is, the data is stored in folder B in folder A in disk D in the first data center. The second storage path refers to the storage location of the data in the second data center after it is backed up to the second data center. Optionally, the second storage path is the same as the first storage path, that is, when the first storage path is: disk D / folder A / folder B, the second storage path is also: disk D / folder A / folder B; or, the second storage path is different from the first storage path.

[0112] The resource load parameter refers to the CPU resources or GPU resources consumed by the first data center in the process of processing data.

[0113] The data type refers to the file type of data stored in the first data center, for example, distributed file data refers to file data in a distributed file system (Hadoop Distributed File System, HDFS).

[0114] The memory load parameter corresponding to the data refers to the memory capacity occupied by the data stored in the first data center.

[0115] The data quantity refers to the quantity of data in the first data center that is backed up to the second data center.

[0116] The data backup speed refers to the backup speed of data from the first data center to the second data center.

[0117] Through the above method, users can configure the parameters of the backup content requirements of the disaster recovery backup task through a visual interface, avoiding the need for users to manually write the code content of the instructions corresponding to the disaster recovery backup task, reducing the requirements for user code writing capabilities, and thus reducing the difficulty of creating disaster recovery backup tasks and improving task creation efficiency.

[0118] Step 231: Receive a condition configuration operation in the trigger condition configuration area.

[0119] The trigger condition configuration area is used to determine the trigger condition.

[0120] In an illustrative manner, by receiving a condition configuration operation in the trigger condition configuration area, the trigger condition corresponding to the disaster recovery backup task is configured.

[0121] In some embodiments, multiple candidate trigger conditions are displayed in the trigger condition configuration area; in response to receiving a selection operation for the first trigger condition among the multiple candidate trigger conditions, a condition configuration operation is performed; or, in response to receiving a condition content input operation in the trigger condition configuration area, a condition configuration operation is performed.

[0122] In one practicable scenario, multiple candidate trigger conditions are pre-set. Therefore, the multiple candidate trigger conditions are displayed in the trigger condition configuration area corresponding to the task configuration interface. When a selection operation is received for the first trigger condition among the multiple candidate trigger conditions, it is considered as a condition configuration operation. The first trigger condition is the trigger condition configuration result.

[0123] In another possible implementation, the trigger condition configuration operation is implemented by receiving a condition content input operation.

[0124] The above conditional configuration operation can meet the user's operation mode under different configuration requirements, thereby improving the efficiency of conditional configuration.

[0125] Step 232: Obtain a conditional configuration result corresponding to the disaster recovery backup task based on the conditional configuration operation.

[0126] In one feasible case, the selected first trigger condition is used as the condition configuration result; in another feasible case, the input condition content is used as the condition configuration result.

[0127] Indicatively, after receiving the condition configuration operation, the trigger condition corresponding to the disaster recovery backup task is displayed in the task configuration interface as the condition configuration result.

[0128] In summary, the disaster recovery backup method provided in the embodiment of the present application obtains a disaster recovery backup task of backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery association relationship. By receiving the content configuration operation and the trigger condition configuration operation for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center according to the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when the backup command needs to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can be achieved only after the user manually executes the backup instruction. The disaster recovery backup process is optimized, which not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup.

[0129] In this embodiment, the visual task configuration is realized by displaying the task configuration interface, which allows the user to directly configure various parameters of the disaster recovery backup task through the task configuration interface, reducing the requirements on the user's operating ability and thereby improving the efficiency of task configuration.

[0130] In an optional embodiment, the process of obtaining the disaster recovery backup task is described in detail. For example, please refer to Figure 5 , which shows a flow chart of a disaster recovery backup method provided by an exemplary embodiment of the present application, that is, step 210 also includes steps 211 to 213, and step 240 also includes steps 241 to 242, such as Figure 5 The method includes the following steps.

[0131] Step 211 : In response to receiving a task creation operation, an initial disaster recovery task is obtained.

[0132] In this embodiment, before obtaining a disaster recovery backup, it is first necessary to create an initial disaster recovery task.

[0133] The initial disaster recovery task is only used to indicate that there is currently a task for backing up data in at least two data centers, but the disaster recovery task does not specifically refer to the data centers and related data.

[0134] The following is a detailed description of the task creation process.

[0135] In some embodiments, a disaster recovery object creation interface is displayed, which includes an object creation area, which is used to create a disaster recovery backup object; in response to receiving a name input operation in the object creation area, an object name corresponding to the disaster recovery backup object is obtained; in response to receiving an address input operation in the object creation area, first connection information corresponding to the first data center and second connection information corresponding to the second data center are obtained; in response to receiving a content generation operation in the object creation area, object content information corresponding to the disaster recovery backup object is obtained; and the disaster recovery backup object is obtained based on the object name, the first connection information, the second connection information and the object content information.

[0136] In this embodiment, when the terminal runs a disaster recovery backup system, a disaster recovery object creation interface is displayed. The disaster recovery object creation interface includes an object creation area for creating a disaster recovery backup object.

[0137] Among them, the disaster recovery backup object refers to an object with a disaster recovery relationship between at least two data centers, that is, when the first data center and the second data center are defined in the disaster recovery backup object, it means that a disaster recovery relationship is established between the first data center and the second data center.

[0138] Before establishing the initial disaster recovery task, first, in the object creation area, accept the name input operation and enter the object name corresponding to the disaster recovery backup object.

[0139] Next, an address input operation is received, and the first connection information corresponding to the first data center and the second connection information corresponding to the second data center are obtained.

[0140] Taking the first connection information as an example, the first connection information refers to information used to establish a communication connection with the first data center, and is used to access or manage the first data center. The second connection information can be obtained similarly.

[0141] Optionally, the connection information includes at least one of the following information types: Internet Protocol Address (IP), port number of a data center, protocol type, authentication information, connection mode, topology structure, etc.

[0142] Among them, the protocol type refers to the communication protocol used between each node in the data center, the authentication information refers to the user name, password, key and other information used to access the data center, the connection method includes at least one of the connection methods such as direct connection, network connection or virtualization connection, and the topology structure refers to the connection relationship between each node in the data center.

[0143] In this embodiment, the data center may also be referred to as a cluster.

[0144] Secondly, a content generation operation is received to obtain object content information corresponding to the disaster recovery backup object, wherein the object content information includes at least one of the following content information: the geographical area where the data center is located, the center's operating status, the center name of the data center, the components deployed in the data center, the object creation time, and the creator.

[0145] Finally, a disaster recovery backup object is obtained according to the object name, the first connection information, the second connection information, and the plurality of object content information, to indicate that the first data center and the second data center currently have a disaster recovery association relationship.

[0146] For illustration, please refer to Figure 6 , which shows a schematic diagram of a disaster recovery object creation interface provided by an exemplary embodiment of the present application, including an object creation area 610.

[0147] Among them, object creation 610 can be used to create object name, object identification code, creator, creation time, first connection information (not shown) corresponding to the first data center and the second data center respectively, second connection information (not shown), geographic location, operating status and deployment components.

[0148] This method can establish a disaster recovery association for the data center by creating a disaster recovery backup object in the visual interface, making it easier to directly bind the disaster recovery backup object to achieve data backup between the two data centers during the subsequent creation of disaster recovery backup tasks. There is no need to separately determine the data center that needs to be backed up for each disaster recovery backup task, thereby improving task creation efficiency.

[0149] Step 212: Obtain a disaster recovery backup object.

[0150] The disaster recovery backup object includes first connection information corresponding to the first data center and second connection information corresponding to the second data center. The first connection information is used to establish a communication connection with the first data center, and the second connection information is used to establish a communication connection with the second data center.

[0151] In some embodiments, a task configuration interface is displayed, which includes multiple candidate disaster recovery objects, and the candidate disaster recovery objects include backup parameters corresponding to at least two devices with a disaster recovery backup relationship; in response to receiving a selection operation of specifying an object among multiple candidate disaster recovery objects, a disaster recovery backup object is obtained.

[0152] In this embodiment, multiple different disaster recovery backup objects can be created through the object creation interface to represent multiple different data centers with disaster recovery relationships, from which the disaster recovery backup object representing the disaster recovery relationship between the first data center and the second data center is determined.

[0153] This method creates multiple disaster recovery backup objects in advance, so that when creating a disaster recovery backup task, the data center for executing the backup task can be directly determined by selecting a specified object, which simplifies the task creation process and improves task creation efficiency.

[0154] For illustration, please refer to Figure 7 , which shows a schematic diagram of a disaster recovery backup object creation process provided by an exemplary embodiment of the present application, such as Figure 7 As shown, it includes step 710, creating a disaster recovery backup object and step 720, filling in the first connection information and the second connection information.

[0155] Step 710: Create a disaster recovery backup object.

[0156] The disaster recovery object creation interface is displayed. The disaster recovery object creation interface includes an object creation area. The object creation area receives input operations of multiple different information, including object name and multiple object content information, to create a disaster recovery backup object.

[0157] Step 720: Fill in the first connection information and the second connection information.

[0158] When the first connection information corresponding to the first data center and the second connection information corresponding to the second data center are obtained, the first connection information and the second connection information are input into the object creation area to obtain a disaster recovery backup object indicating a disaster recovery relationship between the first data center and the second data center.

[0159] Step 213: In response to receiving the binding operation between the disaster recovery backup object and the initial disaster recovery task, a disaster recovery backup task is obtained.

[0160] In an illustrative manner, after obtaining the disaster recovery backup object, the object name corresponding to the disaster recovery backup object is input into the object name corresponding to the initial disaster recovery task, thereby binding the disaster recovery backup object and the initial disaster recovery task, and obtaining the bound disaster recovery backup task, which is used to indicate that the data in the first data center is backed up to the second data center.

[0161] This method gradually creates disaster recovery backup objects and then creates disaster recovery backup tasks. It splits the task establishment process into processes and converts each process into visual parameter configuration, which reduces the difficulty of task configuration and improves disaster recovery backup efficiency and backup accuracy.

[0162] Step 241: Call the data backup process.

[0163] The data backup process is used to back up data in the first data center to the second data center.

[0164] In this embodiment, the process of creating disaster recovery backup objects and disaster recovery backup tasks can be implemented as being executed at the front end of the terminal. In the process of creating disaster recovery backup objects and disaster recovery backup tasks, a database is provided in the server configured by the terminal for storing object parameters corresponding to the disaster recovery backup objects, as well as configuration parameters corresponding to the content configuration results and trigger condition configuration results corresponding to the disaster recovery backup tasks.

[0165] In this embodiment, the server can directly call the data backup process, or a scheduling system is set up in the disaster recovery backup system, and a scheduling backup task (shell task) is created by calling the specified interface of the scheduling system, and the object parameters and configuration parameters are written into the scheduling backup task.

[0166] Step 242: delivering the content configuration result and the condition configuration result to the data backup process to obtain the disaster recovery backup result.

[0167] The scheduling system starts the scheduling backup task when the trigger conditions are met, passes the object parameters and matching value parameters to the scheduling backup task, and executes the scheduling backup task through the scheduling system.

[0168] During the scheduled backup task execution, the data synchronization code content is downloaded from the scheduling system's external storage, and the corresponding code process is launched as the data backup process. The object parameters, configuration parameters, and disaster recovery backup tasks are passed to the data backup process. The data in the first data center is backed up to the second data center through the data backup process. When the backup is complete, the data backup process terminates.

[0169] Optionally, the data backup process includes a Java process, a shell process, and a Python process.

[0170] In some embodiments, during the execution of the data backup process, it is necessary to perform data verification on the backed up data. The data verification process is described in detail below.

[0171] In some embodiments, the first data center includes first data; a preset divisor is obtained; check data is added to a specified field position of the first data to obtain first check data, the number of characters in the check data corresponds to the number of characters in the preset divisor, and the first data corresponds to a first field position in the first check data; based on a data backup process, the first check data is backed up from the first data center to the second data center to obtain second check data of the second data center; a division calculation is performed on the second check data and the preset divisor to obtain a division calculation result; when the remainder in the division calculation result meets the preset division condition, the data in the first field position in the second check data is used as a disaster recovery backup result.

[0172] In this embodiment, a cyclic redundancy check (CRC) is used to verify the data backed up in the second data center. First, a divisor (i.e., a generating polynomial) is obtained for performing a division operation on the received data when verifying the data in the second data center. Second, the number of binary bits corresponding to the selected divisor is determined (assuming k bits, where k is a positive integer) as a preset divisor. Next, k-1 bits of "0" are added to the first data (assuming m bits, where m is a positive integer), where the k-1 bits of "0" are the verification data, thereby obtaining the first verification data. The first verification data is then backed up to the second data center to obtain the second verification data, and the second verification data is divided by the preset divisor using a "modulo 2 division" method. Modulo 2 division refers to a division operation with no carry or borrow. The obtained trigger operation result includes a remainder (i.e., a binary bit string). If the remainder is 0, it indicates that the data transmission is correct, and the first m bits of the characters in the second verification data are used as the disaster recovery backup result.

[0173] This method can timely detect the backup accuracy during the data backup process through data verification, thereby improving the accuracy of data backup.

[0174] In some embodiments, a disaster recovery backup task corresponds to a task identifier, and the content configuration result and the condition configuration result are respectively associated with the task identifier; multiple candidate task identifiers are obtained, and the multiple candidate task identifiers respectively correspond to different candidate disaster recovery tasks; a parameter configuration set is obtained, and the parameter configuration set includes candidate configuration results corresponding to multiple candidate disaster recovery tasks; when a target identifier corresponding to the task identifier is selected from multiple candidate task identifiers, the parameter configuration result corresponding to the disaster recovery backup task is obtained from the parameter configuration set, and the parameter configuration result includes the content configuration result and the condition configuration result.

[0175] In this embodiment, the disaster recovery backup task corresponds to a task identifier, and the task identifier is associated with the content configuration result and trigger condition configuration result corresponding to the disaster recovery backup task. Therefore, by obtaining multiple candidate task identifiers, the task identifier is selected from them, and then the task representation is used to obtain the content configuration results and trigger condition configuration results with an associated relationship in the parameter configuration set.

[0176] This method directly obtains content configuration results and trigger condition configuration results by setting task identifiers, without calling the scheduled backup task. Instead, the content configuration results and trigger condition configuration results obtained in the above manner are directly input into the data backup process, saving computer resource overhead.

[0177] For illustration, please refer to Figure 8 , which shows a schematic diagram of the disaster recovery backup task execution process provided by an exemplary embodiment of the present application, such as Figure 8 As shown, it includes step 810, creating an initial backup task, step 820, configuring a disaster recovery backup object, step 830, content configuration operation, step 840, trigger condition configuration operation, step 850, creating a disaster recovery backup task, and step 860, executing the disaster recovery backup task through the scheduling system.

[0178] Step 810: Create an initial backup task.

[0179] Enter the task name in the task configuration interface through the concurrent computing model (Actor model) to create the initial backup task.

[0180] In this embodiment, each node in the backup system is configured with a corresponding Actor model. For example, the terminal is configured with Actor model 1, the first data center is configured with Actor model 2, and the second data center is configured with Actor model 3. The Actor model corresponding to each node is used to execute the operations and behaviors corresponding to the node. For example, Actor model 1 executes a series of operations of the terminal to complete various user operation instructions received by the terminal.

[0181] Step 820: Configure disaster recovery backup objects.

[0182] A designated backup object is selected from multiple pre-configured candidate backup objects as a disaster recovery backup object, and the disaster recovery backup object is bound to the initial backup task.

[0183] Step 830: Configure backup content requirements.

[0184] In the task configuration interface, accept content configuration operations and configure the backup content requirements for the disaster recovery backup task.

[0185] Step 840: Configure trigger conditions.

[0186] In the task configuration interface, accept the trigger condition configuration operation and configure the trigger conditions for the disaster recovery backup task.

[0187] Step 850: The disaster recovery backup task is created.

[0188] After obtaining the triggering conditions and backup content requirements, the configured initial backup task is obtained as a disaster recovery backup task.

[0189] Step 860: The scheduling system executes the disaster recovery backup task on a regular basis.

[0190] The above scheduling system executes disaster recovery backup tasks according to trigger conditions and content configuration requirements.

[0191] In some embodiments, the first data center includes second data, and the second data corresponds to a third storage path in the first data center, and the third storage path is used to indicate that the second data is stored in a first folder in the first data center; when the trigger condition is met and in the process of backing up the second data from the first data center to the second data center, the first folder is traversed based on the third storage path to obtain multiple candidate data in the first folder; when there is third data that has not been backed up among the multiple candidate data and the backup of the second data is completed, the third data is backed up from the first data center to the second data center.

[0192] In this embodiment, the second data is stored in the first data center, and the third storage path corresponding to the second data indicates that the second data is stored in the first folder of the first data center. When the second data is backed up from the first data center to the second data center, the first folder in the first data center is determined according to the third storage path, and the data in the first folder is traversed. When there is third data that has not been backed up, the third data is backed up to the second data center after the second data backup is completed.

[0193] This method improves data backup efficiency by backing up the data in the same folder in sequence according to the storage path corresponding to the currently backed up data.

[0194] In summary, the disaster recovery backup method provided in the embodiment of the present application obtains a disaster recovery backup task of backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery association relationship. By receiving the content configuration operation and the trigger condition configuration operation for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center according to the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when the backup command needs to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can be achieved only after the user manually executes the backup instruction. The disaster recovery backup process is optimized, which not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup.

[0195] In this embodiment, the data backup process is pulled out periodically by the scheduling system to perform data backup, thereby ensuring the backup accuracy and backup efficiency of the disaster recovery backup process.

[0196] For illustration, please refer to Figure 9, which shows a flow chart of the backup task backend provided by an exemplary embodiment of the present application, such as Figure 9 As shown, the method includes the following steps.

[0197] Step 910: The disaster recovery system front end creates disaster recovery and disaster recovery task data, and calls the disaster recovery system back end service through an interface.

[0198] In the disaster recovery system, the terminal creates and configures disaster recovery backup tasks by receiving various configuration operations, and calls the back-end server corresponding to the terminal through the specified interface.

[0199] Step 920: The disaster recovery system backend service saves the disaster recovery task information to a relational database and calls a timing scheduling system interface to create a task.

[0200] After calling the back-end server, the configuration parameters corresponding to the backup content requirements and trigger conditions are stored in a relational database preset in the server, and the scheduling system is called through the scheduling system interface.

[0201] Create scheduled backup tasks through the scheduling system.

[0202] Step 930: The timing scheduling system registers the shell task and writes the parameters in the shell.

[0203] After registering the scheduled backup task through the scheduling system, write the configuration parameters into the scheduled backup task.

[0204] In another feasible situation, disaster recovery and disaster recovery task information can be directly created by calling the back-end service of the disaster recovery system through other services without going through the front-end.

[0205] For illustration, please refer to Figure 10 , which shows a flowchart of the data backup process execution process provided by an exemplary embodiment of the present application, such as Figure 10 As shown, the method includes the following steps.

[0206] Step 1010: According to the configured scheduling period, the scheduling system starts the task on a scheduled basis and passes the disaster recovery configuration parameters to the scheduled task.

[0207] According to the scheduling cycle corresponding to the trigger bar, the scheduling system is called regularly, the scheduling backup task is started through the scheduling system, and the configuration parameters are passed to the scheduling backup task.

[0208] Step 1020: The scheduling system executes the shell task.

[0209] This shell task downloads the data synchronization code JAR package from external storage, starts the Java data backup process corresponding to the JAR package, and passes the parameters accepted by the scheduled task to this Java process.

[0210] Step 1030: The data backup process executes the data task and performs data verification.

[0211] The data in the first data center is backed up to the second data center through data backup, and the accuracy of the data backed up in the second data center is verified by a CRC verification method.

[0212] Step 1040: The data backup task is completed and the Java process exits.

[0213] In summary, the disaster recovery backup method provided in the embodiment of the present application obtains a disaster recovery backup task of backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery association relationship. By receiving the content configuration operation and the trigger condition configuration operation for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center according to the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when the backup command needs to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can be achieved only after the user manually executes the backup instruction. The disaster recovery backup process is optimized, which not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup.

[0214] The beneficial effects provided by this application include the following:

[0215] 1. By scheduling the system to periodically execute synchronization tasks, data changes in the primary cluster can be synchronized to the disaster recovery backup cluster in a timely manner, ensuring the real-time nature of the data after disaster recovery.

[0216] 2. All user operations are completed in the visual interface, reducing the user's usage threshold and the chance of operational errors.

[0217] 3. Users can manage multiple configured tasks in a visual interface without having to manually view the task code.

[0218] Figure 11 This is a structural block diagram of a disaster recovery backup device provided by an exemplary embodiment of the present application. Figure 11 As shown, the device includes the following parts:

[0219] An acquisition module 1110 is configured to acquire a disaster recovery backup task, wherein the disaster recovery backup task is configured to instruct data in a first data center to be backed up to a second data center. The first data center and the second data center have a disaster recovery association, wherein the disaster recovery association is configured to instruct that if the first data center stops executing a first service, the first service be switched to the second data center for continued execution.

[0220] The configuration module 1120 is configured to obtain, in response to receiving a content configuration operation for the disaster recovery backup task, a content configuration result corresponding to the disaster recovery backup task, wherein the content configuration result is used to indicate a backup content requirement corresponding to backing up the data in the first data center to the second data center;

[0221] The configuration module 1120 is further configured to, in response to receiving a trigger condition configuration operation for the disaster recovery backup task, obtain a condition configuration result corresponding to the disaster recovery backup task, wherein the condition configuration result is used to indicate a trigger condition corresponding to starting to back up data in the first data center to the second data center;

[0222] Execution module 1130 is used to execute the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result. The disaster recovery backup result is used to indicate that when the trigger condition is met, the data in the first data center will be backed up to the second data center according to the backup content requirements.

[0223] In some embodiments, the configuration module 1120 is used to display a task configuration interface, which includes a trigger condition configuration area, and the trigger condition configuration area is used to determine the trigger condition; receive a condition configuration operation in the trigger condition configuration area; and obtain the condition configuration result corresponding to the disaster recovery backup task based on the condition configuration operation.

[0224] In some embodiments, the configuration module 1120 is used to display multiple candidate trigger conditions in the trigger condition configuration area; in response to receiving a selection operation for the first trigger condition among the multiple candidate trigger conditions, as the condition configuration operation; or in response to receiving a condition content input operation in the trigger condition configuration area, as the condition configuration operation.

[0225] In some embodiments, the acquisition module 1110 is used to obtain an initial disaster recovery task in response to receiving a task creation operation; obtain a disaster recovery backup object, wherein the disaster recovery backup object includes first connection information corresponding to the first data center and second connection information corresponding to the second data center, the first connection information is used to establish a communication connection with the first data center, and the second connection information is used to establish a communication connection with the second data center; in response to receiving a binding operation on the disaster recovery backup object and the initial disaster recovery task, the disaster recovery backup task is obtained.

[0226] In some embodiments, the acquisition module 1110 is used to display a task configuration interface, which includes multiple candidate disaster recovery objects, and the candidate disaster recovery objects include backup parameters corresponding to at least two devices with a disaster recovery backup relationship; in response to receiving a selection operation of specifying an object among the multiple candidate disaster recovery objects, the disaster recovery backup object is obtained.

[0227] In some embodiments, the acquisition module 1110 is used to display a disaster recovery object creation interface, wherein the disaster recovery object creation interface includes an object creation area, and the object creation area is used to create the disaster recovery backup object; in response to receiving a name input operation in the object creation area, the object name corresponding to the disaster recovery backup object is obtained; in response to receiving an address input operation in the object creation area, the first connection information corresponding to the first data center and the second connection information corresponding to the second data center are obtained; in response to receiving a content generation operation in the object creation area, the object content information corresponding to the disaster recovery backup object is obtained; and the disaster recovery backup object is obtained based on the object name, the first connection information, the second connection information and the object content information.

[0228] In some embodiments, the backup content requirements include at least one of a first storage path, a second storage path, a resource load parameter, a memory load parameter, a data type, a data quantity, or a data backup speed; wherein, the first storage path is used to indicate the storage location of the data backed up in the first data center in the first data center, the second storage path is used to indicate the storage location of the backed up data in the second data center, the resource load parameter is used to indicate the amount of computing resources occupied by the data in the first data center, and the memory load parameter is used to indicate the amount of memory occupied by the data in the first data center.

[0229] In some embodiments, the execution module 1130 is used to call a data backup process, which is used to back up the data in the first data center to the second data center; pass the content configuration result and the condition configuration result to the data backup process to obtain the disaster recovery backup result.

[0230] In some embodiments, the first data center includes first data;

[0231] The execution module 1130 is used to obtain a preset divisor; add verification data at a specified field position of the first data to obtain first verification data, the number of characters of the verification data corresponds to the number of characters of the preset divisor, and the first data corresponds to a first field position in the first verification data; based on the data backup process, the first verification data is backed up from the first data center to the second data center to obtain second verification data of the second data center; perform division calculation on the second verification data and the preset divisor to obtain a division calculation result; when the remainder in the division calculation result meets the preset division condition, the data at the first field position in the second verification data is used as the disaster recovery backup result.

[0232] In some embodiments, the disaster recovery backup task corresponds to a task identifier, and the content configuration result and the condition configuration result are associated with the task identifier respectively;

[0233] The execution module 1130 is used to obtain multiple candidate task identifiers, each of which corresponds to a different candidate disaster recovery task; obtain a parameter configuration set, which includes candidate configuration results corresponding to multiple candidate disaster recovery tasks; in response to receiving a selection operation on a target identifier corresponding to the task identifier among the multiple candidate task identifiers, obtain a parameter configuration result corresponding to the disaster recovery backup task from the parameter configuration set, wherein the parameter configuration result includes the content configuration result and the condition configuration result.

[0234] In some embodiments, the first data center includes second data, the second data corresponds to a third storage path in the first data center, and the third storage path is used to indicate that the second data is stored in a first folder in the first data center;

[0235] The execution module 1130 is used to traverse the first folder based on the third storage path to obtain multiple candidate data in the first folder when the trigger condition is met and when the second data is backed up from the first data center to the second data center; if there is third data that has not been backed up among the multiple candidate data and the backup of the second data is completed, back up the third data from the first data center to the second data center.

[0236] In summary, the disaster recovery backup device provided in the embodiment of the present application obtains a disaster recovery backup task of backing up data in a first data center to a second data center, wherein the first data center and the second data center are two data centers located in different geographical areas and having a disaster recovery association relationship. By receiving the content configuration operation and the trigger condition configuration operation for the disaster recovery backup task, the backup content requirements and trigger conditions of the disaster recovery backup task are configured. Compared with the method of manually creating backup instructions in the related art, the visual configuration of the backup task reduces the difficulty of operation and improves the efficiency of disaster recovery backup. Furthermore, after the configuration is completed, the data of the first data center is backed up to the second data center according to the backup content requirements when the trigger conditions are met. Compared with the related art in which disaster recovery backup can only be performed when the backup command needs to be executed between different data centers, multiple disaster recovery backups are automatically performed according to the configuration results when the trigger conditions are met. Disaster recovery backup can be achieved only after the user manually executes the backup instruction, which optimizes the disaster recovery backup process, not only reduces the data overhead of computer resources, but also improves the real-time performance of disaster recovery backup.

[0237] It should be noted that the disaster recovery backup device provided in the above embodiment is merely an example of the division of the aforementioned functional modules. In actual applications, the aforementioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. Furthermore, the disaster recovery backup device provided in the above embodiment and the disaster recovery backup method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0238] Figure 12The following is a block diagram of a computer device 1200 according to an exemplary embodiment of the present application. Computer device 1200 may be a portable mobile terminal, such as a smartphone, tablet computer, MP3 player (Moving Picture Experts Group Audio Layer III), MP4 player (Moving Picture Experts Group Audio Layer IV), laptop computer, or desktop computer. Computer device 1200 may also be referred to as user equipment, portable terminal, laptop terminal, desktop terminal, or other similar names.

[0239] Typically, the computer device 1200 includes a processor 1201 and a memory 1202 .

[0240] The processor 1201 may include one or more processing cores, such as a 4-core processor, a 12-core processor, etc. The processor 1201 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), or PLA (Programmable Logic Array). The processor 1201 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1201 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1201 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0241] The memory 1202 may include one or more computer-readable storage media, which may be non-transitory. The memory 1202 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices and flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1202 is used to store at least one instruction, which is used to be executed by the processor 1201 to implement the classification model training method and data classification method provided in the method embodiment of the present application.

[0242] In some embodiments, the computer device 1200 may optionally include other components, which can be understood by those skilled in the art. Figure 12 The structure shown in the figure does not constitute a limitation on the computer device 1200, and the computer device 1200 may include more or fewer components than shown in the figure, or combine some components, or adopt a different component arrangement.

[0243] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium, which can be a computer-readable storage medium included in the memory in the above embodiments; or a separate computer-readable storage medium that is not installed in the terminal. The computer-readable storage medium stores at least one instruction, at least one program, code set, or instruction set. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the classification model training method and data classification method described in any of the above embodiments.

[0244] Optionally, the computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a solid-state drive (SSD), or an optical disk. Among them, the random access memory may include a resistance random access memory (ReRAM) and a dynamic random access memory (DRAM). The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0245] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0246] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A disaster recovery backup method, characterized in that: The method comprises: Obtain a disaster recovery backup task, where the disaster recovery backup task is used to instruct data in a first data center to be backed up to a second data center. The first data center and the second data center have a disaster recovery association relationship, where the disaster recovery association relationship is used to instruct that if the first data center stops running while executing a first service, the first service is switched to the second data center for continued execution. In response to receiving a content configuration operation for the disaster recovery backup task, obtaining a content configuration result corresponding to the disaster recovery backup task, the content configuration result being used to indicate a backup content requirement corresponding to backing up the data in the first data center to the second data center; In response to receiving a trigger condition configuration operation for the disaster recovery backup task, obtaining a condition configuration result corresponding to the disaster recovery backup task, the condition configuration result being used to indicate a trigger condition corresponding to starting to back up data in the first data center to the second data center; The disaster recovery backup task is executed based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result, which is used to indicate that when the trigger condition is met, the data in the first data center will be backed up to the second data center according to the backup content requirements.

2. The method according to claim 1, characterized in that The step of obtaining, in response to receiving the trigger condition configuration operation for the disaster recovery backup task, a condition configuration result corresponding to the disaster recovery backup task, includes: Displaying a task configuration interface, wherein the task configuration interface includes a trigger condition configuration area, wherein the trigger condition configuration area is used to determine the trigger condition; receiving a condition configuration operation in the trigger condition configuration area; The condition configuration result corresponding to the disaster recovery backup task is obtained based on the condition configuration operation.

3. The method according to claim 2, characterized in that The receiving condition configuration operation in the trigger condition configuration area includes: Displaying a plurality of candidate trigger conditions in the trigger condition configuration area; in response to receiving a selection operation of a first trigger condition among the plurality of candidate trigger conditions as the condition configuration operation; or In response to receiving a conditional content input operation in the trigger condition configuration area, as the condition configuration operation.

4. The method according to any one of claims 1 to 3, characterized in that: The disaster recovery backup task includes: In response to receiving the task creation operation, obtaining an initial disaster recovery task; Obtain a disaster recovery backup object, where the disaster recovery backup object includes first connection information corresponding to the first data center and second connection information corresponding to the second data center, where the first connection information is used to establish a communication connection with the first data center, and the second connection information is used to establish a communication connection with the second data center; In response to receiving a binding operation on the disaster recovery backup object and the initial disaster recovery task, the disaster recovery backup task is obtained.

5. The method according to claim 4, characterized in that The obtaining of the disaster recovery backup object includes: Displaying a task configuration interface, wherein the task configuration interface includes a plurality of candidate disaster recovery objects, wherein the candidate disaster recovery objects include connection information corresponding to at least two devices having a disaster recovery backup relationship; In response to receiving a selection operation of specifying an object from the plurality of candidate disaster recovery objects, the disaster recovery backup object is obtained.

6. The method according to claim 4, characterized in that Before obtaining the disaster recovery backup object, the method further includes: Displaying a disaster recovery object creation interface, wherein the disaster recovery object creation interface includes an object creation area, and the object creation area is used to create the disaster recovery backup object; In response to receiving a name input operation in the object creation area, obtaining an object name corresponding to the disaster recovery backup object; In response to receiving an address input operation in the object creation area, obtaining first connection information corresponding to the first data center and second connection information corresponding to the second data center; In response to receiving a content generation operation in the object creation area, obtaining object content information corresponding to the disaster recovery backup object; The disaster recovery backup object is obtained based on the object name, the first connection information, the second connection information, and the object content information.

7. The method according to any one of claims 1 to 3, characterized in that: The backup content requirement includes at least one of a first storage path, a second storage path, a resource load parameter, a memory load parameter, a data type, a data quantity, or a data backup speed; Among them, the first storage path is used to indicate the storage location of the data backed up in the first data center in the first data center, the second storage path is used to indicate the storage location of the backed up data in the second data center, the resource load parameter is used to indicate the amount of computing resources occupied by the data in the first data center, and the memory load parameter is used to indicate the amount of memory occupied by the data in the first data center.

8. The method according to any one of claims 1 to 3, characterized in that: The performing of the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result includes: Invoking a data backup process, wherein the data backup process is used to back up data in the first data center to the second data center; The content configuration result and the condition configuration result are passed to the data backup process to obtain the disaster recovery backup result.

9. The method according to claim 8, characterized in that The first data center includes first data; The transferring the content configuration result and the condition configuration result to the data backup process to obtain the disaster recovery backup result includes: Get the preset divisor; Adding check data to a specified field position of the first data to obtain first check data, wherein the number of characters in the check data corresponds to the number of characters in the preset divisor, and the first data corresponds to a first field position in the first check data; Backing up the first verification data from the first data center to the second data center based on the data backup process to obtain second verification data of the second data center; Performing a division calculation on the second verification data and the preset divisor to obtain a division calculation result; When the remainder in the division calculation result meets the preset division condition, the data at the first field position in the second verification data is used as the disaster recovery backup result.

10. The method according to any one of claims 1 to 3, characterized in that: The disaster recovery backup task corresponds to a task identifier, and the content configuration result and the condition configuration result are respectively associated with the task identifier; The performing of the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result includes: Acquire multiple candidate task identifiers, where the multiple candidate task identifiers correspond to different candidate disaster recovery tasks respectively; Obtaining a parameter configuration set, wherein the parameter configuration set includes candidate configuration results corresponding to multiple candidate disaster recovery tasks; In response to receiving a selection operation on a target identifier corresponding to the task identifier among the multiple candidate task identifiers, a parameter configuration result corresponding to the disaster recovery backup task is obtained from a parameter configuration set, the parameter configuration result including the content configuration result and the condition configuration result.

11. The method according to any one of claims 1 to 3, characterized in that: The first data center includes second data, the second data corresponds to a third storage path in the first data center, and the third storage path is used to indicate that the second data is stored in a first folder in the first data center; The performing of the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result includes: When the trigger condition is met and in the process of backing up the second data from the first data center to the second data center, traversing the first folder based on the third storage path to obtain multiple candidate data in the first folder; If there is third data among the plurality of candidate data that has not been backed up and the backup of the second data is complete, the third data is backed up from the first data center to the second data center.

12. A disaster recovery backup device, characterized in that: The device comprises: an acquisition module, configured to acquire a disaster recovery backup task, wherein the disaster recovery backup task is configured to instruct data in a first data center to be backed up to a second data center, wherein the first data center and the second data center have a disaster recovery association relationship, and wherein the disaster recovery association relationship is configured to instruct that if the first data center stops running while executing a first business, the first business is switched to the second data center for continued execution; a configuration module configured to obtain, in response to receiving a content configuration operation for the disaster recovery backup task, a content configuration result corresponding to the disaster recovery backup task, wherein the content configuration result is used to indicate a backup content requirement corresponding to backing up the data in the first data center to the second data center; The configuration module is further configured to, in response to receiving a trigger condition configuration operation for the disaster recovery backup task, obtain a condition configuration result corresponding to the disaster recovery backup task, wherein the condition configuration result is used to indicate a trigger condition corresponding to starting to back up data in the first data center to the second data center; An execution module is used to execute the disaster recovery backup task based on the content configuration result and the condition configuration result to obtain a disaster recovery backup result. The disaster recovery backup result is used to indicate that when the trigger condition is met, the data in the first data center will be backed up to the second data center according to the backup content requirements.

13. A computer device, characterized in that: The computer device includes a processor and a memory, wherein the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the disaster recovery backup method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that The storage medium stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the image object recognition method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the disaster recovery backup method according to any one of claims 1 to 11.

Images