CN111464332A - Disaster recovery method, device and equipment - Google Patents
Disaster recovery method, device and equipment Download PDFInfo
- Publication number
- CN111464332A CN111464332A CN202010150986.6A CN202010150986A CN111464332A CN 111464332 A CN111464332 A CN 111464332A CN 202010150986 A CN202010150986 A CN 202010150986A CN 111464332 A CN111464332 A CN 111464332A
- Authority
- CN
- China
- Prior art keywords
- data
- class
- domain name
- service
- local
- 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.)
- Granted
Links
Images
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/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Abstract
The invention discloses a disaster recovery method, a device and equipment, wherein the method comprises the following steps: receiving target service data synchronized by other data centers; when the service center central systems of other data centers are abnormal, electing a candidate data center from the data center with the normal service center central system; when the candidate data center is elected, the domain name resolution system is triggered to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system, so that the local business class intermediate system provides target business data for the first terminal of the geographic area corresponding to the abnormal business class intermediate system.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a disaster recovery method, apparatus, and device.
Background
At present, for the purpose of disaster recovery, an enterprise generally constructs at least two data centers, including a main data center and a plurality of backup data centers, and under normal conditions, the main data center undertakes core services of a user, and the backup data centers do not undertake or undertake a small amount of non-core work, and have fewer processing tasks. When a disaster occurs, such as the main data center is down, the backup data center can quickly restore data and application according to the backup content, and take the task of the original main data center, so that the loss of users caused by the disaster is reduced.
However, because the disaster is a small-probability event, and a primary-secondary or primary-secondary mode is adopted, the backup data center can only play a role when the disaster occurs, and with the improvement of the disaster recovery construction standard of enterprises, backup resources and capital are more and more invested and cannot be reused, thereby causing waste.
Disclosure of Invention
Embodiments of the present invention provide a disaster recovery method, apparatus, and device, so as to solve a problem in the prior art that some data centers, such as a backup data center, are used only when a disaster occurs, thereby causing resource waste.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, a disaster recovery method is provided, which is applied to a data center in a multi-activity disaster recovery system, where the multi-activity disaster recovery system includes a domain name resolution system and multiple data centers, the data center at least includes a foreground system and a service class foreground system, and the service class foreground system includes service data having a preset corresponding relationship with a pre-divided geographic area;
the method comprises the following steps:
receiving target service data synchronized by other data centers;
when the service center central systems of the other data centers are abnormal, electing candidate data centers from the data centers with normal service center central systems;
when the candidate data center is selected, the domain name resolution system is triggered to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system, so that the local business class intermediate system provides the target business data for the first terminal of the geographic area corresponding to the abnormal business class intermediate system.
In a second aspect, a disaster recovery device is provided, which is applied to a data center in a multi-activity disaster recovery system, where the multi-activity disaster recovery system includes a domain name resolution system and multiple data centers, the data center at least includes a foreground system and a service class central system, and the service class central system includes service data having a preset corresponding relationship with a pre-divided geographic area;
the device comprises:
the receiving module is used for receiving the target service data synchronized by other data centers;
the election module is used for electing candidate data centers from the data centers with normal business center systems when the business center systems of other data centers are abnormal;
and the sending module is used for triggering the domain name resolution system to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system when the candidate data center is elected, so that the local business class intermediate system provides the target business data for the first terminal of the geographical area corresponding to the abnormal business class intermediate system.
In a third aspect, a disaster recovery device is provided, the terminal device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the method according to the first aspect.
In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of the method according to the first aspect.
In the embodiment of the invention, the data center can receive target service data synchronized by other data centers, when the service class central station system of other data centers is abnormal, the candidate data center is selected from the data centers with normal service class central station systems, if the candidate data center is selected, the domain name resolution system can be triggered to point the domain name of the abnormal service class central station system to the IP address of the local service class central station system by sending the IP address of the local service class central station system to the domain name resolution system, so that the local service class central station system provides the target service data for the first terminal of the geographical area corresponding to the abnormal service class central station system.
As can be seen from the above, in this embodiment, a corresponding geographic area may be set in advance for service data of a station system in a service class of different data centers, so that different data centers may provide service data for terminals in different geographic areas based on respective service data. Therefore, the data centers in the embodiment can be used under normal conditions, so that the problem of resource waste caused by the fact that some data centers are only used when a disaster occurs in the prior art is effectively solved.
In addition, the embodiment can also perform "unitized" processing on the data center, that is, the data center is divided into different unit parts, such as a foreground system, a business class middle system, and the like, and business data in the business class middle system is divided into business data respectively corresponding to different geographical areas, and the like, because the divided unit parts are not interfered with each other, when some unit parts are abnormal, only the abnormal unit parts are subjected to corresponding disaster recovery processing, such as modifying the corresponding domain name-directed IP address, and the like, without performing disaster recovery processing on the whole data center, thereby greatly reducing the disaster recovery processing speed and resource consumption.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
fig. 1 is a schematic flow chart of a disaster recovery method according to an embodiment of the present invention;
fig. 2 is a schematic block diagram of a disaster recovery device according to an embodiment of the present invention;
fig. 3 is a schematic hardware structure diagram of a disaster recovery device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to the specific embodiments of the present invention and the accompanying drawings. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a schematic flow chart of a disaster recovery method according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step 102: and receiving the target service data synchronized by other data centers.
Step 104: and when the service center central system of other data centers is abnormal, selecting a candidate data center from the data centers with normal service center central systems.
Step 106: when the candidate data center is selected, the domain name resolution system is triggered to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system, so that the local business class intermediate system provides the target business data for the first terminal of the geographic area corresponding to the abnormal business class intermediate system.
In the embodiment of the present invention, the multi-activity disaster recovery system may include a domain name resolution system and a plurality of data centers, where the data centers may include at least a foreground system and a service-class middle-station system, and the domain name resolution system may be configured to direct a domain name of the foreground system and a domain name of the service-class middle-station system to respective corresponding IP addresses.
The foreground system can be used for providing services for the terminal, and the service type middle station system can be used for providing corresponding service support for the foreground system. In the multi-activity disaster recovery system, foreground systems configured by different data centers can be the same, and business class foreground systems configured by different data centers can be different. In one embodiment, the service class base system may include service data having a preset correspondence with a pre-divided geographic area, and the geographic areas corresponding to the service data of the service class base systems in different service classes are different.
In one example, the foreground system may be comprised of a front-end or reverse proxy, a foreground unified API (application programming Interface) gateway, and foreground applications. The front end can be responsible for providing a system access interface to the outside; the reverse proxy may be responsible for proxy third party interfacing; the foreground unified gateway is a unified inlet of foreground application and can realize functions of authority verification, monitoring, caching, service routing and the like; the foreground application is responsible for finishing the organization of the request information and calling the middle station system to finish the response.
In the embodiment of the invention, foreground systems of different data centers can provide indiscriminate external services. For example, two data centers may be provided and geographically divided into southern provinces and northern provinces. Then, terminals of a plurality of provinces in the south can be default-drained to a foreground system deployed in a south data center through a domain name resolution system, and terminals of a plurality of provinces in the north can be default-drained to a foreground system deployed in a north data center through the domain name resolution system.
When the foreground system is deployed, the terminal users can be divided into internet users, internal users and third-party docking users according to access sources, and three safe connection areas are designed according to the access sources: a DMZ (thinned zone) zone, an inline zone, and an extralink zone. If the user is an internet user, the foreground system has a public network domain name and can be accessed after being analyzed by an internet DNS (domain name system), so that the foreground system can be deployed in the DMZ; if the System is an intranet user, the System has an intranet Domain Name, and can be accessed after being analyzed by an internal DNS (Domain Name System), so that a foreground System can be deployed in an intranet area; if the user is a third party docking user, the user generally uses IP to directly access due to the mutual domain name recognition problem of the two parties, so that the foreground system can be deployed in the external connection area.
In an embodiment of the present invention, the data center of the multi-disaster recovery system may further include a base class middlebox system, where the base class middlebox system may include base data having a preset relationship with a pre-divided geographic area. The base class middlebox system can be used to provide corresponding base data support to the foreground system.
In another embodiment of the present invention, the data center of the multi-activity disaster recovery system may further include a data support class middle system, where the data support class middle system may include service support data generated according to service data in the service class middle system, such as service statistical data generated by performing statistics on the service data. The data support class of the desktop system can be used to provide data support of the corresponding support class to the desktop system.
In the embodiment of the present invention, any data center in the multi-active disaster recovery system may receive target service data synchronized by other data centers in the multi-active disaster recovery system, and correspondingly, any data center in the multi-active disaster recovery system may also synchronize local service data to other data centers in the multi-active disaster recovery system, so as to implement that service data of all data centers in the multi-active disaster recovery system are the same.
In the above embodiment, when receiving the target service data synchronized by the other data centers in the multi-active disaster recovery system, any data center in the multi-active disaster recovery system may also receive the target basic data synchronized by the other data centers, and correspondingly, the any data center may also synchronize the local basic data to the other data centers, so as to implement that the basic data of all the data centers in the multi-active disaster recovery system are the same.
It should be noted that, since the service support data in the data support class intermediate system can be generated according to the service data, when synchronizing data between the data centers of the multi-activity disaster recovery system, only the service data and the basic data can be synchronized. Any data center can then generate corresponding business support data from the business data synchronized by the other data centers.
As can be seen from the above, in the data synchronization between the data centers in this embodiment, all data may not be synchronized, but the data is first divided into basic data, service data, and service support data, and then the basic data and the service data are synchronized, instead of synchronizing the service support data that has a large data volume and can be generated by the service data, so that a large amount of data traffic may be saved.
In one embodiment, the multi-disaster recovery system may be provided with two data centers, such as a south data center and a north data center, wherein the south data center and the north data center may respectively serve terminals in a geographic area that is geographically south of each other and a geographic area that is geographically north of each other. The south data center and the north data center can mutually synchronize respective basic data and service data, and generate service support data according to the service data synchronized by the opposite side, at the moment, the two sides can mutually be regarded as 'standby data centers' of the opposite side, namely, the two sides can not only currently provide service for the terminal of the corresponding geographic area, but also serve as 'standby data centers' to replace the opposite side to provide service for the terminal of the corresponding geographic area of the opposite side when the opposite side has problems.
When the service class central systems of other data centers in the multi-activity disaster tolerance system are abnormal, the current data center can select candidate data centers from the data centers with normal service class central systems, wherein the other data centers with normal service class central systems in the multiple disaster tolerance systems can participate in the selection process simultaneously and respectively select corresponding candidate data centers.
In an example, when a candidate data center is elected from a data center with a normal service center system, a data center with a normal service center system closest to a data center with an abnormal service center system in the service class may be elected as the candidate data center, or a data center with the most idle data center in a data center with a normal service center system in the service class may be elected as the candidate data center, which is not limited in this embodiment.
When the candidate data center is elected, the current data center can send the IP address of the local service type middle station system to the domain name resolution system so as to trigger the domain name resolution system to point the domain name of the abnormal service type middle station system to the IP address of the local service type middle station system of the current data center, so that the local service type middle station system can provide the target service data for the first terminal of the geographic area corresponding to the abnormal service type middle station system.
In one example, a corresponding independent domain name may be set for each corresponding geographic area in the service class desktop system, and the service class desktop system deployed to the geographic area may be resolved using an a (Address) record. Therefore, when the service class middlebox system changes, the domain name resolution system can correspondingly direct the a record resolution to a new service class middlebox system, such as the selected service class middlebox system of the data center. In the scheme, the local data center can pre-load the service type middling station system of the remote data center.
In this embodiment, the geographic area corresponding to the service class central system may be a geographic area corresponding to service data of the service class central system. When the candidate center is elected, the service class middling system of the current data center may temporarily "replace" the abnormal service class middling system to provide a service, such as the target service data, for the first terminal served by the abnormal service class middling system before the abnormality. The target service data required by the first terminal served by the abnormal service class middling system is obtained by the current data center through the target service data synchronized by the abnormal service class middling system in advance, so that the current data center can continuously provide the target service data to the corresponding first terminal in the abnormal service class middling system abnormal process.
It should be noted that, because the current data center is always in an operating state, when an abnormality occurs, for example, a domain name system in a service class is abnormal, only the resolution rule of the corresponding domain name, for example, the domain name resolution rule of the platform system in the abnormal service class, needs to be adjusted, and the corresponding traffic of the data center in the abnormal service class, for example, the traffic corresponding to the platform system in the service class, can be directed to the current data center, thereby implementing disaster backup switching RTO (Recovery time objective) and RPO (Recovery Point objective) at the minute level, and avoiding the occurrence of the situation of the RTO time and the RPO time caused by the longer starting process of the backup data center in the current disaster backup scheme.
In the embodiment of the present invention, since the service support data is generated according to the service data, when the service class middle station system changes, the service support class middle station system also changes along with the service class middle station system. That is, when the service class middle station system is abnormal, the elected data center corresponding to the abnormal service class middle station system may trigger the domain name resolution system to point the domain name of the service support class middle station system of the data center of the abnormal service class middle station system to the IP address of the local service support class middle station system by sending the IP address of the local service support class middle station system to the domain name resolution system, so that the local service support class middle station system provides the target service support data generated according to the target service data for the terminal in the geographic region corresponding to the abnormal service class middle station system.
Correspondingly, in the embodiment of the present invention, when a second terminal in a geographic area corresponding to a station system in a base class of another data center appears in a geographic area corresponding to the data center, the domain name resolution system may be triggered to point an access domain name, when the second terminal accesses the station system in the base class, to an IP address of the station system in the local base class by sending the IP address of the station system in the local base class to the domain name resolution system, so that the station system in the local base class provides target base data for the second terminal.
When the location of the terminal changes, for example, when the terminal moves from a geographic area in charge of a base type middleware system of a certain data center to a geographic area in charge of a base type middleware system of another data center, the terminal can be provided with a base data service according to the base type middleware system corresponding to the geographic area where the terminal is currently located. Because the basic type middle station system of the data center is always in the running state, when the terminal moves, the switching of the basic type middle station system can be rapidly carried out, so that the switching time can be effectively shortened, and better experience is brought to a user.
Correspondingly, when the base type middle station system is abnormal, if the distance between the current data center and the third terminal corresponding to the abnormal base type middle station system is smaller than the distance between the third terminal and the normal data center of the other base type middle station systems, the domain name resolution system can be triggered to point the access domain name when the third terminal accesses the base type middle station system to the IP address of the local base type middle station system by sending the IP address of the local base type middle station system of the current data center to the domain name resolution system, so that the local base type middle station system provides target base data for the target terminal. That is, when the service class central station system is abnormal, the data center which is closest to the abnormal service class central station system and has a normal service class central station system can be determined, and the service class central station system of the data center is used to provide basic data service for the terminal corresponding to the abnormal service class central station system, that is, the third terminal.
In an embodiment of the present invention, after receiving target service data synchronized by other data centers in the multi-activity disaster recovery system, the current data center may further determine service data with a historical hit rate higher than a threshold from the target service data, and preload the service data with the historical hit rate higher than the threshold, so as to improve a switching speed of the service class intermediate system.
In another embodiment of the present invention, the station system in the service class of the current data center may also retransmit the message in the message queue. Since the messages in the message queue cannot be copied to the disaster recovery environment during the disaster recovery handover, the messages must be retransmitted at the application layer. Therefore, after receiving the sequence number of the successfully received message sent by the message receiver, the current data center can determine the unsuccessfully sent message in the message queue according to the received sequence number, and resend the unsuccessfully sent message in the message queue.
In another embodiment of the present invention, when the data center with the abnormal platform system in the business class is the data center currently processing the timing processing task, the data center for processing the timing processing task may be selected from the data centers with the normal platform system in the business class. The data center selected for processing the timed machining task may then receive the timed machining task and process the received timed machining task.
In the embodiment of the invention, the data center can receive target service data synchronized by other data centers, when the service class central station system of other data centers is abnormal, the candidate data center is selected from the data centers with normal service class central station systems, if the candidate data center is selected, the domain name resolution system can be triggered to point the domain name of the abnormal service class central station system to the IP address of the local service class central station system by sending the IP address of the local service class central station system to the domain name resolution system, so that the local service class central station system provides the target service data for the first terminal of the geographical area corresponding to the abnormal service class central station system.
As can be seen from the above, in this embodiment, a corresponding geographic area may be set in advance for service data of a station system in a service class of different data centers, so that different data centers may provide service data for terminals in different geographic areas based on respective service data. Therefore, the data centers in the embodiment can be used under normal conditions, so that the problem of resource waste caused by the fact that some data centers are only used when a disaster occurs in the prior art is effectively solved.
In addition, the embodiment can also perform "unitized" processing on the data center, that is, the data center is divided into different unit parts, such as a foreground system, a business class middle system, and the like, and business data in the business class middle system is divided into business data respectively corresponding to different geographical areas, and the like, because the divided unit parts are not interfered with each other, when some unit parts are abnormal, only the abnormal unit parts are subjected to corresponding disaster recovery processing, such as modifying the corresponding domain name-directed IP address, and the like, without performing disaster recovery processing on the whole data center, thereby greatly reducing the disaster recovery processing speed and resource consumption.
Corresponding to the above disaster recovery method, an embodiment of the present invention further provides a disaster recovery device, which is applied to a data center in a multi-active disaster recovery system, where the multi-active disaster recovery system includes a domain name resolution system and a plurality of data centers, the data center includes at least a foreground system and a business class foreground system, the business class foreground system includes business data having a preset corresponding relationship with a pre-divided geographic area, fig. 2 is one of schematic diagrams of module compositions of the disaster recovery device provided in an embodiment of the present invention, and as shown in fig. 2, the disaster recovery device includes:
a receiving module 2010, configured to receive target service data synchronized by other data centers;
the election module 2020 is configured to elect a candidate data center from a data center in which the service class center system is normal when the service class center system of the other data center is abnormal;
a sending module 2030, configured to, when the candidate data center is elected, send an IP address of a local service class middle station system to the domain name resolution system to trigger the domain name resolution system to point the domain name of the abnormal service class middle station system to the IP address of the local service class middle station system, so that the local service class middle station system provides the target service data for the first terminal in the geographic area corresponding to the abnormal service class middle station system.
Optionally, the data center further includes a basic class middlebox system, where the basic class middlebox system includes basic data having a preset corresponding relationship with a pre-divided geographic area;
after the sending the IP address of the intermediate system in the local service class to the domain name resolution system to trigger the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the apparatus further includes:
the first synchronization module 2040 is configured to receive target basic data synchronized by other data centers;
a first triggering module 2050, configured to, when a second terminal in a geographic area corresponding to a base type middlewares of other data centers appears in a corresponding geographic area, send an IP address of a local base type middlewares to the domain name resolution system to trigger the domain name resolution system to point, to the IP address of the local base type middlewares, an access domain name obtained when the second terminal accesses the base type middlewares, so that the local base type middlewares provide the target base data for the second terminal.
Optionally, after the sending, to the domain name resolution system, the IP address of the local base class middlebox system to trigger the domain name resolution system to point, to the IP address of the local base class middlebox system, the access domain name when the target terminal accesses the local base class middlebox system, the apparatus further includes:
a second triggering module 2060, configured to, when the distance from the third terminal is smaller than the distance from the third terminal to the data center where the other basic class intermediate station systems are normal, send the IP address of the local basic class intermediate station system to the domain name resolution system to trigger the domain name resolution system to point the access domain name, when the third terminal accesses the basic class intermediate station system, to the IP address of the local basic class intermediate station system, so that the local basic class intermediate station system provides the target basic data for the target terminal, where the basic class intermediate station system corresponding to the third terminal is abnormal.
Optionally, the data center further includes a data support class-type platform system, where the data support class-type platform system includes service support data generated according to service data in the service class-type platform system, and after receiving first service data synchronized by another data center, the apparatus further includes:
a generating module 2070, configured to generate corresponding target service support data according to the target service data;
after the sending the IP address of the intermediate system in the local service class to the domain name resolution system to trigger the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the apparatus further includes:
a third triggering module 2080, configured to trigger the domain name resolution system to direct the domain name of the service support class intermediate system of the data center of the abnormal service class intermediate system to the IP address of the local service support class intermediate system by sending the IP address of the local service support class intermediate system to the domain name resolution system, so that the local service support class intermediate system provides the target service support data for the first terminal in the geographic area corresponding to the abnormal service class intermediate system.
Optionally, after the service class of the other data center is abnormal, the apparatus further includes:
the first processing module 2090 is configured to select, when the data center with the abnormal platform system in the business class is a data center currently processing the timing processing task, a data center for processing the timing processing task from the data center with the normal platform system in the business class;
the second processing module 2100 is configured to receive the scheduled processing task and process the received scheduled processing task when selected as a data center for processing the scheduled processing task.
Optionally, after receiving the target service data synchronized by the other data centers, the apparatus further includes:
a determining module 2110 for determining, from the target traffic data, traffic data with a history hit rate higher than a threshold;
and the preloading module 2120 is configured to preload the service data with the history hit rate higher than the threshold.
Optionally, after the sending the IP address of the local service class intermediate system to the domain name resolution system to trigger the domain name resolution system to point the domain name of the abnormal service class intermediate system to the IP address of the local service class intermediate system, the apparatus further includes:
a first retransmission module 2130, configured to receive a sequence number of a successfully received message sent by a message receiver;
the second retransmission module 2140 is configured to determine, according to the received sequence number, an unsuccessfully sent message in the message queue, and resend the unsuccessfully sent message in the message queue.
Optionally, before the abnormality of the central system in the service class of the other data center, the apparatus further includes:
and a second synchronization module 2150, configured to synchronize local service data with other data centers.
In the embodiment of the invention, the data center can receive target service data synchronized by other data centers, when the service class central station system of other data centers is abnormal, the candidate data center is selected from the data centers with normal service class central station systems, if the candidate data center is selected, the domain name resolution system can be triggered to point the domain name of the abnormal service class central station system to the IP address of the local service class central station system by sending the IP address of the local service class central station system to the domain name resolution system, so that the local service class central station system provides the target service data for the first terminal of the geographical area corresponding to the abnormal service class central station system.
As can be seen from the above, in this embodiment, a corresponding geographic area may be set in advance for service data of a station system in a service class of different data centers, so that different data centers may provide service data for terminals in different geographic areas based on respective service data. Therefore, the data centers in the embodiment can be used under normal conditions, so that the problem of resource waste caused by the fact that some data centers are only used when a disaster occurs in the prior art is effectively solved.
In addition, the embodiment can also perform "unitized" processing on the data center, that is, the data center is divided into different unit parts, such as a foreground system, a business class middle system, and the like, and business data in the business class middle system is divided into business data respectively corresponding to different geographical areas, and the like, because the divided unit parts are not interfered with each other, when some unit parts are abnormal, only the abnormal unit parts are subjected to corresponding disaster recovery processing, such as modifying the corresponding domain name-directed IP address, and the like, without performing disaster recovery processing on the whole data center, thereby greatly reducing the disaster recovery processing speed and resource consumption.
Corresponding to the above disaster recovery method, an embodiment of the present invention further provides a disaster recovery device, and fig. 3 is a schematic diagram of a hardware structure of the disaster recovery device according to an embodiment of the present invention.
The disaster recovery device may be a terminal device or a server for disaster recovery provided in the above embodiment.
Disaster recovery devices may vary significantly depending on configuration or performance, and may include one or more processors 301 and memory 302, where the memory 302 may store one or more stored applications or data. Memory 302 may be, among other things, transient storage or persistent storage. The application stored in the memory 302 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for the disaster recovery device. Still further, the processor 301 may be configured to communicate with the memory 302 to execute a series of computer-executable instructions in the memory 302 on the disaster recovery device. The disaster recovery device may also include one or more power sources 303, one or more wired or wireless network interfaces 304, one or more input-output interfaces 305, one or more keyboards 306.
In particular, in this embodiment, the disaster recovery device includes a memory and one or more programs, where the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the disaster recovery device, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:
receiving target service data synchronized by other data centers;
when the service center central systems of the other data centers are abnormal, electing candidate data centers from the data centers with normal service center central systems;
when the candidate data center is selected, the domain name resolution system is triggered to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system, so that the local business class intermediate system provides the target business data for the first terminal of the geographic area corresponding to the abnormal business class intermediate system.
Optionally, the data center further includes a basic class middlebox system, where the basic class middlebox system includes basic data having a preset corresponding relationship with a pre-divided geographic area;
after the sending of the IP address of the intermediate system in the local service class to the domain name resolution system triggers the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the method further includes:
receiving target basic data synchronized by other data centers;
when a second terminal of a geographic area corresponding to a base type intermediate station system of another data center appears in a corresponding geographic area, an IP address of a local base type intermediate station system is sent to the domain name resolution system to trigger the domain name resolution system to point an access domain name of the second terminal to the IP address of the local base type intermediate station system when the second terminal accesses the base type intermediate station system, so that the local base type intermediate station system provides the target base data for the second terminal.
Optionally, after the triggering, by sending the IP address of the local infrastructure class middlebox system to the domain name resolution system, that the domain name resolution system points the access domain name when the target terminal accesses the local infrastructure class middlebox system to the IP address of the local infrastructure class middlebox system, the method further includes:
when the distance between the third terminal and the third terminal is smaller than the distance between the third terminal and a data center where other basic type intermediate station systems are normal, sending an IP address of a local basic type intermediate station system to the domain name resolution system to trigger the domain name resolution system to point an access domain name when the third terminal accesses the basic type intermediate station system to the IP address of the local basic type intermediate station system, so that the local basic type intermediate station system provides the target basic data for the target terminal, wherein the basic type intermediate station system corresponding to the third terminal is abnormal.
Optionally, the data center further includes a data support class-type platform system, where the data support class-type platform system includes service support data generated according to service data in the service class-type platform system, and after receiving first service data synchronized by another data center, the method further includes:
generating corresponding target service support data according to the target service data;
after the sending of the IP address of the intermediate system in the local service class to the domain name resolution system triggers the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the method further includes:
and triggering the domain name resolution system to point the domain name of the service support class intermediate system of the data center of the abnormal service class intermediate system to the IP address of the local service support class intermediate system by sending the IP address of the local service support class intermediate system to the domain name resolution system, so that the local service support class intermediate system provides the target service support data for the first terminal of the geographical area corresponding to the abnormal service class intermediate system.
Optionally, after the abnormality of the central system in the service class of the other data center, the method further includes:
when the data center with the abnormal platform system in the business class is the data center for processing the timing processing task at present, selecting the data center for processing the timing processing task from the data centers with the normal platform system in the business class;
and when the data center is selected as the data center for processing the timing processing task, receiving the timing processing task and processing the received timing processing task.
Optionally, after receiving the target service data synchronized by the other data centers, the method further includes:
determining the business data with the historical hit rate higher than a threshold value from the target business data;
and preloading the service data with the historical hit rate higher than a threshold value.
Optionally, after the sending the IP address of the intermediate system in the local service class to the domain name resolution system to trigger the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the method further includes:
receiving the sequence number of the successfully received message sent by the message receiver;
and determining the unsuccessfully sent message in the message queue according to the received sequence number, and resending the unsuccessfully sent message in the message queue.
Optionally, before the service class of the other data center is abnormal, the method further includes:
and synchronizing local service data to other data centers.
In the embodiment of the invention, the data center can receive target service data synchronized by other data centers, when the service class central station system of other data centers is abnormal, the candidate data center is selected from the data centers with normal service class central station systems, if the candidate data center is selected, the domain name resolution system can be triggered to point the domain name of the abnormal service class central station system to the IP address of the local service class central station system by sending the IP address of the local service class central station system to the domain name resolution system, so that the local service class central station system provides the target service data for the first terminal of the geographical area corresponding to the abnormal service class central station system.
As can be seen from the above, in this embodiment, a corresponding geographic area may be set in advance for service data of a station system in a service class of different data centers, so that different data centers may provide service data for terminals in different geographic areas based on respective service data. Therefore, the data centers in the embodiment can be used under normal conditions, so that the problem of resource waste caused by the fact that some data centers are only used when a disaster occurs in the prior art is effectively solved.
In addition, the embodiment can also perform "unitized" processing on the data center, that is, the data center is divided into different unit parts, such as a foreground system, a business class middle system, and the like, and business data in the business class middle system is divided into business data respectively corresponding to different geographical areas, and the like, because the divided unit parts are not interfered with each other, when some unit parts are abnormal, only the abnormal unit parts are subjected to corresponding disaster recovery processing, such as modifying the corresponding domain name-directed IP address, and the like, without performing disaster recovery processing on the whole data center, thereby greatly reducing the disaster recovery processing speed and resource consumption.
In the 90 th generation of 20 th century, it is obvious that improvements in Hardware (for example, improvements in Circuit structures such as diodes, transistors and switches) or software (for improvement in method flow) can be distinguished for a technical improvement, however, as technology develops, many of the improvements in method flow today can be regarded as direct improvements in Hardware Circuit structures, designers almost all obtain corresponding Hardware Circuit structures by Programming the improved method flow into Hardware circuits, and therefore, it cannot be said that an improvement in method flow cannot be realized by Hardware entity modules, for example, Programmable logic devices (Programmable logic devices L organic devices, P L D) (for example, Field Programmable Gate Arrays (FPGAs) are integrated circuits whose logic functions are determined by user Programming of devices), and a digital system is "integrated" on a P L D "by self Programming of designers without requiring many kinds of integrated circuits manufactured and manufactured by special chip manufacturers to design and manufacture, and only a Hardware software is written in Hardware programs such as Hardware programs, software programs, such as Hardware programs, software, Hardware programs, software programs, Hardware programs, software, Hardware programs, software, Hardware programs, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software, Hardware, software.
A controller may be implemented in any suitable manner, e.g., in the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, Application Specific Integrated Circuits (ASICs), programmable logic controllers (PLC's) and embedded microcontrollers, examples of which include, but are not limited to, microcontrollers 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone L abs C8051F320, which may also be implemented as part of the control logic of a memory.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in a plurality of software and/or hardware when implementing the invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
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 process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present invention, and is not intended to limit the present invention. Various modifications and alterations to this invention will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (10)
1. A disaster recovery method is characterized in that the method is applied to a data center in a multi-activity disaster recovery system, the multi-activity disaster recovery system comprises a domain name resolution system and a plurality of data centers, the data center at least comprises a foreground system and a business class foreground system, and the business class foreground system comprises business data which have preset corresponding relations with pre-divided geographic areas;
the method comprises the following steps:
receiving target service data synchronized by other data centers;
when the service center central systems of the other data centers are abnormal, electing candidate data centers from the data centers with normal service center central systems;
when the candidate data center is selected, the domain name resolution system is triggered to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system, so that the local business class intermediate system provides the target business data for the first terminal of the geographic area corresponding to the abnormal business class intermediate system.
2. The disaster recovery method according to claim 1, wherein the data center further comprises a basic class middlebox system, the basic class middlebox system comprising basic data having a preset correspondence with a pre-divided geographical area;
after the sending of the IP address of the intermediate system in the local service class to the domain name resolution system triggers the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the method further includes:
receiving target basic data synchronized by other data centers;
when a second terminal of a geographic area corresponding to a base type intermediate station system of another data center appears in a corresponding geographic area, an IP address of a local base type intermediate station system is sent to the domain name resolution system to trigger the domain name resolution system to point an access domain name of the second terminal to the IP address of the local base type intermediate station system when the second terminal accesses the base type intermediate station system, so that the local base type intermediate station system provides the target base data for the second terminal.
3. The method according to claim 2, wherein after the triggering the domain name resolution system to point the access domain name of the target terminal when accessing the base class middlebox system to the IP address of the local base class middlebox system by sending the IP address of the local base class middlebox system to the domain name resolution system, the method further comprises:
when the distance between the third terminal and the third terminal is smaller than the distance between the third terminal and a data center where other basic type intermediate station systems are normal, sending an IP address of a local basic type intermediate station system to the domain name resolution system to trigger the domain name resolution system to point an access domain name when the third terminal accesses the basic type intermediate station system to the IP address of the local basic type intermediate station system, so that the local basic type intermediate station system provides the target basic data for the target terminal, wherein the basic type intermediate station system corresponding to the third terminal is abnormal.
4. The method of claim 1, wherein the data center further comprises a data support class-wide platform system, wherein the data support class-wide platform system comprises service support data generated according to service data in the service class-wide platform system, and after the receiving first service data synchronized by other data centers, the method further comprises:
generating corresponding target service support data according to the target service data;
after the sending of the IP address of the intermediate system in the local service class to the domain name resolution system triggers the domain name resolution system to point the domain name of the intermediate system in the abnormal service class to the IP address of the intermediate system in the local service class, the method further includes:
and triggering the domain name resolution system to point the domain name of the service support class intermediate system of the data center of the abnormal service class intermediate system to the IP address of the local service support class intermediate system by sending the IP address of the local service support class intermediate system to the domain name resolution system, so that the local service support class intermediate system provides the target service support data for the first terminal of the geographical area corresponding to the abnormal service class intermediate system.
5. The method of claim 1, wherein after the class of service exception in the other data center, the method further comprises:
when the data center with the abnormal platform system in the business class is the data center for processing the timing processing task at present, selecting the data center for processing the timing processing task from the data centers with the normal platform system in the business class;
and when the data center is selected as the data center for processing the timing processing task, receiving the timing processing task and processing the received timing processing task.
6. The method of claim 1, wherein after receiving the target traffic data synchronized by the other data centers, the method further comprises:
determining the business data with the historical hit rate higher than a threshold value from the target business data;
and preloading the service data with the historical hit rate higher than a threshold value.
7. The method according to claim 1, wherein after the triggering the domain name resolution system to point the domain name of the abnormal traffic class intermediate system to the IP address of the local traffic class intermediate system by sending the IP address of the local traffic class intermediate system to the domain name resolution system, the method further comprises:
receiving the sequence number of the successfully received message sent by the message receiver;
and determining the unsuccessfully sent message in the message queue according to the received sequence number, and resending the unsuccessfully sent message in the message queue.
8. The method according to any one of claims 1 to 7, wherein before the class of services of the other data center is abnormal, the method further comprises:
and synchronizing local service data to other data centers.
9. A disaster recovery device is characterized in that the disaster recovery device is applied to a data center in a multi-activity disaster recovery system, the multi-activity disaster recovery system comprises a domain name resolution system and a plurality of data centers, the data center at least comprises a foreground system and a business class foreground system, and the business class foreground system comprises business data which have preset corresponding relations with pre-divided geographic areas;
the device comprises:
the receiving module is used for receiving the target service data synchronized by other data centers;
the election module is used for electing candidate data centers from the data centers with normal business center systems when the business center systems of other data centers are abnormal;
and the sending module is used for triggering the domain name resolution system to point the domain name of the abnormal business class intermediate system to the IP address of the local business class intermediate system by sending the IP address of the local business class intermediate system to the domain name resolution system when the candidate data center is elected, so that the local business class intermediate system provides the target business data for the first terminal of the geographical area corresponding to the abnormal business class intermediate system.
10. A disaster recovery device, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when executed by the processor, carries out the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010150986.6A CN111464332B (en) | 2020-03-06 | 2020-03-06 | Disaster recovery method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010150986.6A CN111464332B (en) | 2020-03-06 | 2020-03-06 | Disaster recovery method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111464332A true CN111464332A (en) | 2020-07-28 |
| CN111464332B CN111464332B (en) | 2023-02-24 |
Family
ID=71680948
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010150986.6A Active CN111464332B (en) | 2020-03-06 | 2020-03-06 | Disaster recovery method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111464332B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113037560A (en) * | 2021-03-18 | 2021-06-25 | 同盾科技有限公司 | Service flow switching method and device, storage medium and electronic equipment |
| CN114679376A (en) * | 2022-02-22 | 2022-06-28 | 兴业证券股份有限公司 | Multi-data-center disaster recovery method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789435A (en) * | 2016-12-29 | 2017-05-31 | 深圳市深信服电子科技有限公司 | A kind of method for monitoring state and its device, data center and many live data centers |
| CN108234212A (en) * | 2017-12-29 | 2018-06-29 | 深信服网络科技（深圳）有限公司 | Mixed cloud disaster recovery method, server and storage medium |
| US20180341693A1 (en) * | 2016-01-18 | 2018-11-29 | Alibaba Group Holding Limited | Data synchronization method, apparatus, and system |
| CN110474841A (en) * | 2019-08-30 | 2019-11-19 | 中国人民财产保险股份有限公司 | The route processing method and terminal device of service request |
-
2020
- 2020-03-06 CN CN202010150986.6A patent/CN111464332B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180341693A1 (en) * | 2016-01-18 | 2018-11-29 | Alibaba Group Holding Limited | Data synchronization method, apparatus, and system |
| CN106789435A (en) * | 2016-12-29 | 2017-05-31 | 深圳市深信服电子科技有限公司 | A kind of method for monitoring state and its device, data center and many live data centers |
| CN108234212A (en) * | 2017-12-29 | 2018-06-29 | 深信服网络科技（深圳）有限公司 | Mixed cloud disaster recovery method, server and storage medium |
| CN110474841A (en) * | 2019-08-30 | 2019-11-19 | 中国人民财产保险股份有限公司 | The route processing method and terminal device of service request |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113037560A (en) * | 2021-03-18 | 2021-06-25 | 同盾科技有限公司 | Service flow switching method and device, storage medium and electronic equipment |
| CN114679376A (en) * | 2022-02-22 | 2022-06-28 | 兴业证券股份有限公司 | Multi-data-center disaster recovery method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111464332B (en) | 2023-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107368507B (en) | Block chain-based consensus method and device | |
| CN107450979B (en) | Block chain consensus method and device | |
| US11036562B2 (en) | Streaming data distributed processing method and device | |
| US8489697B2 (en) | Brokerage server for supporting fast data access for user terminal, method of operating brokerage server, user terminal and method of operating user terminal | |
| CN106034138B (en) | A kind of remote service calling method and device | |
| CN107018174B (en) | Unitized system service processing method and device and business processing system | |
| CN111464332B (en) | Disaster recovery method, device and equipment | |
| TWI742332B (en) | Information push method, device and equipment | |
| CN105306507A (en) | Disaster tolerance processing method and disaster tolerance processing device in distributed architecture | |
| CN110708163A (en) | Block chain consensus method, device and system and electronic equipment | |
| CN111459724A (en) | Node switching method, device, equipment and computer readable storage medium | |
| US9871910B2 (en) | Usage of software programs on mobile computing devices | |
| CN108776670B (en) | Remote disaster recovery method, system and electronic equipment | |
| CN105592134A (en) | Load sharing method and device | |
| CN111865632A (en) | Switching method of distributed data storage cluster and switching instruction sending method and device | |
| US10313221B1 (en) | Endpoint monitoring for a messaging framework | |
| CN105307130A (en) | Resource allocation method and resource allocation system | |
| CN113630317B (en) | Data transmission method and device, nonvolatile storage medium and electronic device | |
| CN107656936B (en) | Terminal database construction method in field of instant messaging | |
| CN114296869A (en) | Server node service method and device based on TCP long connection | |
| CN114328129A (en) | Message sending method, device, equipment and storage medium | |
| CN104125266A (en) | Position information processing method and device | |
| CN111931797B (en) | Method, device and equipment for identifying network to which service belongs | |
| CN110019023B (en) | Method, device and equipment for pushing mechanism information message | |
| CN111796864A (en) | Data verification method and device |
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 |