Protection method and device for disaster recovery switching data, equipment and storage medium

Abstract

The invention relates to the technical field of application disaster recovery, and discloses a disaster recovery switching data protection method, device and equipment and a storage medium, and the method comprises the steps: controlling a management device to create a disaster recovery switching task after application access is configured in the management device; after the disaster recovery switching task is issued to the agent device through the management and control channel, the agent device is controlled to process the switching task in a layered mode; after the agent device completes the switching task, the control channel is controlled to upload local data generated by the agent device to the management device, and the agent device is controlled to start data write forbidding protection; and the control management device re-calculates the data delay and the rule total amount based on the local data and then judges whether the write forbidding releasing condition is met, and if yes, a write forbidding releasing instruction is issued to the agent device through the control channel. According to the method, manual intervention is not needed, the disaster recovery switching efficiency can be improved, correctness verification is carried out before data writing, the influence of data inconsistency on services is reduced, and service flow switching is smoothly completed.

Description

Technical Field

[0001] The present invention relates to the technical field of application disaster recovery, and in particular to a method, device, equipment and storage medium for protecting disaster recovery switching data. Background Art

[0002] The basic method of application disaster recovery is to establish a redundant site outside the production site. After a disaster occurs, the redundant site can take over the user's normal business to achieve the goal of uninterrupted business. Application multi-active technology is the basic solution for achieving business-level disaster recovery. When a business failure requires traffic switching, different multi-active architectures may produce a variety of data inconsistency scenarios due to reasons such as data synchronization and configuration delays. From the end state of the system, the accuracy of the data represents the accuracy of the business. When managing the application multi-active architecture, it is often necessary to perform full-stack control of the vertical traffic link at the access layer, application layer, and data layer. The processing of data consistency is difficult. Generally, businesses will adopt partial loss, post-compensation or manual intervention methods, such as:

[0003] (1) Manual non-smooth switching, briefly shut down the system during switching, and then restart the system after confirming that there is no conflict.

[0004] (2) During post-data reconciliation, customized data correction strategies and manual intervention are required.

[0005] (3) Perform simple customized data write prohibition, but the implementation has a large impact and cannot be reused. Summary of the invention

[0006] In view of this, the present invention provides a method, device, equipment and storage medium for protecting disaster recovery switching data to solve the problem that the disaster recovery switching process requires manual intervention and has a high error rate.

[0007] In a first aspect, the present invention provides a method for protecting disaster recovery switching data, which is applied to business traffic management between a primary site and a backup site. The architecture of disaster recovery switching includes a management device, an agent device and a control channel. The management device is used for rule management, task generation and task driving. The agent device is used to control layered traffic and rule parsing. The control channel is used to exchange data between the management device and the agent device. The method includes: after configuring application access in the management device, controlling the management device to create a disaster recovery switching task; after using the control channel to send the disaster recovery switching task to the agent device, controlling the agent device to process the switching task in layers; when the agent device completes the switching task, controlling the control channel to upload the local data generated by the agent device to the management device, and controlling the agent device to enable data write-ban protection; after controlling the management device to recalculate the data delay and the full amount of rules based on the local data, it is determined whether the write-ban release condition is met. If so, a write-ban release instruction is sent to the agent device through the control channel.

[0008] The disaster recovery switching data protection method provided by the present invention involves two types of devices, namely a management device and an agent device. The management device and the agent device cooperate to complete the rule issuance, data writing prohibition, and writing prohibition lifting processes without human intervention, thereby improving data processing efficiency. Before data is written, the management device re-performs protection measures such as data delay and full rule calculation, thereby improving the operational efficiency of the disaster recovery switching process, reducing the occurrence of data inconsistency, and smoothly completing business traffic switching.

[0009] In an optional implementation, the process of configuring application access in the management device includes: selecting a multi-active disaster recovery architecture based on the current application scenario; configuring routing identifier parsing rules and routing allocation rules; and deploying integrated proxy devices in layers within the application.

[0010] In an optional implementation, the process of the management device creating a disaster recovery switching task includes: configuring new routing rules for the disaster recovery switching process, calculating the switching route difference, and then generating a process template for the switching task; after calculating the application data delay and write-disable rules, the write-disable rules and the process template for the switching task are issued as a disaster recovery switching task.

[0011] In an optional embodiment, the proxy device is composed of an access layer, an application layer and a data layer of a vertical link. The data layer stores all data in a database. The process of controlling the proxy device to process switching tasks in layers includes: controlling the access layer to extract the routing label from the switching task, and forwarding the routing label to the back-end service through the reverse proxy rules customized by the access layer; controlling the application layer to parse the routing label and set it to the local processing context, and then calculating and setting the attachment delivery traffic identifier; controlling the data layer proxy database to drive and save the write-blocking rules.

[0012] In an optional implementation, the process of controlling the proxy device to enable data write-ban protection includes: controlling the data layer to globally ban writing before the full switch of rules, and intercepting database reading and writing after the full switch of rules; after the control data layer parses the SQL hit and matches the write-ban rule, the data layer interrupts the write request by throwing an exception.

[0013] In an optional implementation, the process of the proxy device enabling data write-ban protection also includes: controlling the management device to calculate the synchronization delay time between the business traffic and the data in the scenario of business reading and writing the main database of the primary site and switching the main database, and then controlling the backup site to maintain the write-ban state according to the synchronization delay time, and performing data delay write-ban switching between the primary site and the backup site; controlling the access layer and the application layer to perform traffic error correction and Service removal, and then penetrating to the data layer to interrupt the write request by throwing an exception through SQL hit, and performing unitized normal non-local traffic write-ban.

[0014] In a second aspect, the present invention provides a disaster recovery switching data protection device, comprising: a creation module, used to create a disaster recovery switching task after configuring application access in a management device; a task formulation module, used to control the agent device to process the switching task in layers after sending the disaster recovery switching task to the agent device via a management and control channel; a task processing module, used to control the management and control channel to upload the local data generated by the agent device to the management device after the agent device completes the switching task, and control the agent device to enable data write-ban protection; a write-ban release module, used to control the management device to determine whether the write-ban release conditions are met based on local data, and if so, send a contact write-ban instruction to the agent device through the management and control channel.

[0015] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the disaster recovery switching data protection method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0016] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the disaster recovery switching data protection method of the first aspect or any corresponding embodiment thereof.

[0017] In a fifth aspect, the present invention provides a computer program product, including computer instructions, where the computer instructions are used to enable a computer to execute the disaster recovery switching data protection method of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 is a schematic diagram of a management device and an agent device according to an embodiment of the present invention;

[0020] Figure 2 is a flow chart of a method for protecting disaster recovery switching data according to an embodiment of the present invention;

[0021] Figure 3 is a flow chart of another method for protecting disaster recovery switching data according to an embodiment of the present invention;

[0022] Figure 4is a flow chart of another method for protecting disaster recovery switching data according to an embodiment of the present invention;

[0023] Figure 5 is a flow chart of another method for protecting disaster recovery switching data according to an embodiment of the present invention;

[0024] Figure 6 is a schematic diagram of data write-forbidden protection according to an embodiment of the present invention;

[0025] Figure 7 is a structural block diagram of protection of disaster recovery switching data according to an embodiment of the present invention;

[0026] Figure 8 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0028] In addition, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0029] The basic method of application disaster recovery is to establish a redundant site outside the production site. After a disaster occurs, the redundant site can take over the normal business of the user to achieve the purpose of uninterrupted business. According to the degree of protection of the disaster recovery system to the application system, it can be divided into data-level disaster recovery, application-level disaster recovery and business-level disaster recovery:

[0030] (1) Data-level disaster recovery: Only the data in the production center is copied to the disaster recovery center. When a failure occurs in the production center, only the storage system can be taken over or the data can be restored.

[0031] (2) Application-level disaster recovery: Based on data-level disaster recovery, basic replication of the production center system is added. The disaster recovery center establishes a backup environment equivalent to the local production environment, including hosts, networks, applications, IP and other resources. When a disaster occurs in the production system, the remote system can provide a fully available production environment.

[0032] (3) Business-level disaster recovery: The disaster recovery center has a complete replication of the business system. The production center and the disaster recovery center process business requests simultaneously. In the event of a failure, only business traffic needs to be switched to ensure continuous business availability.

[0033] Application multi-active technology is a basic solution for achieving business-level disaster recovery. When a business failure requires traffic switching, different multi-active architectures may produce various data inconsistency scenarios due to data synchronization and configuration delays. From the end state of the system, data accuracy represents business accuracy. When managing application multi-active architecture, it is often necessary to perform full-stack control of traffic vertical links at the access layer, application layer, and data layer. The processing of data consistency is difficult, and general businesses will adopt partial loss, post-compensation, or manual intervention methods.

[0034] According to an embodiment of the present invention, an embodiment of a method for protecting disaster recovery switching data is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0035] In this embodiment, a method for protecting disaster recovery switching data is provided. Figure 1 As shown, the architecture of the disaster recovery switch used for business traffic management between the primary site and the backup site includes a management device, an agent device and a control channel. The management device is used for rule management, task generation and task driving. The agent device is used to control layered traffic and rule parsing. The control channel is used to exchange data between the management device and the agent device. Figure 2 FIG. 1 is a flow chart of a method for protecting disaster recovery switching data according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0036] Step S1: After configuring application access in the management device, control the management device to create a disaster recovery switching task.

[0037] Alternatively, if Figure 3 As shown, the process of configuring application access in the management device and controlling the management device to create a disaster recovery switching task includes:

[0038] Step S11: Select a multi-active disaster recovery architecture based on the current application scenario.

[0039] Step S12: configure the parsing rules of the routing identifiers and the allocation rules of the routing; and deploy the integrated proxy device in layers within the application.

[0040] Step S13: configuring a new routing rule for the disaster recovery switching process, calculating the switching route difference, and generating a process template for the switching task.

[0041] Step S14: After calculating the application data delay and the write-forbidden rule, the write-forbidden rule and the process template of the switching task are issued as a disaster recovery switching task.

[0042] Specifically, refer to Figure 1 The management device is responsible for rule management, task generation and task driving, including sub-modules such as routing rule templates, routing rule calculation, data delay calculation, and task process management. The proxy device is responsible for adapting the access layer, application layer, and data layer components of the business traffic link, integrating into the node instance, and is responsible for controlling layered traffic and receiving the management and control channel, including sub-modules such as routing rule parsing, routing rule calculation, SQL parsing, and data read and write interception. The management and control channel is responsible for connecting the management device and the proxy device, assisting in the management of the proxy device instance under the site, receiving the rule push from the management device and sending it to the proxy device instance, collecting the local data of the proxy device instance and reporting it to the management device.

[0043] Step S2: After sending the disaster recovery switching task to the proxy device using the management and control channel, the proxy device is controlled to process the switching task in layers.

[0044] Specifically, using a layered proxy, the proxy device consists of an access layer, an application layer, and a data layer of a vertical link. The data layer stores all data in a database, such as Figure 4 As shown, the process of controlling the agent device to hierarchically process the switching task includes:

[0045] Step S21: After the control access layer extracts the routing label from the switching task, the routing label is forwarded to the backend service through the reverse proxy rule customized by the access layer.

[0046] Step S22: After the control application layer parses the routing label and sets it into the local processing context, it calculates and sets the attachment delivery flow identifier.

[0047] Step S23: Control the data layer proxy database driver and save the write-forbidden rule.

[0048] Specifically, the access layer, application layer, and data layer of the proxy device perform switching tasks in sequence:

[0049] (1) The access layer proxy device handles the switching task: parsing new routing rules, parsing new routing labels, setting link context routing labels, and reporting the switching completion.

[0050] (2) The application layer proxy device handles the switching task: parsing new routing rules, parsing new routing labels, transferring link context routing labels, and reporting the completion of the switching.

[0051] (3) The data layer proxy device handles the switching tasks: parsing new routing rules and saving write-blocking rules.

[0052] Step S3: After the proxy device completes the switching task, the control channel is controlled to upload the local data generated by the proxy device to the management device, and the proxy device is controlled to enable data write-ban protection.

[0053] Optionally, after the access layer, application layer and data layer of the proxy device have completed the switching task, the data layer proxy device processes the data operation, such as Figure 5 As shown, the process of controlling the proxy device to enable data write-ban protection includes:

[0054] Step S31: Control the data layer to globally prohibit writing before the full switch of rules, and intercept database reading and writing after the full switch of rules.

[0055] Step S32: After the control data layer parses the SQL and matches the write-forbidden rule, the data layer interrupts the write request by throwing an exception.

[0056] Step S33: When the business reads and writes the main database of the primary site and switches the main database, the control management device calculates the synchronization delay time of the business traffic and data, controls the backup site to maintain the write-disabled state according to the synchronization delay time, and performs data delay write-disabled switching between the primary site and the backup site.

[0057] Step S34: After controlling the access layer and the application layer to perform traffic error correction and service removal, the access layer penetrates into the data layer and interrupts the write request by throwing an exception through SQL hit, and performs unitized normal non-local traffic writing prohibition.

[0058] Specifically, refer to Figure 6 The aforementioned business traffic management can provide a reusable disaster recovery switching data protection process. In this embodiment, through scenario induction, the management device can identify different active-active architectures, define routing rule descriptions, calculate switching route differences, and minimize write-blocking time and data range. The main rules include:

[0059] (1) Data delay during master-slave switchover: In scenarios where both services read and write from the primary database, when the primary database is switched, there may be a write conflict between service traffic and data synchronization. By calculating the data synchronization delay t, the entire target site is prohibited from writing data for a period of t, and writing is allowed again after the data are equalized.

[0060] (2) Unitized normal non-local traffic write prohibition: Normal traffic protection is also divided into three layers. The access layer and application layer are mainly for traffic error correction and service removal. When penetrating into the data layer, SQL hits and throws exceptions to interrupt write requests. When a service instance cannot provide services normally due to some reasons (such as downtime, maintenance, etc.), the registration center needs to remove the instance information from the list of available services, that is, service removal.

[0061] (3) All unit switching rules are disabled before full volume: When traffic is switched, the access gateway and application nodes may have inconsistent routing rules for a short period of time. The target site will be completely disabled for about one configuration cycle.

[0062] (4) Differential write prohibition after full volume of unitized flow switching rules: The write prohibition control after full volume of rules can only prohibit the writing of migrated users.

[0063] Step S4: After the control management device recalculates the data delay and the full amount of rules based on the local data, it determines whether the write ban lifting conditions are met. If so, a write ban lifting instruction is sent to the proxy device through the control channel.

[0064] Specifically, when the rule penetrates to the data layer proxy device, the write ban is lifted; when the proxy device determines that the write ban has timed out, the current write ban is lifted.

[0065] The disaster recovery switching data protection method provided by the present invention involves two types of devices, namely a management device and an agent device. The management device and the agent device cooperate to complete the rule issuance, data writing prohibition, and writing prohibition lifting processes without human intervention, thereby improving data processing efficiency. Before data is written, the management device re-performs protection measures such as data delay and full rule calculation, thereby improving the operational efficiency of the disaster recovery switching process, reducing the occurrence of data inconsistency, and smoothly completing business traffic switching.

[0066] In this embodiment, a protection device for disaster recovery switching data is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0067] This embodiment provides a protection device for disaster recovery switching data, such as Figure 7 As shown, including:

[0068] The creation module 701 is used to create a disaster recovery switching task after configuring the application access in the management device.

[0069] The task formulation module 702 is used to send the disaster recovery switching task to the proxy device by using the management and control channel, and then control the proxy device to process the switching task in layers.

[0070] The task processing module 703 is used to control the control channel to upload the local data generated by the proxy device to the management device after the proxy device completes the switching task, and control the proxy device to enable data write-ban protection.

[0071] The write-ban release module 704 is used to control the management device to determine whether the write-ban release condition is met based on local data. If so, a write-ban release instruction is sent to the proxy device through the management and control channel.

