CN117294723A - Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium - Google Patents
Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN117294723A CN117294723A CN202210701552.XA CN202210701552A CN117294723A CN 117294723 A CN117294723 A CN 117294723A CN 202210701552 A CN202210701552 A CN 202210701552A CN 117294723 A CN117294723 A CN 117294723A
- Authority
- CN
- China
- Prior art keywords
- disaster recovery
- standby
- synchronous
- side car
- main
- 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.)
- Pending
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 215
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000001360 synchronised effect Effects 0.000 claims abstract description 163
- 230000008859 change Effects 0.000 claims abstract description 72
- 230000005540 biological transmission Effects 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 10
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 230000000903 blocking effect Effects 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 5
- 238000004891 communication Methods 0.000 description 13
- 238000012423 maintenance Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 6
- 238000004140 cleaning Methods 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000002184 metal Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000013486 operation strategy Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- 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 application relates to a disaster recovery system control method, a disaster recovery system, an electronic device and a readable storage medium, wherein the method comprises the following steps: acquiring main abstract information of disaster recovery data in a main service container through a main side vehicle, and receiving standby abstract information sent by a standby side vehicle; the master side car compares the master abstract information with the standby abstract information to obtain a synchronous data change object, and sends the synchronous data change object to a master synchronous coordinator; and carrying out data synchronization operation according to the synchronization data change object through the master synchronization coordinator. The backup of disaster recovery data is realized by disposing the side car on the service container, the disaster recovery system does not invade the service, the service is decoupled from the disaster recovery, and the service itself does not participate in the disaster recovery, thereby being convenient for realizing the service development.
Description
Technical Field
The present disclosure relates to the field of communications, and in particular, to a disaster recovery system control method, a disaster recovery system, an electronic device, and a readable storage medium.
Background
The 5G communication network is developed towards SDN/NFV, the management capacity of a communication network management system is also increased gradually, various services and management information data volume generated by the network are increased in an explosive manner, the corresponding system has high availability, and disaster recovery guarantee of key data is particularly important. Meanwhile, architecture distributed, virtualized and PaaS clouding have become standard architecture technologies. The current universal selectable disaster recovery scheme on PaaS can be divided into an infrastructure storage layer disaster recovery scheme, a service application layer disaster recovery scheme and a PaaS middleware layer disaster recovery scheme, which are respectively applicable to different service scene requirements. The current off-site disaster recovery scheme on the industrial PaaS platform comprises middleware object layer disaster recovery; the middleware object layer disaster recovery scheme has no strong coupling with the business, the underlying hardware and the file system, has strong universal applicability and high disaster recovery RTO/RPO index, and has huge commercial advantages; however, the original middleware layer disaster recovery scheme needs to use FTP middleware for file system data disaster recovery synchronization, and meanwhile, the business participation is realized, so that the disaster recovery scheme is tightly coupled with the file system data, and the business development burden is increased.
Disclosure of Invention
The application provides a disaster recovery system control method, a disaster recovery system, an electronic device and a readable storage medium, and aims to solve the technical problem that in the prior art, a middleware object layer disaster recovery scheme is tightly coupled with file system data, and service development burden is increased.
In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides a disaster recovery system control method, including the steps of:
acquiring main abstract information of disaster recovery data in a main service container through a main side vehicle, and receiving standby abstract information sent by a standby side vehicle;
the master side car compares the master abstract information with the standby abstract information to obtain a synchronous data change object, and sends the synchronous data change object to a master synchronous coordinator;
and carrying out data synchronization operation according to the synchronization data change object through the master synchronization coordinator.
Optionally, the step of performing, by the active synchronization coordinator, a data synchronization operation according to the synchronization data change object includes:
transmitting the synchronous data change object to the standby synchronous coordinator through the active synchronous coordinator;
transmitting the synchronous data change object to the standby side car corresponding to the incremental content data through the standby synchronous coordinator;
and writing the synchronous data change object into the corresponding standby service container through the standby side car.
Optionally, the step of comparing the primary summary information with the backup summary information to obtain a synchronous data change object includes:
comparing the main abstract information with the standby abstract information to obtain abstract difference data;
and acquiring a disaster recovery file corresponding to the abstract difference data, and packaging the disaster recovery file to obtain the synchronous data change object.
Optionally, the step of encapsulating the disaster recovery file to obtain the synchronous data change object includes:
judging whether the size of each disaster recovery file is larger than a preset volume or not for each disaster recovery file;
if the size of the disaster recovery file is larger than the preset volume, extracting incremental data of the disaster recovery file according to the main abstract information and the standby abstract information;
and packaging the incremental data to obtain the synchronous data change object.
Optionally, the step of obtaining the primary summary information of the disaster recovery data in the primary service container and receiving the backup summary information sent by the backup side vehicle includes:
acquiring a latest synchronous time stamp, and generating the main abstract information according to the monitored file change event of the corresponding service container after the latest synchronous time stamp;
And receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to the monitored file change event of the corresponding service container after the latest synchronous time stamp.
Optionally, the step of obtaining the primary summary information of the disaster recovery data in the primary service container and receiving the backup summary information sent by the backup side vehicle includes:
if a full synchronization signal sent by a side car manager is received, generating the main abstract information according to all files of the corresponding service container;
and receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to all files of the corresponding service container after receiving the full synchronization signal.
Optionally, before the step of obtaining, by the primary side vehicle, primary summary information of disaster recovery data in the primary service container, the method includes:
detecting a micro-service blueprint of a service system through a side car manager, and extracting disaster recovery parameters if the micro-service blueprint is detected to contain the disaster recovery parameters;
and generating a disaster recovery side car blueprint according to the disaster recovery parameters through the side car manager, and adding the disaster recovery side car blueprint into the micro-service blueprint to perform associated deployment on the side car and the service container.
Optionally, the method further comprises:
the disaster recovery control console sends a main signal or a standby signal to the side car manager according to the received management instruction;
if the side car management controller receives the main signal, a main setting signal is sent to the main side car and the main synchronous coordinator so that the main side car executes main synchronous operation, and the main synchronous coordinator sets the data transmission direction as output;
and if the side car management controller receives the standby signal, sending a standby setting signal to the standby side car and the standby synchronous coordinator so as to initialize the service container corresponding to the blocking of the standby side car and execute standby synchronous operation, wherein the standby synchronous coordinator sets the data transmission direction as input.
In order to achieve the above object, the present invention further provides a disaster recovery system, which is characterized in that the disaster recovery system includes a plurality of disaster recovery sites, the plurality of disaster recovery sites include a main site and at least one backup site, the main site is connected to a main service system, the backup site is connected to a backup service system, the main site includes a main side car and a main synchronization coordinator, the main side car is connected to a main service container and the main synchronization coordinator of the main service system, the backup site includes a backup side car and a backup synchronization coordinator, the backup side car is connected to a backup service container and the backup synchronization coordinator of the backup service system, the main side car is connected to the backup side car, and the main synchronization coordinator is connected to the backup synchronization coordinator, wherein:
The master side car is used for acquiring master abstract information of disaster recovery data in the master service container, receiving standby abstract information sent by the standby side car, and sending a synchronous data change object obtained by comparing the master abstract information with the standby abstract information to the master synchronous coordinator;
and the master synchronous coordinator is used for carrying out data synchronous operation according to the synchronous data change object.
Optionally, the disaster recovery site further comprises a disaster recovery console and a side car manager; the side car manager is respectively connected with the disaster recovery control console, the side car and the synchronous coordinator, wherein:
the disaster recovery control console is used for receiving the management instruction and sending a corresponding control signal to the side car manager according to the management instruction;
the side car manager is used for responding to the control signal to execute preset operation corresponding to the control signal;
the side car manager is further configured to send a setting signal to the side car and the synchronization coordinator when a preset condition is met;
the side car is used for adjusting the running state of the side car according to the setting signal;
the synchronous coordinator is used for adjusting the running state of the synchronous coordinator according to the setting signal.
In order to achieve the above object, the present invention also provides an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of the disaster recovery system control method as described above when executed by the processor.
To achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the disaster recovery system control method as described above.
The invention provides a disaster recovery system control method, a disaster recovery system, an electronic device and a readable storage medium, wherein main abstract information of disaster recovery data in a main service container is obtained through a main side vehicle, and standby abstract information sent by a standby side vehicle is received; the master side car compares the master abstract information with the standby abstract information to obtain a synchronous data change object, and sends the synchronous data change object to a master synchronous coordinator; and carrying out data synchronization operation according to the synchronization data change object through the master synchronization coordinator. The backup of disaster recovery data is realized by disposing the side car on the service container, the disaster recovery system does not invade the service, the service is decoupled from the disaster recovery, and the service itself does not participate in the disaster recovery, thereby being convenient for realizing the service development.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a schematic diagram of a disaster recovery system according to the present invention;
FIG. 2 is a flowchart of a disaster recovery system control method according to a first embodiment of the present invention;
fig. 3 is a schematic block diagram of an electronic device according to the present invention.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The invention provides a disaster recovery system control method, which is applied to a disaster recovery system, referring to fig. 1, wherein the disaster recovery system comprises a plurality of disaster recovery sites, the plurality of disaster recovery sites comprise a main site and at least one standby site, the main site is connected with a main service system, and the standby site is connected with a standby service system;
it can be understood that the number of the service systems is a plurality of, and different service systems are arranged in different places, and one disaster recovery site is connected with one service system; the service system comprises a main service system and at least one standby service system; the active service system is a service system for executing service operation, the standby service system is a service system synchronous with the active service system, it is understood that the active service system and the standby service system are identical in structure and implementation function, and the active service system and the standby service system can be switched when certain conditions are met, for example, when the active service system fails or an operation and maintenance personnel controls to perform active-standby switching, the active service system can be converted into the standby service system, the standby service system can be converted into the active service system, meanwhile, the disaster recovery site also is converted along with the conversion of the service system, namely, when the active service system is converted into the standby service system, the active site is converted into the standby site, and when the standby service system is converted into the active service system, the standby site connected with the service system is converted into the active site. The communication connection between different disaster recovery sites may specifically include a control pipeline for transmitting related instructions and a data pipeline for transmitting synchronous data.
The main station comprises a main side car and a main synchronous coordinator, the main side car is respectively connected with a main service container of the main service system and the main synchronous coordinator, the standby station comprises a standby side car and a standby synchronous coordinator, the standby side car is respectively connected with a standby service container of the standby service system and the standby synchronous coordinator, the main side car is also connected with the standby side car, and the main synchronous coordinator is also connected with the standby synchronous coordinator.
It should be noted that, in this embodiment, the primary and standby modules of the side car, the synchronous coordinator and the like follow the disaster recovery site where the modules are located, that is, if the disaster recovery site is the primary site, the side car included in the disaster recovery site is the primary side car, and the synchronous coordinator is the primary synchronous coordinator, and vice versa; the side car and the synchronous coordinator can realize all functions in the two modes of the main mode and the standby mode, and execute the operation in the main mode when the side car and the synchronous coordinator are in the main mode, and execute the operation in the standby mode when the side car and the synchronous coordinator are in the standby mode.
The master side car is used for acquiring master abstract information of disaster recovery data in the master service container, receiving standby abstract information sent by the standby side car, and sending a synchronous data change object obtained by comparing the master abstract information with the standby abstract information to the master synchronous coordinator;
The side car refers to a separate process for realizing additional functions in a micro-service system outside the application; the side vehicles are used for carrying out dynamic deployment on the service containers, monitoring and calculating disaster tolerance data in the corresponding service containers to obtain abstract information, wherein the main service containers correspond to main abstract information, the standby service containers correspond to standby abstract information, and the main side vehicles are also used for comparing synchronous data change objects obtained by the main abstract information and the standby abstract information and sending the synchronous data change objects to the main synchronous coordinator; the standby side car is also used for blocking the initialization of the corresponding service container, receiving the synchronous data change object sent by the standby synchronous coordinator and writing the synchronous data change object into the file catalogue of the corresponding service container.
It should be noted that the number of side cars in a single disaster recovery site is a plurality of, specifically, the number of side cars depends on the number of service containers in a service system connected to the disaster recovery site, and one side car is correspondingly arranged in one service container. The service containers in different systems are correspondingly arranged, so that the side cars arranged in different disaster recovery sites are correspondingly arranged based on the service containers.
And the master synchronous coordinator is used for carrying out data synchronous operation according to the synchronous data change object.
The synchronous coordinator is used for carrying out synchronous data transmission between the main station and the standby station; specifically, the synchronous coordinator establishes a control pipeline and a data pipeline between the main station and the standby station, wherein the data pipeline comprises a plurality of data synchronous pipelines with different priorities, and is further used for controlling disaster-tolerant data to stop or resume synchronous transmission when a start-stop control instruction is received; the main synchronous coordinator is also used for transmitting the synchronous data change object sent by the main side car to the standby synchronous coordinator and selecting a corresponding data synchronous pipeline for synchronous transmission according to the priority of the synchronous data change object; the standby synchronous coordinator is also used for sending the synchronous data change object transmitted by the main synchronous coordinator to the standby side car.
The disaster recovery site also comprises a disaster recovery control console and a side car manager; the side car manager is respectively connected with the disaster recovery control console, the side car and the synchronous coordinator, wherein:
the disaster recovery control console is used for receiving the management instruction and sending a corresponding control signal to the side car manager according to the management instruction;
The disaster recovery control console provides a disaster recovery parameter configuration registry and a user operation and maintenance center, and performs interactive operation with operation and maintenance personnel; the disaster recovery parameters comprise disaster recovery file directory parameters, disaster recovery configuration parameters, disaster recovery automatic active-standby switching strategies and the like of each service container; the operation and maintenance personnel can set or trigger various disaster recovery services such as disaster recovery configuration parameters, start and stop control of disaster recovery services, main and standby switching of disaster recovery, monitoring of disaster recovery running states and the like on a visual interface of a disaster recovery control console, generate corresponding management instructions, and send corresponding control signals to a side vehicle manager based on the management instructions by the control console; the disaster recovery control console can also be connected with the side car or the synchronous coordinator to directly send corresponding control signals to the side car or the synchronous coordinator.
The side car manager is used for responding to the control signal to execute preset operation corresponding to the control signal;
the side car manager is further configured to send a setting signal to the side car and the synchronization coordinator when a preset condition is met;
the side car is used for adjusting the running state of the side car according to the setting signal;
the synchronous coordinator is used for adjusting the running state of the synchronous coordinator according to the setting signal.
The side car manager is used for controlling the running states of the side car and the synchronous coordinator according to the control signal of the disaster recovery control console; the side car manager is mainly used for managing the life cycle and the running state of the side car, and dynamically dispatching and deploying the side car corresponding to each service container according to disaster recovery file catalog parameters defined by service container statement or disaster recovery configuration parameters issued by a disaster recovery control console.
The disaster recovery site may further include middleware such as PG/FTP/ES, to implement a remote disaster recovery data synchronization scheme of the middleware object, where specific settings may be selected based on an actual application scenario, which is not described herein. The disaster recovery site may further include basic structural modules such as laaS or bare metal servers, magnetic arrays or other storage hardware, and specific settings may be selected based on actual application scenarios, which are not described herein.
Referring to fig. 2, fig. 2 is a flow chart of a first embodiment of a disaster recovery system control method according to the present invention, the method includes the steps of:
step S10, acquiring main abstract information of disaster recovery data in a main service container through a main side vehicle, and receiving standby abstract information sent by a standby side vehicle;
it can be understood that not all data in the service container are required to be subjected to disaster recovery, operation and maintenance personnel set the data which need to be subjected to disaster recovery in the service container, namely disaster recovery data by setting disaster recovery file catalog parameters, and the side car scans the disaster recovery data in the service container in real time to obtain abstract information corresponding to the disaster recovery data, wherein the abstract information is used for reflecting main parameters of the disaster recovery data, and the standby side car sends the obtained standby abstract information to the main side car.
When the side car scans disaster recovery data, a file list abstract can be calculated according to file names, sizes and time stamps of files in the disaster recovery data, the file size is scanned to obtain a quick calculation abstract, and when the file size is scanned, the file can be divided according to fixed sizes and then scanned to obtain the quick calculation abstract; different scanning modes have different efficiency based on different file sizes and numbers, so that different algorithms, such as rsync, RDC, zsync, etc., can be selected to scan different types of files, such as a large number of small files and a single oversized file.
Step S20, comparing the main abstract information with the standby abstract information to obtain a synchronous data change object through the main side car, and sending the synchronous data change object to a main synchronous coordinator;
the synchronous data change object is a differential file between the main service container and the standby service container; the differential file indicates that the disaster recovery data in the primary service container and the backup service container are not synchronized at this time, so that the disaster recovery data in the primary service container and the backup service container need to be synchronized through the differential file.
And step S30, carrying out data synchronization operation according to the synchronization data change object through the master synchronization coordinator.
The main synchronous coordinator transmits the synchronous data change object to enable the standby disaster recovery site to carry out data synchronization on the corresponding service container through the synchronous data change object, so that disaster recovery data synchronization in the main service container and the standby service container is realized.
According to the embodiment, the backup of disaster recovery data is realized by disposing the side car on the service container, the disaster recovery system does not invade the service, the service is decoupled from the disaster recovery, and the service does not participate in the disaster recovery, so that the service development is convenient to realize.
Further, in the second embodiment of the disaster recovery system control method according to the present invention set forth in the first embodiment of the present invention, the step S30 includes the steps of:
step S31, the synchronous data change object is sent to the standby synchronous coordinator through the main synchronous coordinator;
step S32, the standby synchronous coordinator sends the synchronous data change object to the standby side car corresponding to the incremental content data;
and step S33, writing the synchronous data change object into the corresponding standby service container through the standby side car.
When the primary synchronization coordinator receives the synchronization data change object, the primary synchronization coordinator acquires the data synchronization pipeline corresponding to the data priority of the synchronization data change object, and synchronously copies the synchronization data change object to the standby synchronization coordinator through the data synchronization pipeline based on a Qos (Quality of Service) rate strategy.
It should be noted that, because the number of the side vehicles may be multiple, and the main side vehicle and the standby side vehicle are correspondingly set based on the service container, the synchronization data change object may include sub-objects from different side vehicles, after receiving the synchronization data change object, the standby synchronization coordinator needs to send the sub-objects in the synchronization data change object to the corresponding standby side vehicles, after receiving the sub-objects, the standby side vehicle writes the sub-objects into the standby service container, when the synchronization data in the sub-objects is newly added data, corresponding data is newly added in the file directory of the service container, and if the synchronization data in the sub-objects is updated data of original data, the original data is updated through the synchronization data.
The embodiment can realize data synchronization operation.
Further, in a third embodiment of the disaster recovery system control method according to the present invention set forth in the first embodiment of the present invention, the step S20 includes the steps of:
Step S21, comparing the main abstract information with the standby abstract information to obtain abstract difference data;
step S22, obtaining a disaster recovery file corresponding to the abstract difference data, and packaging the disaster recovery file to obtain the synchronous data change object.
It should be noted that, if the main abstract information has a newly added disaster recovery file relative to the standby abstract information, the newly added disaster recovery file is added to the abstract difference data; if the main abstract information has reduced disaster recovery files relative to the standby abstract information, generating cleaning instruction data according to the reduced disaster recovery files, and adding the cleaning instruction data into abstract difference data; the cleaning instruction data are used for indicating redundant data in the standby service container, and when the standby side car receives the cleaning instruction data, the disaster recovery file corresponding to the cleaning instruction data in the standby service container is deleted.
The step S22 includes the steps of:
step S221, judging whether the size of each disaster recovery file is larger than a preset volume or not;
step S222, if the size of the disaster recovery file is larger than a preset volume, extracting incremental data of the disaster recovery file according to the main abstract information and the standby abstract information;
If the size of the disaster recovery file is smaller than or equal to the preset volume, the disaster recovery file is packaged to obtain the synchronous data change object;
and S223, packaging the incremental data to obtain the synchronous data change object.
If the disaster recovery file updated by the primary abstract information relative to the standby abstract information occurs, the disaster recovery file contains the original data and the updated data, so that the volume of the synchronous data change object is often larger, in order to reduce the volume of the synchronous data change object, only the updated data, namely the incremental data, can be synchronously transmitted during synchronization, after the transmission, the standby side car can realize synchronization by updating the original data through the incremental data, and the specific value of the preset volume can be set based on the actual application scene without limitation.
The embodiment can accurately acquire the synchronous data change object.
Further, in a fourth embodiment of the disaster recovery system control method according to the present invention set forth in the first embodiment of the present invention, the step S10 includes the steps of:
step S11, a latest synchronous time stamp is obtained, and the master abstract information is generated according to the monitored file change event of the corresponding service container after the latest synchronous time stamp;
Step S12, receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to the monitored file change event of the corresponding service container after the latest synchronous time stamp.
Under incremental synchronization, the side car scans disaster recovery data in the service container in real time to synchronize, and after each synchronization is completed, relevant synchronization information and a synchronization time stamp are recorded, and because the incremental synchronization is continuous, after each synchronization is completed, the disaster recovery data in the main service container and the standby service container are kept synchronous, so that only corresponding data generated by file change events occurring after the time stamp need to be synchronized; in order to avoid the excessive data processing amount, the corresponding abstract information is obtained by scanning the file generated by the file change event occurring after the latest synchronous time stamp, and then the data synchronous operation is executed according to the abstract information. The step S10 includes the steps of:
step S13, if a full synchronization signal sent by a side car manager is received, generating the main abstract information according to all files of the corresponding service container;
And step S14, receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to all files of the corresponding service container after receiving the full synchronization signal.
The full synchronization signal can be set to periodically trigger, and the operation and maintenance personnel can select corresponding functions to trigger on the disaster recovery control console.
In the operation process of the disaster recovery system, the disaster recovery files between the main service system and the standby service system are seriously inconsistent due to the events of network abnormal interruption, station power failure shutdown maintenance or newly-added standby stations and the like, and the time is too long if the synchronization is performed only in an incremental mode; at this time, a full-scale synchronization operation is performed; in the full-volume synchronous operation, summary information is obtained by scanning all disaster recovery files of the service container, namely, all disaster recovery files between the main service system and the standby service system are compared, and the consistency between the main service system and the standby service system is quickly restored. It can be understood that in the full synchronization, the differential files between the main service system and the standby service system are synchronized as well.
The embodiment realizes optimal synchronization efficiency by setting the increment synchronization and the full synchronization respectively and executing different synchronization modes under different scenes.
Further, in a fifth embodiment of the disaster recovery system control method according to the present invention set forth in the first embodiment of the present invention, before the step S10, the method includes the steps of:
step S40, detecting a micro-service blueprint of a service system through a side car manager, and extracting disaster recovery parameters if the micro-service blueprint is detected to contain the disaster recovery parameters;
and S50, generating a disaster recovery side car blueprint according to the disaster recovery parameters through the side car manager, and adding the disaster recovery side car blueprint into the micro-service blueprint to perform associated deployment on the side car and the service container.
The micro-service blueprint and the disaster recovery parameters are set by operation and maintenance personnel on a disaster recovery control console; firstly, respectively installing PaaS system micro-service grids in a disaster recovery site environment, deploying modules such as a disaster recovery control console, a side car manager and a synchronous coordinator, starting the operation of the disaster recovery system, and setting related parameters by operation and maintenance personnel in the disaster recovery control console; and the side car manager starts to intercept a micro-service blueprint deployment flow event of the service system after running, when a disaster recovery parameter is defined in the micro-service blueprint to be deployed, the disaster recovery parameter is extracted, a disaster recovery side car blueprint is added in the micro-service blueprint according to the disaster recovery parameter, and then the micro-service blueprint deployment flow event is continuously executed to deploy each service container, and meanwhile, the side cars are associated and deployed. By the method, the service system does not need to participate in disaster recovery setting, and decoupling of the service and the disaster recovery is realized.
After the service container and the side vehicles are deployed, the operation and maintenance personnel can also modify the disaster recovery parameters at the disaster recovery control console, and the side vehicle manager deletes or newly adds the corresponding side vehicle or adjusts the data required to carry out disaster recovery through the modified disaster recovery parameters.
The method further comprises the steps of:
step S50, the disaster recovery control console sends a main signal or a standby signal to the side car manager according to the received management instruction;
step S60, if the side car management controller receives the main signal, a main setting signal is sent to the main side car and the main synchronous coordinator so that the main side car executes main synchronous operation, and the main synchronous coordinator sets the data transmission direction as output;
the main side car is used for realizing the data synchronization function and is not repeated. For data synchronization, the primary station is connected to the backup station, and therefore the primary synchronization coordinator sets the data transmission direction as output.
And step S70, if the side car management controller receives the standby signal, a standby setting signal is sent to the standby side car and the standby synchronous coordinator so that the standby side car blocks the corresponding service container for initialization, and standby synchronous operation is executed, and the standby synchronous coordinator sets the data transmission direction as input.
In order to prevent data collision caused by synchronous writing of the main service system and the standby service system, the standby side vehicle needs to block the initialization of the corresponding service container in addition to the synchronous operation so as to prevent the normal operation of the standby service container, thereby enabling the standby service container to be incapable of writing data through own service.
The operation and maintenance personnel can rapidly switch the service from the main service system to the standby service system through the main-standby switching function of the disaster recovery control console when events such as natural disasters or disaster recovery exercise test occur in the operation of the main service system; an automatic active/standby switching strategy can be set, and automatic switching can be completed under the condition that the automatic switching condition is met.
Specifically, when the primary and standby switching is required, a primary signal is sent to an original standby side car through a side car manager so that the standby side car is converted into the primary side car, and a standby signal is sent to the original primary side car so that the primary side car is converted into the standby side car;
the original standby service container is always in an initialized state when being blocked by the standby side vehicle, and stops blocking when the standby side vehicle is converted into the main side vehicle, and the standby service container is converted into the main service container after initialization is completed; because the original main service container is operated, the original main service container needs to be restarted, and the standby side car can block the restarting of the original main service container in the restarting process and is converted into the standby service container.
In the embodiment, the main-standby switching can be realized only by setting the state of the side vehicle, so that the time consumption is low, the RTO index of the disaster-tolerant main-standby switching is very small, the second level is basically reached, the seamless switching requirement of the service can be supported, and the high standard requirement similar to the disaster-tolerant double-activity scheme is reached.
Furthermore, during the upgrade and maintenance of the service system or disaster recovery site, the data synchronization process between the main and standby sites needs to be interrupted, so as to avoid abnormal data synchronization. The operation and maintenance personnel can select the function of file data pause synchronization through the disaster recovery control console to trigger a pause instruction so as to pause all or pause the data synchronization of the service container according to the service as required.
The side car manager sends a pause signal to the corresponding side car and the synchronous coordinator based on the pause instruction, and the main side car continuously monitors file change events in the service container and generates abstract information after receiving the pause signal, but pauses and suspends the processes of comparing the difference of the main abstract information and the standby abstract information and pushing the synchronous data change object to the main synchronous coordinator; the master synchronous coordinator stops synchronous transmission; and after waiting for the disaster recovery control console to issue a recovery instruction, the side car and the synchronous coordinator recover the synchronous flow.
The basic operation strategy of the disaster recovery system based on the side car is perfectly set in the embodiment.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the present application.
From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method described in the embodiments of the present application.
Referring to fig. 3, the electronic device may include components such as a communication module 10, a memory 20, and a processor 30 in a hardware configuration. In the electronic device, the processor 30 is connected to the memory 20 and the communication module 10, and the memory 20 stores a computer program, and the computer program is executed by the processor 30 at the same time, where the computer program implements the steps of the method embodiments described above when executed.
The communication module 10 is connectable to an external communication device via a network. The communication module 10 may receive a request sent by an external communication device, and may also send a request, an instruction, and information to the external communication device, where the external communication device may be another electronic apparatus, a server, or an internet of things device, such as a television, etc.
The memory 20 is used for storing software programs and various data. The memory 20 may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required for at least one function (such as obtaining, by a host side vehicle, host summary information of disaster recovery data in a host service container), and the like; the storage data area may include a database, may store data or information created according to the use of the system, and the like. In addition, the memory 20 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 30, which is a control center of the electronic device, connects various parts of the entire electronic device using various interfaces and lines, performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 20, and calling data stored in the memory 20, thereby performing overall monitoring of the electronic device. Processor 30 may include one or more processing units; alternatively, the processor 30 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 30.
Although not shown in fig. 3, the electronic device may further include a circuit control module, where the circuit control module is used to connect to a power source to ensure normal operation of other components. It will be appreciated by those skilled in the art that the electronic device structure shown in fig. 3 is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
The present invention also proposes a computer-readable storage medium on which a computer program is stored. The computer readable storage medium may be the Memory 20 in the electronic device of fig. 3, or may be at least one of ROM (Read-Only Memory)/RAM (Random Access Memory ), magnetic disk, or optical disk, and the computer readable storage medium includes several instructions for causing a terminal device (which may be a television, an automobile, a mobile phone, a computer, a server, a terminal, or a network device, etc.) having a processor to perform the method according to the embodiments of the present invention.
In the present invention, the terms "first", "second", "third", "fourth", "fifth" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance, and the specific meaning of the above terms in the present invention will be understood by those of ordinary skill in the art depending on the specific circumstances.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, the scope of the present invention is not limited thereto, and it should be understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications and substitutions of the above embodiments may be made by those skilled in the art within the scope of the present invention, and are intended to be included in the scope of the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (12)
1. A disaster recovery system control method, the method comprising:
acquiring main abstract information of disaster recovery data in a main service container through a main side vehicle, and receiving standby abstract information sent by a standby side vehicle;
the master side car compares the master abstract information with the standby abstract information to obtain a synchronous data change object, and sends the synchronous data change object to a master synchronous coordinator;
and carrying out data synchronization operation according to the synchronization data change object through the master synchronization coordinator.
2. The disaster recovery system control method according to claim 1, wherein the step of performing data synchronization operation by the active synchronization coordinator according to the synchronization data change object comprises:
Transmitting the synchronous data change object to the standby synchronous coordinator through the active synchronous coordinator;
transmitting the synchronous data change object to the standby side car corresponding to the incremental content data through the standby synchronous coordinator;
and writing the synchronous data change object into the corresponding standby service container through the standby side car.
3. The disaster recovery system control method according to claim 1, wherein the step of comparing the primary digest information with the backup digest information to obtain a synchronous data change object comprises:
comparing the main abstract information with the standby abstract information to obtain abstract difference data;
and acquiring a disaster recovery file corresponding to the abstract difference data, and packaging the disaster recovery file to obtain the synchronous data change object.
4. The disaster recovery system control method as set forth in claim 3, wherein said step of encapsulating said disaster recovery file to obtain said synchronous data change object comprises:
judging whether the size of each disaster recovery file is larger than a preset volume or not for each disaster recovery file;
if the size of the disaster recovery file is larger than the preset volume, extracting incremental data of the disaster recovery file according to the main abstract information and the standby abstract information;
And packaging the incremental data to obtain the synchronous data change object.
5. The disaster recovery system control method according to claim 1, wherein the step of obtaining main summary information of disaster recovery data in the main service container and receiving backup summary information sent by the backup side car comprises:
acquiring a latest synchronous time stamp, and generating the main abstract information according to the monitored file change event of the corresponding service container after the latest synchronous time stamp;
and receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to the monitored file change event of the corresponding service container after the latest synchronous time stamp.
6. The disaster recovery system control method according to claim 1, wherein the step of obtaining main summary information of disaster recovery data in the main service container and receiving backup summary information sent by the backup side car comprises:
if a full synchronization signal sent by a side car manager is received, generating the main abstract information according to all files of the corresponding service container;
And receiving standby abstract information sent by the standby side car, wherein the standby abstract information is generated by the standby side car according to all files of the corresponding service container after receiving the full synchronization signal.
7. The disaster recovery system control method according to claim 1, wherein the step of obtaining, by the host side vehicle, the host summary information of the disaster recovery data in the host service container includes:
detecting a micro-service blueprint of a service system through a side car manager, and extracting disaster recovery parameters if the micro-service blueprint is detected to contain the disaster recovery parameters;
and generating a disaster recovery side car blueprint according to the disaster recovery parameters through the side car manager, and adding the disaster recovery side car blueprint into the micro-service blueprint to perform associated deployment on the side car and the service container.
8. The disaster recovery system control method as set forth in claim 1, wherein the method further comprises:
the disaster recovery control console sends a main signal or a standby signal to the side car manager according to the received management instruction;
if the side car management controller receives the main signal, a main setting signal is sent to the main side car and the main synchronous coordinator so that the main side car executes main synchronous operation, and the main synchronous coordinator sets the data transmission direction as output;
And if the side car management controller receives the standby signal, sending a standby setting signal to the standby side car and the standby synchronous coordinator so as to initialize the service container corresponding to the blocking of the standby side car and execute standby synchronous operation, wherein the standby synchronous coordinator sets the data transmission direction as input.
9. The disaster recovery system is characterized by comprising a plurality of disaster recovery sites, wherein the plurality of disaster recovery sites comprise a main site and at least one standby site, the main site is connected with a main service system, the standby site is connected with a standby service system, the main site comprises a main side car and a main synchronous coordinator, the main side car is respectively connected with a main service container of the main service system and the main synchronous coordinator, the standby site comprises a standby side car and a standby synchronous coordinator, the standby side car is respectively connected with a standby service container of the standby service system and the standby synchronous coordinator, the main side car is also connected with the standby side car, and the main synchronous coordinator is also connected with the standby synchronous coordinator, wherein:
The master side car is used for acquiring master abstract information of disaster recovery data in the master service container, receiving standby abstract information sent by the standby side car, and sending a synchronous data change object obtained by comparing the master abstract information with the standby abstract information to the master synchronous coordinator;
and the master synchronous coordinator is used for carrying out data synchronous operation according to the synchronous data change object.
10. The disaster recovery system of claim 9, wherein the disaster recovery site further comprises a disaster recovery console and a sidecar manager; the side car manager is respectively connected with the disaster recovery control console, the side car and the synchronous coordinator, wherein:
the disaster recovery control console is used for receiving the management instruction and sending a corresponding control signal to the side car manager according to the management instruction;
the side car manager is used for responding to the control signal to execute preset operation corresponding to the control signal;
the side car manager is further configured to send a setting signal to the side car and the synchronization coordinator when a preset condition is met;
the side car is used for adjusting the running state of the side car according to the setting signal;
The synchronous coordinator is used for adjusting the running state of the synchronous coordinator according to the setting signal.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the disaster recovery system control method according to any one of claims 1 to 8.
12. A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and the computer program when executed by a processor implements the steps of the disaster recovery system control method according to any one of claims 1 to 8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210701552.XA CN117294723A (en) | 2022-06-17 | 2022-06-17 | Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium |
| PCT/CN2023/099276 WO2023241466A1 (en) | 2022-06-17 | 2023-06-09 | Disaster recovery system control method, disaster recovery system, electronic apparatus and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210701552.XA CN117294723A (en) | 2022-06-17 | 2022-06-17 | Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117294723A true CN117294723A (en) | 2023-12-26 |
Family
ID=89192150
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210701552.XA Pending CN117294723A (en) | 2022-06-17 | 2022-06-17 | Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN117294723A (en) |
| WO (1) | WO2023241466A1 (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11249856B2 (en) * | 2018-10-25 | 2022-02-15 | EMC IP Holding Company LLC | Application consistent snapshots as a sidecar of a containerized application |
| CN111294391A (en) * | 2020-01-17 | 2020-06-16 | 深信服科技股份有限公司 | Configuration synchronization method, device, equipment and readable storage medium |
| CN111367871B (en) * | 2020-02-29 | 2022-06-10 | 华南理工大学 | Method for increment synchronization among files based on SAPCI (software application programming interface) variable-length blocks |
| CN111563009A (en) * | 2020-04-26 | 2020-08-21 | 深圳震有科技股份有限公司 | File synchronization method, system and storage medium based on dual-computer redundancy system |
| CN111651523B (en) * | 2020-05-29 | 2022-09-16 | 烽火通信科技股份有限公司 | MySQL data synchronization method and system of Kubernetes container platform |
| CN114328005B (en) * | 2021-09-08 | 2022-08-26 | 深圳市木浪云科技有限公司 | Method and system for incremental backup of container data |
-
2022
- 2022-06-17 CN CN202210701552.XA patent/CN117294723A/en active Pending
-
2023
- 2023-06-09 WO PCT/CN2023/099276 patent/WO2023241466A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023241466A1 (en) | 2023-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101908980B (en) | Network management upgrading method and system | |
| CN110581782B (en) | Disaster tolerance data processing method, device and system | |
| CN111427728B (en) | State management method, main/standby switching method and electronic equipment | |
| CN113051110A (en) | Cluster switching method, device and equipment | |
| CN105426213A (en) | Software update method and system | |
| CN115576655B (en) | Container data protection system, method, device, equipment and readable storage medium | |
| CN106850724B (en) | Data pushing method and device | |
| CN113472956A (en) | Cloud mobile phone management method and device | |
| CN100512474C (en) | Automatic synchronization method for master-slave board storage version of the communication system | |
| CN102045187A (en) | Method and equipment for realizing HA (high-availability) system with checkpoints | |
| CN112052127B (en) | Data synchronization method and device for dual-computer hot standby environment | |
| CN112929438B (en) | Business processing method and device of double-site distributed database | |
| CN117294723A (en) | Disaster recovery system control method, disaster recovery system, electronic device and readable storage medium | |
| CN111400263A (en) | Monitoring switch-back method and device based on file change | |
| CN110620798A (en) | Control method, system, equipment and storage medium for FTP connection | |
| CN110351122B (en) | Disaster recovery method, device, system and electronic equipment | |
| CN116166470A (en) | Redis cluster clone replication method and device, medium and equipment | |
| CN114726711A (en) | Method and system for cooperative processing service between devices | |
| CN114385366A (en) | Elastic capacity expansion method, system, medium and equipment for container group of container cloud platform | |
| CN111241200B (en) | Master-slave synchronous processing method and device based on SQLite database | |
| CN108600354B (en) | System response time fluctuation suppression method and system | |
| CN113821334A (en) | Method, device and system for configuring edge side equipment | |
| CN112527552A (en) | Disaster recovery method, device, local point and storage medium | |
| CN105512116A (en) | Data synchronization method and device | |
| KR100211585B1 (en) | Method for data recovery for data consistency in pcs system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |