CN102831038B - The disaster recovery method and ENUM-DNS of ENUM-DNS - Google Patents
The disaster recovery method and ENUM-DNS of ENUM-DNS Download PDFInfo
- Publication number
- CN102831038B CN102831038B CN201110164445.XA CN201110164445A CN102831038B CN 102831038 B CN102831038 B CN 102831038B CN 201110164445 A CN201110164445 A CN 201110164445A CN 102831038 B CN102831038 B CN 102831038B
- Authority
- CN
- China
- Prior art keywords
- database
- standby
- data
- enum
- dns
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses the disaster recovery method of ENUM-DNS a kind of and ENUM-DNS, ENUM-DNS includes active system and back-up system, this method comprises the following steps: after active system stops working, the back-up system for being loaded with standby database receives the service request from SPN；Back-up system carries out business processing corresponding with service request.It ensure that the stability of business processing through the invention.
Description
Technical field
The present invention relates to the communications fields, map domain name analysis system in particular to a kind of telephone number
The disaster recovery method and ENUM- of (tElephone Number Mapping-Domain Name System, referred to as ENUM-DNS)
DNS。
Background technique
Currently, IMS-ENUM system has active and standby two sets of ENUM-DNS.There is kiosk (for example, providing in ENUM-DNS
BOSS business), database (Data Base, referred to as DB) two-shipper and O&M.BOSS business major function is to receive service to provide
The BOSS that network (Service Provider Network, referred to as SPN) issues is opened, cancellation is requested.Under normal circumstances, SPN
It is interacted with BOSS business, request is opened, cancellation operates.
Since spare ENUM-DNS is provided solely for backup database, (for example, delay machine) is stopped working in main equipment room in this way
In the case of, although can guarantee the complete of database data, it not can guarantee being normally carried out for the business from SPN but.
In the case that main equipment room stops working in the prior art, not can guarantee the business processing from SPN normally into
Capable problem, currently no effective solution has been proposed.
Summary of the invention
The main purpose of the present invention is to provide the disaster recovery method of ENUM-DNS a kind of and ENUM-DNS, at least to solve
State problem.
According to an aspect of the invention, there is provided a kind of disaster recovery method of ENUM-DNS, the ENUM-DNS includes master
With system and back-up system, described method includes following steps: after the active system stops working, being loaded with spare number
The service request from SPN is received according to the back-up system in library；The back-up system carries out corresponding with the service request
Business processing.
Preferably, the above method further include: after the active system is normal, by the data in the standby database
It is synchronized to primary database；After the active system loads the primary database, the service request from the SPN is received
And carry out business processing.
Preferably, before the active system stops working, further includes: the active system is pressed with the back-up system
The service request from the SPN is received according to respective load, and carries out business processing, wherein primary database and spare number
It keeps synchronizing according to library.
Preferably, the primary database and the data of the standby database synchronize include: the primary database and
Data in database are generated full dose file or delta file, concurrently by the newer side of data in the standby database
Give another party in the primary database and the standby database；Described another party is according to the full dose file or described
Delta file synchronizes.
Preferably, the above method further includes that the side that data are newer in the primary database and the standby database is logical
It crosses File Transfer Protocol and the full dose file or the delta file is sent to described another party.
According to another aspect of the present invention, a kind of ENUM-DNS, including active system and back-up system are provided, is loaded
The back-up system of preliminary data includes: receiving module, after the active system stops working, is come from for receiving
The service request of SPN；Processing module, for carrying out business processing corresponding with the service request.
Preferably, the back-up system further include: the back-up system further include: synchronization module, for described primary
After system is normal, the data in the standby database are synchronized to primary database；The active system includes: reception mould
Block, after loading the primary database, for receiving the service request from the SPN；Processing module, for carrying out industry
Business processing.
Preferably, before the active system stops working, further includes: in the active system and the back-up system
Receiving module, according to respective load receive the service request from the SPN, and be sent to business module carry out business at
Reason, wherein primary database is synchronous with standby database holding.
Preferably, the primary database is synchronous by data simultaneous module with the data of the standby database, wherein
The data simultaneous module, for the data of the newer side of data in the primary database and the standby database are raw
At full dose file or delta file, and the another party being sent in the primary database and the standby database carries out together
Step.
Preferably, the data simultaneous module sends the full dose file or increment text by File Transfer Protocol
Part.
Through the invention, the service request from SPN, spare system are received using the back-up system for being loaded with standby database
System carries out corresponding with service request business processing, solves in the prior art when host system stops working, not can guarantee
The problem of business from SPN is normally carried out, and then ensure that service stability.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the flow chart of the disaster recovery method of ENUM-DNS according to an embodiment of the present invention；
Fig. 2 is the flow chart of the disaster recovery method of ENUM-DNS according to the preferred embodiment of the invention；
Fig. 3 is the structural block diagram of ENUM-DNS according to an embodiment of the present invention；
Fig. 4 is the structural block diagram of ENUM-DNS according to the preferred embodiment of the invention；
Fig. 5 is the flow chart of the ENUM-DNS disaster recovery method of bi-directional synchronization according to an embodiment of the present invention；
Fig. 6 is the network architecture diagram of ENUM-DNS system according to the preferred embodiment of the invention；
Fig. 7 is the data synchronization message interaction between the system of ENUM-DNS under normal circumstances being preferably implemented according to the present invention
Flow chart；
Fig. 8 is the data-message interaction of standby ENUM-DNS system in the case of host delay machine according to the preferred embodiment of the invention
Flow chart；
Fig. 9 is that the data synchronization message of ENUM-DNS system under host recovery situation according to the preferred embodiment of the invention is handed over
Mutual flow chart.
Specific embodiment
Hereinafter, the present invention will be described in detail with reference to the accompanying drawings and in combination with Examples.It should be noted that not conflicting
In the case of, the features in the embodiments and the embodiments of the present application can be combined with each other.
In the examples below, ENUM-DNS includes active system and back-up system, wherein active system and back-up system
It include kiosk (such as BOSS business), DB.As one than preferably embodiment, in active system and back-up system
It can also include O&M, certain DB can also be by the way of two-shipper.
Fig. 1 is the flow chart of the disaster recovery method of ENUM-DNS according to an embodiment of the present invention, which includes primary
System and back-up system, as shown in Figure 1, this method comprises the following steps:
Step S102, after active system stops working, the back-up system for being loaded with standby database is received from SPN
Service request；
Step S104, back-up system carry out business processing corresponding with service request.
Through the above steps, back-up system provides the processing function to the business from SPN, to ensure that at business
The stability of reason.
Implement when, if the hardware configuration of active system and back-up system be it is comparable, active system restore
After work, active system can not be enabled immediately and business is handled, can opened again after back-up system stops working
Use active system.Certainly, in order to save hardware cost, the hardware configuration of back-up system can be lower than active system, in this way, spare
The processing speed of system can be not so good as active system, after active system recovery, can enable active system immediately.Fig. 2 is
The flow chart of the disaster recovery method of ENUM-DNS according to the preferred embodiment of the invention, as shown in Fig. 2, the process includes following step
It is rapid:
Data in standby database are synchronized to primary database after active system is normal by step S202；
Step S204, after active system loads primary database, service request of the reception from SPN is gone forward side by side at industry business
Reason (for example, active system can be started, or active system can also be enabled immediately after back-up system stops working).
After active system restores normal, back-up system can stop receiving the data that SPN is issued, and stop to relevant
Data are handled, and the data of the standby database (i.e. standby database) of back-up system are synchronized to during active system is deactivated
The primary database (i.e. primary database) of active system；Certainly, as one than preferably embodiment, back-up system can also
To continue to the data that SPN is issued, according to respective load, either proportionally distribution reception SPN is issued with active system
Data, and its business is handled jointly, at this point, the data of the database of the database and back-up system of active system are protected
Hold synchronization.By the preferred embodiment, the resource of active system and back-up system can be farthest utilized.
Certainly, before active system stops working, it can be only business of the active system processing from SPN, it can also
To be active system and back-up system according to service request of the respective load reception from SPN, and business processing is carried out,
In, primary database is synchronous with standby database holding.Certainly, if the hardware configuration of back-up system and hardware operating parameter not
Such as the hardware configuration and hardware operating parameter of active system, before active system stops working, back-up system can be only same
The data for walking primary database, the data issued without receiving SPN, do not carry out the processing of business, only in active system to it
After stopping working, back-up system (cannot receive the data that SPN is issued and to it into main operating system as temporary convert for a long time
Handled), the data that SPN is issued are received, and handle the data service.To ensure that primary database and spare
The consistency of database.
It is synchronous with standby database for primary database can by the way of full dose and also use increment side
Formula, for example, the data in database are generated full dose file by the newer side of data in primary database and standby database
Or delta file, and the another party being sent in primary database and standby database, another party is according to full dose file or increment
File synchronizes.As a preferably embodiment, the newer side of data can in primary database and standby database
Full dose file or delta file to be sent by File Transfer Protocol (File Transfer Protocol, referred to as FTP)
To another party.The embodiment is realized simple and reliable.
In the present embodiment, a kind of ENUM-DNS is additionally provided, for realizing above-described embodiment and its preferred embodiment,
The descriptions that have already been made will not be repeated.The module being related in the system is illustrated below.It should be noted that such as with
Used in lower, the combination of the software and/or hardware of predetermined function is may be implemented in term " module " " system ".Although implementing below
System and method described in example are preferably realized with software, but the combined realization of hardware or software and hardware
It may and be contemplated.
Fig. 3 is the structural block diagram of ENUM-DNS according to an embodiment of the present invention, as shown in figure 3, the ENUM-DNS includes master
With system 30 and back-up system 32, wherein the back-up system 32 for being loaded with preliminary data includes receiving module 320, processing module
322.The modules of the ENUM-DNS are illustrated below.
Receiving module 320, after active system 30 stops working, for receiving the service request from SPN；Handle mould
Block 322 is connected to receiving module 320, and the module is for carrying out business processing corresponding with SPN service request.
Fig. 4 is the structural block diagram of ENUM-DNS according to the preferred embodiment of the invention, in the preferred embodiment, spare system
System 32 further include: synchronization module 324, for after active system 30 is normal, the data in standby database to be synchronized to master
Use database；Active system 30 includes: receiving module 300, after loading primary database, for receiving the industry from SPN
Business request；Processing module 302 is connected to receiving module 300, and for carrying out business processing, synchronization module 304 is connected to the module
Processing module 302, for synchronizing primary database and standby database after active system 30 is normal.
Preferably, before active system 30 stops working, further includes: the reception in active system 30 and back-up system 32
Module (receiving module 300 of active system 30, the receiving module 320 of back-up system) receives according to respective load and comes from SPN
Service request, and be sent to business module carry out business processing, wherein primary database is synchronous with standby database holding.
Preferably, primary database is synchronous by data simultaneous module with the data of standby database, wherein data are synchronous
Module can be located at active system, can also be located in back-up system or active system and back-up system and there are data
Synchronization module, the module are used to the data of the newer side of data in primary database and standby database generating full dose file
Or delta file, and the another party being sent in primary database and standby database synchronizes.It is preferably real as one
Mode is applied, data simultaneous module sends full dose file or delta file by FTP.
Through the foregoing embodiment and preferred embodiment, it receives by using the back-up system for being loaded with standby database
From the service request of SPN, back-up system carries out corresponding with SPN service request business processing, solve in the prior art when
When host system stops working, SPN can not normally be interacted with ENUM-DNS (for example, can not normal request open, cancellation
Operation) the problem of.To ensure that, SPN can carry out normal business friendship with ENUM-DNS system after host stops working
Mutually.
Another preferred embodiment is illustrated below, this embodiment combines above-described embodiment and preferred implementation sides
Formula provides a kind of ENUM-DNS disaster tolerance solution of bi-directional synchronization in the present embodiment, and this method is (primary in main equipment room
System is located in main equipment room) stop working after, the business in standby host room (back-up system is located in standby host room) receiving host room, and right
Related service is handled, and when main equipment room restores, the data in standby host room are automatically synchronized to main equipment room.
Fig. 5 is the flow chart of the ENUM-DNS disaster recovery method of bi-directional synchronization according to an embodiment of the present invention, as shown in figure 5,
The process includes the following steps:
Step S502 is automatically performed the synchronization of the active and standby database of active and standby ENUM-DNS system under normal circumstances.It needs
Illustrate, which can be completed by database synchronization module, which can be deployed in master
In ENUM-DNS system, but not limited to this.It is carried out simultaneously using the fault recovery process of database synchronization module and business itself
It is synchronous, so that it is guaranteed that when standby host room enables database data consistency, avoid because the exception of database synchronization module causes
The mistake of data.
Step S504, after host delay machine (host delay machine is a kind of mode that host stops working), standby BOSS service announcements
Received shipment dimension will be loaded into standby ENUM-DNS for data full dose in database.
Step S506, after loading successfully, main equipment room is replaced in standby host room.For example, the standby main BOSS business (example of BOSS service take-over
Such as, receive the opening of SPN, cancellation request, opened, the load of cancellation data).
Step S508, host restores, and after standby host detects successfully automatically, standby BOSS business will notify received shipment dimension to stop working,
Simultaneously primary database database will be then synchronized to for data export in database.It synchronizes and is divided into full dose synchronization and increment synchronization
Two ways.Due to supporting full dose synchronous simultaneously and increment synchronization mode, the record number issued according to SPN selects increment or complete
Amount.It is synchronous only to need the data record that SPN is issued during synchronous standby host enabling under incremental mode.Increment synchronization will greatly reduce
Synchronous record number is needed when host restores, and shortens the recovery time of host.
Step S510, after database synchronization success, main BOSS business will notify main O&M to load data in primary database
To main ENUM-DNS.After loading successfully, main BOSS business is reactivated, and completes resuming work for main equipment room.Bi-directional synchronization, including
Active and standby synchronization with it is standby, main synchronous.Active and standby synchronization is real-time synchronization, and synchronous main body is database synchronization module；Standby, main synchronization
Disposably to synchronize, synchronous main body is standby, main BOSS business.When the host recovers, standby, main BOSS business complete jointly it is standby,
Standby, primary database data consistency are realized in main synchronization.
In the preferred embodiment, all synchronization processes, including active and standby synchronization with it is standby, main synchronous, synchronizing process is all
Automatically it executes, is participated in without artificial, to not only reduce cost, while being avoided because artificially participating in possible accidentally behaviour
Make.And it is possible to when effectively ensureing the stability of entire ENUM-DNS and enhancing the ability to ward off risks and disaster generation, ENUM-
The availability and correctness of DNS.
Fig. 6 is the network architecture diagram of ENUM-DNS system according to the preferred embodiment of the invention, as shown in fig. 6, active and standby
ENUM-DNS system has 4 main network elements: business recipient processor (for example, BOSS), operation and maintenance management (Operation
Mantainace Management, referred to as OMM), provide DNS server and database (when implementation, can also be deployed in
In magnetic battle array), wherein BOSS and OMM is for realizing receiving module 300, receiving module 320, processing module 302 and processing module
322 function.Each network element and its function are illustrated below.
BOSS, the request for receiving, handling SPN opens, the message of cancellation, and the message data that SPN is issued is saved to number
According to library.
OMM, the zone added at interface for receiving user or record data, wherein zone be for distinguish it is different come
The different business in source generates corresponding file (for example, full dose file or delta file), then notifies according to database data
ENUM-DNS is loaded.
The server of DNS is provided, for realizing domain name conversion function.
DB database issues the data of data or interface addition for storing SPN.
Between primary database and standby database, by the database synchronization module of deployment, (module is same for realizing data
Walk the function of module 324), realize the real-time synchronization of data.Equally, there is also synchronizations between main ENUM-DNS and standby ENUM-DNS
Process, and be real-time synchronization.It should be noted that in the preferred embodiment, synchronous mode can be divided into full dose it is synchronous and
Increment synchronization two ways.
Fig. 7 is the data synchronization message interaction between the system of ENUM-DNS under normal circumstances being preferably implemented according to the present invention
Flow chart, in the present embodiment, under normal circumstances, main BOSS business enables, standby BOSS business deactivates.As shown in fig. 7, the process
Include the following steps:
Step S702, main BOSS business receive the opening of SPN, cancellation data.
Step S704, main BOSS business place the data in primary database in A table (for example, cache table).
Step S706, when needing synchronous table to change in database, database synchronization module can be detected, then
It notifies standby database to carry out identical operation, is finally completed the synchronization of database.
The record of A table in primary database periodically can be transferred to B table (for example, the number in database by step S708, main O&M
According to table) in, while full dose or delta file are generated according to the record of A table, file is then uploaded to the specified of main ENUM-DNS
Under catalogue.
Step S710, main O&M notify that main ENUM-DNS is loaded.
Step S712, main ENUM-DNS return load successfully corresponding.
Step S714, what main BOSS business can periodically specify relevant information (for example, sequence number) write-in of zone daily
File, while database can be needed the data of synchronous meter back up.Then the file of zone sequence number and database is standby
Part file is uploaded to by FTP under the specified folder of standby host.
Step S716, main ENUM-DNS send active and standby notify message to standby ENUM-DNS.
Step S718, standby ENUM-DNS return to notify response.
Step S720, main ENUM-DNS send active and standby IXF request to standby ENUM-DNS.
Step S722, standby ENUM-DNS return to IXF and respond
Fig. 8 is the data-message interaction of standby ENUM-DNS system in the case of host delay machine according to the preferred embodiment of the invention
Flow chart, as shown in figure 8, the process includes the following steps:
Step S802, after main equipment room delay machine, standby BOSS business reads the zone sequence number file that main BOSS business uploads, than
It is whether consistent with standby host current sequence number compared with the sequence number of host, decide whether the database for loading main BOSS business FTP
Backup file.If the sequence number of host is consistent with standby host current sequence number, load document is not needed, directly execution step
S804；If the sequence number of host and standby host current sequence number are inconsistent, load document is needed, executes step after loading successfully
S804。
Step S804, standby BOSS notice received shipment dimension carry out full dose and load data.
Step S806 after received shipment dimension receives the loading messages of standby BOSS, according to data in standby database table, generates full dose
Load document, and be uploaded under ENUM-DNS specified directory by FTP.
Step S808, after uploading successfully, received shipment dimension notifies standby BOSS to load successfully.
Step S810 after standby BOSS receives success message, notifies standby ENUM-DNS to load data.Standby ENUM-DNS is from specified
Increment or full dose file that received shipment dimension uploads are obtained under catalogue, are loaded.
Step S812 returns to the response message of standby BOSS after standby ENUM-DNS load.
Step S814, received shipment dimension enable.
Step S816, received shipment dimension, which returns, opens success response.
Port is listened in step S818, standby BOSS notice HTTP processing module HTTPPROC unlatching.
Step S820, HTTPPROC, which is returned, opens listening port response.Wherein, step S814 and step S818 can be together
Shi Jinhang is also possible to according to progress the step of this process.
Step S822, standby BOSS complete to substitute the work of main BOSS, standby BOSS start to enable (receive SPN and issue data, and
Its data service is handled).It should be noted that increment and two kinds of full dose work can be divided into after standby BOSS is enabled
Mode.
Step S824, under incremental mode, standby BOSS record saves the relevant database manipulation of data information that SPN is issued,
And it will be in the specified file of database manipulation deposit.
Fig. 9 is that the data synchronization message of ENUM-DNS system under host recovery situation according to the preferred embodiment of the invention is handed over
Mutual flow chart, as shown in figure 9, the process includes the following steps:
Step S902, after standby BOSS business detects that host restores, notice received shipment dimension is stopped using.
Step S904, received shipment dimension, which returns, closes response.
Step S906, standby BOSS, which are sent, closes the listening port order of standby BOSS to HTTPPROC.
Step S908, HTTPPROC return to the response of close port.
Main BOSS is notified to stop using simultaneously, the process of the main BOSS in active system is identical with back-up system, benefit
Step S902 to S908 is executed with equipment corresponding with back-up system in active system.
Step S910, when incremental mode, the file that database of record operates is uploaded to main BOSS's by FTP by standby BOSS
Then specified directory notifies that main BOSS is loaded.It should be noted that the step can also in such a way that full dose is synchronous,
When full dose is synchronous, standby BOSS will be for data export in database, and is uploaded to the specified directory of main BOSS, then notice master
BOSS is loaded.
Step S912, under incremental mode, main BOSS carries out identical database behaviour according to the database manipulation of file record
Make.It should be noted that the step can also be in such a way that full dose be synchronous, in full dose mode, main BOSS is according to data text
Data are loaded onto database by part.
After the database synchronization success of step S914, primary database and standby database, main BOSS will notify main O&M
It is loaded.
Step S916, main O&M are loaded by FTP upload data file to ENUMDNS.
Step S918, main O&M, which returns, records success response.
Step S920, main BOSS notify main ENUM-DNS to carry out increment or full dose load.
Step S922, after main ENUM-DNS is loaded successfully, main BOSS notice enables O&M and opens listening port.At this point,
Main equipment room restores to complete, and main BOSS business starts to receive the data distributing of SPN.
Through the foregoing embodiment, the stability and the enhancing ability to ward off risks of entire ENUM-DNS system have effectively been ensured,
Meanwhile when disaster occurs, the availability and correctness of ENUM-DNS system ensure that.
Industrial applicibility
Above-described embodiment and preferred embodiment can be applied to the ENUM-DNS in disaster tolerance environment, it is ensured that at the ENUM-DNS
The stability of reason business and the safety of data and consistency.
In another embodiment, a kind of disaster tolerance software is additionally provided, the software is for executing above-described embodiment and excellent
Select technical solution described in embodiment.
In another embodiment, a kind of storage medium is additionally provided, it is soft that above-mentioned disaster tolerance is stored in the storage medium
Part, which includes but is not limited to: CD, floppy disk, hard disk, scratch pad memory etc..
Obviously, those skilled in the art should be understood that each module of the above invention or each step can be with general
Computing device realize that they can be concentrated on a single computing device, or be distributed in multiple computing devices and formed
Network on, optionally, they can be realized with the program code that computing device can perform, so as to be stored in
It is performed by computing device in storage device, perhaps they are fabricated to each integrated circuit modules or will be in them
Multiple modules or step be fabricated to single integrated circuit module to realize.In this way, the present invention is not limited to any specific hard
Part and software combine.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (8)
1. a kind of disaster recovery method of telephone number mapping domain name analysis system, which is characterized in that the telephone number maps domain name
Resolution system includes active system and back-up system, and described method includes following steps:
After the active system stops working, the back-up system for being loaded with standby database is received to be provided from service
The service request of network SPN；
The back-up system carries out business processing corresponding with the service request；
Wherein, before the active system stops working, further includes: the active system is with the back-up system according to respective
Load receive the service request from the SPN, and carry out business processing, wherein primary database and standby database are protected
Hold synchronization.
2. the method according to claim 1, wherein further include:
After the active system is normal, the data in the standby database are synchronized to primary database；
After the active system loads the primary database, the service request from the service providing network SPN is received
And carry out business processing.
3. the method according to claim 1, wherein the data of the primary database and the standby database
It synchronizes and includes:
Data in database are generated full dose by the newer side of data in the primary database and the standby database
File or delta file, and the another party being sent in the primary database and the standby database；
Described another party synchronizes according to the full dose file or the delta file.
4. according to the method described in claim 3, it is characterized in that, data in the primary database and the standby database
The full dose file or the delta file are sent to described another party by File Transfer Protocol by a newer side.
5. a kind of telephone number maps domain name analysis system, which is characterized in that including active system and back-up system, be loaded with standby
Include: with the back-up system of data
Receiving module is asked after the active system stops working for receiving the business from service providing network SPN
It asks；
Processing module, for carrying out business processing corresponding with the service request；
Wherein, before the active system stops working, further includes: the reception in the active system and the back-up system
Module receives the service request from the SPN according to respective load, and is sent to business module and carries out business processing,
In, primary database is synchronous with standby database holding.
6. system according to claim 5, which is characterized in that the back-up system further include:
The back-up system further include: synchronization module is used for after the active system is normal, will be in the standby database
Data be synchronized to primary database；
The active system includes: receiving module, after loading the primary database, is mentioned for receiving from the service
For the service request of network SPN；Processing module, for carrying out business processing.
7. system according to claim 5, which is characterized in that the data of the primary database and the standby database
It is synchronous by synchronization module, wherein the synchronization module is used for data in the primary database and the standby database
The data of a newer side generate full dose file or delta file, and are sent to the primary database and the standby database
In another party synchronize.
8. system according to claim 7, which is characterized in that the synchronization module passes through described in File Transfer Protocol transmission
Full dose file or the delta file.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110164445.XA CN102831038B (en) | 2011-06-17 | 2011-06-17 | The disaster recovery method and ENUM-DNS of ENUM-DNS |
| PCT/CN2012/070851 WO2012171346A1 (en) | 2011-06-17 | 2012-02-02 | Telephone number mapping-domain name system (enum-dns) and disaster tolerance method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110164445.XA CN102831038B (en) | 2011-06-17 | 2011-06-17 | The disaster recovery method and ENUM-DNS of ENUM-DNS |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102831038A CN102831038A (en) | 2012-12-19 |
| CN102831038B true CN102831038B (en) | 2019-03-01 |
Family
ID=47334187
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110164445.XA Active CN102831038B (en) | 2011-06-17 | 2011-06-17 | The disaster recovery method and ENUM-DNS of ENUM-DNS |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102831038B (en) |
| WO (1) | WO2012171346A1 (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468244B (en) * | 2014-12-31 | 2018-04-20 | 北京奇虎科技有限公司 | Domain name analysis system calamity is for constructing method and device |
| CN105635341A (en) * | 2016-01-18 | 2016-06-01 | 浪潮通信信息系统有限公司 | Disaster recovery method and device based on DNS |
| CN106330945B (en) * | 2016-08-31 | 2020-04-24 | 北京信安世纪科技股份有限公司 | Digital certificate synchronization method, digital signature server and digital certificate synchronization system |
| CN107066480B (en) * | 2016-12-20 | 2020-08-11 | 创新先进技术有限公司 | Method, system and equipment for managing main and standby databases |
| CN107038094A (en) * | 2017-04-27 | 2017-08-11 | 紫光华山信息技术有限公司 | A kind of data back up method and device |
| CN109005246B (en) * | 2018-09-12 | 2021-10-01 | 北京国电通网络技术有限公司 | Data synchronization method, device and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1180569C (en) * | 2001-12-24 | 2004-12-15 | 华为技术有限公司 | Method for setting backup attaching position register |
| US7007042B2 (en) * | 2002-03-28 | 2006-02-28 | Hewlett-Packard Development Company, L.P. | System and method for automatic site failover in a storage area network |
| US7680876B1 (en) * | 2006-12-14 | 2010-03-16 | Cisco Technology, Inc. | Highly available domain name system |
| CN101309167B (en) * | 2008-06-27 | 2011-04-20 | 华中科技大学 | Disaster allowable system and method based on cluster backup |
| CN101729290A (en) * | 2009-11-04 | 2010-06-09 | 中兴通讯股份有限公司 | Method and device for realizing business system protection |
-
2011
- 2011-06-17 CN CN201110164445.XA patent/CN102831038B/en active Active
-
2012
- 2012-02-02 WO PCT/CN2012/070851 patent/WO2012171346A1/en active Application Filing
Non-Patent Citations (1)
| Title |
|---|
| 容灾抗毁系统研究;刘晓洁等;《全国网络与信息安全技术研讨会’2007》;20071231;全文 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102831038A (en) | 2012-12-19 |
| WO2012171346A1 (en) | 2012-12-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107526626B (en) | Docker container thermal migration method and system based on CRIU | |
| CN102831038B (en) | The disaster recovery method and ENUM-DNS of ENUM-DNS | |
| CN106250270B (en) | A kind of data back up method under cloud computing platform | |
| US9934242B2 (en) | Replication of data between mirrored data sites | |
| CN108964948A (en) | Principal and subordinate's service system, host node fault recovery method and device | |
| CN113641511B (en) | Message communication method and device | |
| CN109376197B (en) | Data synchronization method, server and computer storage medium | |
| CN102984194A (en) | Sychronization of configuration file of virtual application distribution chassis | |
| CN112463535B (en) | Multi-cluster exception handling method and device | |
| WO2019210580A1 (en) | Access request processing method, apparatus, computer device, and storage medium | |
| CN104753817A (en) | Local analogy method and local analogy system for cloud computing message queue service | |
| CN105721582A (en) | Multi-node file backup system | |
| CN111597197B (en) | Data reconciliation method and device between databases, storage medium and electronic equipment | |
| CN110032478A (en) | Method, device and system for real-time synchronization of data of main and standby centers and storage medium | |
| CN107729515B (en) | Data synchronization method, device and storage medium | |
| WO2016177231A1 (en) | Dual-control-based active-backup switching method and device | |
| CN115576655B (en) | Container data protection system, method, device, equipment and readable storage medium | |
| CN100512474C (en) | Automatic synchronization method for master-slave board storage version of the communication system | |
| CN105320577B (en) | A kind of data backup and resume method, system and device | |
| CN114297296A (en) | Server active-standby switching system for broadcasting | |
| CN105591801A (en) | Virtual network function VNF fault processing method and VNF management equipment | |
| CN102185717A (en) | Service processing equipment, method and system | |
| CN105323271B (en) | Cloud computing system and processing method and device thereof | |
| CN105872073A (en) | Design method of distributed timed task system based on etcd cluster | |
| CN111475537B (en) | Global data synchronization system based on pulsar |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |