CN115086150B - Disaster recovery control system - Google Patents
Disaster recovery control system Download PDFInfo
- Publication number
- CN115086150B CN115086150B CN202210614956.5A CN202210614956A CN115086150B CN 115086150 B CN115086150 B CN 115086150B CN 202210614956 A CN202210614956 A CN 202210614956A CN 115086150 B CN115086150 B CN 115086150B
- Authority
- CN
- China
- Prior art keywords
- disaster recovery
- response
- data center
- instruction
- disaster
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 507
- 230000004044 response Effects 0.000 claims abstract description 169
- 238000004891 communication Methods 0.000 claims abstract description 93
- 230000000977 initiatory effect Effects 0.000 claims abstract description 72
- 238000001914 filtration Methods 0.000 claims abstract description 18
- 239000003999 initiator Substances 0.000 claims description 14
- 238000001514 detection method Methods 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 abstract description 17
- 238000000034 method Methods 0.000 abstract description 17
- 230000008569 process Effects 0.000 abstract description 16
- 206010047289 Ventricular extrasystoles Diseases 0.000 description 16
- 238000005129 volume perturbation calorimetry Methods 0.000 description 16
- 238000007726 management method Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 13
- 238000012544 monitoring process Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 4
- 238000011835 investigation Methods 0.000 description 2
- 230000004888 barrier function Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000593 degrading effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1851—Systems using a satellite or space-based relay
- H04B7/18513—Transmission in a satellite or space-based system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1851—Systems using a satellite or space-based relay
- H04B7/18519—Operations control, administration or maintenance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0604—Management of faults, events, alarms or notifications using filtering, e.g. reduction of information by using priority, element types, position or time
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Astronomy & Astrophysics (AREA)
- Aviation & Aerospace Engineering (AREA)
- General Physics & Mathematics (AREA)
- Alarm Systems (AREA)
Abstract
The embodiment of the invention provides a disaster recovery control system, which comprises: the system comprises a disaster recovery initiating terminal, a disaster recovery receiving terminal, a disaster recovery control terminal and a disaster recovery response terminal, wherein the disaster recovery initiating terminal and the disaster recovery receiving terminal are provided with satellite communication links. After the main data center fails, the disaster recovery control end can generate and send a disaster recovery instruction to the disaster recovery initiating end. The disaster recovery initiating terminal utilizes the filtering function of the disaster recovery initiating terminal to select and utilize the satellite communication link to transmit the disaster recovery instruction to the disaster recovery receiving terminal. The filtering function of the disaster recovery initiating terminal can prevent information irrelevant to disaster recovery from entering the satellite communication link with limited bandwidth. Then, the disaster recovery receiving end can receive the disaster recovery instruction by means of the satellite communication link, and the disaster recovery responding end responds to the disaster recovery instruction. Therefore, in the process of realizing disaster recovery by means of the satellite transmission link, the disaster recovery control system can also reduce the possibility of carrying out satellite communication link by means of the filtering function of the disaster recovery initiating terminal so as to improve the success rate of disaster recovery.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a disaster recovery control system.
Background
In order to ensure the security of Data in a Data Center (Data Center), the continuous availability of the Data is improved, and the Data Center can have disaster recovery capability by setting a main Data Center and a standby Data Center. When the main data center fails, the main data center and the standby data center can be switched by means of the physical communication link between the main data center and the standby data center, so that disaster recovery is realized.
However, when the main data center fails in a large area to form a data island, the physical communication link between the main data center and the standby data center is also in a disconnected state, so that the switching of the main data center and the standby data center cannot be completed, and disaster recovery failure is caused. In order to improve this situation, a satellite communication link may also be established, which may be used to effect a handover of the primary and secondary data centers when they become data islands.
However, in practice, the bandwidth of the satellite communication link is generally limited, and thus, how to implement disaster recovery using the satellite communication link with limited bandwidth is a problem to be solved.
Disclosure of Invention
In view of this, an embodiment of the present invention provides a disaster recovery control system, which is configured to implement disaster recovery by using a satellite communication link with limited bandwidth when a main data center becomes a data island.
In a first aspect, an embodiment of the present invention provides a disaster recovery control system, including: generating a disaster recovery instruction by failure;
the disaster recovery initiating terminal is used for receiving the disaster recovery instruction; forwarding the disaster recovery instruction to the disaster recovery receiving end according to a satellite communication link between the disaster recovery initiating end and the disaster recovery receiving end, wherein a network address of the disaster recovery control end is in a first preset network segment;
the disaster recovery receiving end is used for forwarding the disaster recovery instruction to the disaster recovery response end; forwarding a response result of the disaster recovery instruction to the disaster recovery initiating terminal, wherein the response result reflects a switching result of the main and standby data centers;
the disaster recovery response end is used for responding to the disaster recovery instruction and generating the response result.
The disaster recovery control system provided by the embodiment of the invention comprises a disaster recovery control end, a disaster recovery receiving end of a disaster recovery initiating end and a disaster recovery response end, wherein a satellite communication link is arranged between the disaster recovery initiating end and the disaster recovery receiving end. After the main data center fails, the disaster recovery control end can generate and send a disaster recovery instruction to the disaster recovery initiating end. Furthermore, the disaster recovery initiating terminal can determine a disaster recovery instruction sent by the disaster recovery control terminal with the reserved network address in the first preset network segment by utilizing the filtering function of the disaster recovery initiating terminal, and forward the disaster recovery instruction to the disaster recovery receiving terminal by utilizing the satellite communication link. In the above process, the first preset network segment may filter out instructions and/or messages (hereinafter referred to as information) which are not related to disaster tolerance and are sent by other devices, that is, only the information sent by the device whose network address is in the first preset network segment is considered as the information related to disaster tolerance, and further forwarded to the disaster tolerance receiving end. By filtering, information irrelevant to disaster tolerance can be prevented from entering a satellite communication link with limited bandwidth. Of course, in order to ensure normal transmission of information related to disaster recovery, network addresses of the disaster recovery control end and other devices capable of generating information related to disaster recovery are set in the first preset network segment.
Then, after receiving the disaster recovery instruction by the satellite communication link, the disaster recovery receiving end can further forward the disaster recovery instruction to the disaster recovery response end, and the disaster recovery response end responds to the disaster recovery instruction, namely, the switching between the main data center and the standby data center is performed, namely, the original standby data center is upgraded to the main data center, and the original main data center is downgraded to the standby data center. Finally, the disaster recovery receiving end can still utilize the satellite communication link to feed back the response result of the disaster recovery instruction containing the switching result to the disaster recovery initiating end.
Therefore, in the process of realizing disaster recovery by means of the satellite transmission link, the disaster recovery control system provided by the embodiment of the invention can also reduce the possibility that information irrelevant to disaster recovery is carried out in the satellite communication link by means of the filtering function of the disaster recovery initiating terminal, thereby reducing the situation that disaster recovery instructions cannot be transmitted in time and finally cause disaster recovery failure due to the fact that the satellite communication link with limited bandwidth is occupied by irrelevant information.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic structural diagram of a disaster recovery system according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of another disaster recovery system according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a disaster recovery system including a disaster recovery control system according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a disaster recovery control system according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a disaster recovery control system according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a disaster recovery control system according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a network architecture of another disaster recovery control system according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a physical network according to an embodiment of the present invention;
fig. 9 is an application schematic diagram of a disaster recovery control system according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, the "plurality" generally includes at least two, but does not exclude the case of at least one.
It should be understood that the term "and/or" as used herein is merely one relationship describing the association of the associated objects, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to an identification", depending on the context. Similarly, the phrase "if determined" or "if identified (stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when identified (stated condition or event)" or "in response to an identification (stated condition or event), depending on the context.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a product or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such product or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a commodity or system comprising such elements.
Some embodiments of the present invention are described in detail below with reference to the accompanying drawings. In the case where there is no conflict between the embodiments, the following embodiments and features in the embodiments may be combined with each other. In addition, the sequence of steps in the method embodiments described below is only an example and is not strictly limited.
As described in the background art, disaster recovery can be achieved by setting a primary and a secondary data center, and a common disaster recovery system can be shown in fig. 1. Before describing the embodiments of the present invention in detail, a common disaster recovery manner may be described based on the system shown in fig. 1:
As shown in fig. 1, the system may include a data center 1 and a data center 2. The data center 1 is a main data center, the data center 2 is a standby data center, and a traditional physical communication link is established between the two data centers. Alternatively, the primary and secondary data centers may be disposed in the same or different areas, e.g., data center 1 may be located in a second area and data center 2 may be disposed in a first area.
When the data center 1 fails, the data center 2 can respond to the failure of the data center 1 and send a disaster recovery control command to the data center 1 by means of a physical communication link between the data center 1 and the data center 2, so that the disaster recovery command is utilized to control the data center 1 to be degraded into a standby data center, and meanwhile, the data center 2 is also controlled to be upgraded into a main data center. Through the above up-down process, that is, the primary-backup switching of the data center is realized, the client can normally write data into the upgraded data center, that is, disaster recovery is realized.
The disaster tolerance instruction may be in the form of a uniform resource locator (Uniform Resource Locator, abbreviated as URL). Downgrade of data center 1 may be considered to set the database deployed in data center 1 to a read-only state and upgrade of data center 2 may be considered to set the database deployed in data center 2 to a writable state. And optionally, different types of databases may be deployed in the data center, either relational databases such as MySQL, SQLite, etc., or non-relational databases such as the structural data storage system (TAIR), mongoDb, redis, etc.
The disaster recovery mode is suitable for the situation that the main data center has small-scale faults and the physical communication link can be used. In practice, when the main data center breaks down the physical communication link between the main data center and the standby data center due to a large-area fault caused by natural or artificial reasons, the main data center becomes a data island, and at this time, the switching of the main data center and the standby data center cannot be completed in the above manner, thereby causing disaster recovery failure.
In order to improve the above situation, a disaster recovery system shown in fig. 2 may be used, where the disaster recovery system may include a disaster recovery control system provided in the following embodiments of the present invention. Because the disaster recovery control system can provide a brand new communication link, namely a satellite communication link, even if the physical communication link fails, the satellite communication link can be used for transmitting disaster recovery instructions to the main data center so as to realize the switching of the main data center and the standby data center to realize disaster recovery. Namely, in the case of an extreme fault in the data center 1, the disaster recovery control system provided by the embodiments of the present invention provides a bottom protection mode for disaster recovery.
Based on the above description, the working process of the disaster recovery control system according to each embodiment of the present invention is described in detail below. On the basis of the disaster recovery system shown in fig. 2, fig. 3 is a schematic structural diagram of another disaster recovery system according to an embodiment of the present invention. The disaster recovery system specifically comprises a disaster recovery control system, and the disaster recovery control system specifically comprises: the system comprises a disaster recovery control end, a disaster recovery initiating end, a disaster recovery receiving end and a disaster recovery responding end. The satellite communication link exists between the disaster recovery initiating terminal and the disaster recovery receiving terminal.
Whether the data center fails or not can be carried out by independent monitoring equipment, and the monitoring equipment can monitor the running state of each main and standby data center in the whole disaster recovery system. When the monitoring equipment monitors that the main data center fails, the monitoring result can be sent to the disaster recovery control end, so that the disaster recovery control end responds to the monitoring result to generate a disaster recovery instruction, and the disaster recovery instruction is further sent to the disaster recovery initiating end. Optionally, while generating the disaster recovery instruction, the disaster recovery control end and other devices also deployed in the first area may also generate a disaster recovery notification message related to the disaster recovery, and of course, may also generate an instruction and/or a message unrelated to the disaster recovery. For simplicity of the following description, instructions and/or messages related to or not related to disaster tolerance generated by each device deployed in the first area are collectively referred to as first information, and these information can be sent to a disaster tolerance initiating terminal.
Considering that the bandwidth of the satellite communication link is limited, in order to avoid occupation of the satellite communication link caused by that the first information irrelevant to disaster tolerance enters the satellite communication link, the disaster tolerance initiating terminal can filter the first information received by itself to filter the first information irrelevant to disaster tolerance. Specifically, the disaster recovery initiating terminal may preset a first preset network segment in the initial configuration stage, and implement filtering of the first information by using the first preset network segment: in the first area, information sent by the equipment with the network address in the first preset network segment is reserved by the disaster recovery initiating terminal, and the rest information is filtered. In practice, the network address of the disaster recovery control end is obviously located in the first preset network segment, so that the disaster recovery instruction generated by the disaster recovery control end and used for controlling the switching of the active and standby data centers is not filtered by the disaster recovery initiation end.
Optionally, in order to ensure that information related to disaster recovery can enter the satellite communication link, network addresses of other devices capable of generating information related to disaster recovery in the first area may be preset to be within the first preset network segment. Other devices often generate disaster recovery notification messages.
Then, by utilizing the filtering function of the disaster recovery initiating terminal, the disaster recovery instruction can be forwarded to the disaster recovery receiving terminal by means of the satellite communication link between the disaster recovery instruction and the disaster recovery receiving terminal. The disaster recovery response terminal can further respond to the received disaster recovery instruction, so as to generate a response result reflecting the switching result of the active and standby data centers. And if the response result shows that the switching of the main data center and the standby data center is successful, the disaster recovery is successful. The response result can be fed back to the disaster recovery initiating terminal by means of a satellite communication link between the disaster recovery receiving terminal and the disaster recovery initiating terminal. The switching of the active/standby data center is a switching process of the read/write states of each database in the data center, and the specific content can be referred to the description in the embodiment shown in fig. 1 and will not be described herein.
In practice, when the active and standby data centers are set in different places, the disaster recovery control end and the disaster recovery initiation end may be located in the same area as the data center 2, i.e. the first area in fig. 3, and the disaster recovery receiving end may be located in the same area as the data center 1, i.e. the second area in fig. 3. The disaster recovery control end, the disaster recovery initiating end, the disaster recovery receiving end and the disaster recovery responding end can exist in a cloud server mode. Of course, in order to improve the availability of the whole disaster recovery control system and ensure the disaster recovery success rate, each end in the system can also be in a cloud server cluster form. Optionally, in order to further improve the success rate of disaster recovery, each end in the disaster recovery control system may be set to be multiple.
In this embodiment, after the main data center fails, the disaster recovery control end may generate and send a disaster recovery instruction to the disaster recovery initiation end. Furthermore, the disaster recovery initiating terminal can select and reserve the disaster recovery instruction generated by the disaster recovery control terminal with the network address in the first preset network segment by utilizing the filtering function of the disaster recovery initiating terminal, and the disaster recovery receiving terminal forwards the disaster recovery instruction to the disaster recovery receiving terminal by utilizing the satellite communication link. Then, the disaster recovery receiving end can receive the disaster recovery instruction by means of the satellite communication link, and the disaster recovery response end responds to the disaster recovery instruction, namely, the switching between the main data center and the standby data center is carried out, namely, the original standby data center is upgraded to the main data center, and the original main data center is downgraded to the standby data center. Finally, the disaster recovery receiving end can still utilize the satellite communication link to feed back the response result of the disaster recovery instruction containing the switching result to the disaster recovery initiating end.
In the actual process, the first preset network segment has the function of filtering information of the disaster recovery initiating terminal, that is, only the first information sent by the equipment with the network address in the first preset network segment is forwarded to the disaster recovery receiving terminal by the disaster recovery initiating terminal. In the implementation of the invention, in the process of realizing disaster recovery by means of the satellite transmission link, the possibility that information irrelevant to disaster recovery is carried out in the satellite communication link can be reduced by means of the filtering function of the disaster recovery initiating terminal, so that the situation that the disaster recovery instruction cannot be transmitted in time and finally the disaster recovery fails due to the fact that the satellite communication link with limited bandwidth is occupied by irrelevant instructions and/or information is reduced.
In order to further increase the success rate of disaster recovery, optionally, the number of satellite communication links between the disaster recovery initiator and the disaster recovery receiver may be at least two. That is, after one satellite communication link is disconnected, other links can be continuously used to transmit disaster recovery instructions.
As can be seen from the above description, the disaster recovery instruction may be transmitted by means of a satellite communication link between the disaster recovery initiator and the disaster recovery receiver. It is easy to understand that the transmission of the disaster recovery instruction obviously needs to be realized by means of a satellite, that is, the disaster recovery instruction can be sent from the disaster recovery initiating terminal to the satellite, and then the satellite forwards the disaster recovery instruction to the disaster recovery receiving terminal. The disaster tolerance command can be transmitted in the form of a radio signal, and the frequency of the radio signal is required to be located in a preset frequency band supported by the satellite. The preset frequency band can be any one of a C frequency band, a KU frequency band or a KA frequency band. However, considering that the satellite communication link is the last barrier for controlling the switching of the primary and secondary data centers, the C-band with the highest availability may alternatively be set as the preset band. The setting of the frequency band may be preset when the satellite communication link is established.
For the selection of the frequency bands supported by at least two satellite communication links, from a cost perspective, one satellite communication link may correspond to the C frequency band, the link may be a main link, the other satellite communication links may correspond to the KU frequency band or the KA frequency band, and the other satellite communication links may be spare links. From the point of view of stability and availability, at least two satellite communication links may each correspond to the C-band.
In practice, other satellites having other roles may be deployed while deploying satellites for transmitting disaster recovery instructions (which may be referred to as target satellites for clarity of the following description). And the target satellite and other satellites may be respectively set to support different frequency bands, where the frequency band supported by the different satellites may be considered as any one of the above-mentioned C-band, KU-band, or KA-band, or one sub-band of any one of the frequency bands. Because of the plurality of satellites, when adjacent satellites support adjacent sub-bands, signal interference is easy to occur between the satellites, so that transmission of disaster recovery instructions and response results is affected, and switching failure of the main data center and the standby data center is possibly caused. In order to reduce the switching failure caused by the signal interference, the satellite link establishment cube can also modify the frequency band supported by the target satellite when the signal interference is found to occur, so that the target satellite can normally receive the disaster recovery instruction without being interfered by other satellites.
As can be seen from the description in the embodiment shown in fig. 3, the response result of the disaster recovery response terminal to the disaster recovery instruction can be fed back to the disaster recovery initiation terminal by means of the satellite communication link between the disaster recovery receiving terminal and the disaster recovery initiation terminal. Besides the response result, the disaster recovery response end and other devices also deployed in the second area can generate disaster recovery notification messages related to disaster recovery, and of course, instructions and/or messages unrelated to disaster recovery can also be generated. For simplicity of the following description, instructions and/or messages related to or unrelated to disaster tolerance generated by the disaster tolerance control terminal and other devices are collectively referred to as second information, and the second information can be sent to the disaster tolerance receiving terminal, where optionally, in order to avoid that the second information related to disaster tolerance enters a satellite communication link with limited bandwidth to cause occupation of the satellite communication link, the disaster tolerance receiving terminal is the same as the disaster tolerance initiating terminal, and may also have a filtering function. Specifically, the disaster recovery initiating terminal may preset a second preset network segment in the initial configuration stage, so as to implement filtering of the second information by means of the second preset network segment: the information sent by the equipment with the network address in the second preset network segment is not filtered by the disaster recovery receiving end.
Therefore, the disaster recovery receiving end actually judges whether the second information sent by the equipment is related to the disaster recovery according to the network address of the equipment, and in practice, the network address of the disaster recovery response end obviously needs to be in the second preset network segment, so that the response result of the disaster recovery instruction generated by the disaster recovery response end is not filtered by the disaster recovery receiving end. And in order to ensure that the second information related to disaster recovery can enter the satellite communication link, network addresses of other devices capable of generating the information related to disaster recovery in the second area are preset to be in a second preset network segment. Optionally, other devices generate disaster recovery notification messages.
In this embodiment, by means of the filtering functions of the disaster recovery initiating end and the disaster recovery receiving end, the first information and/or the second information which are irrelevant to disaster recovery can be guaranteed not to enter the satellite communication link to the maximum extent from different information transmission directions, so that the success rate of disaster recovery is guaranteed.
The generation of disaster recovery instructions can also be described in detail based on the embodiment shown in fig. 3. Fig. 4 is a schematic structural diagram of another disaster recovery control system according to an embodiment of the present invention. On the basis of the system shown in fig. 3, the disaster recovery control end in the system specifically includes a first control device and a second control device, where the data centers 1 and 2 are not shown in fig. 4.
According to the description of the above embodiments, the response of the disaster recovery instruction is to switch the read-write states of the databases of different types in the active/standby data center. Optionally, the disaster recovery control end may generate corresponding disaster recovery instructions for different types of databases. For the disaster recovery management and control end expressed in the form of a cloud server cluster, disaster recovery instructions corresponding to different types of databases can be respectively generated by first management and control equipment and second management and control equipment in the cluster, namely, the first management and control equipment can generate disaster recovery instructions aiming at the first type of databases, and the second management and control equipment can generate disaster recovery instructions aiming at the second type of databases. The first type of database may include, among other things, non-relational databases, such as the TAIR mentioned above. The second type of database may be a relational database or a non-relational database outside of the TAIR. Also, in order to avoid instructions not related to disaster recovery from entering the satellite communication link, network addresses of the first management and control device and the second management and control device are also within the first preset network segment.
In this embodiment, the disaster recovery control end of the disaster recovery control system specifically includes a first disaster recovery device and a second disaster recovery device for generating disaster recovery instructions for different types of databases, so as to control switching of read-write states of the different types of databases by using the different disaster recovery instructions, thereby improving accuracy of switching, that is, improving success rate of disaster recovery. In addition, the details not described in detail in this embodiment and the technical effects achieved can also be referred to the embodiment shown in fig. 3, which is not described herein.
The process of transmitting the disaster recovery instructions by the disaster recovery initiator and the disaster recovery receiver using the satellite communication link and the process of generating the disaster recovery instructions have been described in detail in the embodiments shown in fig. 3 and fig. 4. The response process of the disaster recovery instruction can be described on the basis. Fig. 5 is a schematic structural diagram of another disaster recovery control system according to an embodiment of the present invention. Based on the system shown in fig. 4, the disaster recovery response end in the system specifically may include: the system comprises a first disaster recovery response end and a second disaster recovery end.
The first disaster recovery end, the disaster recovery control end, the disaster recovery initiation end and the data center 2 may be disposed in the same area, i.e. the first area in the graph. The second disaster recovery end and the disaster recovery receiving end and the data center 1 are in the same area, namely a second area 1 in the figure. In practice, the two disaster recovery responding ends may also be represented as cloud servers. Optionally, in order to improve the availability of disaster recovery response ends, each disaster recovery response end may also be represented as a cloud server cluster.
The second disaster recovery response end is used for receiving and responding to the disaster recovery instruction received by the disaster recovery receiving end through the satellite communication link, so as to set the read-write state of each database in the data center 1 to be a read-only state. The first disaster recovery response end is directly connected with the disaster recovery instruction sent by the disaster recovery initiation end to set the read-write state of each database in the data center 2 to be writable. Through the arrangement, the switching of the main data center and the standby data center is realized. The setting result can be fed back to the disaster recovery initiating terminal as the response result of the disaster recovery instruction, and the feedback of the response result also needs to be by means of a satellite communication link.
In this embodiment, the first disaster recovery response end in the disaster recovery control system is configured to switch the read-write status of each database in the data center 2 to be writable, that is, upgrade the original backup data center to the main data center; the second disaster recovery response end is used for switching the read-write state of each database in the data center 1 to read-only, namely degrading the primary original primary data center to the backup data center, thereby realizing disaster recovery. In addition, the details of the embodiment and the technical effects that can be achieved are not described in detail in the present embodiment, and are not described in detail herein, referring to the embodiment shown in fig. 3 or fig. 4.
According to the embodiment shown in fig. 4, the disaster recovery control end may be in a cloud server cluster, where different control devices are configured to generate disaster recovery instructions for different types of databases, and similar to this, optionally, the first disaster recovery response end and the second disaster recovery response end may also be in a cloud server cluster, and are configured to respond to the disaster recovery instructions for different types of databases in the primary and secondary data centers, respectively. Fig. 6 is a schematic structural diagram of another disaster recovery control system according to an embodiment of the present invention. On the basis of the system shown in fig. 5, the second disaster recovery response end in the system may specifically include a first response device and a second response device, and the first disaster recovery response end may specifically include a third response device and a fourth response device.
As shown in the figure, the first response device and the second response device are both in the second area with the disaster recovery receiving end and the data center 1. The network addresses of the first and second responding devices are within a second predetermined network segment. The third response device and the fourth response device are located in the first area together with the disaster recovery initiation end, the disaster recovery control end and the data center 2.
The first response device deployed in the second area may respond to the disaster recovery instruction generated by the first management and control device and directed against the first type database in the data center 1, so as to set the first type database to be in a read-only state; the second response device may respond to the disaster recovery instruction generated by the second management and control device and directed to the second class database in the data center 1, so as to set the second class database to be in a read-only state.
For the disaster recovery instructions received by the disaster recovery receiving end and aiming at different types of databases, in order to ensure that the disaster recovery instructions can be correctly forwarded to corresponding response devices, optionally, the corresponding relation between the response devices and the domain name can be pre-established, optionally, the corresponding relation between the response devices and the paths can also be pre-established, and then the disaster recovery receiving end can forward the disaster recovery instructions to the corresponding first response devices or second response devices according to any corresponding relation.
In practice, in order to improve the forwarding efficiency of the disaster recovery instruction, optionally, the second disaster recovery response end may further include a first forwarding device, which is configured to perform a load balancing function on sending the disaster recovery instruction. Meanwhile, the first forwarding device can also pre-establish a corresponding relation between the first forwarding device and the domain name or the path, and send the disaster recovery instruction to the first response device or the second response device in the second disaster recovery response end by utilizing the corresponding relation.
Similar to the first response device and the second response device, the third response device deployed in the first area may respond to the disaster recovery instruction for the first type database in the backup data center generated by the first management and control device, so as to set the first type database to be in a writable state; the fourth response device may respond to the disaster recovery instruction generated by the second management and control device for the second class database in the backup data center, so as to set the second class database to be in a writable state. The disaster recovery instructions generated by the third response device and the fourth response device may not be transmitted by using the satellite communication link.
Optionally, in order to improve the forwarding efficiency of the disaster recovery instruction, the first disaster recovery response end may also optionally include a second forwarding device, which is used for performing a load balancing function on sending the disaster recovery instruction. Meanwhile, the second forwarding device can also pre-establish a corresponding relation between the second forwarding device and the domain name or the path, and forward the disaster recovery instruction to the corresponding third response device or fourth response device by utilizing the corresponding relation.
In this embodiment, the first disaster recovery response end and the second disaster recovery response end of the disaster recovery control system may each include a plurality of response devices, configured to respond to the corresponding disaster recovery instruction respectively, so as to set a read-write state of each type of database in the active/standby data center. The disaster recovery response end can also comprise forwarding equipment with load balancing capability, so that the quick and accurate switching of the read-write states of the database is realized, and the success rate of disaster recovery is improved. In addition, the details of the embodiments and the technical effects that can be achieved are not described in detail in the present embodiment, and are not described in detail herein.
Optionally, in the system of the embodiment shown in fig. 6, the setting of the read-write states of the first response device and the second response device on the database may be used as a response result of the disaster recovery instruction, where the response result may be considered as a disaster recovery notification message, and may be fed back to the disaster recovery initiator by means of the satellite communication link. In combination with the foregoing embodiments, in the feedback process, in order to avoid information irrelevant to disaster recovery from entering the satellite communication link and finally feeding back to the disaster recovery initiator, the second disaster recovery receiver may have a filtering function. When the first forwarding device is further disposed in the second disaster recovery response end, the response result may be sent to the first forwarding device first and then sent to the disaster recovery initiation end by means of the satellite communication link. The filtering capability of the disaster recovery receiving end can also be transferred to the first forwarding device in order to avoid that messages and/or instructions which are not related to disaster recovery enter the satellite communication link and are fed back to the disaster recovery initiating end.
Alternatively, with the disaster recovery control system provided in the above embodiments, each end and each device in the system may be deployed in different networks in the manner shown in fig. 7.
The disaster recovery control end, the disaster recovery initiation end and the first disaster recovery response end in the first area can be deployed in the first physical network. And the disaster recovery control end and the first disaster recovery response end can operate in an independent virtual private cloud network (Virtual Private Cloud, abbreviated as VPC) under the first physical network, and the disaster recovery initiating end operates in another VPC under the first physical network. The disaster recovery receiving end and the second disaster recovery response end in the second area may be deployed in the second physical network. And the disaster recovery receiving end and the second disaster recovery response end can respectively operate in different VPCs under the second physical network. Optionally, devices in different VPCs under the first physical network may communicate by means of a cloud enterprise network (Cloud Enterptise Network, CEN for short). Devices in different VPCs under the second physical network may also communicate by means of CEN. The CEN can be used for communication between the disaster recovery control end and the disaster recovery initiating end, and between the disaster recovery receiving end and the second disaster recovery responding end.
Optionally, a springboard machine may also be operated in the VPC operating with the disaster recovery control end and the first disaster recovery response end, where the springboard machine may perform initial configuration on the disaster recovery initiation end in response to configuration operation triggered by a user. In the operation process of the disaster recovery initiation terminal, the springboard machine can also respond to the detection operation triggered by the user to provide an operation platform for the user to conduct fault investigation on the disaster recovery initiation terminal. And in the same way, a springboard machine can be deployed in the VPC running with the second disaster recovery response end, and the springboard machine is used for carrying out initial configuration on the disaster recovery receiving end and providing a platform for fault detection.
Optionally, in the VPC running with the disaster recovery control end, the first disaster recovery response end and the trigger, the first control device and the second control device in the disaster recovery control end and the trigger may run in a sub-network of the VPC. The second forwarding device in the first disaster recovery response end may operate in another sub-network in the VPC, and the third response device and the fourth response device in the first disaster recovery response end may operate in one sub-network in the VPC.
Optionally, the second disaster recovery response end may specifically include a first response device, a second response device, and a first forwarding device, where the first response device and the second response device may operate in a sub-network in one VPC, and the first forwarding device operates in another sub-network in the VPC. And the springboard machine running in the same VPC with the second disaster recovery response end may also be in the same sub-network as the first forwarding device, as shown in fig. 7. Of course, alternatively, the springboard machine may be in the same sub-network as the first and second responding devices.
In the above embodiments, it is also mentioned that the disaster recovery instruction may be transmitted from the disaster recovery initiator to the disaster recovery receiver by means of the satellite communication link. Alternatively, this transmission process may be specifically: and the disaster recovery initiating terminal transmits the disaster recovery instruction to the satellite communication link by utilizing a first switch set deployed in the first physical network. The disaster recovery receiving end can also obtain a disaster recovery instruction from the satellite communication link by using the second switch cluster deployed in the second physical network. Correspondingly, the response result generated by the second disaster recovery response end also needs to be transmitted to the disaster recovery initiation end by using the second switch cluster and the first switch cluster successively.
It has been mentioned in the above embodiments that the satellite communication link between the disaster recovery initiator and the disaster recovery receiver needs to be implemented by means of satellites, alternatively more specifically, satellites and associated satellite ground stations. The first area and the second area where the disaster recovery initiating terminal and the disaster recovery receiving terminal are respectively located are both provided with satellite ground stations, and then the transmission process of the disaster recovery instruction can be as follows:
after the disaster recovery control end in the first area sends the disaster recovery instruction to the disaster recovery initiating end, the disaster recovery initiating end can further send the disaster recovery instruction to the satellite ground station 1 in the first area, and the satellite ground station 1 forwards the disaster recovery instruction to the satellite. At this time, the disaster recovery instruction can be forwarded to the satellite ground station 2 in the second area by means of the satellite communication link, and then the satellite ground station 2 forwards the disaster recovery instruction to the disaster recovery receiving end, and finally reaches the second disaster recovery response end.
In practice, the disaster recovery control end, the disaster recovery initiation end and the satellite ground station 1 in the first area are located in the same physical network, i.e. the first physical network, and in addition, other network devices for implementing disaster recovery instruction transmission may be deployed in the first physical network. In the first area, the disaster recovery instructions can be transmitted from the disaster recovery control terminal to the satellite ground station 1 by means of the network device.
Correspondingly, the satellite ground station 2 and the disaster recovery receiving end in the second area are also in the same physical network, namely, a second physical network, and network equipment is also deployed in the second physical network, so as to transmit the disaster recovery instruction from the satellite ground station to the disaster recovery receiving end. Wherein the network devices arranged in the first physical network and the second physical network are the same. And the process of transmitting the disaster recovery instruction from the disaster recovery control terminal to the second disaster recovery response terminal by means of the network device can participate in fig. 8.
The DPA in fig. 8 is a three-layer network consisting of a cluster of switches, including in particular a distribution layer switch (DSW), a convergence layer switch (PSW), and an access layer switch (ASW). Fig. 8 further includes a Gateway (GW), an access switch (LSW), an intranet access switch (CSW), and a router (ISR) for implementing interconnection between data centers, and an intra-bullet MC and an extra-bullet MC of the switches in the metropolitan area network of each of the first area and the second area, and the CSR is a router. The above-mentioned various network devices are commonly used to implement forwarding of disaster recovery instructions and response results.
Based on various network devices shown in fig. 8, for transmission of the disaster recovery instruction, after the disaster recovery instruction reaches the CSW in the first area, the disaster recovery instruction may be further transmitted to the satellite ground station 1 in the first area by using any one of the following paths: path 1: directly from the CSW to the satellite ground station 1; path 2: to satellite ground station 1 by means of intra-missile MC; path 3: is transmitted to the satellite ground station 1 by means of intra-missile MC, ISR. In practice, since the forwarding logic is simple, path 1 is generally selected to transmit the disaster recovery instruction.
In the above embodiments, when the main data center, that is, the data center 1 fails in a large area, the disaster recovery initiator may transmit the disaster recovery instruction by means of the satellite communication link and finally realize the switching between the main data center and the standby data center. In practice, after the failure of the primary data center is recovered, the disaster recovery control end can also generate a recovery instruction to recover the primary-backup relationship between the data centers. Alternatively, for transmission of the resume instruction, a satellite communication link may be used as well. Of course, since the failure of the main data center has been recovered at this time, that is, the physical communication link between the disaster recovery initiator and the disaster recovery receiver has also been recovered, the above recovery command may also be propagated by means of the physical communication link.
For easy understanding, the working process of the disaster recovery control system provided in each of the above embodiments will be described below with reference to a specific example.
It is assumed that both the data center 1 in the second area (primary data center) and the data center 2 in the first area (backup data center) are deployed with a database containing non-relational databases, namely TAIR database, and relational databases, namely MySQL. And a physical communication link and a satellite communication link can be pre-established between the primary and the secondary data centers. Normally, the data center 1 in the second area is used as main data, and data generated by the client can be written into various types of databases of the data center 1.
A physical communication link and a satellite communication link may be pre-established between the primary and secondary data centers. When the data center 1 operates normally, the primary and secondary data centers can perform data synchronization by using a physical communication link. And when the data center 1 has a small-range fault and the physical communication link is not disconnected, the physical communication link can be used for switching the main data center and the standby data center, so that disaster recovery is realized. However, when the data center 1 fails over a large area due to natural (such as earthquake) or artificial reasons, and the physical communication link is not available, the satellite communication link can be used to perform the switching between the active and standby data centers. It can be seen from the above that the switching of the primary and backup data centers is actually switching the read-write state of the database, i.e. the database in the primary data center is changed to the read-only state, and the database in the backup data center is changed to the writable state.
The respective operating states of the primary and secondary data centers can be monitored by independent monitoring equipment. When a large-scale fault of the primary data center is monitored, the specific switching process of the primary and the standby data centers can be understood by combining with fig. 9: the monitoring device may send a monitoring message indicating a large-area fault of the primary data center to the disaster recovery control end in the first area, that is, to the first control device and the second control device. The first management and control device and the second management and control device may generate a disaster recovery instruction (may be referred to as a first disaster recovery instruction for brevity of description to follow) for the TAIR database and a disaster recovery instruction (may be referred to as a second disaster recovery instruction) for the MySQL database, respectively, in response to the monitoring message. The first management and control device and the second management and control device operate in the same VPC, and meanwhile, a trigger jumper can be deployed in the VPC. The springboard machine is used for carrying out initial configuration on the disaster recovery initiating terminal and providing an operation platform for a user to carry out fault investigation when the disaster recovery initiating terminal fails.
For the transmission process of the first disaster recovery instruction, one direction is: according to the path shown in fig. 8, the first disaster recovery instruction may be transmitted to the disaster recovery initiation terminal, then transmitted to the satellite ground station 1 in the first area, and then sequentially transmitted to the satellite ground station 2 and the disaster recovery receiving terminal in the second area by means of the satellite communication link, and finally reaches the first response device in the second disaster recovery response terminal. The first response device responds to the first disaster recovery instruction to set the TAIR database in the data center 1 to be in a read-only state.
In this transmission process, the disaster recovery initiator may also filter the received information according to the preset first preset network segment, that is, only if the information sent by the device with the network address in the first preset network segment is considered as the information related to disaster recovery, the information not related to disaster recovery can enter the satellite communication link, and finally, the information not related to disaster recovery does not enter the satellite communication link and is transmitted to each device in the second area, that is, the disaster recovery failure caused by the occupation of irrelevant traffic of the satellite communication link is avoided. In practice, the network address of the device capable of sending information related to disaster tolerance is often set in the first preset network segment.
When the first disaster recovery instruction reaches the disaster recovery receiving end, in order to ensure the forwarding efficiency of the first disaster recovery instruction, the first forwarding device with load balancing capability can be used for forwarding the first disaster recovery instruction to the first response device. Furthermore, as different databases need to respond to the corresponding disaster recovery instructions, in order to ensure the accuracy of forwarding, the first forwarding device may also pre-establish a correspondence between itself and the domain name or the path, and implement forwarding of the first disaster recovery instructions by using the correspondence.
For the transmission of the first disaster recovery instruction, the other direction is: the first disaster recovery instruction may be sent to a first disaster recovery response end also located in the first area, so that a third response device in the first disaster recovery response end responds to the first disaster recovery instruction, so as to set a TAIR database in the data center 2 to be in a writable state. Optionally, in order to improve forwarding efficiency, a second forwarding device may be disposed in the first area, and the first disaster recovery instruction may be sent to the third response device according to a pre-established correspondence between the second forwarding device and the domain name or the path.
The second disaster recovery instruction may also have two transmission directions, that is, to the second response device and to the fourth response device, and the transmission processes in these two directions are the same as those of the first disaster recovery instruction, which will not be described herein.
According to the above manner, after the first response device and the second response device respond to the first disaster recovery instruction and the second disaster recovery instruction respectively, the TAIR database and the MySQL database in the data center 1 are both in a read-only state, and after the third response device and the fourth response device respond to the first disaster recovery instruction and the second disaster recovery instruction respectively, each database in the data center 2 is in a writable state, and at this time, the switching of the active and standby data centers is completed.
It is easy to understand that after the read-write states of the databases in the data center 1 are switched to the read-only state, the first response device and the second response device can also feed back the response result of successful switching to the disaster recovery initiator through the satellite communication link. The first forwarding device can perform load balancing and also can perform information filtering by using a second preset network segment which is preset, so that a response result related to disaster tolerance is sent to a disaster tolerance receiving end and fed back to a disaster tolerance initiating end by means of a satellite communication link, and information which is generated by each device in a second area and is not related to disaster tolerance cannot enter the satellite communication link and is sent to the disaster tolerance initiating end. Similarly, after the read-write states of the databases in the data center 2 are switched to the writable state, the third response device and the fourth response device can also feed back the response result of successful switching to the disaster recovery initiator. The response result can be forwarded after load balancing by the second forwarding device.
Alternatively, in order to improve the success rate of disaster recovery, a plurality of ends in the disaster recovery control system may be provided.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (14)
1. A disaster recovery control system, comprising: the disaster recovery control terminal is deployed in the first area, and the network address of the disaster recovery control terminal is in a first preset network segment;
the disaster recovery control end is used for responding to the faults of the main data center and generating disaster recovery instructions;
the disaster recovery initiating terminal is configured to receive first information generated by each device in the first area, where the first information includes the disaster recovery instruction; filtering the first information according to the first preset network segment to obtain the disaster recovery instruction; forwarding the disaster recovery instruction to the disaster recovery receiving end according to a satellite communication link between the disaster recovery initiating end and the disaster recovery receiving end;
the disaster recovery receiving end is used for forwarding the disaster recovery instruction to the disaster recovery response end; forwarding a response result of the disaster recovery instruction to the disaster recovery initiating terminal, wherein the response result reflects a switching result of the main and standby data centers;
the disaster recovery response end is used for responding to the disaster recovery instruction and generating the response result.
2. The system of claim 1, wherein the disaster recovery initiator is configured to forward a disaster recovery notification message sent by a device having a network address in the first preset network segment to the disaster recovery receiver.
3. The system of claim 1, wherein the network address of the disaster recovery response side is within a second predetermined network segment.
4. The system of claim 1, wherein the disaster recovery management and control terminal specifically comprises: the first management and control device and the second management and control device;
the first management and control equipment is used for generating disaster recovery instructions aiming at a first type of database in the main data center;
the second management and control equipment is used for generating disaster recovery instructions aiming at a second class database in the main data center.
5. The system of claim 1, wherein the disaster recovery response side specifically includes: the first disaster recovery response end and the second disaster recovery response end;
the disaster recovery initiating terminal, the first disaster recovery responding terminal and the backup data center are deployed in a first area; the disaster recovery receiving end, the second disaster recovery response end and the main data center are deployed in a second area.
6. The system of claim 5, wherein the first disaster recovery response side is configured to set a database in the backup data center to a writable state in response to the disaster recovery instruction; sending the writable state as the response result to the disaster recovery control end;
The second disaster recovery response end is configured to set a database in the main data center to be in a read-only state in response to the disaster recovery instruction; and sending the read-only state to the disaster recovery receiving end as the response result.
7. The system of claim 6, wherein the second disaster recovery response side specifically includes: a first response device and a second response device;
the first response device is configured to respond to a disaster recovery instruction corresponding to a first type database in the main data center, and set the first type database to be in a read-only state;
the second response device is configured to set the second type database to a read-only state in response to a disaster recovery instruction corresponding to the second type database in the main data center.
8. The system of claim 7, wherein the disaster recovery receiving end is configured to send the disaster recovery instruction to the corresponding first response device or the second response device according to a domain name or a path in the disaster recovery instruction.
9. The system of claim 7, wherein the second disaster recovery response side further comprises: and the forwarding device is used for sending the disaster recovery instruction to the corresponding first response device or the second response device according to the domain name or the path in the disaster recovery instruction.
10. The system of claim 9, wherein the forwarding device is further configured to forward, to the disaster recovery receiving end, a disaster recovery notification message sent by a device whose network address belongs to a second preset network segment, where the disaster recovery notification message includes the response result generated by the first response device and/or the second response device, and the network addresses of the first response device and the second response device respectively belong to the second preset network segment.
11. The system of claim 5, wherein the disaster recovery management and control end and the disaster recovery initiation end operate in different private cloud networks under a first physical network corresponding to the first area;
the disaster recovery receiving end and the second disaster recovery response end operate in different private cloud networks in a second physical network of the second area.
12. The system of claim 11, wherein a trigger is further deployed in the private cloud network in which the disaster recovery control end and the second disaster recovery response end operate respectively;
the springboard machine is operated in the same private cloud network with the disaster recovery control end and is used for responding to detection operation triggered by a user to detect the working state of the disaster recovery initiation end;
And the springboard machine which runs in the same private cloud network with the second disaster recovery response end is used for responding to the detection operation triggered by the user and detecting the working state of the disaster recovery receiving end.
13. The system of claim 12, wherein a first response device and a second response device in the second disaster recovery response end operate in a first subnetwork in a private cloud network corresponding to the second disaster recovery response end;
and the forwarding equipment and the springboard machine in the second disaster recovery response end operate in a second sub-network in the private cloud network corresponding to the second disaster recovery response end.
14. The system of claim 11, wherein the disaster recovery initiator is configured to transmit the disaster recovery instructions to a satellite communication link using a first switch cluster, the first switch cluster being in the first physical network;
the disaster recovery receiving end is configured to receive the disaster recovery instruction from the satellite communication link by using a second switch cluster, where the second switch cluster operates in the second physical network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210614956.5A CN115086150B (en) | 2022-05-31 | 2022-05-31 | Disaster recovery control system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210614956.5A CN115086150B (en) | 2022-05-31 | 2022-05-31 | Disaster recovery control system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115086150A CN115086150A (en) | 2022-09-20 |
| CN115086150B true CN115086150B (en) | 2023-12-29 |
Family
ID=83248727
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210614956.5A Active CN115086150B (en) | 2022-05-31 | 2022-05-31 | Disaster recovery control system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115086150B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004061665A2 (en) * | 2002-12-30 | 2004-07-22 | At & T Corporation | Service continuity data backup of network elements |
| CN107241430A (en) * | 2017-07-03 | 2017-10-10 | 国家电网公司 | A kind of enterprise-level disaster tolerance system and disaster tolerant control method based on distributed storage |
| WO2017198144A1 (en) * | 2016-05-20 | 2017-11-23 | 中兴通讯股份有限公司 | Disaster tolerance method for iptv system, and iptv disaster tolerance system |
| CN108365985A (en) * | 2018-02-07 | 2018-08-03 | 深圳壹账通智能科技有限公司 | A kind of cluster management method, device, terminal device and storage medium |
| CN108683450A (en) * | 2018-05-15 | 2018-10-19 | 国网上海市电力公司 | A kind of Synergistic method holding disconnected satellite network and power private network late based on appearance |
| CN113890850A (en) * | 2020-07-01 | 2022-01-04 | 阿里巴巴集团控股有限公司 | Route disaster tolerance system and method |
| CN113938395A (en) * | 2021-08-30 | 2022-01-14 | 阿里巴巴（中国）有限公司 | Data analysis method, system, device and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10528433B2 (en) * | 2016-04-01 | 2020-01-07 | Acronis International Gmbh | Systems and methods for disaster recovery using a cloud-based data center |
| US11048598B2 (en) * | 2019-03-28 | 2021-06-29 | Sap Se | Enhanced disaster recovery procedure of applications in a cloud environment |
-
2022
- 2022-05-31 CN CN202210614956.5A patent/CN115086150B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004061665A2 (en) * | 2002-12-30 | 2004-07-22 | At & T Corporation | Service continuity data backup of network elements |
| WO2017198144A1 (en) * | 2016-05-20 | 2017-11-23 | 中兴通讯股份有限公司 | Disaster tolerance method for iptv system, and iptv disaster tolerance system |
| CN107241430A (en) * | 2017-07-03 | 2017-10-10 | 国家电网公司 | A kind of enterprise-level disaster tolerance system and disaster tolerant control method based on distributed storage |
| CN108365985A (en) * | 2018-02-07 | 2018-08-03 | 深圳壹账通智能科技有限公司 | A kind of cluster management method, device, terminal device and storage medium |
| CN108683450A (en) * | 2018-05-15 | 2018-10-19 | 国网上海市电力公司 | A kind of Synergistic method holding disconnected satellite network and power private network late based on appearance |
| CN113890850A (en) * | 2020-07-01 | 2022-01-04 | 阿里巴巴集团控股有限公司 | Route disaster tolerance system and method |
| CN113938395A (en) * | 2021-08-30 | 2022-01-14 | 阿里巴巴（中国）有限公司 | Data analysis method, system, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115086150A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102439903B (en) | Method, device and system for realizing disaster-tolerant backup | |
| US6112249A (en) | Non-disruptively rerouting network communications from a secondary network path to a primary path | |
| US6377374B1 (en) | Method apparatus and computer program product for optical network restoration | |
| US5914798A (en) | Restoration systems for an optical telecommunications network | |
| US7233568B2 (en) | System and method for selection of redundant control path links in a multi-shelf network element | |
| CN100449521C (en) | Restoration mechanism for network topologies | |
| JPH08307457A (en) | Method and equipment for response routing control | |
| WO1997024901A9 (en) | Restoration systems for an optical telecommunications network | |
| CA2441470A1 (en) | High availability packet forwarding apparatus and method | |
| US20030233473A1 (en) | Method for configuring logical connections to a router in a data communication system | |
| CN108075825B (en) | SDN-based multi-controller failure processing method for space-based information network | |
| CN102710520B (en) | Method and device for backing up lonworks network service (LNS) | |
| CN115086150B (en) | Disaster recovery control system | |
| CN110830310B (en) | Cross-data-center disaster backup method and BRAS system | |
| CN104125079A (en) | Method and device for determining double-device hot-backup configuration information | |
| CN106027313B (en) | Network link disaster tolerance system and method | |
| JP7103408B2 (en) | Multicast traffic transmission method, related equipment and computer readable storage medium | |
| JP6457962B2 (en) | Node device and redundant network communication method | |
| Tivig et al. | Creating scalable distributed control plane in sdn to rule out the single point of failure | |
| RU2667806C2 (en) | Pseudo-wire (pw) dual-homing protection switching method and system | |
| CN111414411A (en) | High availability database system | |
| KR100438066B1 (en) | Method for switching Plural LAN in network system | |
| CN103607294A (en) | Recovery method of network division, equipment and system thereof | |
| CN115396385B (en) | Method and device for quickly recovering service of stack switch and computing equipment | |
| JPH10243007A (en) | Optical transmission line fault recovery method and node equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |