KR102031484B1 - Server and Recovery server for performing failure recovery of service server using block chain, Method for controlling the server - Google Patents

Abstract

Disclosed are a server and a recovery server for performing disaster recovery of a service server using a block chain, and a control method of the server. The disclosed server is a server that is used for recovery of a service server and operates in a standby state, comprising: a receiving unit which receives recovery data from the service server; A controller configured to calculate a hash value of the received recovery data; And a transmitter configured to transmit the calculated hash value of the repaired data to at least one other standby operation server, wherein the receiver receives the hash value of at least one other service server from the other standby operation server. The controller may be further configured to calculate a root hash value of a Merkle tree based on a hash value of the repair data and a hash value of the repair data of the other service server, and generate a block by using the root hash value. Blocks are registered on the blockchain.

Description

Server and Recovery server for performing failure recovery of service server using block chain, Method for controlling the server}

Embodiments of the present invention relate to a standby operation server for performing disaster recovery of a service server (that is, an active operation server) using a block chain, a recovery server operating in association with the standby operation server, and a control method of the standby operation server. In detail, a standby operation server and a recovery server for determining whether or not the recovery data is abnormal using a block chain, and performing recovery using normal recovery data when there is an error in the recovery data, and a control method of the standby operation server. It is about.

Many companies and organizations today use information systems to provide reliable and efficient services. In the construction and operation of the information system, there was a need for the preparation of countermeasures due to the occurrence of accidents caused by various disasters. Therefore, the countermeasure was prepared by establishing a disaster recovery system to restore the service as soon as possible. Here, the disaster in the aspect of information and communication technology means that the service is interrupted due to an external cause or the system disaster causes the disruption of normal work by exceeding the expected recovery time, and the disaster recovery is interrupted due to the disaster. It means to resume the old service.

Conventional disaster recovery systems are using a method of backing up data in real time or dissipating the data to protect the information and data of the system. In addition, to protect the backed up data, encryption algorithms are used to ensure data integrity.

However, when a forgery occurs in a file copied for recovery, that is, the recovery data itself or when the recovery data is not available, there is a disadvantage in that the recovery data cannot be recovered to the point of time when the recovery data is generated.

In order to solve the problems of the prior art as described above, in the present invention, it is determined whether or not the abnormality of the recovery data using the block chain, and if there is an error of the recovery data, the server performing recovery using normal recovery data and recovery A server and a control method of the server are proposed.

Other objects of the present invention may be derived by those skilled in the art through the following examples.

According to a preferred embodiment of the present invention to achieve the above object, it is used for the recovery of the service server, the server operating in a standby, comprising: a receiving unit for receiving recovery data from the service server; A controller configured to calculate a hash value of the received recovery data; And a transmitter configured to transmit the calculated hash value of the repaired data to at least one other standby operation server, wherein the receiver receives the hash value of at least one other service server from the other standby operation server. The controller may be further configured to calculate a root hash value of a Merkle tree based on a hash value of the repair data and a hash value of the repair data of the other service server, and generate a block by using the root hash value. The server is provided with the characterized in that the registered block is registered in the blockchain.

The block includes a header and a payload, wherein the header includes a hash value of a header of a previous block of the block, a root hash value of the Merkle tree, a time stamp value, and a nonce value, and the payload is the service. Recovery data of the server and recovery data of the other service server.

The transmitter transmits a message including information indicating that the block is generated, a time stamp value and a nonce value used when generating the block, to the other standby operation server, and the other standby server transmits the transmitted time stamp value. And a hash value of the header of the block using a nonce value, and the verification result may be used for block chain registration of the block.

The receiving unit receives a disaster occurrence notification message from the service server, and the transmitting unit transmits the disaster occurrence notification message to a recovery server, wherein the recovery server stores the block chain and the service server included in the block chain. Recovery of the service server may be performed using the recovery data of.

The recovery server transmits a hash value of the recovery data of the service server stored in the recovery server to the other standby operation server, and transmits a hash value of the recovery data of the service server stored in the recovery server to the other standby operation server. Each of the comparison result messages indicating whether the stored hash values of the recovery data of the service server are the same may be received from the other standby operation server, and the recovery of the service server may be performed based on the comparison result message.

When the recovery data of the service server stored in the recovery server is not changed, the recovery server recovers the service server using the recovery data of the service server stored in the recovery server, and the service server stored in the recovery server. When the recovery data of is changed, the recovery server receives the recovery data of the service server which is not changed from one of the other standby operation server, and restores the service server using the received recovery data of the service server. Can be.

Further, according to another embodiment of the present invention, a recovery server for performing a recovery of the service server, the storage unit for storing a block chain containing the recovery data of the service server; A receiver configured to receive a disaster occurrence notification message of the service server from a standby operation server corresponding to the service server; A transmission unit for transmitting the disaster occurrence notification message to another standby operation server, wherein the other standby operation server stores the block chain; And a control unit controlling a recovery operation of the service server, wherein the receiving unit is a hash value of the recovery data of the service server stored in the storage unit from the other standby operation server and the service server stored in the other standby operation server. Receive a comparison result message indicating whether or not the hash value of the recovery data of the same is the same, the control unit determines whether the recovery data of the service server stored in the storage unit on the basis of the comparison result message, When the recovery data of the service server stored in the storage unit is not changed, the recovery server is provided by using the recovery data of the service server stored in the storage unit through the transmission unit.

Further, according to another embodiment of the present invention, a method for controlling a server that is used to recover a service server and operates in a standby state, the method comprising: receiving recovery data from the service server; Calculating a hash value of the received recovery data; Transmitting a hash value of the calculated recovery data to at least one other standby operation server; Receiving a hash value of recovery data of at least one other service server from the other standby operation server; Calculating a root hash value of a merkle tree based on a hash value of the repair data and a hash value of the repair data of the other service server; And generating a block by using the root hash value, wherein the generated block is registered in a block chain.

According to the present invention, there is an advantage in that it is possible to determine whether or not the recovery data is abnormal using the blockchain, and when there is an error of the recovery data, recovery can be performed using normal recovery data.

1 to 3 are diagrams illustrating the concept of a blockchain used in the present invention.
4 is a diagram illustrating a schematic configuration of a server system according to an embodiment of the present invention.
5 is a flowchart illustrating an operation of a system for proceeding with a block generation and registration procedure.
6 is a view showing the structure of a block according to the present invention.
7 is a flow diagram of the operation of system 400 to perform disaster recovery.

As used herein, the singular forms "a", "an" and "the" include plural forms unless the context clearly indicates otherwise. In this specification, terms such as “consisting of” or “comprising” should not be construed as necessarily including all of the various components or steps described in the specification, and some of the components or some steps It should be construed that it may not be included or may further include additional components or steps. In addition, the terms "... unit", "module", etc. described in the specification mean a unit for processing at least one function or operation, which may be implemented in hardware or software or a combination of hardware and software. .

Hereinafter, various embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 to 3 are diagrams illustrating the concept of a blockchain used in the present invention.

Blockchain is a distributed, independent and open common book management technology. Every user who participates in the blockchain owns the contents of the common ledger, and only the blocks recognized by more than half of the participants are connected to the blockchain. Blockchain can be used for low-cost replacement or new development of complex systems that deal with value, or for efficient use without having to go through a specific central processing system that is shared among multiple organizations and interlocked between organizations, or by automating tasks. It can be used to reduce work costs or to build new services in the form of direct participation.

Figure 1 illustrates the formation of the blockchain. Referring to FIG. 1, a block chain has a form in which blocks are connected. If a block is created at the same time, as shown in the 1st and 2nd zones, the longer connected block is used and the remaining blocks are discarded. If the next block is generated using the hash value of the discarded block (more precisely, the hash value of the header of the block), the block is not recognized as a normal block and is not registered in the blockchain.

In addition, FIG. 2 illustrates a block structure connected to a block chain in more detail. Referring to FIG. 2, a block includes a header and a payload, and the calculation of hash values in the blockchain hashes the contents of the header using the SHA-256 hash algorithm without hashing the entire block. In other words, the hash value of the block corresponds to the hash value of the header of the block. Then, when generating the next block, the hash value of the header of the previous block is used. At this time, since it is necessary to ensure the integrity of the payload contents, the hashed value of the payload is used in the header. To get the hash value of the payload, we hash each transaction and make it a Merkle Tree to compute the hash value. An example of the shape of the merkle tree used in the blockchain is shown in FIG. 3.

In addition, each transaction generates and propagates its own hash value. After that, it takes the hash values of the other transactions and builds a Merkle tree with a binary tree structure. Each hash value is hashed again to obtain the final root hash value. The hash value of the block is inserted into the payload hash value in the header of the block.

Hereinafter, a server system for performing disaster recovery of a service server using a block chain will be described in more detail with reference to FIGS. 1 to 3 and the drawings described below.

4 is a diagram illustrating a schematic configuration of a server system according to an embodiment of the present invention.

Referring to FIG. 4, a server system 400 according to an embodiment of the present invention includes a server group 410 and a recovery server 420. Hereinafter, an operation performed for each component will be described in detail.

The server group 410 is a main center including a plurality of servers. In one example, server group 410 may be an Internet Data Center (IDC) center.

In this case, the server group 410 includes at least one active operation server 411 operating in an active state and at least one standby operation server 412 operating in a standby state. That is, in the main center, each of the plurality of servers is configured in an active-standby relationship, and the active operation server and the standby operation server are mirrored to share information in real time.

Here, the active operation server 411 is a service server which is a server providing a service, the standby operation server 412 is asynchronously connected to the active operation server 411, a disaster occurs in the active operation server 411 In this case, it refers to a server performing the service providing operation of the active operation server 411 instead. That is, when a disaster occurs in the active operation server 411, the service operation is stopped by the active operation server 411, and the service operation is performed by the standby operation server 412. In particular, in the case of the present invention, the standby operation server 412 generates a block including recovery data for disaster recovery of the active operation server 411, and the active operation server 411 and the recovery server 420 when performing the recovery operation. ) Can be further performed.

The recovery server 420 is a server that performs a recovery operation of the active operation server 411.

The active operation server 411, the standby operation server 412, and the recovery server 420 each include a communication unit (including a receiver and a transmitter), a controller, and a storage unit. The communication unit is a component that performs a communication connection with another server, the control unit includes a processor, performs or controls the hash value calculation, Merkle tree calculation, block creation and block chain registration, disaster recovery functions, and the storage unit is a hash value Is a component for storing blockchains, etc.

Hereinafter, the operation of the system 400 will be described in more detail with reference to FIGS. 5 and 6.

5 is a flow diagram of the operation of the system 400 for proceeding with the block creation and registration procedure. In this case, operations will be described based on the active operation server A of the active operation server 411 and the standby operation server A of the standby operation server 412.

First, the active operation server A generates its own recovery data (step 502) and transmits the generated recovery data to the standby operation server A (step 504). At this time, the recovery data may be a value encrypted with the private key of the active operation server A.

Next, the standby operation server A which has received the recovery data calculates a hash value of the received recovery data (step 506). At this time, the standby operation server A may calculate a hash value of the recovered data using the SHA-256 hash algorithm. The standby operation server A then sends the calculated hash value of the recovered data to another standby operation server 412 in the server group 410 (step 508). At this time, the other standby operation server 412 may be one or more.

Subsequently, the standby operation server A receives a hash value of the recovery data of the other active operation server 412 from the other standby operation server 412 (step 510). In this case, there may be one or more other active operation servers 412, and are active operation servers corresponding to other standby operation servers 412. That is, the other standby operation server 412 also calculates a hash value of the recovery data of the other active operation server 412, and in step 510, the other standby operation server 412 hashes the recovery data of the other active operation server 412. Corresponds to the step of transmitting a value.

Thereafter, the standby operation server A calculates the root hash value of the Merkle Tree based on the hash value of the recovery data of the active operation server 412 which is different from the hash value of the recovery data of the active operation server A calculated by the standby operation server A (step 512). Here, the merkle tree is a tree structure in which the hash values of individual repair data are formed in the form of a binary tree, and the root hash value of the merkle tree means a hash value located at the root of the merkle tree.

Next, the standby operation server A generates a block using the root hash value (step 514). At this time, the generated block may be registered in the blockchain.

6 is a diagram illustrating the structure of a block.

Referring to FIG. 6, a block is composed of a header and a payload, and the header includes a version, a hash value of a header of a previous block, a root hash value of a merkle tree, a time stamp, and a nonce. Version specifies the version of the blockchain currently in use. The hash value of the header of the previous block is the hash value of the header of the block (i.e., the previous block) immediately preceding the current block in the blockchain. If the previous block does not exist, an arbitrary hash value is used to generate the block. . The time stamp is a time at which the block is generated, and the value may vary, but cannot be used as a value earlier than the time stamp value of the previous block. The nonce is the number of calculations starting at 0 and incremented by 1 until a hash value that satisfies the condition is found. The nonce has a size of 32 bits. The payload contains transaction information, which corresponds to information containing the recovery data of all active operation servers.

Subsequently, the standby operation server A transmits a message including information indicating that the block is generated, and a time stamp value and a nonce value used when generating the block to another standby operation server 412 (step 516).

Thereafter, the other standby operation server 412 verifies the hash value of the header of the block generated at the standby operation server A using the transmitted time stamp value and the nonce value (step 518). At this time, the verification result is used for block chain registration of the generated block. For example, when more than half of the other standby operation servers 412 determine that the verification result is abnormal, the generated block is registered in the blockchain, and the majority or more standby operation server determines that the verification result is abnormal. In this case, discard the created block and perform block creation again.

Meanwhile, steps 514 to 518 are processes performed when the standby operation server A generates a block for the first time. At this time, as mentioned above, the other standby operation server 412 may also generate a block based on the hash value of the recovery data of all active operation servers, and if one of the other standby operation servers 412 is When another standby server generates a block for the first time, the standby operation server A receives a time stamp value and a nonce value used in the generation of the block from another standby server that generated the first block, and verifies the block based thereon.

Accordingly, the generated block is connected to the block chain, and the block chain is stored in all standby operation servers and recovery servers 420.

7 is a flow diagram of the operation of system 400 to perform disaster recovery. In this case, the operation will be described based on the active operation server A of the active operation server 411 and the standby operation server A of the standby operation server 412.

First, when a disaster occurs in the active operation server A, the standby operation server A receives the disaster occurrence notification message from the active operation server (step 702), transmits it to the recovery server 420 (step 704), and the recovery server ( 420 transmits a recovery request confirmation message that is a response message to the disaster occurrence notification message (step 706). In this case, the disaster means that the service is interrupted due to an external cause or the system is damaged and the normal recovery time is exceeded due to the failure of the system.

The recovery server 420 then sends a hash value of the recovery data of the active operation server A stored in the recovery server to another standby operation server 412 (step 708). At this time, the repair data may be stored in the payload of the block in the block chain. The other standby operation server 412 determines whether the hash value of the recovery data of the active operation server A stored in the recovery server 420 is the same as the hash value of the recovery data of the active operation server A stored in the other standby operation server 412. It is determined whether or not (step 710).

That is, steps 708 and 710 are processes for checking whether the active operation server A stored in the recovery server 420 has been changed. In other words, the recovery server 420 checks through the other standby operation server 412 whether the recovery data of the active operation server A stored therein is changed.

Subsequently, the recovery server 420 receives a comparison result message from another standby operation server 412 indicating whether it is the same (step 712), and performs a recovery operation of the active operation server A based on the comparison result message. May be performed (step 716).

If a majority of the other standby operation servers 412 determine that the hash value of the recovery data of the active operation server A stored in the recovery server 420 is the same as the hash value of the recovery data of the active operation server A stored therein, the recovery is performed. The server 420 determines that the recovery data of the active operation server A stored by the server is not changed, and in this case, the recovery server 420 uses the recovery data of the active operation server A stored by the server 420. To recover.

On the contrary, when the majority of the other standby operation server 412 determines that the hash value of the recovery data of the active operation server A stored in the recovery server 420 and the hash value of the recovery data of the active operation server A stored therein are not the same. The recovery server 420 receives recovery data of the active operation server A that is not changed (that is, normal) from one of the other standby operation servers 412, and uses the received recovery data of the active operation server A to activate the active operation server. A can be restored.

In other words, the recovery system 400 according to the present invention determines whether there is a change in the recovery data stored in the recovery server 420, and if it is normal, proceeds with the recovery data stored by the recovery server 420 and changes it. If there is, the recovery data is received from the other standby operation server 412 to proceed with recovery. Accordingly, there is an advantage that reliable and effective recovery can be performed.

In addition, embodiments of the present invention can be implemented in the form of program instructions that can be executed by various computer means may be recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Examples of program instructions such as magneto-optical, ROM, RAM, flash memory, etc. may be executed by a computer using an interpreter as well as machine code such as produced by a compiler. Contains high-level language codes. The hardware device described above may be configured to operate as one or more software modules to perform the operations of one embodiment of the present invention, and vice versa.

In the present invention as described above has been described by the specific embodiments, such as specific components and limited embodiments and drawings, but this is provided to help the overall understanding of the present invention, the present invention is not limited to the above embodiments, Various modifications and variations can be made by those skilled in the art to which the present invention pertains. Therefore, the spirit of the present invention should not be limited to the described embodiments, and all the things that are equivalent to or equivalent to the claims as well as the following claims will belong to the scope of the present invention. .

Claims (9)

In the server that is used for the recovery of the service server, the standby server,
A receiving unit for receiving recovery data from the service server;
A controller configured to calculate a hash value of the received recovery data; And
And a transmitter configured to transmit the calculated hash value of the repaired data to at least one other standby operation server.
The receiving unit receives a hash value of the recovery data of at least one other service server from the other standby operation server,
The controller calculates a root hash value of the Merkle tree based on the hash value of the repair data and the hash value of the repair data of the other service server, and generates a block using the root hash value, wherein the generated block is generated. Is registered on the blockchain,
The receiving unit receives a disaster occurrence notification message from the service server, and the transmission unit transmits the disaster occurrence notification message to a recovery server,
And the recovery server stores the block chain and recovers the service server using the recovery data of the service server included in the block chain. The method of claim 1,
The block consists of a header and a payload,
The header includes a hash value of the header of the previous block of the block, the root hash value of the Merkle Tree, a time stamp value and a nonce value,
And the payload includes recovery data of the service server and recovery data of the other service server. The method of claim 1,
The transmission unit transmits a message including information indicating that the block is generated, a time stamp value and a nonce value used when generating the block, to the other standby operation server.
The other standby server verifies a hash value of a header of the block by using the transmitted time stamp value and a nonce value, and the verification result is used for block chain registration of the block. delete The method of claim 1,
The recovery server,
Transmit a hash value of the recovery data of the service server stored in the recovery server to the other standby operation server,
Receive from the other standby operation server a comparison result message indicating whether the hash value of the recovery data of the service server stored in the recovery server and the hash value of the recovery data of the service server stored in the other standby operation server are the same; And recovering the service server based on the comparison result message. The method of claim 5,
If the recovery data of the service server stored in the recovery server is not changed, the recovery server recovers the service server using the recovery data of the service server stored in the recovery server,
When the recovery data of the service server stored in the recovery server is changed, the recovery server receives the recovery data of the service server which does not change from one of the other standby operation servers, and recovers the received recovery data of the service server. Recovering the service server using the server. A recovery server performing recovery of a service server,
A storage unit for storing a block chain including recovery data of the service server;
A receiver configured to receive a disaster occurrence notification message of the service server from a standby operation server corresponding to the service server;
A transmission unit for transmitting the disaster occurrence notification message to another standby operation server, wherein the other standby operation server stores the block chain; And
And a control unit controlling a recovery operation of the service server.
The receiving unit receives a comparison result message indicating whether the hash value of the recovery data of the service server stored in the storage unit and the hash value of the recovery data of the service server stored in the other standby operation server are the same from the other standby operation server. Receive each,
The control unit determines whether the recovery data of the service server stored in the storage unit is changed based on the comparison result message, and if the recovery data of the service server stored in the storage unit is not changed, Recovery server, characterized in that for recovering the service server using the recovery data of the service server stored in the storage. In the method of controlling a server that is used to recover a service server and operates in a standby mode,
(a) receiving recovery data from the service server;
(b) calculating a hash value of the received recovery data;
(c) transmitting the calculated hash value of the repaired data to at least one other standby operation server;
(d) receiving a hash value of recovery data of at least one other service server from the other standby operation server;
(e) calculating a root hash value of a merkle tree based on a hash value of the repair data and a hash value of the repair data of the other service server; And
(f) generating a block using the root hash value;
The generated block is registered in the blockchain,
The step (a) receives a disaster occurrence notification message from the service server, and the step (c) transmits the disaster occurrence notification message to a recovery server,
And the recovery server stores the block chain and performs recovery of the service server using recovery data of the service server included in the block chain. A computer-readable recording medium having recorded thereon a program for performing the method of claim 8.

Images