CN112596945A - Disaster recovery method based on double main units - Google Patents

Disaster recovery method based on double main units Download PDF

Info

Publication number
CN112596945A
CN112596945A CN202011375958.0A CN202011375958A CN112596945A CN 112596945 A CN112596945 A CN 112596945A CN 202011375958 A CN202011375958 A CN 202011375958A CN 112596945 A CN112596945 A CN 112596945A
Authority
CN
China
Prior art keywords
data
disaster recovery
backup
recovery method
disaster
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011375958.0A
Other languages
Chinese (zh)
Inventor
邬玉良
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhongke Hot Standby Beijing Cloud Computing Technology Co ltd
Original Assignee
Zhongke Hot Standby Beijing Cloud Computing Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhongke Hot Standby Beijing Cloud Computing Technology Co ltd filed Critical Zhongke Hot Standby Beijing Cloud Computing Technology Co ltd
Priority to CN202011375958.0A priority Critical patent/CN112596945A/en
Publication of CN112596945A publication Critical patent/CN112596945A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1464Management of the backup or restore process for networked environments

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Hardware Redundancy (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention provides a disaster recovery method based on double masters, which relates to the field of computer data processing and realizes the disaster recovery method based on double masters.

Description

Disaster recovery method based on double main units
Technical Field
The invention relates to a disaster recovery method based on double masters, and belongs to the field of computer data safety processing.
Background
In recent years, with the development of information methods, enterprises are gradually increasing in information application and requirements, information coverage is increasing, and information is more and more important in life and work of people, so that the information security problem also becomes a key point in the field of computer data security at present. Disaster recovery backup in the modern society has solved the information security problem of the IT industry and has been well popularized.
The disaster-backup system is characterized in that two or more sets of IT systems with the same function are established in different places far away from each other, health status monitoring and function switching can be performed among the IT systems, and when one system stops working due to accidents (such as fire, earthquake and the like), the whole application system can be switched to the other system, so that the functions of the system can continue to work normally. The disaster recovery technology is a component of the high-availability technology of the system, and the disaster recovery system emphasizes the processing of the influence of the external environment on the system, particularly the influence of a catastrophic event on the whole IT node, and provides a node-level system recovery function.
The technology for enabling the main production end database and the standby machine end database to simultaneously run on line and be in a readable and queryable state in the double-main disaster backup, namely the disaster backup system.
The disaster recovery system is divided into a data disaster recovery system and an application disaster recovery system according to the protection degree of the disaster recovery system on the system. Data disaster recovery refers to the establishment of a data system in a different location, which is a real-time copy of local critical application data. The application disaster recovery is that a set of complete backup application systems (which can be mutual backup) equivalent to the local production system is established in different places on the basis of data disaster recovery, and under the disaster condition, the remote system takes over the service operation rapidly. The data disaster recovery is the guarantee against disaster, and the application of the disaster recovery is the target of the disaster recovery system construction.
Data disaster recovery
The data disaster recovery refers to establishing a data system at a different place, wherein the system is an available copy of local critical application data. When the local data and the whole application system have disasters, the system at least stores a piece of available data of key services in different places. This data may be a full real-time copy of the local production data, or may be slightly behind the local data, but must be available. The main technologies used are data backup and data replication technologies.
The method for applying disaster recovery is to establish a set of complete backup application systems (which can be mutual backups) equivalent to a local production system in different places on the basis of data disaster recovery. The set-up of such a system is relatively complex, requiring not only a copy of the available data, but also resources including network, host, application, and even IP, and good coordination between the resources. The main technologies include load balancing and clustering technologies. The data disaster recovery is a technology of application disaster recovery, and the application disaster recovery is a target of the data disaster recovery.
When the structure of the disaster recovery system is selected, a multi-level wide area network fault switching mechanism is also established. The local high-availability system means that in the case that a plurality of servers run one or more applications, when any fault occurs to any server, the running application cannot be interrupted, and the application programs and the system should be quickly switched to other servers to run, namely, the local system cluster and the hot backup.
In a remote disaster recovery system, to implement complete application disaster recovery, the system should include a security mechanism of a local system and a remote data replication mechanism, and also have a remote fault switching capability and a fault diagnosis capability in a wide area network range.
The cluster system is formed by running high-reliability software on the basis of a redundant common availability system. The high-reliability software is used for automatically detecting the running state of the system, and automatically transferring the set service to another server in the case of failure of one server. When the service provided by the operating server is unavailable, the backup server automatically takes over the work of the operating server without restarting the system, and when the operating server is recovered to be normal, the service is switched to the operating service to operate in an automatic or manual mode according to the setting of a user. The backup server may execute other applications in addition to taking over its services when the active server fails.
Depending on these factors and different applications, disaster backup is typically divided into four levels.
Stage 0: without a backup center
The primary disaster recovery backup has no disaster recovery capability, only carries out data backup locally, and the backed-up data is only stored locally and is not sent to a different place.
Stage 1: local tape backup, off-site storage
And backing up the key data locally and then sending the key data to a remote place for storage. And after the disaster happens, recovering the system and the data according to a preset data recovery program. This solution is low cost and easy to configure. However, when the amount of data increases, there is a problem that the storage medium is difficult to manage, and when a disaster occurs, there is a problem that a large amount of data is difficult to recover in time. To solve this problem, when a disaster occurs, critical data is restored first, and then non-critical data is restored.
Stage 2: hot backup site backup
And establishing a hot backup point in different places, and backing up data through a network. That is, the data of the primary site is backed up to the backup site in a synchronous or asynchronous manner through the network, and the backup site generally only backs up the data and does not undertake the service. When a disaster occurs, the backup site takes over the service of the primary site, thereby maintaining the continuity of service operation.
Stage 3: movable standby center
Two data centers are respectively established at remote places, are in working states and carry out mutual data backup. When a disaster occurs in one data center, another data center takes over its work tasks. The backup of this level can be divided into two types according to the actual requirement and the amount of invested funds: firstly, mutual backup of key data is limited between two data centers; and the two data centers are mirror images of each other, namely zero data loss and the like. Zero data loss is the most demanding backup mode at present, and it requires that the system can ensure the safety of data no matter what disaster happens. Therefore, it requires complex management software and dedicated hardware devices, requiring relatively maximum investment, but also the fastest recovery speed.
Disclosure of Invention
The invention aims to realize double main disaster recovery, data is processed and stored, so that the data is consistent between two storages, and when one storage is damaged, the data can be accessed through the other storage, thereby improving the safety of the data and more effectively protecting the data of a user.
The scheme of the invention is realized by a double-main-based disaster recovery method, which comprises the following steps:
the client application program sends out a write request
Write requests sent to MDC over LAN
MDC processes the request, responds to which disk blocks data are written by the client through LAN by using double main disaster backup method
The client side directly writes the data into the storage at a linear speed, and synchronously copies the data to the disaster recovery center to realize double-main disaster recovery.
Drawings
Fig. 1 is a schematic diagram of a disaster recovery application with two main systems.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention aims to realize the dual main functions of data storage, data is processed and stored, so that the data is consistent between two storages, and when one storage is damaged, the data can be accessed through the other storage, thereby improving the safety of the data and more effectively protecting the data of a user.
The method comprises the following steps:
the client application program sends out a write request
Write requests sent to MDC over LAN
The MDC processes the request, responds to which disk blocks the client writes data to through the LAN using dual-master technology
The client side directly writes the data into the storage at a linear speed, and synchronously copies the data to the disaster recovery center to realize double-main disaster recovery.

Claims (3)

1. A disaster recovery method based on double main is characterized in that a writing request is sent to a software modem through a network;
the software modem processes the request, and responds to which disk blocks the client writes data through the network by using a double-active technology;
the client side directly writes the data into the storage at a linear speed, and synchronously copies the data to the disaster recovery center to realize double-activity disaster recovery.
2. A dual master based disaster recovery method as claimed in claim 1 wherein the sending of the write request to the software modem over the network means that the user issues the request.
3. A dual-master-based disaster recovery method as claimed in claim 1, wherein the software modem processes the request and responds to which disk blocks the client writes data to by using dual-active technology through the network, which means that the database of the production center is backed up to the disaster recovery center by using dual-active technology.
CN202011375958.0A 2020-11-30 2020-11-30 Disaster recovery method based on double main units Pending CN112596945A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011375958.0A CN112596945A (en) 2020-11-30 2020-11-30 Disaster recovery method based on double main units

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011375958.0A CN112596945A (en) 2020-11-30 2020-11-30 Disaster recovery method based on double main units

Publications (1)

Publication Number Publication Date
CN112596945A true CN112596945A (en) 2021-04-02

Family

ID=75187333

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011375958.0A Pending CN112596945A (en) 2020-11-30 2020-11-30 Disaster recovery method based on double main units

Country Status (1)

Country Link
CN (1) CN112596945A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116226093A (en) * 2023-04-25 2023-06-06 北京庚顿数据科技有限公司 Real-time database system based on dual-activity high-availability architecture

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105988894A (en) * 2015-02-10 2016-10-05 北京中科同向信息技术有限公司 Disaster tolerance technique of active-active mode
CN107391294A (en) * 2017-07-28 2017-11-24 郑州云海信息技术有限公司 A kind of method for building up and device of IPSAN disaster tolerance systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105988894A (en) * 2015-02-10 2016-10-05 北京中科同向信息技术有限公司 Disaster tolerance technique of active-active mode
CN107391294A (en) * 2017-07-28 2017-11-24 郑州云海信息技术有限公司 A kind of method for building up and device of IPSAN disaster tolerance systems

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116226093A (en) * 2023-04-25 2023-06-06 北京庚顿数据科技有限公司 Real-time database system based on dual-activity high-availability architecture
CN116226093B (en) * 2023-04-25 2023-08-08 北京庚顿数据科技有限公司 Real-time database system based on dual-activity high-availability architecture

Similar Documents

Publication Publication Date Title
CA2543493C (en) System and method for failover
EP2281240B1 (en) Maintaining data integrity in data servers across data centers
US7689862B1 (en) Application failover in a cluster environment
US7428657B2 (en) Method for rolling back from snapshot with log
JP5352115B2 (en) Storage system and method for changing monitoring condition thereof
US9619172B1 (en) Method and system for managing changed block tracking and continuous data protection replication
CN101635638A (en) Disaster tolerance system and disaster tolerance method thereof
CN111327467A (en) Server system, disaster recovery backup method thereof and related equipment
CN110727709A (en) Cluster database system
US9367409B2 (en) Method and system for handling failures by tracking status of switchover or switchback
CN105988894A (en) Disaster tolerance technique of active-active mode
CN104660386A (en) DB2 disaster recovery high-availability improving method based on Itanium platform
US7260739B2 (en) Method, apparatus and program storage device for allowing continuous availability of data during volume set failures in a mirrored environment
CA2514845A1 (en) Alternate server system
CN106293998A (en) A kind of system backup method based on snapping technique
CN104850628A (en) Data synchronization method and apparatus in database
CN112596945A (en) Disaster recovery method based on double main units
US10296517B1 (en) Taking a back-up software agnostic consistent backup during asynchronous replication
CN103793296A (en) Method for assisting in backing-up and copying computer system in cluster
CN112948484A (en) Distributed database system and data disaster recovery drilling method
CN111190770A (en) COW snapshot technology for data storage and data disaster recovery
CN107590032A (en) The method and storage cluster system of storage cluster failure transfer
CN114706714A (en) Method for synchronizing computer memory division snapshots
CN108845891A (en) It is a kind of novel based on the quick disaster recovery backup implementation method of snapshot realization
CN113626517B (en) PostgreSQL database stream replication exception handling method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20210402