Storage data synchronization method and device, storage medium and electronic equipment
By detecting the node interconnection view and link status, only the associated storage volumes are synchronized, and parallel transmission technology is adopted to solve the problem of low data synchronization efficiency and improve the business continuity and performance of the data center.
Patent Information
- Application Number
- CN202411204303.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-08-29
AI Technical Summary
In the prior art, the efficiency of data storage is low, resulting in the host device I/O silencing time which affects the business continuity and performance of the data center.
By detecting the node interconnection view update status and link connection status of the storage cluster in the data production node, only the target storage volume with association relationships is synchronized, and data packet slicing is configured using parallel transmission to reduce the amount of synchronized data and transmission time.
Improves the efficiency of storage data synchronization, reduces the I/O silence time of host equipment, and enhances business continuity and data center management optimization.
Smart Images

Figure CN119088307A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the computer field, and more specifically, to a method, device, storage medium and electronic device for synchronizing stored data. Background Art
[0002] In order to prevent large-scale data disasters, multi-point disaster recovery has gradually become one of the development directions in the field of disaster recovery, that is, storing business data on each node in the data center. At present, in order to maintain the consistency of data of each node in the data center, when the node interconnection view changes, the configuration data needs to be synchronized to all nodes. When synchronizing the configuration data, the host device I / O (Input / Output) needs to be silent. Since the full amount of business data is stored on each node, a large amount of configuration data needs to be synchronized to each node, which increases the remote replication delay and causes the host device I / O to be silent for too long and restart.
[0003] In view of the problems in the related technologies such as low efficiency of storage data synchronization, no effective solution has been proposed yet. Summary of the invention
[0004] The embodiments of the present application provide a method, device, storage medium and electronic device for synchronizing stored data, so as to at least solve the problem of low efficiency of synchronization of stored data in the related art.
[0005] According to an embodiment of the present application, a method for synchronizing stored data is provided, wherein a data center of a target business includes: a first storage cluster and a second storage cluster with a first link established, a data production node and a first disaster recovery node with a second link established are deployed in the first storage cluster, a second disaster recovery node is deployed in the second storage cluster, the data production node is used to connect to a business device of the target business, and the business device is used to use the data center to store business data of the target business, and the method includes:
[0006] Detecting, by the data production node, an update status of a node interconnection view of the first storage cluster, wherein the update status is used to indicate whether the node interconnection view has been updated;
[0007] In the case where it is detected that the update status is used to indicate that the node interconnection view has been updated, detecting the connection status of the first link through the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link;
[0008] When it is detected that the connection state indicates that a change has occurred on the first link, searching, by the data production node, from the storage volumes stored on the data production node, a target storage volume associated with the change occurred on the first link;
[0009] The configuration data of the target storage volume is synchronized to nodes in the first storage cluster through the data production node.
[0010] In an exemplary embodiment, detecting the connection status of the first link through the data production node includes: detecting the link status of the first link, wherein the link status includes a disconnected status and a connected status; when the link status of the first link is the disconnected status, determining that the connection status is detected to indicate that a change has occurred on the first link; when the link status of the first link is the connected status, detecting whether a reconnection event has occurred on the first link, wherein the reconnection event is used to indicate that a reconnection has been performed between the links; when a reconnection event is detected on the first link, determining that the connection status is detected to indicate that a change has occurred on the first link.
[0011] In an exemplary embodiment, searching, through the data production node, the storage volumes stored on the data production node for a target storage volume associated with the change situation occurring on the first link, includes: detecting a synchronization attribute of each storage volume stored on the data production node, wherein the synchronization attribute is used to indicate whether the corresponding storage volume is allowed to be synchronized to the second storage cluster via the first link; searching, according to the synchronization attribute, the storage volumes stored on the data production node for a storage volume that is allowed to be synchronized to the second storage cluster via the first link; and determining the storage volume that is allowed to be synchronized to the second storage cluster via the first link as the target storage volume associated with the change situation occurring on the first link.
[0012] In an exemplary embodiment, the detecting of the synchronization attribute of each storage volume stored on the data production node includes: detecting whether the business data stored in each storage volume stored on the data production node is allowed to be synchronized to the second storage cluster via the first link; in the case where it is detected that the business data stored in the storage volume is allowed to be synchronized to the second storage cluster via the first link, determining that the synchronization attribute of the storage volume is used to indicate that the storage volume is allowed to be synchronized to the second storage cluster via the first link; in the case where it is detected that the business data stored in the storage volume is not allowed to be synchronized to the second storage cluster via the first link, determining that the synchronization attribute of the storage volume is used to indicate that the storage volume is not allowed to be synchronized to the second storage cluster via the first link.
[0013] In an exemplary embodiment, synchronizing the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node includes: obtaining the configuration data of the target storage volume; encapsulating the configuration data into a target data packet; dividing the target data packet into N data packet slices, wherein N is an integer greater than 1; transmitting the N data packet slices in parallel to the nodes in the first storage cluster, wherein the nodes in the first storage cluster are used to parse the N data packet slices upon receiving the N data packet slices to obtain the configuration data corresponding to the N data packet slices and use the configuration data to update the configuration data in the first storage cluster.
[0014] In an exemplary embodiment, encapsulating the configuration data into a target data packet includes: splitting the configuration data into multiple initial structure units; converting the multiple initial structure units into target structure units according to a target format to obtain multiple target structure units, wherein the target format is a format allowed for transmitting the configuration data; integrating the multiple target structure units into a data structure to obtain a target data structure; and compressing the target data structure to obtain the target data packet.
[0015] In an exemplary embodiment, a first counter and a second counter are deployed on the second link; before the update status of the node interconnection view of the first storage cluster is detected by the data production node, the method further includes: detecting whether a transmission abnormality occurs in the second link in the current cycle, wherein the transmission abnormality includes a first abnormality caused by failure to execute a command request due to timeout and a second abnormality caused by failure to complete an input / output operation due to timeout; in the case of detecting that the first abnormality occurs in the second link, recording the occurrence of the first abnormality in the second link in the current cycle through the first counter; and A counter is used to count a first frequency of the first abnormality occurring in the second link; when the first frequency is greater than or equal to a first frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected; when the second abnormality is detected to occur in the second link, the second counter is used to record the occurrence of the second abnormality in the second link within the current cycle; the second frequency of the second abnormality occurring in the second link is counted by the second counter; when the second frequency is greater than or equal to a second frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected.
[0016] According to another embodiment of the present application, a synchronization device for storing data is provided, wherein a data center of a target service includes: a first storage cluster and a second storage cluster with a first link established, a data production node and a first disaster recovery node with a second link established are deployed in the first storage cluster, a second disaster recovery node is deployed in the second storage cluster, the data production node is used to connect to a service device of the target service, and the service device is used to use the data center to store service data of the target service, and the device includes:
[0017] A first detection module, used for detecting an update status of a node interconnection view of the first storage cluster through the data production node, wherein the update status is used for indicating whether the node interconnection view has been updated;
[0018] a second detection module, configured to detect the connection status of the first link through the data production node when it is detected that the update status indicates that the node interconnection view has been updated, wherein the connection status indicates whether a change has occurred on the first link;
[0019] a search module configured to search, through the data production node, from the storage volumes stored on the data production node for a target storage volume associated with the change that has occurred on the first link when it is detected that the connection state indicates that a change has occurred on the first link;
[0020] A synchronization module is used to synchronize the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node.
[0021] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when running.
[0022] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0023] According to another embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.
[0024] Through the present application, the update status of the node interconnection view of the first storage cluster is detected by a data production node, wherein the update status is used to indicate whether the node interconnection view has been updated; when it is detected that the update status is used to indicate that the node interconnection view has been updated, the connection status of the first link is detected by the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link; when it is detected that the connection status is used to indicate that a change has occurred on the first link, the data production node searches for a target storage volume that is associated with the change that has occurred on the first link from the storage volumes stored on the data production node; and the configuration data of the target storage volume is synchronized to the nodes in the first storage cluster through the data production node. That is to say, when the node interconnection view is updated, only the configuration data of the target storage volume that is associated with the changes occurring on the first link is synchronized, thereby reducing the amount of synchronized configuration data and reducing the restart caused by the increased remote replication latency and the long I / O silence time of the host device. Therefore, the problem of low efficiency of storage data synchronization can be solved, thereby achieving the effect of improving the efficiency of storage data synchronization. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 It is a hardware structure block diagram of a server device of a method for synchronizing stored data according to an embodiment of the present application;
[0026] Figure 2 is a flowchart of a method for synchronizing stored data according to an embodiment of the present application;
[0027] Figure 3is a schematic diagram of a data center according to an embodiment of the present application;
[0028] Figure 4 is a schematic diagram of updating a node interconnection view of a data center according to an embodiment of the present application;
[0029] Figure 5 is a schematic diagram of a counting method of a first counter and a second counter according to an embodiment of the present application;
[0030] Figure 6 is a schematic diagram of a working process of a data center according to an embodiment of the present application;
[0031] Figure 7 is a structural block diagram of a synchronization device for storing data according to an embodiment of the present application;
[0032] Figure 8 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0033] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0035] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a server device of a method for synchronizing stored data in an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 The server device includes a processor 102 (only one is shown in the figure) (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is for illustration only and does not limit the structure of the above-mentioned server device. Figure 1 More or fewer components than shown, or with different Figure 1 Different configurations are shown.
[0036] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the synchronization method for storing data in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0037] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
[0038] In this embodiment, a method for synchronizing stored data is provided, wherein a data center of a target business includes: a first storage cluster and a second storage cluster with a first link established, a data production node and a first disaster recovery node with a second link established are deployed in the first storage cluster, a second disaster recovery node is deployed in the second storage cluster, the data production node is used to connect to a business device of the target business, and the business device is used to use the data center to store business data of the target business, Figure 2 is a flowchart of a method for synchronizing stored data according to an embodiment of the present application. Figure 2 As shown, the process includes the following steps:
[0039] Step S202, detecting an update status of a node interconnection view of the first storage cluster through the data production node, wherein the update status is used to indicate whether the node interconnection view has been updated;
[0040] Step S204, when it is detected that the update status is used to indicate that the node interconnection view has been updated, detecting the connection status of the first link through the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link;
[0041] Step S206, when it is detected that the connection state indicates that a change has occurred on the first link, searching, through the data production node, from the storage volumes stored on the data production node, for a target storage volume associated with the change that has occurred on the first link;
[0042] Step S208: Synchronize the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node.
[0043] Through the above steps, the update status of the node interconnection view of the first storage cluster is detected through the data production node, wherein the update status is used to indicate whether the node interconnection view has been updated; when it is detected that the update status is used to indicate that the node interconnection view has been updated, the connection status of the first link is detected through the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link; when it is detected that the connection status is used to indicate that a change has occurred on the first link, the data production node searches for a target storage volume that is associated with the change that has occurred on the first link from the storage volumes stored on the data production node; and the configuration data of the target storage volume is synchronized to the nodes in the first storage cluster through the data production node. That is to say, when the node interconnection view is updated, only the configuration data of the target storage volume that is associated with the changes occurring on the first link is synchronized, thereby reducing the amount of synchronized configuration data and reducing the restart caused by the increased remote replication latency and the long I / O silence time of the host device. Therefore, the problem of low efficiency of storage data synchronization can be solved, thereby achieving the effect of improving the efficiency of storage data synchronization.
[0044] Optionally, in this embodiment, the storage data synchronization method proposed in the present application is used in a wide range of scenarios, which may include but are not limited to: 3DC (Data Centers), 2DC, distributed storage systems, etc. In the following embodiments, the storage data synchronization method mentioned above may be described using the application in the 3DC scenario as an example but is not limited to the usage scenario. Any storage scenario that uses multiple disaster recovery nodes to store business data can use the storage data synchronization method proposed in the present application.
[0045] Optionally, in this embodiment, the first storage cluster includes a data production node and a first disaster recovery node. The data production node is connected to the business equipment of the target business and is connected to the first disaster recovery node through a second link. The first disaster recovery node is connected to the second disaster recovery node in the second storage cluster through the first link.
[0046] Optionally, in this embodiment, the first disaster recovery node may be deployed at a location close to the data production node, for example, the first disaster recovery node may be deployed within 40 kilometers from the data production node. Optical fiber may be used as the second link to connect the data production node and the first disaster recovery node, or other links suitable for short-distance data transmission may be used as the second link.
[0047] Optionally, in this embodiment, the second storage cluster may be deployed at a location far away from the first storage cluster, for example, the second storage cluster may be deployed at a location 1,000 kilometers away from the first storage cluster. The IP remote replication link may be used as the first link to transmit data between the first storage cluster and the second storage cluster, or other links suitable for long-distance data transmission may be used as the first link. One or more second disaster recovery nodes for storing business data remotely may be deployed in the second storage cluster, but not limited to.
[0048] In one exemplary embodiment, an example of a data center is provided. Figure 3 is a schematic diagram of a data center according to an embodiment of the present application, such as Figure 3 As shown in the figure, the business equipment is the front-end host, the first storage cluster is cluster A, the second storage cluster is cluster B, the data production node is the production center deployed in cluster A, the first disaster recovery node is the local disaster recovery center deployed in cluster A, and the second disaster recovery node is the remote disaster recovery center deployed in cluster B. Cluster B is deployed at a location more than 1,000 kilometers away from cluster A, and data is transmitted through IP remote replication links. The production center in cluster A is connected to the front-end host, and the local disaster recovery center is deployed within 40 kilometers of the production center, and data is transmitted through FC (Fiber Channel) optical fibers.
[0049] Controller 1 and controller 2 are deployed on the production center, and controller 2 can be used as a backup device for controller 1, but is not limited to controller 2; controller 3 and controller 4 are deployed on the first disaster recovery node, and controller 4 can be used as a backup device for controller 3, but is not limited to controller 4. Controller 1 and controller 2 are deployed on the second disaster recovery node, and controller 2 can be used as a backup device for controller 1, but is not limited to controller 2.
[0050] Since the remote disaster recovery center is far away from cluster A and has more communication links, the data transmission process of the remote disaster recovery center is subject to signal attenuation, noise interference, etc., and the communication quality and reliability become restrictive factors affecting the data center. In the storage data synchronization method proposed in the present application, since only the configuration data of the target storage volume is synchronized, the host I / O silent time caused by the data synchronization operation is reduced, thereby reducing the impact on business performance, optimizing the management of the remote replication link, ensuring that the business can be quickly restored when a failure occurs, and enhancing business continuity.
[0051] In the technical solution provided in the above step S202, in the storage system, the reasons for updating the node interconnection view may include but are not limited to: when a new node joins the cluster or an existing node exits, the view needs to be updated to reflect the new status of the cluster members; when the first link is disconnected or reconnected, the view needs to be updated; when the role of the node in the cluster changes (for example, the master node fails over to the backup node), the view needs to be updated; when a storage volume is added, deleted or the attributes are modified, such as capacity, performance parameters, etc., the view is updated to reflect the new status of the resource; during data replication or synchronization, if the synchronization status changes, the view is updated, etc.
[0052] Optionally, in this embodiment, the data production node can detect whether the node interconnection view has been updated in a variety of ways, but is not limited to: the data production node uses a specific management protocol to exchange status information and configuration updates to identify view changes, the data production node can be used to detect node status changes, including node joining and exiting, through periodic heartbeat signals, the data production node uses configuration management tools to monitor and manage system configuration, these tools can detect configuration changes and report view updates to the data production node, the data production node uses an API (Application Programming Interface) or a script interface to automate the system to query the cluster status and detect view changes, etc.
[0053] In an exemplary embodiment, an example of updating a node interconnection view of a data center is provided. Figure 4 is a schematic diagram of updating a node interconnection view of a data center according to an embodiment of the present application, such as Figure 4As shown, taking the business device as the front-end host, the first storage cluster as cluster A, the second storage cluster as cluster B, the data production node as the production center deployed in cluster A, the first disaster recovery node as the same-city disaster recovery center deployed in cluster A, and the second disaster recovery node as the remote disaster recovery center deployed in cluster B as an example, when the remote replication link between cluster A and cluster B is disconnected, the view of cluster A is changed. In the storage data synchronization method proposed in the present application, the configuration data to be synchronized is synchronized serially to each controller, thereby reducing the I / O silence during the configuration data transmission, causing the front-end host I / O to be blocked, thereby causing the transmission to take too long and causing the front-end host to timeout and restart.
[0054] It should be noted that the present application can be, but is not limited to, testing the data center in the related technology (for example, simulation testing, building the same equipment environment as on-site. Set a signal simulator in the IP link, add a simulation delay, set the packet loss rate, and retransmit the data packet. The remote replication link is automatically disconnected when the CL layer protocol command times out. When the remote replication link is disconnected and reconnected, the storage system IO is silent. After repeated debugging, the problem phenomenon is reproduced. According to the debugging log, the root cause is located layer by layer: when the remote replication link between clusters is disconnected and reconnected, the TM module is triggered to update the node interconnection view. At this time The RC module then initiates a disconnect action, synchronizing configuration data between cluster nodes and sending data of all instances (without distinguishing between valid and invalid data). 32KB packets are sent serially, resulting in poor link quality and high latency, which leads to slow transmission. During the configuration data transmission, IO is kept silent, causing host IO to be blocked. The host timed out and restarted due to the long transmission time. Analysis shows that the cause of the front-end host timed out and restarted is: during the configuration data transmission, I / O is kept silent, causing the front-end host I / O to be blocked, resulting in the front-end host timed out and restarted.
[0055] Furthermore, it is possible but not limited to improve the data center in the related art according to the conclusion obtained through testing that the front-end host I / O is blocked due to I / O silence during the configuration data transmission, thereby causing the front-end host to time out and restart, that is, by reducing the business data to be synchronized (screening the remote replication volume), the configuration data of the storage volume to be synchronized is reduced, and a parallel synchronization method is adopted to reduce the time spent on synchronizing the configuration data of the storage volume, and prevent the front-end host I / O from being blocked due to I / O silence during the configuration data transmission, thereby causing the front-end host to time out and restart. In addition, the first counter and the second counter are used to count the number of errors, and the system no longer restarts immediately when a timeout occurs, but counts according to a period, thereby improving the robustness of the front-end host in the face of abnormal situations.
[0056] In the technical solution provided in the above step S204, the changes allowed to occur on the above first link may include but are not limited to: disconnection of the first link, reconnection of the first link after disconnection, etc. It may be but is not limited to the case where one of the above changes is detected on the first link, determining that the connection state of the first link is detected is used to indicate that a change has occurred on the first link.
[0057] In an exemplary embodiment, the connection status of the first link can be detected by the data production node in the following manner but is not limited to: detecting the link status of the first link, wherein the link status includes a disconnected state and a connected state; when the link status of the first link is the disconnected state, determining that the connection status is detected to indicate that a change has occurred on the first link; when the link status of the first link is the connected state, detecting whether a reconnection event has occurred on the first link, wherein the reconnection event is used to indicate that a reconnection has been performed between the links; when a reconnection event is detected on the first link, determining that the connection status is detected to indicate that a change has occurred on the first link.
[0058] Optionally, in this embodiment, it is possible but not limited to first detecting whether the first link is in a disconnected state. When it is detected that the first link is in a disconnected state, it is determined that a change is detected on the first link; when it is not detected that the first link is in a disconnected state, continue to detect whether a reconnection event occurs on the first link. When it is detected that a reconnection event occurs on the first link, it is determined that the detected connection state is used to indicate that a change occurs on the first link; when it is not detected that a reconnection event occurs on the first link, it is determined that the detected connection state is used to indicate that no change occurs on the first link.
[0059] In the technical solution provided in the above step S206, the storage volume to be synchronized from the data production node to the second disaster recovery node may be determined as, but is not limited to, a target storage volume associated with the change situation occurring on the first link.
[0060] Optionally, in this embodiment, it is possible but not limited to define which business data needs to be synchronized to the second storage cluster based on the business needs of the target business and the system architecture of the data center. When the connection status is detected to indicate that a change has occurred on the first link, the business data that needs to be synchronized to the second storage cluster is extracted from the storage volumes stored on the data production node, and the storage volumes where the business data has changed and the storage volumes where the configuration data has changed are identified from the business data that needs to be synchronized to the second storage cluster, and these storage volumes are determined as target storage volumes that have an associated relationship with the changes that have occurred on the first link.
[0061] In an exemplary embodiment, the following method can be used, but is not limited to: searching the storage volumes stored on the data production node through the data production node for a target storage volume associated with the change situation occurring on the first link: detecting a synchronization attribute of each storage volume stored on the data production node, wherein the synchronization attribute is used to indicate whether the corresponding storage volume is allowed to be synchronized to the second storage cluster through the first link; searching the storage volumes stored on the data production node for a storage volume that is allowed to be synchronized to the second storage cluster through the first link according to the synchronization attribute; and determining the storage volume that is allowed to be synchronized to the second storage cluster through the first link as the target storage volume associated with the change situation occurring on the first link.
[0062] Optionally, in this embodiment, the synchronization attribute of the storage volume can be determined based on, but not limited to, whether the storage volume is allowed to be synchronized to the second storage cluster. For example, if the synchronization attribute of the storage volume is allowed to be synchronized to the second storage cluster, the synchronization attribute is determined to be allowing the storage volume to be synchronized to the second storage cluster; if the synchronization attribute of the storage volume is not allowed to be synchronized to the second storage cluster, the synchronization attribute is determined to be not allowing the storage volume to be synchronized to the second storage cluster, etc.
[0063] In an exemplary embodiment, the synchronization attribute of each storage volume stored on the data production node can be detected in the following manner but is not limited to: detecting whether the business data stored in each storage volume stored on the data production node is allowed to be synchronized to the second storage cluster through the first link; in the case where it is detected that the business data stored in the storage volume is allowed to be synchronized to the second storage cluster through the first link, determining that the synchronization attribute of the storage volume is used to indicate that the storage volume is allowed to be synchronized to the second storage cluster through the first link; in the case where it is detected that the business data stored in the storage volume is not allowed to be synchronized to the second storage cluster through the first link, determining that the synchronization attribute of the storage volume is used to indicate that the storage volume is not allowed to be synchronized to the second storage cluster through the first link.
[0064] Optionally, in this embodiment, the data type of business data to be synchronized to the second storage cluster can be pre-set but is not limited to. When the data production node transmits business data to the first disaster recovery node, the first disaster recovery node detects the data type of the business data and determines whether it needs to be synchronized to the second storage cluster based on the data type.
[0065] In the technical solution provided in the above step S208, the configuration data of the target storage volume can be synchronized to the nodes in the first storage cluster in a serial transmission manner, but is not limited to it. For example, the configuration data of each target storage volume is transmitted to each node in the first storage cluster in turn, that is, after the configuration data of the current target storage volume is transmitted to each node in the first storage cluster, the configuration data transmission process of the next target storage volume is executed;
[0066] Alternatively, the configuration data of the target storage volume is synchronized to the nodes in the first storage cluster in a parallel transmission manner, and the configuration data of multiple target storage volumes are transmitted in parallel to each node in the first storage cluster. For example, taking the configuration data including configuration data A, configuration data B, configuration data C and configuration data D as an example, configuration data A and configuration data B are transmitted in parallel, and in the current transmission cycle, when the transmission of configuration data A and configuration data B is completed, configuration data C and configuration data D are continuously transmitted; in the current transmission cycle, when the transmission of configuration data A is not completed, configuration data A and configuration data C are continuously transmitted, etc.;
[0067] Alternatively, the configuration data of the target storage volume may be synchronized to the nodes in the first storage cluster in a serial-non-parallel collaborative manner, and the transmission method to be used may be determined, but is not limited to, according to the transmission parameters of the current data production node. For example, when the transmission parameter is greater than or equal to the first transmission threshold, the current data production node is considered to have a high transmission efficiency, and a parallel transmission method is used. The amount of configuration data to be transmitted in parallel is determined based on the transmission parameters, and the transmission parameter is positively correlated with the data amount. When the transmission parameter is less than the first transmission threshold and greater than or equal to the second transmission threshold, the current data production node is considered to have a medium transmission efficiency, and serial transmission and parallel transmission methods are periodically used. The amount of configuration data to be transmitted in parallel is determined based on the transmission parameters, and the transmission parameter is positively correlated with the data amount. When the transmission parameter is less than the second transmission threshold, the current data production node is considered to have a poor transmission efficiency, and a serial transmission method is used.
[0068] In an exemplary embodiment, the configuration data of the target storage volume can be synchronized to the nodes in the first storage cluster through the data production node in the following manner, but is not limited to: obtaining the configuration data of the target storage volume; encapsulating the configuration data into a target data packet; dividing the target data packet into N data packet slices, wherein N is an integer greater than 1; transmitting the N data packet slices in parallel to the nodes in the first storage cluster, wherein the nodes in the first storage cluster are used to parse the N data packet slices upon receiving the N data packet slices to obtain the configuration data corresponding to the N data packet slices and use the configuration data to update the configuration data in the first storage cluster.
[0069] Optionally, in this embodiment, the configuration data of the target storage volume can be obtained and the configuration data can be encapsulated into a target data packet in the following manner but is not limited to: obtaining the volume ID, size, permissions, replication status and other attributes of the target storage volume; abstracting the obtained attributes into data structures such as classes, structures or dictionaries; creating instances according to the defined structural unit templates, filling in specific attribute values to obtain the structural units of each target storage volume, wherein the structural unit templates are predefined key information containing the target storage volume; encapsulating each structural unit into an independent data packet; integrating all structural unit instances into a data set, such as a list, array or other data structure; compressing the integrated data set to reduce the amount of transmitted data; adding necessary metadata to the data set, such as timestamp, version number, synchronization batch, etc., to obtain the target data packet.
[0070] In an exemplary embodiment, the configuration data may be encapsulated into a target data packet in the following manner but is not limited to: splitting the configuration data into a plurality of initial structure units; converting the plurality of initial structure units into target structure units according to a target format to obtain a plurality of target structure units, wherein the target format is a format allowed for transmitting the configuration data; integrating the plurality of target structure units into a data structure to obtain a target data structure; and compressing the target data structure to obtain the target data packet.
[0071] Optionally, in this embodiment, the storage volumes in the first storage cluster may be divided into, but not limited to, local replication volumes, active-active volumes, remote replication volumes, and thin volumes, etc., for executing different storage services. The disconnection and reconnection of the first link only affect the remote replication volumes, and have no impact on the local replication volumes, active-active volumes, compressed volumes, and thin volumes, etc. of the production center. Therefore, the remote replication volume is determined as the target storage volume.
[0072] Optionally, in this embodiment, when the first link is disconnected or reconnected, it will cause the cluster node view to change (including the view formed by all connected nodes). In order to maintain the data consistency of each node in the data center, when the node view changes, the configuration data (volume data changes and other configurations) can be synchronized to all nodes through the RC module but is not limited to.
[0073] Optionally, in this embodiment, when N data packet slices are obtained, it is no longer necessary to wait for each packet (32k) to be successfully delivered before transmitting the next one. Instead, the entire packet is sliced in memory and sent in parallel to improve transmission efficiency. The success flag is sent back after all reception is completed.
[0074] In an exemplary embodiment, a first counter and a second counter are deployed on the second link; before the update status of the node interconnection view of the first storage cluster is detected through the data production node, it can be determined whether to disconnect the second link between the data production node and the first disaster recovery node in the following manner but not limited to: detecting whether a transmission anomaly occurs in the second link in the current cycle, wherein the transmission anomaly includes a first anomaly caused by failure to execute a command request due to timeout and a second anomaly caused by failure to complete an input / output operation due to timeout; in the case of detecting that the first anomaly occurs in the second link, recording the occurrence of the second link in the current cycle through the first counter The first abnormality is detected; a first frequency of the first abnormality occurring in the second link is counted by the first counter; when the first frequency is greater than or equal to a first frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected; when the second abnormality is detected in the second link, the second abnormality occurring in the second link in the current cycle is recorded by the second counter; a second frequency of the second abnormality occurring in the second link is counted by the second counter; when the second frequency is greater than or equal to a second frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected.
[0075] In an exemplary embodiment, an example of a counting method of a first counter and a second counter is provided. Figure 5 is a schematic diagram of a counting method of a first counter and a second counter according to an embodiment of the present application, such as Figure 5 As shown, taking the first storage cluster as cluster A and the second storage cluster as cluster B as an example, cluster A as a CL initiator and cluster B as a CL responder as an example, the first counter is used to record the first exception caused by the timeout and failure to execute the command request in the second link in the current cycle. It can be but not limited to the following cases, it is considered that the first exception has occurred in the second link:
[0076] The first exception (IO full process timeout) refers to the time taken for the CL module initiator to send an IO request, transmit through the link, reach the other node, and the other node responder to feedback the result (status or data+status), which is transmitted through the link and sent to the local CL module initiator. If the IO full process takes too long, it naturally indicates poor communication performance, because there is an upper limit on the number of IO concurrency, which affects the IO concurrency operation.
[0077] According to the formula: protocol command timeout (CMD_TIMEOUT) = link transmission time + maximum response scheduling time + idle wait + detection cycle + IO return scheduling time, it can be known that protocol command timeout = (2000+400)+800+800+400+800=5200 milliseconds, and the IO full process timeout threshold is 5.2s.
[0078] That is to say, within a cycle, if the execution time of an IO request exceeds 5.2s, it is considered that a timeout error has occurred, and the first counter +1 discards the protocol command that has timed out. If the above situation occurs in each consecutive detection cycle, the count is +1. When the cumulative count reaches 5 (the first frequency threshold), the link is disconnected and the count is reset to 0. If the cumulative count reaches the target number (for example: 3) and there is no timeout in the next cycle, the count is -1 until it reaches 0.
[0079] The second counter is used to record the occurrence of a second exception in the second link in the current cycle due to an input / output operation not being completed due to timeout. The second exception may be considered to have occurred in the second link in the following cases, but is not limited to:
[0080] The second exception (protocol command interval timeout) refers to the maximum time interval between two IO requests received by the CL module responder. Protocol command timeout is to detect whether the communication link is blocked, timed out, or other abnormal conditions from the initiator, and protocol command interval timeout is to detect blockage, timeout, or other abnormal conditions at the responder.
[0081] According to the formula: protocol command interval timeout (COMPLETION_TIMEOUT) = protocol command timeout + maximum time consumption of new command response scheduling, it can be known that protocol command interval timeout = CMD_TIMEOUT + 800 = 600 milliseconds, and the protocol command interval timeout threshold is 6s.
[0082] That is to say, within a cycle, if the maximum time interval between receiving two IO applications exceeds 6s, it is considered that a timeout error has occurred, and the second counter +1 discards the protocol command that has timed out. If the above situation occurs in each consecutive detection cycle, the count is +1. When the cumulative count reaches 5 (the second frequency threshold), the link is disconnected and the count is reset to 0. If the cumulative count reaches the target number (for example: 3) and there is no timeout in the next cycle, the count is -1 until it reaches 0.
[0083] The above process improves the tolerance of the CL module to abnormal situations. Ordinary protocol command timeout or idle timeout no longer directly disconnects the link. Instead, timeouts occur continuously within a certain time range, and then the link is actively disconnected and reset. This reduces the number of changes in the first link, and subsequently reduces the number of updates to the node interconnection view of the first storage cluster.
[0084] Optionally, in this embodiment, in order to better understand the process of synchronization of the above-mentioned stored data in the method for synchronizing stored data proposed in this application, the above-mentioned process is further described below in conjunction with an optional embodiment, but the technical solution of the embodiment of this application is not limited.
[0085] In an exemplary embodiment, an example of a working process of a data center is provided. Figure 6 is a schematic diagram of a working process of a data center according to an embodiment of the present application, such as Figure 6 As shown, taking the first storage cluster as cluster A, the second storage cluster as cluster B, the data production node as the production center deployed in cluster A, the first disaster recovery node as the local disaster recovery center deployed in cluster A, and the second disaster recovery node as the remote disaster recovery center deployed in cluster B as an example, the business data in the production center is stored as local replication volumes, dual-active volumes, remote replication volumes and thin volumes respectively, the local replication volumes, dual-active volumes, remote replication volumes and thin volumes are stored in the local disaster recovery center, and the remote replication volumes are selected to be stored in the remote disaster recovery center. When it is detected that the node interconnection view has been updated and a change has occurred on the first link, the remote replication volume is determined as the target storage volume, and the configuration data of the remote replication volume is obtained, and the configuration data is synchronized to the local disaster recovery center.
[0086] Through the storage data synchronization method proposed in the present application, by improving the tolerance of the CL module to abnormal situations, ordinary protocol command timeout or idle timeout no longer directly disconnects the link, but timeouts occur continuously within a certain time range, and then the link is actively disconnected and reset, thereby improving the robustness of the first link in the face of abnormal situations; by reducing the size of the configuration data of the synchronous transmission and adjusting the synchronization mode from serial to parallel, the synchronization efficiency of the configuration data is improved.
[0087] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD), including a number of instructions to enable a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0088] In this embodiment, a synchronization device for storing data is provided, and the data center of the target business includes: a first storage cluster and a second storage cluster that have established a first link, a data production node and a first disaster recovery node that have established a second link are deployed in the first storage cluster, and a second disaster recovery node is deployed in the second storage cluster. The data production node is used to connect to the business equipment of the target business, and the business equipment is used to use the data center to store the business data of the target business. The device is used to implement the above-mentioned embodiments and preferred implementation methods, and those that have been explained will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.
[0089] Figure 7 is a structural block diagram of a synchronization device for storing data according to an embodiment of the present application, such as Figure 7 As shown, the device comprises:
[0090] A first detection module 72, used for detecting an update status of a node interconnection view of the first storage cluster through the data production node, wherein the update status is used to indicate whether the node interconnection view has been updated;
[0091] A second detection module 74 is used to detect the connection status of the first link through the data production node when it is detected that the update status is used to indicate that the node interconnection view has been updated, wherein the connection status is used to indicate whether a change has occurred on the first link;
[0092] A search module 76, configured to search, through the data production node, from the storage volumes stored on the data production node for a target storage volume associated with the change occurring on the first link, when it is detected that the connection status indicates that a change has occurred on the first link;
[0093] The synchronization module 78 is used to synchronize the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node.
[0094] Through the above-mentioned device, the update status of the node interconnection view of the first storage cluster is detected through the data production node, wherein the update status is used to indicate whether the node interconnection view has been updated; when it is detected that the update status is used to indicate that the node interconnection view has been updated, the connection status of the first link is detected through the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link; when it is detected that the connection status is used to indicate that a change has occurred on the first link, the target storage volume that has an associated relationship with the change occurring on the first link is searched from the storage volumes stored on the data production node through the data production node; and the configuration data of the target storage volume is synchronized to the nodes in the first storage cluster through the data production node. That is to say, when the node interconnection view is updated, only the configuration data of the target storage volume that is associated with the changes occurring on the first link is synchronized, thereby reducing the amount of synchronized configuration data and reducing the restart caused by the increased remote replication latency and the long I / O silence time of the host device. Therefore, the problem of low efficiency of storage data synchronization can be solved, thereby achieving the effect of improving the efficiency of storage data synchronization.
[0095] In an exemplary embodiment, the second detection module includes:
[0096] A first detection unit, used to detect a link state of the first link, wherein the link state includes a disconnected state and a connected state;
[0097] a first determining unit, configured to, when the link state of the first link is the disconnected state, determine that the connection state is detected to indicate that a change occurs on the first link;
[0098] a second detection unit, configured to detect whether a reconnection event occurs on the first link when the link state of the first link is the connection state, wherein the reconnection event is used to indicate that a reconnection is performed between the links;
[0099] The second determining unit is configured to, when a reconnection event is detected on the first link, determine that the connection state is detected to indicate that a change occurs on the first link.
[0100] In an exemplary embodiment, the search module includes:
[0101] a third detection unit, configured to detect a synchronization attribute of each storage volume stored on the data production node, wherein the synchronization attribute is used to indicate whether synchronization of the corresponding storage volume to the second storage cluster through the first link is allowed;
[0102] a search unit, configured to search, according to the synchronization attribute, from the storage volumes stored on the data production node for a storage volume that is allowed to be synchronized to the second storage cluster through the first link;
[0103] The third determining unit is configured to determine the storage volume that is allowed to be synchronized to the second storage cluster through the first link as the target storage volume associated with the change situation occurring on the first link.
[0104] In an exemplary embodiment, the third detection unit is also used to: detect whether the business data stored in each storage volume stored on the data production node is allowed to be synchronized to the second storage cluster through the first link; when it is detected that the business data stored in the storage volume is allowed to be synchronized to the second storage cluster through the first link, determine the synchronization attribute of the storage volume to indicate that the storage volume is allowed to be synchronized to the second storage cluster through the first link; when it is detected that the business data stored in the storage volume is not allowed to be synchronized to the second storage cluster through the first link, determine the synchronization attribute of the storage volume to indicate that the storage volume is not allowed to be synchronized to the second storage cluster through the first link.
[0105] In an exemplary embodiment, the synchronization module includes:
[0106] an acquisition unit, used for acquiring the configuration data of the target storage volume;
[0107] An encapsulation unit, used for encapsulating the configuration data into a target data packet;
[0108] A dividing unit, used for dividing the target data packet into N data packet slices, wherein N is an integer greater than 1;
[0109] A transmission unit is used to transmit the N data packet slices in parallel to the nodes in the first storage cluster, wherein the nodes in the first storage cluster are used to parse the N data packet slices upon receiving the N data packet slices to obtain configuration data corresponding to the N data packet slices and use the configuration data to update the configuration data in the first storage cluster.
[0110] In an exemplary embodiment, the encapsulation unit is further used to: split the configuration data into multiple initial structure units; convert the multiple initial structure units into target structure units according to a target format to obtain multiple target structure units, wherein the target format is a format allowed for transmitting the configuration data; integrate the multiple target structure units into a data structure to obtain a target data structure; and compress the target data structure to obtain the target data packet.
[0111] In an exemplary embodiment, a first counter and a second counter are deployed on the second link; before detecting the update status of the node interconnection view of the first storage cluster through the data production node, the device also includes:
[0112] a third detection module, configured to detect whether a transmission anomaly occurs in the second link in a current cycle, wherein the transmission anomaly includes a first anomaly caused by failure to execute a command request due to timeout and a second anomaly caused by failure to complete an input / output operation due to timeout;
[0113] a first recording module, configured to record the occurrence of the first abnormality in the second link in the current period by using the first counter when the first abnormality is detected in the second link; a first statistical module, configured to count the first frequency of the occurrence of the first abnormality in the second link by using the first counter; and a first disconnection module, configured to disconnect the second link between the data production node and the first disaster recovery node when the first frequency is greater than or equal to a first frequency threshold;
[0114] a second recording module, for recording the occurrence of the second abnormality in the second link in the current period by using the second counter when the occurrence of the second abnormality in the second link is detected; a second statistical module, for counting the second frequency of the occurrence of the second abnormality in the second link by using the second counter; and a second disconnection module, for disconnecting the second link between the data production node and the first disaster recovery node when the second frequency is greater than or equal to a second frequency threshold.
[0115] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules are located in different processors in any combination.
[0116] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0117] In an exemplary embodiment, the computer-readable storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store computer programs.
[0118] An embodiment of the present application also provides an electronic device, Figure 8 is a structural block diagram of an electronic device according to an embodiment of the present application, such as Figure 8 As shown, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the method embodiments described above.
[0119] In an exemplary embodiment, the electronic device may include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0120] An embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.
[0121] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.
[0122] The embodiments of the present application also provide a computer program, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in any one of the above method embodiments.
[0123] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.
[0124] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the present application is not limited to any specific combination of hardware and software.
[0125] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.
Claims
1. A method for synchronizing stored data, characterized in that: The data center of the target business includes: a first storage cluster and a second storage cluster with a first link established, a data production node and a first disaster recovery node with a second link established are deployed in the first storage cluster, a second disaster recovery node is deployed in the second storage cluster, the data production node is used to connect to a business device of the target business, and the business device is used to use the data center to store business data of the target business, and the method includes: Detecting, by the data production node, an update status of a node interconnection view of the first storage cluster, wherein the update status is used to indicate whether the node interconnection view has been updated; In a case where it is detected that the update status is used to indicate that the node interconnection view has been updated, detecting the connection status of the first link through the data production node, wherein the connection status is used to indicate whether a change has occurred on the first link; When it is detected that the connection state indicates that a change has occurred on the first link, searching, by the data production node, from the storage volumes stored on the data production node, a target storage volume associated with the change that has occurred on the first link; The configuration data of the target storage volume is synchronized to nodes in the first storage cluster through the data production node.
2. The method according to claim 1, characterized in that The detecting the connection status of the first link by the data production node includes: Detecting a link state of the first link, wherein the link state includes a disconnected state and a connected state; When the link state of the first link is the disconnected state, determining that the connection state is detected to indicate that a change has occurred on the first link; When the link state of the first link is the connection state, detecting whether a reconnection event occurs on the first link, wherein the reconnection event is used to indicate that the links are reconnected; In a case where a reconnection event is detected on the first link, it is determined that the connection state is detected to indicate that a change occurs on the first link.
3. The method according to claim 1, characterized in that The searching, by the data production node, from the storage volumes stored on the data production node, for a target storage volume associated with the change situation occurring on the first link includes: Detecting a synchronization attribute of each storage volume stored on the data production node, wherein the synchronization attribute is used to indicate whether synchronization of the corresponding storage volume to the second storage cluster through the first link is allowed; searching, from the storage volumes stored on the data production node according to the synchronization attribute, a storage volume that is allowed to be synchronized to the second storage cluster through the first link; A storage volume that is allowed to be synchronized to the second storage cluster through the first link is determined as the target storage volume associated with the change situation occurring on the first link.
4. The method according to claim 3, characterized in that The detecting the synchronization attribute of each storage volume stored on the data production node includes: Detecting whether the business data stored in each storage volume stored on the data production node is allowed to be synchronized to the second storage cluster through the first link; In a case where it is detected that the service data stored in the storage volume is allowed to be synchronized to the second storage cluster through the first link, determining a synchronization attribute of the storage volume to indicate that synchronization of the storage volume to the second storage cluster through the first link is allowed; When it is detected that the service data stored in the storage volume is not allowed to be synchronized to the second storage cluster through the first link, it is determined that the synchronization attribute of the storage volume is used to indicate that the storage volume is not allowed to be synchronized to the second storage cluster through the first link.
5. The method according to claim 1, characterized in that The synchronizing the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node includes: Acquire the configuration data of the target storage volume; Encapsulating the configuration data into a target data packet; Dividing the target data packet into N data packet slices, where N is an integer greater than 1; The N data packet slices are transmitted in parallel to the nodes in the first storage cluster, wherein the nodes in the first storage cluster are used to parse the N data packet slices upon receiving the N data packet slices to obtain configuration data corresponding to the N data packet slices and use the configuration data to update the configuration data in the first storage cluster.
6. The method according to claim 5, characterized in that The step of encapsulating the configuration data into a target data packet comprises: Splitting the configuration data into a plurality of initial structure units; Converting the plurality of initial structure units into target structure units according to a target format to obtain a plurality of target structure units, wherein the target format is a format allowed to be used for transmitting the configuration data; Integrating the plurality of target structure units into one data structure to obtain a target data structure; The target data structure is compressed to obtain the target data packet.
7. The method according to claim 1, characterized in that A first counter and a second counter are deployed on the second link; Before detecting the update status of the node interconnection view of the first storage cluster by the data production node, the method further includes: Detecting whether a transmission anomaly occurs in the second link in the current cycle, wherein the transmission anomaly includes a first anomaly caused by failure to execute a command request due to timeout and a second anomaly caused by failure to complete an input / output operation due to timeout; When the first abnormality is detected to have occurred in the second link, the first counter is used to record the occurrence of the first abnormality in the second link in the current cycle; the first counter is used to count the first frequency of the occurrence of the first abnormality in the second link; when the first frequency is greater than or equal to a first frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected; When it is detected that the second exception occurs in the second link, the second counter records the occurrence of the second exception in the second link in the current period; the second counter counts the second frequency of the second exception occurring in the second link; and when the second frequency is greater than or equal to a second frequency threshold, the second link between the data production node and the first disaster recovery node is disconnected.
8. A synchronization device for storing data, characterized in that: The data center of the target business includes: a first storage cluster and a second storage cluster with a first link established, a data production node and a first disaster recovery node with a second link established are deployed in the first storage cluster, a second disaster recovery node is deployed in the second storage cluster, the data production node is used to connect to a business device of the target business, and the business device is used to use the data center to store business data of the target business, and the device includes: A first detection module, configured to detect an update status of a node interconnection view of the first storage cluster through the data production node, wherein the update status is used to indicate whether the node interconnection view has been updated; A second detection module is used to detect the connection status of the first link through the data production node when it is detected that the update status indicates that the node interconnection view has been updated, wherein the connection status is used to indicate whether a change has occurred on the first link; a search module configured to search, through the data production node, from the storage volumes stored on the data production node for a target storage volume associated with the change that occurred on the first link when it is detected that the connection state indicates that a change has occurred on the first link; A synchronization module is used to synchronize the configuration data of the target storage volume to the nodes in the first storage cluster through the data production node.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Management method and device for storage cluster equipment, equipment and storage medium
CN115454329A
Distributed block storage data access method based on stateful DHT and storage system
CN116627315A
Configuration data verification method and device, storage medium and electronic equipment
CN118250157A
Disaster recovery method for database, and related device
WO2024131184A1
