Data Tripartite Disaster Tolerance Abnormality Monitoring and Processing Method, System, Terminal and Storage Medium

Abstract

The present invention relates to the technical field of data disaster recovery, and specifically provides a method, system, terminal and storage medium for monitoring and processing data three-party disaster recovery anomalies, including: monitoring the online status and communication status of three-party sites; judging whether there are anomalies in the three-party sites during the synchronous start and stop process of changing volume snapshots according to the online status and communication status of the three-party sites: if so, skip the start and stop operations of the abnormal snapshots. Through anomaly handling, the present invention can ensure the normal operation of the strategy before the ring 3DC failure scenario is switched, and the normal disaster recovery of data, avoiding the problem that the strategy cannot be executed or io timeout occurs before the failure scenario response due to the occurrence of an abnormal scenario.

Description

Technical Field

[0001] The present invention relates to the technical field of data disaster recovery, and particularly to a method, a system, a terminal and a storage medium for monitoring and processing data three-party disaster recovery anomalies. Background Art

[0002] The existing ring two-site three-center (ring 3DC) realizes data backup by managing three sites through a third-party disaster recovery management software. During the implementation process, message passing is required between sites. When the volume corresponding to a certain site is offline (the primary volume in the remote replication relationship is offline, the secondary volume is offline, the changed volume is offline), and the link between sites fails but does not reach the failover condition, it needs to be treated as an abnormal scenario to meet the business requirements issued by the host. Once an abnormal scenario occurs, it will lead to problems such as policy execution failure and data transmission timeout. Summary of the Invention

[0003] Aiming at the problem that the abnormal scenario in the prior art cannot be effectively processed, resulting in data transmission timeout, the present invention provides a method, a system, a terminal and a storage medium for monitoring and processing data three-party disaster recovery anomalies to solve the above technical problems.

[0004] In a first aspect, the present invention provides a method for monitoring and processing data three-party disaster recovery anomalies, including:

[0005] Monitoring the online status and communication status of the three-party sites;

[0006] Judging whether there is an anomaly in the three-party sites during the synchronous start and stop process of the changed volume snapshot according to the online status and communication status of the three-party sites:

[0007] If so, skip the start and stop operations of the abnormal snapshot.

[0008] Further, monitoring the online status and communication status of the three-party sites includes:

[0009] Monitoring the online status of the first site, the second site and the third site and the communication status among them. The first site and the second site perform real-time data synchronization through the first link. The second site and the third site perform periodic asynchronous remote replication data through the second link. The first site and the third site perform periodic asynchronous remote replication data through the third link. Wherein, when one of the second link and the third link is in normal use state in the same time period, the other link is in backup and not in use state; wherein, when data is synchronized through the first link, the first site is the primary volume and the second site is the secondary volume. When data is replicated through the second link, the second site is the primary volume and the third site is the secondary volume. When data is replicated through the third link, the first site is the primary volume and the third site is the secondary volume.

[0010] Further, determine whether there is an abnormality in the process of synchronously starting and stopping the change volume snapshot of the three-party site according to the online status and communication status of the three-party site, including:

[0011] When remotely replicating data through the second link, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before and after the first link is silent;

[0012] Verify whether both the volume of the second site and the changed volume are in the online state;

[0013] Verify whether both the volume of the third site and the changed volume are in the online state;

[0014] Verify whether the communication status between the second site and the third site is connected;

[0015] If all the verification contents pass, the second link successfully starts the main change volume snapshot, the third link starts the change volume snapshot, and the first link exits the silent state;

[0016] If there is any verification content that fails to pass, generate an abnormal alarm prompt and end the program for starting the main change volume snapshot this time, waiting for the next cycle.

[0017] Further, determine whether there is an abnormality in the process of synchronously starting and stopping the change volume snapshot of the three-party site according to the online status and communication status of the three-party site, including:

[0018] After the second link completes data replication, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before and after the first link is silent;

[0019] If all the verification contents pass, the second link stops the change card snapshot, the third link stops the change volume snapshot, and the first link exits the silent state;

[0020] If there is any verification content that fails to pass, generate an abnormal alarm prompt and end the program for stopping the main change volume snapshot this time, waiting for the next cycle.

[0021] Further, determine whether there is an abnormality in the process of synchronously starting and stopping the change volume snapshot of the three-party site according to the online status and communication status of the three-party site, including:

[0022] When remotely replicating data through the third link, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before the first link is silent;

[0023] Verify whether both the volume of the first site and the changed volume are in the online state;

[0024] If all the verification content passes, the third link successfully starts the main change volume snapshot to record the data differences between the first site and the third site, and controls the first link to exit the silent state;

[0025] If there is verification content that fails the verification, an exception alarm prompt is generated and the program for starting the main change volume snapshot of the third link this time ends, waiting for the next cycle.

[0026] Furthermore, it is judged whether there is an abnormality in the process of synchronous start and stop of the change volume snapshot of the three-party site according to the online status and communication status of the three-party site, including:

[0027] After the third link completes data replication, the first link is controlled to be silent;

[0028] If the first link is in the silent state, the third link successfully stops the main change volume snapshot;

[0029] If the first link is not in the silent state, an exception alarm prompt is generated and the program for stopping the main change volume snapshot of the third link this time ends, waiting for the next cycle.

[0030] In a second aspect, the present invention provides a data three-party disaster tolerance exception monitoring and processing system, including:

[0031] A status monitoring unit for monitoring the online status and communication status of the three-party site;

[0032] An exception judgment unit for judging whether there is an abnormality in the process of synchronous start and stop of the change volume snapshot of the three-party site according to the online status and communication status of the three-party site;

[0033] An operation skipping unit for skipping the start and stop operations of the abnormal snapshot if there is an abnormality in the process of synchronous start and stop of the change volume snapshot of the three-party site.

[0034] Furthermore, the status monitoring unit is used for:

[0035] Monitoring the online status of the first site, the second site and the third site and the communication status among them. The first site and the second site perform real-time data synchronization through the first link. The second site and the third site perform periodic asynchronous remote replication of data through the second link. The first site and the third site perform periodic asynchronous remote replication of data through the third link. Among them, when one of the second link and the third link is in the normal use state in the same time period, the other link is in the backup and non-use state; among them, when data is synchronized through the first link, the first site is the main volume and the second site is the secondary volume. When data is replicated through the second link, the second site is the main volume and the third site is the secondary volume. When data is replicated through the third link, the first site is the main volume and the third site is the secondary volume.

[0036] In a third aspect, a terminal is provided, including:

[0037] a processor and a memory, wherein,

[0038] the memory is used for storing a computer program,

[0039] the processor is used for calling and running the computer program from the memory, so that the terminal executes the method of the terminal as described above.

[0040] In a fourth aspect, a computer storage medium is provided, and instructions are stored in the computer-readable storage medium, and when the instructions run on a computer, the computer is enabled to execute the methods described in the above aspects.

[0041] The beneficial effects of the present invention are as follows. The method, system, terminal and storage medium for triple-party disaster tolerance and abnormal monitoring and processing provided by the present invention can ensure the normal operation of the policy and the normal disaster tolerance of data before the switching of the ring 3DC failure scenario through abnormal processing, and avoid the problem that the policy cannot be executed or the io timeout problem occurs before the failure scenario response due to the occurrence of the abnormal scenario.

[0042] In addition, the design principle of the present invention is reliable and the structure is simple, and it has a very wide application prospect. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained according to these drawings without creative efforts.

[0044] Figure 1 is an exemplary flowchart of the method according to an embodiment of the present invention.

[0045] Figure 2 is a topological schematic diagram of triple-party disaster tolerance.

[0046] Figure 3 is an exemplary flowchart of starting snapshots of the second link and the third link of the method according to an embodiment of the present invention.

[0047] Figure 4 is an exemplary flowchart of stopping snapshots of the second link and the third link of the method according to an embodiment of the present invention.

[0048] Figure 5 is a schematic block diagram of the system according to an embodiment of the present invention.

[0049] Figure 6 is a schematic structural diagram of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0050] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0051] Figure 1 It is a schematic flowchart of a method according to an embodiment of the present invention. Among them, Figure 1 The execution subject may be a data tripartite disaster tolerance anomaly monitoring and processing system.

[0052] As Figure 1 shown, the method includes:

[0053] Step 110, monitor the online status and communication status of the tripartite site;

[0054] Step 120, determine whether there is an anomaly in the tripartite site during the synchronization start and stop process of the changed volume snapshot according to the online status and communication status of the tripartite site:

[0055] Step 130, if so, skip the start and stop operations of the abnormal snapshot.

[0056] For the convenience of understanding the present invention, the following further describes the data tripartite disaster tolerance anomaly monitoring and processing method provided by the present invention with reference to the principle of the data tripartite disaster tolerance anomaly monitoring and processing method of the present invention and the process of anomaly monitoring and processing of data tripartite disaster tolerance in the embodiments.

[0057] Specifically, the data tripartite disaster tolerance anomaly monitoring and processing method includes:

[0058] As Figure 2As shown in the figure, A, B, and C are three data sites. Site A is the production data center, B is the disaster recovery data center in the same city, and C is the disaster recovery data center in a different location. Site A and B use RCx (synchronous remote replication relationship or active-active) to synchronize data between the two sites; Site B and C use RCy (periodic asynchronous remote replication relationship) to synchronize data between the two sites; Site A and C use RCz (periodic asynchronous remote replication relationship) to synchronize data between the two sites. In the initial deployment, only one of RCy and RCz is a remote replication relationship in normal use, and the other is a remote replication relationship that is not used for backup. Here, we take the initial deployment of RCy as enabled and RCz as a backup and not enabled as an example. The disaster recovery management software implements unified management of the three sites. When a volume is offline or the partnership is disconnected and before the failover, exception processing is required. The exception scenarios are mainly divided into the following five situations: master volume offline, slave volume offline, master change volume offline, slave change volume offline, and partnership disconnected. Taking RCy as enabled and RCz as standby as an example, different processing methods for different abnormal scenarios are introduced. A, B, and C are connected through a partnership. In RCx, A is the primary volume and B is the secondary volume. In RCy, B is the primary volume and C is the secondary volume. B_change is the primary volume change volume and C_change is the secondary volume change volume. In RCz, A is the primary volume and C is the secondary volume. A_change is the primary volume change volume and C_change is the secondary volume change volume.

[0059] The ring 3DC strategy is mainly implemented by starting and stopping the master change volume snapshots in RCy and RCz at the same time when RCx is silent, under the premise that A and B are completely synchronized. That is, the RC bitmap and the change volume snapshot bitmap that record the data differences between the two remote replication relationships RCy and RCz are synchronized. Figure 1 And clear the RC bitmap of RCz when lcz stops, the flow chart is as follows Figure 3 The business is issued through volume A, and the abnormal scenarios are as follows:

[0060] (1) How to handle abnormal scenarios during the process of changing volume snapshots and starting simultaneously, such as the process Figure 3 As shown:

[0061] When remotely replicating data through RCx, controlling RCx to be silent and respectively checking whether the communication status between the first site and the second site is connected before and after RCx is silent;

[0062] Verify that the volume and the change volume at the second site are both online;

[0063] Verify that the volume and the change volume at the third site are both online;

[0064] Verify whether the communication status between the second site and the third site is connected;

[0065] If all the verification content passes, then RCy successfully starts the main change volume snapshot to begin remotely replicating the data from the second site to the third site, and controls RCx to exit the silent state;

[0066] If there is verification content that fails the verification, an exception alarm prompt is generated and the program for starting the main change volume snapshot this time ends, waiting for the next cycle.

[0067] When remotely replicating data through RCz, control RCx to be silent and verify whether the communication status between the first site and the second site is connected before RCx goes silent;

[0068] Verify whether both the volume and the change volume of the first site are in the online state;

[0069] If all the verification content passes, then RCz successfully starts the main change volume snapshot to begin remotely replicating the data from the first site to the third site, and controls RCx to exit the silent state;

[0070] If there is verification content that fails the verification, an exception alarm prompt is generated and the program for starting the RCz main change volume snapshot this time ends, waiting for the next cycle.

[0071] (2) Abnormal scenario handling method during the simultaneous stop of the change volume snapshot, as shown in the process Figure 4 as follows:

[0072] After RCy completes data replication, control RCx to be silent and verify whether the communication status between the first site and the second site is connected before and after RCx goes silent;

[0073] If all the verification content passes, then RCy successfully stops the main change volume snapshot;

[0074] If there is verification content that fails the verification, an exception alarm prompt is generated and the program for stopping the main change volume snapshot this time ends, waiting for the next cycle.

[0075] After RCz completes data replication, control RCx to be silent;

[0076] If RCx is in the silent state, then RCz successfully stops the main change volume snapshot;

[0077] If RCx is not in the silent state, an exception alarm prompt is generated and the program for stopping the RCz main change volume snapshot this time ends, waiting for the next cycle.

[0078] The following restrictions need to be followed during abnormal scenario handling:

[0079] (1) Since the changed volume snapshots at both ends of RCy and RCz are not started and stopped simultaneously due to abnormal scenarios, when starting lcz, if it is found that lcz has already been started, it will be directly skipped and lcz will not be stopped and restarted.

[0080] (2) When stopping lcz, if it is found that lcz has already been stopped, it will be directly skipped and lcz will not be started and restarted. At this time, the RC bitmap of RCz will not be cleared.

[0081] As Figure 5 shown, the system 500 includes:

[0082] A status monitoring unit 510 for monitoring the online status and communication status of the three-party site;

[0083] An anomaly judgment unit 520 for judging whether there is an anomaly in the three-party site during the synchronous start and stop process of the changed volume snapshot according to the online status and communication status of the three-party site;

[0084] An operation skip unit 530 for skipping the start and stop operations of the abnormal snapshot if there is an anomaly in the three-party site during the synchronous start and stop process of the changed volume snapshot.

[0085] Optionally, as an embodiment of the present invention, the status monitoring unit is used for:

[0086] Monitoring the online status of the first site, the second site, and the third site and the communication status among them. The first site and the second site perform real-time data synchronization through the first link. The second site and the third site perform periodic asynchronous remote replication of data through the second link. The first site and the third site perform periodic asynchronous remote replication of data through the third link. Among them, when one of the second link and the third link is in normal use during the same period, the other link is in a backup and unused state. Among them, when data is synchronized through the first link, the first site is the main volume and the second site is the secondary volume. When data is replicated through the second link, the second site is the main volume and the third site is the secondary volume. When data is replicated through the third link, the first site is the main volume and the third site is the secondary volume.

[0087] Figure 6 It is a schematic structural diagram of a terminal 600 provided by an embodiment of the present invention. The terminal 600 can be used to execute the data three-party disaster tolerance anomaly monitoring and processing method provided by the embodiment of the present invention.

[0088] Among them, the terminal 600 may include: a processor 610, a memory 620, and a communication unit 630. These components communicate via one or more buses. Those skilled in the art can understand that the structure of the server shown in the figure does not constitute a limitation on the present invention. It can be a bus structure, a star structure, and may also include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0089] Among them, the memory 620 can be used to store the execution instructions of the processor 610. The memory 620 can be implemented by any type of volatile or non-volatile storage terminal or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disc. When the execution instructions in the memory 620 are executed by the processor 610, the terminal 600 is enabled to execute some or all of the steps in the above method embodiments.

[0090] The processor 610 is the control center of the storage terminal, connecting various parts of the entire electronic terminal using various interfaces and lines. By running or executing the software programs and / or modules stored in the memory 620, and by invoking the data stored in the memory, it executes various functions of the electronic terminal and / or processes data. The processor may be composed of an integrated circuit (IC). For example, it may be composed of a single packaged IC, or may be composed of multiple packaged ICs with the same or different functions connected together. For example, the processor 610 may only include a central processing unit (CPU). In the embodiment of the present invention, the CPU may be a single arithmetic core or may include multiple arithmetic cores.

[0091] The communication unit 630 is used to establish a communication channel so that the storage terminal can communicate with other terminals. It receives user data sent by other terminals or sends user data to other terminals.

[0092] The present invention also provides a computer storage medium. Among them, the computer storage medium may store a program, and when the program is executed, it may include some or all of the steps in the various embodiments provided by the present invention. The storage medium may be a magnetic disk, an optical disc, a read-only memory (ROM), or a random access memory (RAM), etc.

[0093] Therefore, through exception handling, the present invention can ensure the normal operation of the policy before the switching of the ring 3DC fault scenario and the normal disaster recovery of data, avoiding the situation that the policy cannot be executed or the io timeout problem occurs before the fault scenario response due to the occurrence of an abnormal scenario. The technical effects achievable by this embodiment can be referred to the description above and will not be elaborated here.

[0094] Those skilled in the art can clearly understand that the technologies in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solutions in the embodiments of the present invention, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc., which can store program codes, and includes several instructions for causing a computer terminal (which can be a personal computer, a server, or a second terminal, a network terminal, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0095] The same or similar parts among the various embodiments in this specification can be referred to each other. In particular, for the terminal embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the descriptions in the method embodiments.

[0096] In several embodiments provided by the present invention, it should be understood that the disclosed systems and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces. The indirect coupling or communication connection of the systems or units can be in an electrical, mechanical, or other forms.

[0097] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0098] In addition, in each embodiment of the present invention, the functional units can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0099] Although the present invention has been described in detail by referring to the accompanying drawings and in conjunction with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, those of ordinary skill in the art can make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions should all be within the scope of the present invention. / Any person skilled in the art within the technical scope disclosed by the present invention can easily conceive of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for monitoring and processing data three-party disaster tolerance anomalies, characterized in that, including: monitoring the online status and communication status of the three-party site; judging whether there is any abnormality in the three-party site during the synchronous start-stop process of the changed volume snapshot according to the online status and communication status of the three-party site: if so, skipping the start-stop operation of the abnormal snapshot; monitoring the online status and communication status of the three-party site, including: monitoring the online status of the first site, the second site, and the third site and the communication status among them. The first site and the second site perform real-time data synchronization through the first link. The second site and the third site perform periodic asynchronous remote replication of data through the second link. The first site and the third site perform periodic asynchronous remote replication of data through the third link. When one of the second link and the third link is in normal use during the same period, the other link is in backup and not in use. Among them, when data is synchronized through the first link, the first site is the main volume and the second site is the secondary volume. When data is replicated through the second link, the second site is the main volume and the third site is the secondary volume. When data is replicated through the third link, the first site is the main volume and the third site is the secondary volume; judging whether there is any abnormality in the three-party site during the synchronous start-stop process of the changed volume snapshot according to the online status and communication status of the three-party site, including: when remotely replicating data through the second link, controlling the first link to be silent and respectively verifying whether the communication status between the first site and the second site is connected before and after the first link is silent; verifying whether both the volume of the second site and the changed volume are in the online state; verifying whether both the volume of the third site and the changed volume are in the online state; verifying whether the communication status between the second site and the third site is connected; if all the verification contents pass, the second link successfully starts the main changed volume snapshot and the third link starts the changed volume snapshot, and the first link exits the silent state; if there is any verification content that fails to pass, generating an abnormal alarm prompt and ending the program for starting the main changed volume snapshot this time and waiting for the next cycle; judging whether there is any abnormality in the three-party site during the synchronous start-stop process of the changed volume snapshot according to the online status and communication status of the three-party site, including: after the second link completes data replication, controlling the first link to be silent and respectively verifying whether the communication status between the first site and the second site is connected before and after the first link is silent; if all the verification contents pass, the second link stops the changed volume snapshot, the third link stops the changed volume snapshot, and the first link exits the silent state; if there is any verification content that fails to pass, generating an abnormal alarm prompt and ending the program for stopping the main changed volume snapshot this time and waiting for the next cycle; judging whether there is any abnormality in the three-party site during the synchronous start-stop process of the changed volume snapshot according to the online status and communication status of the three-party site, including: when remotely replicating data through the third link, controlling the first link to be silent and verifying whether the communication status between the first site and the second site is connected before the first link is silent; verifying whether both the volume of the first site and the changed volume are in the online state; if all the verification contents pass, the third link successfully starts the main changed volume snapshot to record the data difference between the first site and the third site, and controls the first link to exit the silent state; If there is verification content that fails the verification, an exception warning prompt is generated and the program for starting the main change volume snapshot of the third link this time ends, waiting for the next cycle; Based on the online status and communication status of the three-party site, determine whether there are any exceptions during the synchronization start and stop of the change volume snapshot for the three-party site, including: After the data replication on the third link is completed, control the first link to be silent; If the first link is in a silent state, the third link successfully stops the main change volume snapshot; If the first link is not in a silent state, an exception warning prompt is generated and the program for stopping the main change volume snapshot of the third link this time ends, waiting for the next cycle.

2. A data three-party disaster tolerance anomaly monitoring and processing system, characterized in that, Including: A status monitoring unit for monitoring the online status and communication status of the three-party site; An exception judgment unit for determining whether there are any exceptions during the synchronization start and stop of the change volume snapshot for the three-party site based on the online status and communication status of the three-party site; An operation skipping unit for skipping the start and stop operations of the abnormal snapshot if there are any exceptions during the synchronization start and stop of the change volume snapshot for the three-party site; The status monitoring unit is used for: Monitoring the online status of the first site, the second site, and the third site and the communication status among them. The first site and the second site perform real-time data synchronization through the first link. The second site and the third site perform periodic asynchronous remote replication of data through the second link. The first site and the third site perform periodic asynchronous remote replication of data through the third link. Among them, when one of the second link and the third link is in a normal use state during the same period, the other link is in a backup and unused state; among them, when data is synchronized on the first link, the first site is the main volume and the second site is the secondary volume. When data is replicated on the second link, the second site is the main volume and the third site is the secondary volume. When data is replicated on the third link, the first site is the main volume and the third site is the secondary volume; Based on the online status and communication status of the three-party site, determine whether there are any exceptions during the synchronization start and stop of the change volume snapshot for the three-party site, including: When remotely replicating data through the second link, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before and after the first link is silent; Verify whether both the volume and the change volume of the second site are in an online state; Verify whether both the volume and the change volume of the third site are in an online state; Verify whether the communication status between the second site and the third site is connected; If all the verification content passes, the second link successfully starts the main change volume snapshot and the third link starts the change volume snapshot, and the first link exits the silent state; If there is verification content that fails the verification, an exception warning prompt is generated and the program for starting the main change volume snapshot this time ends, waiting for the next cycle; Based on the online status and communication status of the three-party site, determine whether there are any exceptions during the synchronization start and stop of the change volume snapshot for the three-party site, including: After the data replication on the second link is completed, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before and after the first link is silent; If all the verification content passes, the second link stops the change volume snapshot, the third link stops the change volume snapshot, and the first link exits the silent state; If there is verification content that fails the verification, an exception alarm prompt is generated and the stop procedure of the current main change volume snapshot is ended, waiting for the next cycle; Based on the online status and communication status of the three-party site, determine whether there are any abnormalities during the synchronous start and stop of the change volume snapshot for the three-party site, including: When remotely replicating data through the third link, control the first link to be silent and verify whether the communication status between the first site and the second site is connected before the first link goes silent; Verify whether both the volume of the first site and the change volume are in the online state; If all verification content passes, the third link successfully starts the main change volume snapshot to record the data differences between the first site and the third site, and control the first link to exit the silent state; If there is verification content that fails the verification, an exception alarm prompt is generated and the program for starting the main change volume snapshot of the third link in this instance is ended, waiting for the next cycle; Based on the online status and communication status of the three-party site, determine whether there are any abnormalities during the synchronous start and stop of the change volume snapshot for the three-party site, including: After the third link completes data replication, control the first link to be silent; If the first link is in the silent state, the third link successfully stops the main change volume snapshot; If the first link is not in the silent state, an exception alarm prompt is generated and the program for stopping the main change volume snapshot of the third link in this instance is ended, waiting for the next cycle.

3. A terminal, characterized in that, Including: A processor; A memory for storing the execution instructions of the processor; Wherein, the processor is configured to execute the method described in claim 1.

4. A computer-readable storage medium storing a computer program, characterized in that, When the program is executed by the processor, it implements the method described in claim 1.

Images