Hybrid disaster recovery scenario switching method and device

Abstract

The present invention provides a hybrid disaster recovery scenario switching method and device, comprising the following steps: determining a scenario type; selecting multiple target disaster recovery systems, obtaining a target operation process and each process node contained therein; establishing node dependencies; determining virtual nodes, real nodes, and the operation mode of each real node in the target operation process; obtaining a switching control table of a single disaster recovery system, determining the real nodes associated with the single-system process nodes; setting switching logic between the real nodes and the single-system process nodes based on the operation mode and operation content of the real nodes; and, in the process of executing the target operation process, switching each single-system process node to execute the operation of each real node based on the switching logic and node dependencies. By using this method, the hybrid disaster recovery scenario can reuse the results of the single disaster recovery system without repeated configuration. Based on the system scope involved in the switching drill, aggregation and integration are adopted to dynamically execute the switching drill by citing the switching process of the single disaster recovery system.

Description

Technical Field

[0001] The present invention relates to the technical field of disaster recovery switching, and in particular to a hybrid disaster recovery scenario switching method and device. Background Art

[0002] After completing disaster recovery deployment for application systems, the financial industry often organizes single-disaster recovery system "island" disaster recovery switchover drills or production-based drills to ensure the availability of the disaster recovery environment. Following these single-disaster recovery system drills, commercial banks, in accordance with external regulatory requirements, systematically conduct hybrid disaster recovery scenario drills. Due to the limited timeframe for switchover drills, the scope of systems involved varies from one drill to another, typically encompassing multiple systems of various types. Furthermore, given the significant uncertainty inherent in production environment disasters faced by commercial banks, if a switchover plan needs to be redeveloped for each disaster recovery drill or switchover, the results of single-disaster recovery system switchover drills cannot be effectively leveraged. This would increase the workload exponentially and increase the likelihood of errors during switchover drills. Summary of the Invention

[0003] In view of this, the present invention provides a hybrid disaster recovery scenario switching method. Through this method, the hybrid disaster recovery scenario can reuse the results of a single disaster recovery system without repeated configuration. According to the system scope involved in the switching drill, aggregation and integration are adopted, and the switching process of the single disaster recovery system is referenced to dynamically execute the switching drill.

[0004] The present invention also provides a hybrid disaster recovery scenario switching device to ensure the implementation and application of the above method in practice.

[0005] A hybrid disaster recovery scenario switching method includes:

[0006] When a scenario drill simulating a hybrid disaster recovery scenario is required, determining the scenario type of the hybrid disaster recovery scenario;

[0007] Based on the scenario type, selecting multiple target disaster recovery systems corresponding to the hybrid disaster recovery scenario;

[0008] Obtaining a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process;

[0009] Determining the operation content of each process node in each of the target operation processes, and building a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node;

[0010] Determine a virtual node in each target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node, wherein the virtual node is used to manage real nodes of the same operation mode, and the real node is a process node in the target operation process that needs to be switched to a single-system operation process corresponding to a single disaster recovery system, and the operation mode includes an aggregation mode, an integration mode, and a new addition mode;

[0011] Obtaining a switching control table of the single disaster recovery system, and determining, based on the switching control table, a real node associated with each single system process node in the single system operation process;

[0012] Based on the operation mode and operation content of each real node, setting the switching logic between each real node and its associated single system process node;

[0013] Starting each of the target operation processes to simulate the hybrid disaster recovery scenario;

[0014] In the process of executing each of the target operation processes, based on the switching logic between each of the real nodes and its associated single-system process nodes and the node dependencies between each of the target disaster recovery systems, each of the single-system process nodes in the single-system operation process is switched to execute the operations of each of the real nodes in the target operation process.

[0015] In the above method, optionally, the scenario types include: planned drill, planned switch, and unplanned switch, and the method further includes:

[0016] Based on the scenario type, data services corresponding to the scenario type in the hybrid disaster recovery scenario are suspended.

[0017] In the above method, optionally, each of the real nodes includes: a process node for executing a stop of a production-side application, a process node for executing a network switching integration, a process node for executing a database switching, a process node for executing a storage switching, a process node for executing a start of a disaster recovery-side application, and a process node for executing a security whitelist control;

[0018] Among them, when any real node is any one of the process nodes for executing the stop of the production-end application, the process node for executing the database switch, the process node for executing the memory switch, and the process node for executing the start of the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when any real node is the process node for executing the network integration switch, the operation mode of the real node is the integration mode; when any real node is the process node for executing the security whitelist control, the operation mode of the real node is the new addition mode.

[0019] Optionally, the above method includes executing a process node for stopping a production-side application to release node dependencies between the target disaster recovery systems and stop production-side applications in the production side of the target disaster recovery systems.

[0020] The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management range, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management range; generate a firewall activation instruction corresponding to the integrated address, so that each target disaster recovery system corresponding to the integrated address is integrated into the same firewall;

[0021] The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode;

[0022] The process node for executing memory switching is used to switch the memory storing the file from a read-only mode to a writable mode;

[0023] The process node for executing and starting the disaster recovery end application is used to release the node dependencies between the target disaster recovery systems, determine the execution order between the target disaster recovery systems based on the node dependencies between the target disaster recovery systems, and start the disaster recovery end application of the disaster recovery end in each target disaster recovery system in sequence according to the execution order;

[0024] The process node that executes security whitelist control is used to apply the preset transaction service whitelist to verify the availability of each disaster recovery end; when there is any target disaster recovery system that needs to add a new process node, the preset release system verification whitelist is applied to verify the feasibility of the process node to be added.

[0025] The above method may optionally further include, before starting each target operation process to simulate the hybrid disaster recovery scenario:

[0026] Based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process, a system channel is constructed between each target disaster recovery system and the single disaster recovery system.

[0027] A hybrid disaster recovery scenario switching device, comprising:

[0028] A first determining unit is configured to determine a scenario type of a hybrid disaster recovery scenario when a scenario drill simulating a hybrid disaster recovery scenario is required;

[0029] A selection unit, configured to select a plurality of target disaster recovery systems corresponding to the hybrid disaster recovery scenario based on the scenario type;

[0030] A first acquisition unit is configured to acquire a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process;

[0031] A first construction unit is configured to determine the operation content of each process node in each of the target operation processes, and to construct a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node;

[0032] A second determining unit is configured to determine a virtual node in each target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node, wherein the virtual node is used to manage real nodes of the same operation mode, the real node is a process node in the target operation process that needs to be switched to a single-system operation process corresponding to a single disaster recovery system, and the operation mode includes an aggregation mode, an integration mode, and a new addition mode;

[0033] a second acquiring unit, configured to acquire a switching control table of the single disaster recovery system, and determine, based on the switching control table, a single system process node associated with each of the real nodes in the single system operation process;

[0034] A setting unit, configured to set a switching logic between each of the real nodes and its associated single-system process node based on an operation mode and operation content of each of the real nodes;

[0035] A starting unit, configured to start each of the target operation processes to simulate the hybrid disaster recovery scenario;

[0036] A switching unit is used to switch each single-system process node in the single-system operation process to execute the operation of each real node in the target operation process based on the switching logic between each real node and its associated single-system process node and the node dependency relationship between each target disaster recovery system during the execution of each target operation process.

[0037] Optionally, the above-mentioned device may include the following scenario types: planned drill, planned switching, and unplanned switching. The device may further include:

[0038] A pausing unit is configured to suspend, based on the scenario type, a data service corresponding to the scenario type in the hybrid disaster recovery scenario.

[0039] Optionally, the real nodes of the above-mentioned device include: a process node for executing a stop of a production-side application, a process node for executing a network switching integration, a process node for executing a database switching, a process node for executing a storage switching, a process node for executing a start of a disaster recovery-side application, and a process node for executing a security whitelist control;

[0040] Among them, when the operation content of any real node represents that the real node is a process node that executes stopping the production-end application, a process node that executes database switching, a process node that executes memory switching, or a process node that executes starting the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when the operation content of any real node represents that the real node is a process node that executes network integration switching, the operation mode of the real node is the integration mode; when the operation content of any real node represents that the real node is a process node that executes security whitelist control, the operation mode of the real node is the new addition mode.

[0041] The above-mentioned device, optionally, the process node for executing the stop of the production-side application is used to release the node dependency between each of the target disaster recovery systems and stop the production-side application of the production side in each of the target disaster recovery systems;

[0042] The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management range, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management range; generate a firewall activation instruction corresponding to the integrated address, so that each target disaster recovery system corresponding to the integrated address is integrated into the same firewall;

[0043] The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode;

[0044] The process node for executing memory switching is used to switch the memory storing the file from a read-only mode to a writable mode;

[0045] The process node for executing and starting the disaster recovery end application is used to release the node dependencies between the target disaster recovery systems, determine the execution order between the target disaster recovery systems based on the node dependencies between the target disaster recovery systems, and start the disaster recovery end application of the disaster recovery end in each target disaster recovery system in sequence according to the execution order;

[0046] The process node that executes security whitelist control is used to apply the preset transaction service whitelist to verify the availability of each disaster recovery end; when there is any target disaster recovery system that needs to add a new process node, the preset release system verification whitelist is applied to verify the feasibility of the process node to be added.

[0047] The above device may optionally further include:

[0048] The second construction unit is configured to construct a system channel between each target disaster recovery system and the single disaster recovery system based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process.

[0049] A storage medium includes stored instructions, wherein when the instructions are executed, the device where the storage medium is located is controlled to execute the above-mentioned hybrid disaster recovery scenario switching method.

[0050] An electronic device includes a memory and one or more instructions, wherein the one or more instructions are stored in the memory and configured to be executed by one or more processors to perform the above-mentioned hybrid disaster recovery scenario switching method.

[0051] Compared with the prior art, the present invention has the following advantages:

[0052] The present invention provides a hybrid disaster recovery scenario switching method, comprising: when a simulated hybrid disaster recovery scenario drill is required, determining a scenario type; selecting multiple target disaster recovery systems corresponding to the hybrid disaster recovery scenario; obtaining a target operation process corresponding to each target disaster recovery system and each process node contained in each target operation process; constructing a node dependency relationship based on the operation content of the process node; determining virtual nodes, real nodes, and the operation mode of each real node in the target operation process; obtaining a switching control table of a single disaster recovery system, determining the real node associated with each single system process node; setting a switching logic between each real node and its associated single system process node based on the operation mode and operation content of each real node; and in the process of executing each target operation process, switching each single system process node in the single system operation process to execute the operation of the real node in each target operation process based on the switching logic between each real node and its associated single system process node and the node dependency relationship between each target disaster recovery system. By applying the method provided by the present invention, the hybrid disaster recovery scenario can reuse the results of the single disaster recovery system without repeated configuration. According to the system scope involved in the switching drill, the switching process of the single disaster recovery system is referenced by aggregation and integration, so that the switching drill can be dynamically executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0054] Figure 1 A method flow chart of a hybrid disaster recovery scenario switching method provided by an embodiment of the present invention;

[0055] Figure 2 A schematic diagram of the switching relationship between a hybrid disaster recovery scenario and a single disaster recovery system provided by an embodiment of the present invention;

[0056] Figure 3 A diagram showing the structure of a hybrid disaster recovery scenario switching device provided by an embodiment of the present invention;

[0057] Figure 4 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0058] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only 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 ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0059] In this application, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. The terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article or apparatus comprising the element.

[0060] The present invention can be used in a variety of general-purpose or special-purpose computing device environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multi-processor devices, and distributed computing environments including any of the above.

[0061] The embodiment of the present invention provides a hybrid disaster recovery scenario switching method, which can be applied to various system platforms. The execution subject can be a computer terminal or a processor of various mobile devices. The method flow chart of the method is as follows: Figure 1 As shown, specifically including:

[0062] S101: When a scenario drill simulating a hybrid disaster recovery scenario is required, a scenario type of the hybrid disaster recovery scenario is determined.

[0063] It should be noted that hybrid disaster recovery scenarios include planned drills, planned switchovers, and unplanned switchovers. A planned drill involves switching the data replication relationship between the disaster recovery and production environments according to a pre-defined plan, isolating the disaster recovery environment from the production environment. A planned switchover involves switching production operations from the production environment to the disaster recovery environment according to a pre-defined plan. An unplanned switchover occurs without a pre-defined plan and is typically performed in the event of a production failure.

[0064] S102: Based on the scenario type, select multiple target disaster recovery systems corresponding to the hybrid disaster recovery scenario.

[0065] It should be noted that, according to the requirements of the scenario type of the hybrid disaster recovery scenario, multiple target disaster recovery systems are selected to implement the simulated hybrid disaster recovery scenario.

[0066] S103: Acquire the target operation process corresponding to each target disaster recovery system and each process node included in each target operation process.

[0067] It should be noted that the operation process of the disaster recovery system in the hybrid disaster recovery scenario meets the standardized design of the hybrid scenario switching process data entity shown in Table 1:

[0068]

[0069] Table 1

[0070] S104: Determine the operation content of each process node in each of the target operation processes, and build a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node.

[0071] In the present invention, when multiple process nodes in multiple target operating systems have the same operational content, a node dependency relationship is established between the multiple process nodes. For example, if target operation process A contains process node A, and target operation process B also contains process node A, a node dependency relationship is established between target operation process A and target operation process B.

[0072] S105: Determine each virtual node in the target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node.

[0073] The virtual nodes are used to manage real nodes in the same operating mode. These real nodes are process nodes in the target operating process that require switching operations with the single-system operating process corresponding to a single disaster recovery system. The operating modes include aggregation, integration, and addition. Each target disaster recovery system includes a production end and a disaster recovery end, and communication between the production end and the disaster recovery end is carried out through a firewall.

[0074] In the present invention, the target operation process includes multiple process nodes, and the node types of each process node include ordinary nodes, real nodes, and virtual nodes. In obtaining the target operation process corresponding to each target disaster recovery system, the real nodes and virtual nodes in each target operation process can be determined based on the node sequence number or the operation content of the process node.

[0075] Specifically, each real node includes: a process node for executing a stop of a production application, a process node for executing a network switch integration, a process node for executing a database switch, a process node for executing a storage switch, a process node for executing a start of a disaster recovery application, and a process node for executing a security whitelist control;

[0076] Among them, when any real node is any one of the process nodes for executing the stop of the production-end application, the process node for executing the database switch, the process node for executing the memory switch, and the process node for executing the start of the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when any real node is the process node for executing the network integration switch, the operation mode of the real node is the integration mode; when any real node is the process node for executing the security whitelist control, the operation mode of the real node is the new addition mode.

[0077] It should also be noted that since virtual nodes are used to manage real nodes of the same operation mode, based on the above-mentioned real nodes, the virtual nodes in each target operation process include: process nodes for managing the execution of stopping production-end applications, process nodes for executing database switching, process nodes for executing storage switching, and process node aggregation virtual nodes for executing the startup of disaster recovery-end applications, integrated virtual nodes for managing process nodes for executing network switching integration, and newly added virtual nodes for managing process nodes for executing security whitelist control.

[0078] Furthermore, the process node for executing the shutdown of production-side applications is used to release node dependencies between the target disaster recovery systems and to shut down production-side applications in the target disaster recovery systems. In the present invention, for operational safety, the order in which production-side applications are shut down is determined based on predefined node dependencies between applications that are shut down between systems. The shutdown channel of a single production application system is then reused to issue a switching instruction. This node step is configured as an aggregated process, referencing data constraints for dependencies between multiple systems.

[0079] The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management scope, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management scope; generate a firewall activation instruction corresponding to the integrated address, so that each target disaster recovery system corresponding to the integrated address is integrated into the same firewall. In the present invention, based on the network switching instructions of a single system, the instructions issued to the firewall are integrated according to the network address of the disaster recovery application system and the management scope of the firewall, according to the address integration strategy. The network instructions originally issued according to the single system are integrated into those issued according to the firewall as the target object. This node step is set as an integration method, adopting a multi-system execution action integration design. For example, activating a firewall. Activating a firewall for a single system involves the relationship between the address involved in activating the system and external network access. Activating firewalls for multiple systems, however, does not simply aggregate the activation firewalls of the individual systems, but rather requires merging the addresses and splitting them according to the network mask before generating the firewall activation instruction.

[0080] The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode. In the present invention, because the disaster recovery database is normally in disaster recovery mode, the database is in read-only mode. Therefore, it is necessary to switch to production mode and change the database to writable mode. In mixed scenarios, the channels and instructions for single-system switching can be called in parallel. This node step is set to an aggregated mode, and does not require reference to the dependency data constraints between multiple systems.

[0081] The process node for executing memory switching is used to switch the memory for storing files from read-only mode to writable mode. In the present invention, some file-type business data is written from production to disaster recovery end through "mirror storage". In order to ensure business continuity, this part of data also needs to be switched. The switching of mirror storage is somewhat similar to the switching of databases, both of which change the storage of the disaster recovery end from read-only mode to writable mode. This node step is set to an aggregation mode, and there is no need to reference the dependency data constraints between multiple systems.

[0082] The process node for executing and starting the disaster recovery end application is used to release the node dependencies between each of the target disaster recovery systems, determine the execution order between each of the target disaster recovery systems based on the node dependencies between each of the target disaster recovery systems, and start the disaster recovery end application of each of the target disaster recovery systems in turn according to the execution order. In the present invention, after the preparation work is completed, the disaster recovery end application is started. Before starting, the startup order of the disaster recovery end application is determined based on the predefined application startup dependency between systems, and then the channel for starting the disaster recovery end application system of a single system is reused, and a switching instruction is issued. The node step merging method is an aggregation method, which requires referencing the dependency data constraints between multiple systems.

[0083] The process node that executes the security whitelist control is used to apply the preset transaction service whitelist to check the availability of each of the disaster recovery ends; when there is any target disaster recovery system that needs to add a new process node, the preset released system verification whitelist is applied to verify the feasibility of the process node to be added. In the present invention, before providing services to customers, it is necessary to complete the verification of the availability of the disaster recovery end application. Therefore, it is necessary to select a security control strategy to provide a transaction service whitelist and a whitelist that releases the system verification range to verify the availability of the main system. For the transaction service whitelist, it is to require each component to open the type of transaction to ensure system security, and the node step is set to the aggregation mode. For the whitelist that releases the system verification range, it is to require the access relationship between components to be released. The node step can be set to the new addition mode, and a new execution action needs to be added. If both exist, the copy node method can be adopted, one is set to aggregation, and the other is set to addition.

[0084] S106: Obtain a switching control table of the single disaster recovery system, and determine a real node associated with each single system process node in the single system operation process based on the switching control table.

[0085] In the present invention, in order to enable the hybrid disaster recovery switching scenario to reuse the single system process, a standardized design is performed on the data entity of the single system switching. The switching control table shown in Table 2 below is obtained through the standardized design:

[0086]

[0087]

[0088] Table 2

[0089] It should be noted that a single-system process node can be associated with a real node in multiple target operation processes. The operations and order of these associated single-system process nodes and real nodes are consistent. For example, in multiple target disaster recovery systems, if the operation processes corresponding to System A, System B, and System C all contain a real node with node number 3, and the single-system operation process also contains a single-system process node with node number 3, then the single-system process node with node number 3 is associated with each real node with node number 3.

[0090] S107: Based on the operation mode and operation content of each real node, setting the switching logic between each real node and its associated single-system process node.

[0091] It should be noted that different switching logics are used for real nodes with different operation modes and contents. For example, switching between nodes can be performed by building channels or by using instructions.

[0092] S108: Start each of the target operation processes to simulate the hybrid disaster recovery scenario.

[0093] S109: In the process of executing each of the target operation processes, based on the switching logic between each of the real nodes and its associated single-system process nodes and the node dependency between each of the target disaster recovery systems, each of the single-system process nodes in the single-system operation process is switched to execute the operation of each of the real nodes in the target operation process.

[0094] In the present invention, in the process of executing each target operation process, each process node in each target operation process is executed in sequence according to the node order. If the currently executed process node is a real node, according to the switching logic between the real node and the single-system process node associated with it, as well as other real nodes that have a dependent relationship with the real node, the single-system process node in the single-system operation process is switched to replace the operation of the executing real node.

[0095] For example, when executing the target operation process, the operation reaches the process node for executing and starting the disaster recovery end application. Since the process node is a real node, the operation of executing the real node is replaced by the single system process node for executing and starting the disaster recovery end application in the single disaster recovery system.

[0096] It should be noted that each real node in each target operation process includes: a process node for executing the stop of production-side applications, a process node for executing network switching integration, a process node for executing database switching, a process node for executing storage switching, a process node for executing the start of disaster recovery-side applications, and a process node for executing security whitelist control; each single-system process node in a single-system operation process corresponding to a single disaster recovery system also includes: a process node for executing the stop of production-side applications, a process node for executing network switching integration, a process node for executing database switching, a process node for executing storage switching, a process node for executing the start of disaster recovery-side applications, and a process node for executing security whitelist control. Figure 2 As shown, Figure 2 The figure below shows the switching relationship between a hybrid disaster recovery scenario and a single disaster recovery system. In the hybrid disaster recovery scenario, process nodes numbered 3 to 8 are real nodes, and each real node is associated with process nodes numbered 3 to 8 in the single disaster recovery system.

[0097] In the method provided by the embodiment of the present invention, when a scenario drill simulating a hybrid disaster recovery scenario is required, the scenario type is determined, and multiple target disaster recovery systems are selected based on the scenario type. The target operation process of each target disaster recovery system and each process node in the process are obtained, and the node dependency relationship between each target disaster recovery system is constructed based on the operation content of each process node. The virtual node, real node and the operation mode of each world single are determined in each process node. According to the switching control of the single disaster recovery system, the real node associated with each single system process node is determined, and then based on the operation mode and operation content of the real node, the switching logic between the single system process node and the real node with which the facility has an associated relationship is established. Each target operation process is started, and in the process of executing each target operation process, if a certain real node is executed, then according to the switching logic and the node dependency relationship, the operation of the real node is replaced by the single system process node.

[0098] By applying the method provided in the embodiment of the present invention, a hybrid disaster recovery scenario can reuse the results of a single disaster recovery system without repeated configuration. According to the system scope involved in the switching drill, aggregation and integration are adopted, and the switching process of a single disaster recovery system is referenced to dynamically execute the switching drill.

[0099] In the method provided by the embodiment of the present invention, before starting each target operation process to simulate the hybrid disaster recovery scenario, the method further includes:

[0100] Based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process, a system channel is constructed between each target disaster recovery system and the single disaster recovery system.

[0101] It is understandable that after the system channel is constructed, switching between nodes can be achieved through the system channel during the execution of each target operation process.

[0102] The specific implementation processes and derivative methods of the above-mentioned embodiments are all within the protection scope of the present invention.

[0103] and Figure 1 Corresponding to the above method, the embodiment of the present invention further provides a hybrid disaster recovery scene switching device for Figure 1 The specific implementation of the method in the embodiment of the present invention is that the hybrid disaster recovery scene switching device provided by the embodiment of the present invention can be applied to computer terminals or various mobile devices, and its structural diagram is as follows: Figure 3 As shown, specifically including:

[0104] The first determining unit 301 is configured to determine the scenario type of the hybrid disaster recovery scenario when a scenario drill simulating a hybrid disaster recovery scenario is required;

[0105] A selection unit 302 is configured to select a plurality of target disaster recovery systems corresponding to the hybrid disaster recovery scenario based on the scenario type;

[0106] The first acquisition unit 303 is configured to acquire a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process;

[0107] A first constructing unit 304 is configured to determine the operation content of each process node in each target operation process, and construct a node dependency relationship between each target disaster recovery system based on the operation content of each process node;

[0108] A second determining unit 305 is configured to determine a virtual node in each target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node, wherein the virtual node is used to manage real nodes of the same operation mode, and the real node is a process node in the target operation process that needs to be switched to a single-system operation process corresponding to a single disaster recovery system. The operation modes include aggregation mode, integration mode, and addition mode.

[0109] A second obtaining unit 306 is configured to obtain a switching control table of the single disaster recovery system, and determine, based on the switching control table, a single system process node associated with each of the real nodes in the single system operation process;

[0110] A setting unit 307, configured to set a switching logic between each of the real nodes and its associated single-system process node based on the operation mode and operation content of each of the real nodes;

[0111] A starting unit 308 is configured to start each target operation process to simulate the hybrid disaster recovery scenario;

[0112] The switching unit 309 is used to switch each single-system process node in the single-system operation process to execute the operation of each real node in the target operation process based on the switching logic between each real node and its associated single-system process node and the node dependency relationship between each target disaster recovery system during the execution of each target operation process.

[0113] In the device provided by the embodiment of the present invention, when a scenario drill simulating a hybrid disaster recovery scenario is required, the scenario type is determined, and multiple target disaster recovery systems are selected based on the scenario type. The target operation process of each target disaster recovery system and each process node in the process are obtained, and the node dependency relationship between each target disaster recovery system is constructed based on the operation content of each process node. The virtual node, real node and the operation mode of each world single are determined in each process node. According to the switching control of the single disaster recovery system, the real node associated with each single system process node is determined, and then based on the operation mode and operation content of the real node, the switching logic between the single system process node and the real node with which the facility has an associated relationship is established. Each target operation process is started, and in the process of executing each target operation process, if a certain real node is executed, then according to the switching logic and the node dependency relationship, the operation of the real node is replaced by the single system process node.

[0114] By applying the device provided by the embodiment of the present invention, the hybrid disaster recovery scenario can reuse the results of a single disaster recovery system without repeated configuration. According to the system scope involved in the switching drill, aggregation and integration are adopted, and the switching process of the single disaster recovery system is referenced to dynamically execute the switching drill.

[0115] In the apparatus provided in the embodiment of the present invention, the scenario types include: planned drill, planned switch, and unplanned switch, and the apparatus further includes:

[0116] A pausing unit is configured to suspend, based on the scenario type, a data service corresponding to the scenario type in the hybrid disaster recovery scenario.

[0117] In the device provided by the embodiment of the present invention, each real node includes: a process node for executing stopping production-side applications, a process node for executing network switching integration, a process node for executing database switching, a process node for executing storage switching, a process node for executing starting disaster recovery-side applications, and a process node for executing security whitelist control;

[0118] Among them, when the operation content of any real node represents that the real node is a process node that executes stopping the production-end application, a process node that executes database switching, a process node that executes memory switching, or a process node that executes starting the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when the operation content of any real node represents that the real node is a process node that executes network integration switching, the operation mode of the real node is the integration mode; when the operation content of any real node represents that the real node is a process node that executes security whitelist control, the operation mode of the real node is the new addition mode.

[0119] In the device provided by the embodiment of the present invention, the process node for executing the stop of the production-side application is used to release the node dependency between each of the target disaster recovery systems and stop the production-side application of the production side in each of the target disaster recovery systems;

[0120] The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management range, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management range; generate a firewall activation instruction corresponding to the integrated address, so that each target disaster recovery system corresponding to the integrated address is integrated into the same firewall;

[0121] The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode;

[0122] The process node for executing memory switching is used to switch the memory storing the file from a read-only mode to a writable mode;

[0123] The process node for executing and starting the disaster recovery end application is used to release the node dependencies between the target disaster recovery systems, determine the execution order between the target disaster recovery systems based on the node dependencies between the target disaster recovery systems, and start the disaster recovery end application of the disaster recovery end in each target disaster recovery system in sequence according to the execution order;

[0124] The process node that executes security whitelist control is used to apply the preset transaction service whitelist to verify the availability of each disaster recovery end; when there is any target disaster recovery system that needs to add a new process node, the preset release system verification whitelist is applied to verify the feasibility of the process node to be added.

[0125] The device provided in the embodiment of the present invention further includes:

[0126] The second construction unit is configured to construct a system channel between each target disaster recovery system and the single disaster recovery system based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process.

[0127] The specific working process of each unit and sub-unit in the hybrid disaster recovery scenario switching device disclosed in the above embodiment of the present invention can refer to the corresponding content in the hybrid disaster recovery scenario switching method disclosed in the above embodiment of the present invention, and will not be repeated here.

[0128] An embodiment of the present invention further provides a storage medium, which includes stored instructions. When the instructions are executed, the device where the storage medium is located is controlled to execute the above-mentioned hybrid disaster recovery scenario switching method.

[0129] The embodiment of the present invention further provides an electronic device, the structural diagram of which is shown in FIG. Figure 4 As shown, the system specifically includes a memory 401 and one or more instructions 402, wherein the one or more instructions 402 are stored in the memory 401 and are configured to be executed by one or more processors 403 to perform the following operations:

[0130] When a scenario drill simulating a hybrid disaster recovery scenario is required, determining the scenario type of the hybrid disaster recovery scenario;

[0131] Based on the scenario type, selecting multiple target disaster recovery systems corresponding to the hybrid disaster recovery scenario;

[0132] Obtaining a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process;

[0133] Determining the operation content of each process node in each of the target operation processes, and building a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node;

[0134] Determine a virtual node in each target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node, wherein the virtual node is used to manage real nodes of the same operation mode, and the real node is a process node in the target operation process that needs to be switched to a single-system operation process corresponding to a single disaster recovery system, and the operation mode includes an aggregation mode, an integration mode, and a new addition mode;

[0135] Obtaining a switching control table of the single disaster recovery system, and determining, based on the switching control table, a real node associated with each single system process node in the single system operation process;

[0136] Based on the operation mode and operation content of each real node, setting the switching logic between each real node and its associated single system process node;

[0137] Starting each of the target operation processes to simulate the hybrid disaster recovery scenario;

[0138] In the process of executing each of the target operation processes, based on the switching logic between each of the real nodes and its associated single-system process nodes and the node dependencies between each of the target disaster recovery systems, each of the single-system process nodes in the single-system operation process is switched to execute the operations of each of the real nodes in the target operation process.

[0139] Each embodiment in this specification is described in a progressive manner. The same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple. For relevant parts, refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without expending creative work.

[0140] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein may be implemented by electronic hardware, computer software, or a combination of both.

[0141] To clearly illustrate the interchangeability of hardware and software, the above descriptions have generally described the components and steps of each example by function. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of the present invention.

[0142] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A hybrid disaster recovery scenario switching method, characterized in that: include: When a scenario drill simulating a hybrid disaster recovery scenario is required, determining the scenario type of the hybrid disaster recovery scenario; Based on the scenario type, selecting multiple target disaster recovery systems corresponding to the hybrid disaster recovery scenario; Obtaining a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process; Determining the operation content of each process node in each of the target operation processes, and building a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node; Determine each virtual node in the target operation process, at least one real node corresponding to each virtual node, and an operation mode of each real node, wherein the virtual node is used to manage real nodes of the same operation mode, and the real node is a process node in the target operation process that needs to be switched with the single-system operation process corresponding to the single disaster recovery system, and the operation mode includes an aggregation mode, an integration mode, and a new addition mode; each of the real nodes includes: a process node for executing the stop of the production-end application, a process node for executing the network switching integration, a process node for executing the database switching, a process node for executing the memory switching, a process node for executing the startup of the disaster recovery-end application, and a process node for executing the security whitelist control; wherein, when any real node is any one of the process node for executing the stop of the production-end application, the process node for executing the database switching, the process node for executing the memory switching, and the process node for executing the startup of the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when any real node is a process node for executing the network integration switching, the operation mode of the real node is the integration mode; when any real node is a process node for executing the security whitelist control, the operation mode of the real node is the new addition mode; Obtaining a switching control table of the single disaster recovery system, and determining, based on the switching control table, a real node associated with each single system process node in the single system operation process; Based on the operation mode and operation content of each real node, setting the switching logic between each real node and its associated single system process node; Starting each of the target operation processes to simulate the hybrid disaster recovery scenario; In the process of executing each of the target operation processes, based on the switching logic between each of the real nodes and its associated single-system process nodes and the node dependencies between each of the target disaster recovery systems, each of the single-system process nodes in the single-system operation process is switched to execute the operations of each of the real nodes in the target operation process.

2. The method according to claim 1, characterized in that The scenario types include: planned drill, planned switch, and unplanned switch. The method further includes: Based on the scenario type, data services corresponding to the scenario type in the hybrid disaster recovery scenario are suspended.

3. The method according to claim 1, characterized in that The process node for executing the stop of the production-side application is used to release the node dependencies between the target disaster recovery systems and stop the production-side application of the production side in each target disaster recovery system; The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management range, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management range; Generate a firewall activation instruction corresponding to the integration address, so that each target disaster recovery system corresponding to the integration address is integrated into the same firewall; The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode; The process node for executing memory switching is used to switch the memory storing the file from a read-only mode to a writable mode; The process node for executing and starting the disaster recovery end application is used to release the node dependencies between the target disaster recovery systems, determine the execution order between the target disaster recovery systems based on the node dependencies between the target disaster recovery systems, and start the disaster recovery end application of the disaster recovery end in each target disaster recovery system in sequence according to the execution order; The process node that executes security whitelist control is used to apply the preset transaction service whitelist to verify the availability of each disaster recovery end; when there is any target disaster recovery system that needs to add a new process node, the preset release system verification whitelist is applied to verify the feasibility of the process node to be added.

4. The method according to any one of claims 1 to 3, characterized in that Before starting each of the target operation processes to simulate the hybrid disaster recovery scenario, the method further includes: Based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process, a system channel is constructed between each target disaster recovery system and the single disaster recovery system.

5. A hybrid disaster recovery scenario switching device, characterized in that: include: A first determining unit is configured to determine a scenario type of a hybrid disaster recovery scenario when a scenario drill simulating a hybrid disaster recovery scenario is required; A selection unit, configured to select a plurality of target disaster recovery systems corresponding to the hybrid disaster recovery scenario based on the scenario type; A first acquisition unit is configured to acquire a target operation process corresponding to each target disaster recovery system and each process node included in each target operation process; A first construction unit is configured to determine the operation content of each process node in each of the target operation processes, and to construct a node dependency relationship between each of the target disaster recovery systems based on the operation content of each process node; The second determination unit is used to determine the virtual nodes in each of the target operation processes, at least one real node corresponding to each virtual node, and the operation mode of each of the real nodes, wherein the virtual nodes are used to manage real nodes of the same operation mode, and the real nodes are process nodes in the target operation process that need to be switched with the single-system operation process corresponding to the single disaster recovery system, and the operation modes include aggregation mode, integration mode, and new addition mode; each of the real nodes includes: a process node for executing the stop of the production-end application, a process node for executing the network switching integration, a process node for executing the database switching, a process node for executing the memory switching, a process node for executing the startup of the disaster recovery-end application, and a process node for executing the security whitelist control; wherein, when any real node is any one of the process node for executing the stop of the production-end application, the process node for executing the database switching, the process node for executing the memory switching, and the process node for executing the startup of the disaster recovery-end application, the operation mode of the real node is the aggregation mode; when any real node is a process node for executing the network integration switching, the operation mode of the real node is the integration mode; when any real node is a process node for executing the security whitelist control, the operation mode of the real node is the new addition mode; a second acquiring unit, configured to acquire a switching control table of the single disaster recovery system, and determine, based on the switching control table, a single system process node associated with each of the real nodes in the single system operation process; A setting unit, configured to set a switching logic between each of the real nodes and its associated single-system process node based on an operation mode and operation content of each of the real nodes; A starting unit, configured to start each of the target operation processes to simulate the hybrid disaster recovery scenario; A switching unit is used to switch each single-system process node in the single-system operation process to execute the operation of each real node in the target operation process based on the switching logic between each real node and its associated single-system process node and the node dependency relationship between each target disaster recovery system during the execution of each target operation process.

6. The device according to claim 5, characterized in that The scenario types include: planned drill, planned switch and unplanned switch, and the device further includes: A pausing unit is configured to suspend, based on the scenario type, a data service corresponding to the scenario type in the hybrid disaster recovery scenario.

7. The device according to claim 5, characterized in that The process node for executing the stop of the production-side application is used to release the node dependencies between the target disaster recovery systems and stop the production-side application of the production side in each target disaster recovery system; The process node for executing network switching integration is used to obtain the network address of each target disaster recovery system, merge the network addresses belonging to the same firewall management range, and apply a preset network mask to split them to obtain an integrated address belonging to the same firewall management range; Generate a firewall activation instruction corresponding to the integration address, so that each target disaster recovery system corresponding to the integration address is integrated into the same firewall; The process node for executing database switching is used to switch the database storing data from read-only mode to writable mode; The process node for executing memory switching is used to switch the memory storing the file from a read-only mode to a writable mode; The process node for executing and starting the disaster recovery end application is used to release the node dependencies between the target disaster recovery systems, determine the execution order between the target disaster recovery systems based on the node dependencies between the target disaster recovery systems, and start the disaster recovery end application of the disaster recovery end in each target disaster recovery system in sequence according to the execution order; The process node that executes security whitelist control is used to apply the preset transaction service whitelist to verify the availability of each disaster recovery end; when there is any target disaster recovery system that needs to add a new process node, the preset release system verification whitelist is applied to verify the feasibility of the process node to be added.

8. The device according to any one of claims 5 to 7, characterized in that: Also includes: The second construction unit is configured to construct a system channel between each target disaster recovery system and the single disaster recovery system based on the association relationship between each real node in each target operation process and each single system process node in the single system operation process.

Images