CN111857969A - Data disaster recovery reconstruction method, system, device and storage medium - Google Patents
Data disaster recovery reconstruction method, system, device and storage medium Download PDFInfo
- Publication number
- CN111857969A CN111857969A CN202010742749.9A CN202010742749A CN111857969A CN 111857969 A CN111857969 A CN 111857969A CN 202010742749 A CN202010742749 A CN 202010742749A CN 111857969 A CN111857969 A CN 111857969A
- Authority
- CN
- China
- Prior art keywords
- platform
- cluster platform
- data
- access
- cluster
- 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.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Hardware Redundancy (AREA)
Abstract
The application provides a data disaster recovery reconstruction method, a system, a device and a storage medium, and relates to the technical field of disaster recovery reconstruction. When the method is applied to an access platform of a data disaster recovery reconstruction system, the data disaster recovery reconstruction system comprises the following steps: the system comprises a main cluster platform, a standby cluster platform and an access platform. The access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the access platform receives an access request, wherein the access request comprises: an address of a primary cluster platform; and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform. By simultaneously establishing the main cluster platform and the standby cluster platform, when the main cluster platform fails, the standby cluster platform can be switched to in time, so that the service data can be restored in time, and the timeliness and the stability of the restoration of the power data system are improved.
Description
Technical Field
The present application relates to the field of disaster recovery reconstruction technologies, and in particular, to a data disaster recovery reconstruction method, system, device, and storage medium.
Background
Data is the basis of an information system and is an important wealth of an electric power enterprise, data backup is a key technical measure for ensuring data safety, and in order to strengthen data backup management work of the information system, avoid data loss of the information system and ensure safety of application systems such as production, management and management, the particularity of the power industry determines that the data system needs to have higher stability, reliability and manageability, particularly data safety and service continuity, so that recovery exercise of backup data is performed at least once every year for a key service system in the power system.
Kubernetes, K8s for short, is an open-source container cluster management system for managing containerized applications on a plurality of hosts in a cloud platform, is a complete distributed system support platform, provides a series of complete functions such as deployment, dynamic resource allocation, interface discovery and periodic management for containerized applications on the basis of Docker technology, and has the convenience of large-scale container cluster management.
Currently, Kubernetes-based container platforms are widely used in production environments due to their portability, availability, and scalability, and despite the full high availability of Kubernetes itself, when irresistible catastrophic situations occur, such as: when an Internet Data Center (IDC for short) machine room where the whole cluster machine is located is down, the cluster loses the function of high availability, a set of same system needs to be built again by spending a large amount of time even if remote Data backup exists, and then Data is imported, so that the recovery of service Data can be completed, and the requirements of timeliness and stability of an electric power Data system cannot be met.
Disclosure of Invention
In order to solve the problems in the prior art, the application provides a data disaster recovery reconstruction method, a system, a device and a storage medium.
In order to achieve the purpose, the technical scheme adopted by the application is as follows:
a first aspect of the present application provides a data disaster recovery reconstruction method, which is applied to an access platform of a data disaster recovery reconstruction system, where the system includes: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the method comprises the following steps:
the access platform receives an access request, the access request comprising: an address of the primary cluster platform;
and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform.
Optionally, before the access platform receives the access request, the method further includes:
the access platform sends first address allocation information to the main cluster platform, wherein the first address allocation information comprises: an address of the primary cluster platform;
the access platform sends second address assignment information to the standby cluster platform, where the second address assignment information includes: an address of the backup cluster platform.
A second aspect of the present application provides a data disaster recovery reconstruction method, which is applied to a main cluster platform of a data disaster recovery reconstruction system, where the system includes: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the method comprises the following steps:
the main cluster platform monitors whether the data of the main cluster platform is updated or not;
and if the self data is updated, the main cluster platform determines the updated data and synchronizes the updated data to the standby cluster platform.
Optionally, before the determining, by the primary cluster platform, updated data and synchronizing the updated data to the standby cluster platform, the method further includes:
the main cluster platform sends a connection request to the standby cluster platform, wherein the connection request carries the verification information;
and the main cluster platform receives a connection response sent by the standby cluster platform when the verification information is the same as the pre-stored verification information.
A third aspect of the present application provides a data disaster recovery reconstruction system, including: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform;
the access platform is used for receiving an access request, and the access request comprises: an address of the primary cluster platform; if the main cluster platform fails, forwarding the access request to the standby cluster platform;
the main cluster platform is used for monitoring whether the data of the main cluster platform is updated; and if the self data is updated, determining the updated data, and synchronizing the updated data to the standby cluster platform.
Optionally, the access platform is further configured to send first address allocation information to the master cluster platform, where the first address allocation information includes: an address of the primary cluster platform; sending second address assignment information to the standby cluster platform, the second address assignment information including: an address of the backup cluster platform.
Optionally, the access platform is further configured to obtain data of the primary cluster platform and data of the standby cluster platform respectively; and if the data of the main cluster platform is different from the data of the standby cluster platform, generating alarm information.
Optionally, the primary cluster platform is specifically configured to synchronize the updated data to the standby cluster platform through a synchronization program.
Optionally, the access platform is further configured to monitor whether the synchronous program is abnormal, and if the synchronous program is abnormal, generate abnormal notification information.
Optionally, the primary cluster platform is further configured to send a connection request to the standby cluster platform, where the connection request carries the verification information;
and the standby cluster platform is used for comparing the verification information with pre-stored verification information, and sending a connection response to the main cluster platform if the verification information is the same as the pre-stored verification information.
A fourth aspect of the present application provides a data disaster recovery reconstruction device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating over the bus when the apparatus is operated, the processor executing the machine-readable instructions to perform the steps of the method of the first aspect.
A fifth aspect of the present application provides a data disaster recovery reconstruction device, including: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the apparatus is operating, the processor executing the machine-readable instructions to perform the steps of the method of the second aspect.
A sixth aspect of the present application provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the method as provided in the first aspect.
A seventh aspect of the present application provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the method as provided by the second aspect.
In the method, system, device, and storage medium for data disaster recovery reconstruction provided by the present application, when applied to an access platform of a data disaster recovery reconstruction system, the data disaster recovery reconstruction system includes: the system comprises a main cluster platform, a standby cluster platform and an access platform. The access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the access platform receives an access request, wherein the access request comprises: an address of a primary cluster platform; and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform. By simultaneously establishing the main cluster platform and the standby cluster platform, when the main cluster platform fails, the standby cluster platform can be switched to in time, so that the service data can be restored in time, and the timeliness and the stability of the restoration of the power data system are improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram of a data disaster recovery reconstruction system according to an embodiment of the present application;
fig. 2 is a schematic flow chart of a data disaster recovery reconstruction method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of interaction of a data disaster recovery reconstruction method according to another embodiment of the present application;
fig. 4 is a schematic flowchart of a data disaster recovery reconstruction method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a data disaster recovery reconstruction method according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a data disaster recovery and reconstruction device according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data disaster recovery and reconstruction device according to another embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. 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 application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Furthermore, the appearances of the terms "first," "second," and the like, if any, are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
Data is the basis of an information system and is an important wealth of an electric power enterprise, data backup is a key technical measure for ensuring data safety, and in order to strengthen data backup management work of the information system, avoid data loss of the information system and ensure safety of application systems such as production, management and management, the particularity of the power industry determines that the data system needs to have higher stability, reliability and manageability, particularly data safety and service continuity, so that recovery exercise of backup data is performed at least once every year for a key service system in the power system.
Currently, Kubernetes-based container platforms are widely used in production environments due to their portability, availability, and scalability, and despite the full high availability of Kubernetes itself, when irresistible catastrophic situations occur, such as: the idc computer lab that whole cluster machine was located is down, and the high availability of cluster itself just has lost effect, even there is long-range data backup, also need spend a large amount of time to set up one set of same system again, and the data of leading-in again can accomplish the recovery of business data, can't satisfy the demand of electric power data system timeliness and stability.
An embodiment of the present application provides a data disaster recovery reconstruction system, as shown in fig. 1, the system includes: a primary cluster platform 01, a backup cluster platform 02, and an access platform 03. The access platform 03 is in communication connection with the main cluster platform 01 and the standby cluster platform 02 respectively.
It should be noted that, in the embodiment of the present application, the access platform 03 runs on the K8s container cluster management system, and is mainly used for receiving an access request input by a user, where the access request may carry address information that the user wants to access. The access platform 03, the main cluster platform 01 and the standby cluster platform 02 all have their own independent Domain Name Server (DNS) addresses, and a user can access the main cluster platform 01 or the standby cluster platform 02 by inputting the DNS address of the main cluster platform 01 or the standby cluster platform 02 into the access platform 03.
Alternatively, the data disaster recovery and reconstruction system may be applied to the power system, for example, the data stored in the primary cluster platform 01 and the backup cluster platform 02 are power data. But not limited to the power system, the system may also be a shopping system, a catering system, etc., and accordingly, the data stored in the main cluster platform 01 and the standby cluster platform 02 may be commodity price data, food price data, etc.
Fig. 2 is a schematic flow chart of a data disaster recovery reconstruction method according to an embodiment of the present application, where the method is applied to an access platform side, and the method includes the following steps:
s201, the access platform receives an access request.
Alternatively, the access request received by the access platform may be a DNS address of the master cluster platform entered by the user on the access platform. It should be noted that, in this embodiment of the present application, the access platform may specifically be a data disaster recovery reconstruction access platform, and the access platform has an independent DNS Address and an Internet Protocol Address (IP for short), where the access request includes: DNS address of the master cluster platform.
In the embodiment of the application, the data list of the main cluster platform is pre-stored with service data generated by the power system, and the service data can change in real time along with the change of time.
For example, when the power system data changes, the data of the main cluster platform is updated according to the change of the power system data, exemplarily: the change in the power system data may be an addition, deletion, correction, etc. of the power data. It should be noted that, in the embodiment of the present application, the data of the master cluster platform is not limited to the power data, but may also be commodity quantity data and price information data, and the embodiment of the present application is not specifically limited to the data type of the specific master cluster platform.
S202, the access platform determines the fault of the main cluster platform.
It should be noted that, in the embodiment of the present application, the failure of the main cluster platform may be a downtime of a machine room device of the main cluster. Correspondingly, after the access platform receives the access request, the DNS address of the main cluster platform cannot be used for opening the webpage of the main cluster platform, and then the fault of the main cluster platform can be determined.
S203, the access platform forwards the access request to the standby cluster platform.
It should be noted that the access platform runs on the K8s container cluster management system. And when the main cluster platform fails, the access platform forwards the access request to the standby cluster platform. Illustratively, the access platform will switch the DNS address to that of the backup cluster platform.
In the embodiment of the application, the main cluster platform and the standby cluster platform share one set of certificate and an encryption mode. It can be understood that when the certificates and the encryption modes of the main cluster platform and the standby cluster platform are the same, the access platform is not limited between the main cluster platform and the standby cluster platform to cause the switching failure when the main cluster platform and the standby cluster platform are switched.
In this embodiment, the failure of the primary cluster platform may be only a small failure, which can be handled quickly. When the fault of the main cluster platform can be processed in time, the access platform can not be switched to the standby cluster platform by human participation.
The data disaster recovery system provided by the application comprises: the system comprises a main cluster platform, a standby cluster platform and an access platform. The access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the access platform receives an access request, wherein the access request comprises: an address of a primary cluster platform; and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform. By simultaneously establishing the main cluster platform and the standby cluster platform, when the main cluster platform fails, the access platform can be switched to the standby cluster platform in time, so that the service data can be restored in time, and the timeliness and stability of restoration of the power data system are improved.
Fig. 3 is a schematic flow chart of interaction of a data disaster recovery reconstruction method according to another embodiment of the present application, and as shown in fig. 3, an interaction process between a main cluster platform and a standby cluster platform is as follows:
s301, the main cluster platform monitors whether the data of the main cluster platform is updated.
It should be noted that the power data in the main cluster platform may change in real time over time. In order to monitor the change of the power data in the main cluster platform, in the embodiment of the present application, a synchronization program may be run on the main cluster platform, and whether the data on the main cluster platform changes is monitored through the synchronization program, which may be a "Watch" program.
S302, if the data of the cluster platform is updated, the updated data is determined, and the updated data is synchronously updated to the standby cluster platform.
When the synchronization program monitors that the data on the main cluster platform is updated, the synchronization program can determine changed data by comparing the data with the data before updating, and synchronize the changed data to the standby cluster.
Further, on the basis of the above embodiment, a primary cluster platform and a standby cluster platform need to be deployed in advance. In the implementation process, the access platforms can respectively carry out address allocation so as to carry out subsequent access.
Optionally, the access platform is further configured to send first address allocation information to the master cluster platform, where the first address allocation information includes: an address of a primary cluster platform; sending second address assignment information to the standby cluster platform, the second address assignment information comprising: an address of the standby cluster platform.
In addition, in this embodiment, the data of the main cluster platform and the data of the standby cluster platform need to be kept synchronous, and if the data are not synchronous, further improvement is needed.
Optionally, the access platform of the data disaster recovery and reconstruction system is further configured to obtain data of the main cluster platform and data of the standby cluster platform, respectively; and if the data of the main cluster platform is different from the data of the standby cluster platform, generating alarm information.
It should be noted that, in the embodiment of the present application, the access platform specifically monitors data of the primary cluster platform and data of the standby cluster platform through the monitoring program. For example, in the embodiment of the present application, the monitoring program may be a promethrus program.
Furthermore, the worker can check the alarm information through the access platform, and then synchronize the main cluster platform and the standby cluster platform according to the alarm information, that is, the data stored by the main cluster platform and the standby cluster platform are kept consistent.
Optionally, in this embodiment, the primary cluster platform may further be configured to synchronize updated data to the backup cluster platform through a synchronization program.
In a specific implementation process, the main cluster platform can synchronize the updated part to the standby cluster platform after updating the data of the main cluster platform, so that the standby cluster platform updates the data of the main cluster platform according to the received updated data, and further keeps the data consistent with the data of the main cluster platform.
For example, when the power system data changes, the data of the main cluster platform is updated according to the change of the power system data, exemplarily: the change in the power system data may be an addition, deletion, correction, etc. of the power data.
When the synchronization program is abnormal, the data change of the main cluster platform cannot be synchronized to the standby cluster platform in time, so that the data abnormality caused by the inconsistency of the data of the main cluster platform and the data of the standby cluster platform is avoided. In the embodiment of the application, the access platform is further configured to monitor whether the synchronous program is abnormal, and if the synchronous program is abnormal, generate abnormal notification information.
It should be noted that, in the embodiment of the present application, the access platform may specifically monitor the running condition of the synchronization program (watch program) through the monitoring program. When the synchronous program is abnormal, the data of the main cluster platform and the data of the standby cluster platform cannot be synchronously updated in time. When the data of the main cluster platform is different from the data of the standby cluster platform, a worker can check the alarm information through the access platform, and then synchronize the main cluster platform and the standby cluster platform according to the alarm information, namely, the data stored by the main cluster platform and the standby cluster platform are kept consistent.
It can be understood that, in this embodiment, by monitoring the operation condition of the synchronization program, it can be ensured that the data of the main cluster platform and the data of the standby cluster platform are consistent in real time, and the requirement for the stability of the power data is ensured.
Optionally, before the above embodiment is executed, a communication connection needs to be established between the primary cluster platform and the standby cluster platform, and the communication may be performed normally only after the authentication is successful, so as to ensure the security of the communication. For example, the primary cluster platform is further configured to send a connection request to the standby cluster platform, where the connection request carries verification information; and the standby cluster platform is used for comparing the verification information with the pre-stored verification information, and sending a connection response to the main cluster platform if the verification information is the same as the pre-stored verification information.
Fig. 4 is a schematic flow chart of a data disaster recovery reconstruction method according to an embodiment of the present application, where the data disaster recovery reconstruction method is applied to an access platform of a data disaster recovery reconstruction system, and the data disaster recovery reconstruction system includes: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform. As shown in fig. 4, the method includes:
s401, the access platform receives an access request.
It should be noted that, in the embodiment of the present application, the access request includes: the address of the main cluster platform may specifically be a DNS address.
The access platform may be integrated on a terminal through which a user may input the access request to the access platform.
The access platform in the embodiment of the application is based on a kubernets container management platform. By designing the declarative API of Kubernetes, the user need only describe the state that the resource ultimately expects.
S402, if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform.
In the embodiment of the application, when the machine room equipment fails, the main cluster platform fails because the main cluster platform cannot acquire data. When the main cluster platform fails, the access platform forwards the access request to the standby cluster platform.
It should be noted that the forwarded access request may be a DNS address of the standby cluster platform.
The data disaster recovery reconstruction method provided by the application is applied to an access platform of a data disaster recovery reconstruction system, and the data disaster recovery reconstruction system comprises: the system comprises a main cluster platform, a standby cluster platform and an access platform. The access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the access platform receives an access request, wherein the access request comprises: an address of a primary cluster platform; and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform. By simultaneously establishing the main cluster platform and the standby cluster platform, when the main cluster platform fails, the standby cluster platform can be switched to in time, so that the service data can be restored in time, and the timeliness and the stability of the restoration of the power data system are improved.
Optionally, in this embodiment of the application, before step S401, the method further includes: the access platform sends first address allocation information to the main cluster platform, wherein the first address allocation information comprises: an address of a primary cluster platform; the access platform sends second address allocation information to the standby cluster platform, wherein the second address allocation information comprises: an address of the standby cluster platform.
It can be understood that, in the embodiment of the present application, both the main cluster platform and the standby cluster platform have their own individual DNS addresses, and when the IDC machine room of the main cluster goes down, the access platform only needs to forward the access request to the DNS address of the standby cluster, so that the recovery of the service data can be completed. The timeliness and the stability of service data recovery are improved.
Fig. 5 is a schematic flow chart of a data disaster recovery reconstruction method according to another embodiment of the present application, where the data disaster recovery reconstruction method is applied to a primary cluster platform of a data disaster recovery reconstruction system, and the data disaster recovery reconstruction system includes: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform. As shown in fig. 5, the method includes:
s501, the main cluster platform monitors whether the data of the main cluster platform is updated.
It should be noted that, in this embodiment of the application, a synchronization program may be run on the master cluster platform, and whether data on the master cluster platform changes is monitored through the synchronization program, which may specifically be a "Watch" program.
S502, if the data of the main cluster platform is updated, the main cluster platform determines the updated data and synchronizes the updated data to the standby cluster platform.
When the synchronization program monitors that the data on the main cluster platform is updated, the synchronization program can determine changed data by comparing the data with the data before updating, and synchronize the changed data to the standby cluster.
Optionally, in this embodiment of the present application, before step S501, the method further includes: the main cluster platform sends a connection request to the standby cluster platform, and the connection request carries verification information; and the main cluster platform receives a connection response sent by the standby cluster platform when the verification information is the same as the pre-stored verification information.
In the embodiment of the application, the standby cluster is prestored with the verification information. This verification information corresponds to a "key" to open the backup cluster database. Before the connection between the main cluster and the standby cluster is established, the main cluster sends a connection request to the standby cluster, and when the verification information carried in the connection request of the main cluster is the same as the verification information prestored in the standby cluster, the connection between the main cluster and the standby cluster is successfully established.
It can be understood that, in the embodiment of the present application, by executing the verification link before the connection of the main cluster and the standby cluster, it is ensured that the main cluster can be connected to a safe and specified standby cluster, and data leakage is avoided to a certain extent.
Fig. 6 is a schematic structural diagram of a data disaster recovery reconstruction device according to an embodiment of the present application, which corresponds to a method applied to an access platform side of a data disaster recovery reconstruction system; the data disaster recovery reconstruction device may include: the system comprises a processor 510, a storage medium 520 and a bus 530, wherein the storage medium 520 stores machine-readable instructions executable by the processor 510, when the electronic device runs, the processor 510 communicates with the storage medium 520 through the bus 530, and the processor 510 executes the machine-readable instructions to perform the steps of the above-mentioned method embodiment of the data disaster recovery reconstruction system on the access platform side.
Fig. 7 is a schematic structural diagram of a data disaster recovery reconstruction device according to an embodiment of the present application, which corresponds to a method applied to a primary cluster platform side of a data disaster recovery reconstruction system; the data disaster recovery reconstruction device may include: the data disaster recovery system comprises a processor 610, a storage medium 620 and a bus 630, wherein the storage medium 620 stores machine-readable instructions executable by the processor 610, when an electronic device runs, the processor 610 communicates with the storage medium 620 through the bus 630, and the processor 610 executes the machine-readable instructions to perform the steps of the above-mentioned method embodiment on the main cluster platform side of the data disaster recovery system. The specific implementation and technical effects are similar, and are not described herein again.
The embodiment of the application provides a storage medium, wherein a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method for the data disaster recovery and reconstruction system to access the platform side is executed.
The embodiment of the application provides a storage medium, wherein a computer program is stored on the storage medium, and when the computer program is executed by a processor, the method on the side of a main cluster platform of a data disaster recovery and reconstruction system is executed.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (10)
1. A data disaster recovery reconstruction method is applied to an access platform of a data disaster recovery reconstruction system, wherein the system comprises: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the method comprises the following steps:
the access platform receives an access request, the access request comprising: an address of the primary cluster platform;
and if the main cluster platform fails, the access platform forwards the access request to the standby cluster platform.
2. The method of claim 1, wherein prior to the access platform receiving the access request, the method further comprises:
the access platform sends first address allocation information to the main cluster platform, wherein the first address allocation information comprises: an address of the primary cluster platform;
the access platform sends second address assignment information to the standby cluster platform, where the second address assignment information includes: an address of the backup cluster platform.
3. A data disaster recovery reconstruction method is applied to a main cluster platform of a data disaster recovery reconstruction system, wherein the system comprises: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform; the method comprises the following steps:
the main cluster platform monitors whether the data of the main cluster platform is updated or not;
and if the self data is updated, the main cluster platform determines the updated data and synchronizes the updated data to the standby cluster platform.
4. The method of claim 3, wherein before the primary cluster platform determining updated data and synchronizing the updated data to the backup cluster platform, further comprising:
the main cluster platform sends a connection request to the standby cluster platform, wherein the connection request carries verification information;
and the main cluster platform receives a connection response sent by the standby cluster platform when the verification information is the same as the pre-stored verification information.
5. A data disaster recovery reconstruction system, the system comprising: the system comprises a main cluster platform, a standby cluster platform and an access platform, wherein the access platform is respectively in communication connection with the main cluster platform and the standby cluster platform;
the access platform is used for receiving an access request, and the access request comprises: an address of the primary cluster platform; if the main cluster platform fails, forwarding the access request to the standby cluster platform;
the main cluster platform is used for monitoring whether the data of the main cluster platform is updated; and if the self data is updated, determining the updated data, and synchronizing the updated data to the standby cluster platform.
6. The system of claim 5, wherein the access platform is further configured to send first address assignment information to the master cluster platform, the first address assignment information comprising: an address of the primary cluster platform; sending second address assignment information to the standby cluster platform, the second address assignment information including: an address of the backup cluster platform.
7. The system of claim 5, wherein the access platform is further configured to obtain data of the primary cluster platform and data of the backup cluster platform, respectively; and if the data of the main cluster platform is different from the data of the standby cluster platform, generating alarm information.
8. The system according to claim 5, wherein the primary cluster platform is configured to synchronize the updated data to the backup cluster platform via a synchronization procedure.
9. The system of claim 8, wherein the access platform is further configured to monitor whether the synchronous program is abnormal, and if so, generate an abnormal notification message.
10. The system of claim 5, wherein the primary cluster platform is further configured to send a connection request to the backup cluster platform, where the connection request carries verification information;
and the standby cluster platform is used for comparing the verification information with pre-stored verification information, and sending a connection response to the main cluster platform if the verification information is the same as the pre-stored verification information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010742749.9A CN111857969A (en) | 2020-07-30 | 2020-07-30 | Data disaster recovery reconstruction method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010742749.9A CN111857969A (en) | 2020-07-30 | 2020-07-30 | Data disaster recovery reconstruction method, system, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111857969A true CN111857969A (en) | 2020-10-30 |
Family
ID=72945466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010742749.9A Withdrawn CN111857969A (en) | 2020-07-30 | 2020-07-30 | Data disaster recovery reconstruction method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111857969A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023019953A1 (en) * | 2021-08-16 | 2023-02-23 | 中兴通讯股份有限公司 | Data synchronization method and system, server, and storage medium |
-
2020
- 2020-07-30 CN CN202010742749.9A patent/CN111857969A/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023019953A1 (en) * | 2021-08-16 | 2023-02-23 | 中兴通讯股份有限公司 | Data synchronization method and system, server, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11080144B2 (en) | System and method for managing blockchain nodes | |
| KR20210057149A (en) | Smart contract-based data processing method, device and storage medium | |
| US20190205315A1 (en) | System and method for synchronizing data between communication devices in a networked environment without a central server | |
| CN111259072B (en) | Data synchronization method, device, electronic equipment and computer readable storage medium | |
| WO2019061720A1 (en) | Data synchronization method and system | |
| CN108769124B (en) | Application deployment method, device, server and storage medium of PaaS platform | |
| CN112448858A (en) | Network communication control method and device, electronic equipment and readable storage medium | |
| CN113630314B (en) | Disaster recovery method and device for hybrid cloud private line access network | |
| CN111949444A (en) | Data backup and recovery system and method based on distributed service cluster | |
| EP3817338B1 (en) | Method and apparatus for acquiring rpc member information, electronic device and storage medium | |
| CN105933379B (en) | A kind of method for processing business, equipment and system | |
| CN111245656A (en) | Method and system for remote monitoring through mobile equipment | |
| CN111884844A (en) | Message service access method and device based on zookeeper | |
| CN113347037A (en) | Data center access method and device | |
| CN111708668A (en) | Cluster fault processing method and device and electronic equipment | |
| CN111857969A (en) | Data disaster recovery reconstruction method, system, device and storage medium | |
| CN109189854B (en) | Method and node equipment for providing continuous service | |
| CN114553867A (en) | Cloud-native cross-cloud network monitoring method and device and storage medium | |
| CN109104333B (en) | GIT-based distributed cluster synchronization method and device | |
| CN109005203B (en) | Data synchronization method and device, storage medium, processor and terminal | |
| CN114125827B (en) | Terminal management method, device and centralized management system | |
| EP4152158A1 (en) | Method for processing routing message, communication device, storage medium, and system | |
| CN114143330A (en) | Configuration method, device and system of time server | |
| CN109167826B (en) | Method, device and system for putting WEB application on shelf | |
| CN110113192B (en) | Routing method, routing device, system, storage medium and device for virtual desktop |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20201030 |
|
| WW01 | Invention patent application withdrawn after publication |