[0072] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0073] The disaster recovery switching data protection device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0074] The embodiment of the present invention also provides a computer device having the above Figure 7 The protection device for disaster recovery switching data is shown.

[0075] See also Figure 8 , Figure 8 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 8 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 8 A processor 10 is taken as an example.

[0076] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0077] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0078] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0079] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0080] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.

[0081] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0082] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0083] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for protecting disaster recovery switching data, characterized in that: Applied to business traffic management between a primary site and a backup site, the architecture of the disaster recovery switch includes a management device, an agent device and a control channel, the management device is used for rule management, task generation and task driving, the agent device is used to control layered traffic and rule parsing, the control channel is used to exchange data between the management device and the agent device, and the method includes: After configuring application access in the management device, controlling the management device to create a disaster recovery switching task; After the disaster recovery switching task is sent to the proxy device by using the control channel, the proxy device is controlled to process the switching task in layers; When the proxy device completes the switching task, the control channel is controlled to upload the local data generated by the proxy device to the management device, and the proxy device is controlled to enable data write-forbidden protection; After controlling the management device to recalculate the data delay and the full amount of rules based on the local data, it is determined whether the write ban lifting condition is met. If so, a write ban lifting instruction is sent to the proxy device through the control channel.

2. The method according to claim 1, characterized in that: The process of configuring application access in the management device includes: Based on the current application scenarios, select a multi-active disaster recovery architecture; Configure the parsing rules for route identifiers and the allocation rules for routes; Deploy integrated agent devices in layers within applications.

3. The method according to claim 1, characterized in that The process of the management device creating a disaster recovery switching task includes: Configure new routing rules for the disaster recovery switching process, calculate the switching route difference, and generate a process template for the switching task; After calculating the application data delay and the write-forbidden rule, the write-forbidden rule and the process template of the switching task are issued as the disaster recovery switching task.

4. The method according to claim 3, characterized in that The proxy device is composed of an access layer, an application layer and a data layer of a vertical link. The data layer stores all data in a database. The process of controlling the proxy device to handle the switching task in layers includes: After controlling the access layer to extract a routing label from the switching task, forward the routing label to a backend service through a reverse proxy rule customized by the access layer; After controlling the application layer to parse the routing label and set it in the local processing context, calculate and set the attachment delivery flow identifier; Control the data layer proxy database driver and save the write-forbidden rule.

5. The method according to claim 4, characterized in that The process of controlling the proxy device to enable data write-ban protection includes: Control the data layer to globally prohibit writing before the full switch of rules, and intercept database reading and writing after the full switch of rules; After the data layer is controlled to parse the SQL and hit and match the write-forbidden rule, the data layer interrupts the write request by throwing an exception.

6. The method according to claim 4, characterized in that The process of enabling data write-forbidden protection by the proxy device also includes: Control the management device to maintain a write-forbidden state at the standby site according to the synchronization delay time after calculating the synchronization delay time of the business flow and data when the business reads and writes the main database of the main site and switches the main database, and perform data delay write-forbidden switching between the main site and the standby site; After controlling the access layer and the application layer to perform traffic error correction and Service removal, the data layer is penetrated to interrupt the write request by throwing an exception through SQL hit, and the unitized normal non-local traffic is prohibited from writing.

7. A protection device for disaster recovery switching data, characterized in that: include: A creation module is used to create a disaster recovery switching task after configuring application access in the management device; The task formulation module is used to send the disaster recovery switching task to the proxy device through the control channel, and then control the proxy device to process the switching task in layers; The task processing module is used to control the control channel to upload the local data generated by the proxy device to the management device after the proxy device completes the switching task, and control the proxy device to enable data write-ban protection; The write-ban release module is used to control the management device to determine whether the write-ban release conditions are met based on local data. If so, a contact write-ban instruction is sent to the proxy device through the management and control channel.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the disaster recovery switching data protection method according to any one of claims 1 to 6 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the disaster recovery switching data protection method according to any one of claims 1 to 6.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to enable a computer to execute the disaster recovery switching data protection method according to any one of claims 1 to 6.

Images