CN110597673A - Disaster recovery method, device and equipment of storage system and computer readable storage medium - Google Patents

Abstract

The embodiment of the application discloses a disaster recovery method of a storage system. The disaster recovery system comprises a plurality of storage servers, which have data reading and writing functions, and the method comprises the following steps: a first storage server in the storage system receives a first data writing request sent by a service server, and sends a data synchronization request to a second storage server after the first storage server completes data writing according to the first data writing request; the second storage server is the other servers except the first storage server in the plurality of storage servers, and the data synchronization request is used for indicating the second storage server to complete data synchronization and completing data writing according to the first data writing request when receiving the first data writing request sent by the service server. By adopting the embodiment of the application, the condition that only reading can be carried out and writing can not be carried out when the storage server of the storage system fails is optimized, and data reading and data writing services can still be provided under the condition that any storage server in the storage system fails.

Description

Disaster recovery method, device and equipment of storage system and computer readable storage medium

Technical Field

The present application relates to the field of information technologies, and in particular, to a disaster recovery method, apparatus, device, and computer-readable storage medium for a storage system.

Background

In the era of rapid development of information technology, effective storage of data is of great importance to various industries. The disaster tolerance is a very critical link in the design of a storage system, and aims to prevent data loss or interface unavailability and other disastrous emergencies caused by machine faults from occurring, so that uninterrupted operation of data services can be guaranteed.

In the existing disaster tolerance design scheme of the storage system, a main/standby disaster tolerance scheme is often used. In the main/standby disaster recovery scheme, only the main storage server can read and write data, the standby storage server can read and write data, and cannot write data, and when the main storage server fails, only the data read can be normally served, and the request for data write cannot be executed, thereby affecting the normal operation of data service.

Disclosure of Invention

The embodiment of the application discloses a disaster recovery method, a disaster recovery system and related equipment of a storage system, which can realize that the storage system can only read and can not write when only one storage server fails, and can still provide data read-write service when any storage server fails.

In a first aspect, an embodiment of the present application discloses a disaster recovery method for a storage system, where the disaster recovery system includes a plurality of storage servers, and each of the plurality of storage servers has data reading and data writing functions, and includes:

a first storage server receives a first data write-in request sent by a service server; the first storage server is one of the plurality of storage servers;

after the first storage server completes data writing according to the first data writing request, sending a data synchronization request to a second storage server;

wherein the second storage server is a server other than the first storage server in the plurality of storage servers; and the data synchronization request is used for indicating the second storage server to complete data synchronization, and when the second storage server receives a first data writing request sent by a service server, completing data writing according to the first data writing request.

In the method, a plurality of storage servers are arranged in the storage system, and all the storage servers have data reading and data writing functions. In this way, the service server initiates a data write request to any storage server in the storage system, and can complete data write.

Based on the first aspect, in an optional implementation manner, the first data write request carries data content and a data key identifier; after the first storage server receives the first data write request sent by the service server and before the first storage server sends the data synchronization request to the second storage server, the method further includes:

the first storage server judges whether the data key identification exists according to the first data writing request;

if the first storage server does not have the data key identification, the first storage server writes the key identification into a key domain of a data key value pair, writes data content carried by the data writing request into a value domain of the data key value pair, distributes a data version identification to the data content, and sends a data version identification synchronization request to a control server.

In the method, the first data writing request carries the data key identification, the first storage server can judge whether the data is written for the first time through the data key identification, if the data is written for the first time, the data content and the data key identification are stored, the data version identification is distributed to the data content, and the data can be processed more efficiently.

Based on the first aspect, in an optional implementation manner, if the data key identifier exists in the first storage server, the first storage server sends a determination request of a data version identifier to the control server, where the determination request carries the data version identifier corresponding to the data key identifier and stored in the first storage server;

under the condition that the first storage server receives a first judgment result sent by the control server, wherein the first judgment result represents that the data version identification is consistent and carries the latest data version identification; and the first storage server updates the data content and the data version identification in the data key value pair value field.

And under the condition that the first storage server receives a second judgment result sent by the control server, wherein the second judgment result represents that the data version identifications are inconsistent, the first storage server does not update the data key value pair and returns a data non-writable result to the service server.

In the method, the first storage server is identified through the data key, so that the data can be judged whether to be written for the first time or not and need to be updated; whether the data is updated or not can be obtained by judging the data version identification through the control server, if the data version identification is consistent, the data is updated, and if the data version identification is inconsistent, the data is not updated. In this way, the data can be processed more specifically.

Based on the first aspect, in an optional implementation manner, after the sending the data synchronization request to the second storage server, the first storage server further receives a result that the data synchronization is successful or the data synchronization is unsuccessful, where the result is returned by the second storage server.

In a second aspect, an embodiment of the present application provides a disaster recovery method for a storage system, where the disaster recovery system includes a control server, and the method includes:

after a judgment request of a data version identification sent by a first storage server is received, wherein the judgment request of the data version identification carries the data version identification corresponding to the data content stored by the first storage server, the data version identification and the data version identification corresponding to the control server are judged, and a judgment result of the data version identification is returned to the first storage server.

In the method, the control server judges the data version identification to obtain a judgment result and returns the judgment result to the first storage server.

Based on the second aspect, in an optional implementation manner, the determining, by the control server, the data version identifier of the control server and the corresponding data version identifier on the control server, and returning a result of the determination of the data version identifier to the first storage server includes:

the control server judges whether the data version identification of the control server is consistent with the corresponding data version identification on the control server;

if the data version identification is consistent with the current data version identification, the control server updates the current data version identification and returns the result of consistency of the updated data version identification and the data version identification to the first storage server;

and if the data version identifications are inconsistent, the control server does not process the current data version identifications and returns the inconsistent result of the data version identifications to the first storage server.

In the method, the control server obtains the judgment result through the judgment of the data version identification, and then returns the judgment result to the first storage server, so that the first storage server can be informed of the data processing mode, and the data can be processed more efficiently.

In a third aspect, in an optional implementation manner, the disaster recovery system of the storage system includes a service server, and the method includes:

sending a first data writing request to a first storage server after receiving a data writing request of a terminal; the first storage server is one of the plurality of storage servers; the data writing request carries data content, and the first data writing request carries data content and a data key identifier;

and when receiving a data writing unsuccessful result returned by the first storage server, the service server sends a first data writing request to any other storage server except the first storage server in the storage system.

In the method, the service server may send a first data write request to any storage server in the storage system, and may send the first data write request to other storage servers in the storage system when receiving a result that the data write returned by the first storage server is unsuccessful. By the method, the first data writing request can be sent to other storage servers under the condition that any storage server in the storage system cannot write data, and the data writing success is guaranteed.

In an optional implementation manner according to the third aspect, the method further includes:

after the service server sends a first data write-in request to a second storage server, the second storage server does not return a result, which indicates that the second storage server fails, and the service server sends the first data write-in request to any other storage server except the second storage server.

In the method, the first data writing request can be sent to other storage servers under the condition that the second storage server in the storage system fails and cannot write data, so that the data writing success is ensured.

In a fourth aspect, an embodiment of the present application provides a disaster recovery method for a storage system, including:

the method comprises the steps that a service server sends a first data writing request to a first storage server after receiving a data writing request sent by a terminal, wherein the data writing request carries data content, and the first data writing request carries the data content and a data key identifier; the first storage server is one of the plurality of storage servers;

a first storage server receives a first data write-in request sent by a service server;

after the first storage server completes data writing according to the first data writing request, sending a data synchronization request to a second storage server;

wherein the second storage server is a server other than the first storage server in the plurality of storage servers; and the data synchronization request is used for indicating the second storage server to complete data synchronization, and when the second storage server receives a first data writing request sent by a service server, completing data writing according to the first data writing request.

It should be noted that, for the implementation manner and the corresponding beneficial effects of the fourth aspect, reference may be made to descriptions in the first aspect, the second aspect, or the third aspect and the corresponding implementation manner, and details are not described herein again.

In a fifth aspect, an embodiment of the present application provides a disaster recovery device for a storage system, including:

the receiving unit is used for receiving a first data writing request sent by the service server;

a sending unit, configured to send a data synchronization request to a second storage server after the first storage server completes data writing according to the first data writing request;

it should be noted that, for the implementation manner and the corresponding beneficial effects of the fifth aspect, reference may be made to the description in the first aspect and the corresponding implementation manner, and details are not described herein again.

In a sixth aspect, an embodiment of the present application provides a disaster recovery device for a storage system, including:

a judging unit, configured to, after receiving a judgment request for a data version identifier sent by a first storage server, where the judgment request carries the data version identifier corresponding to the data content stored in the first storage server, judge the data version identifier and a data version identifier corresponding to the data content on the control server;

and the sending unit is used for returning the result of the judgment of the data version identification to the first storage server.

It should be noted that, for the implementation manner and the corresponding beneficial effects of the sixth aspect, reference may be made to the description in the second aspect and the corresponding implementation manner, and details are not described herein again.

In a seventh aspect, an embodiment of the present application provides a disaster recovery device for a storage system, including:

the sending unit is used for sending a first data writing request to the first storage server after receiving the data writing request of the terminal; the first storage server is one of the plurality of storage servers;

the sending unit is further configured to send, when receiving a result that data writing returned by the first storage server is unsuccessful, a first data writing request to any one of the other storage servers in the storage system except the first storage server by the service server.

It should be noted that, for the implementation manner and the corresponding beneficial effects of the seventh aspect, reference may be made to the description in the third aspect and the corresponding implementation manner, and details are not described herein again.

In an eighth aspect, an embodiment of the present application provides a disaster recovery device for a storage system, including a memory, a processor, and a communication module; the memory is used for storing a computer program, the communication module is used for data communication with an external device, and the processor executes the computer program in the memory and executes the method according to any one of claims 1-8.

It should be noted that, for the implementation manner and the corresponding beneficial effects of the eighth aspect, reference may be made to descriptions in the first aspect, the second aspect, or the third aspect and the corresponding implementation manner, and details are not described herein again.

In a ninth aspect, an embodiment of the present application provides a disaster recovery system of a storage system, where the system includes a storage server, a control server, and a service server, where,

the storage server is adapted to perform the steps of the method according to any of claims 1-4;

the control server is adapted to perform the steps of the method according to claim 5 or 6;

the service server is adapted to perform the steps of the method according to claim 7 or 8.

In a tenth aspect, embodiments of the present application provide a computer-readable storage medium storing program instructions, which when executed by a processor, cause the processor to perform the method of the first aspect, the second aspect, or the third aspect.

It should be noted that, for the implementation manner and the corresponding beneficial effects of the tenth aspect, reference may be made to the descriptions in the first aspect, the second aspect, or the third aspect and the corresponding implementation manner, and details are not described herein again.

Drawings

In order to explain the technical solutions in the embodiments or the prior art of the present application, the drawings used in the description of the embodiments or the prior art will be described below.

Fig. 1 is a schematic architecture diagram of a disaster recovery system of a storage system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a disaster recovery method of a storage system according to an embodiment of the present disclosure;

fig. 3 is a data structure diagram of a storage system according to an embodiment of the present application;

fig. 4 is a schematic flowchart of another disaster recovery method for a storage system according to an embodiment of the present application;

fig. 5 is a schematic flowchart of another disaster recovery method for a storage system according to an embodiment of the present application;

fig. 6 is a schematic flowchart of another disaster recovery method for a storage system according to an embodiment of the present application;

fig. 7 is a schematic flowchart of another disaster recovery method for a storage system according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a disaster recovery device of a storage system according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a disaster recovery device of a storage system according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

It is to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments. As used in this specification, the terms "device," "unit," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a device may be, but is not limited to, a processor, a data processing platform, a computing device, a computer, 2 or more computers, and the like.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

In order to better understand the disaster recovery method, system, device, and computer-readable storage medium of a storage system provided in the embodiments of the present application, as shown in fig. 1, it is a schematic diagram of an architecture of a disaster recovery system of a storage system provided in the embodiments of the present application, the disaster recovery system of the storage system includes a first storage server 101, a second storage server 102, a third storage server 103, a service server 104, and a control server 105, the first storage server 101, the second storage server 102, the third storage server 103, and the service server 104 implement mutual communication through a network or other communication methods, and the first storage server 101, the second storage server 102, the third storage server 103, and the control server 105 implement mutual communication through a network or other communication methods.

In one possible implementation, the storage server may be a blockchain node server. That is, the first storage server 101, the second storage server 102, and the third storage server 103 may be blockchain node servers.

The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The block chain underlying platform can comprise processing modules such as user management, basic service, intelligent contract and operation monitoring. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after consensus on the valid request is completed, for a new service request, the basic service firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, transmits the service information to a shared account (network communication) completely and consistently after encryption, and performs recording and storage; the intelligent contract module is responsible for registering and issuing contracts, triggering the contracts and executing the contracts, developers can define contract logics through a certain programming language, issue the contract logics to a block chain (contract registration), call keys or other event triggering and executing according to the logics of contract clauses, complete the contract logics and simultaneously provide the function of upgrading and canceling the contracts; the operation monitoring module is mainly responsible for deployment, configuration modification, contract setting, cloud adaptation in the product release process and visual output of real-time states in product operation, such as: alarm, monitoring network conditions, monitoring node equipment health status, and the like.

Referring to fig. 2, a disaster recovery method of a storage system of the present application is described below, as shown in fig. 2, which is a schematic flow chart of a disaster recovery method of a storage system provided in an embodiment of the present application, and shows a situation when data is written for the first time, where the method may be implemented based on the system architecture shown in fig. 2 or other architectures, and the method may include, but is not limited to, the following steps:

step S201, a terminal sends a first data writing request to a service server;

specifically, a user operation terminal sends a data writing request to a service server, wherein the data writing request carries data content;

step S202, a business server sends a first data writing request to a first storage server;

specifically, after receiving a data write request sent by the terminal, the service server sends a first data write request to the first storage server, where the first data write request carries data content and a data key identifier, and the data key identifier may be an identifier that embodies actual meaning of data, such as a block identifier or a transaction identifier.

Step S203, after receiving the first data writing request, the first storage server stores the data;

specifically, after receiving a first data write request sent by a service server, a first storage server stores data content into a value field of a data key-value pair, stores a data key identifier into the key field of the data key-value pair, and allocates a data version identifier to the data content, wherein the data version identifier is stored in the value field of the data key-value pair. As shown in fig. 3, which is a description of a data structure of the storage system, it can be seen from fig. 3 that each type of data has a data key identifier and a data version identifier corresponding thereto, the data key identifier and the data content are stored in different spaces, and the data version identifier and the data content are stored in one space;

the data version identifier refers to a data version identifier used by data to be processed in the first data write request, and the data version identifier may be generated randomly or according to a set rule, such as serial number or serial number + block identifier/transaction identifier. For storage convenience, the present embodiment preferably generates the version identifier according to a set rule.

Step S204, the first storage server synchronizes the stored data key value pairs to the second storage server and other storage servers;

specifically, the first storage server synchronizes the data key identification, the data content, and the data version identification to the second storage server and other storage servers in the storage system.

Step S205, the second storage server and other storage servers return successful data synchronization results to the first storage server;

specifically, the second storage server and other storage servers in the storage system store the data key value pairs after receiving the data synchronization request sent by the first storage server, and send a data synchronization success result to the first storage server after successful storage.

Step S206, the first storage server synchronizes the data version identification to the control server;

specifically, the first storage server synchronizes the data version identification assigned to the data content to the control server.

Step S207, the control server returns a successful result of the synchronization of the data version identification to the first storage server;

specifically, after receiving a data version identification synchronization request sent by the first storage server, the control server stores the data version identification and returns a successful data version identification synchronization result to the first storage server.

Step S208, the first storage server returns a first data writing success result to the service server;

specifically, after receiving a first data writing request sent by a service server, a first storage server stores data content and returns a first data writing success result to the service server;

step S209, the service server returns a data writing success result to the terminal;

specifically, the service server returns a successful result of the first data writing to the terminal after receiving the successful result of the first data writing sent by the first storage server.

It should be noted that, the execution of steps S204 to S207 is not in sequence, and step S204 to step S205 may be executed first, step S206 to step S207 may be executed first, or step S204 to step S205 and step S206 to step S207 may be executed synchronously.

In this embodiment, the first storage server and the second storage server are any storage server in the storage system, and the storage servers in the storage system have data writing and data reading functions.

Fig. 4 is a schematic flow chart of another disaster recovery method for a storage system according to an embodiment of the present application, which shows that data writing, i.e., data updating, is performed for the nth time (N is greater than 1). The method may be implemented based on the system architecture shown in fig. 1 or other architectures, and may include, but is not limited to, the following steps:

s401, the terminal sends a data writing request to a service server;

it should be noted that, the specific content may refer to step S201, and is not described herein again.

S402, the service server sends a first data write-in request to a first storage server;

it should be noted that, the specific content may refer to step S202, and is not described herein again.

S403, after receiving a first data writing request, the first storage server sends a data version identification judgment request to a control server, wherein the data version judgment request carries a data version identification stored on the first storage server;

s404, after receiving the data version identification judgment request, the control server judges the data version identification stored on the first storage server and the data version identification stored on the control server to obtain a result that the data version identifications are consistent, and the control server updates the data version identification in a mode of adding one;

and if the addition processing is yes, the data version identification is an integer value, and the new data version identification is determined to be added by one on the basis of the previous version identification.

S405, the control server returns a first judgment result to the first storage server, wherein the first judgment result represents that the data version identification is consistent and carries the latest data version identification;

s406, after receiving a first judgment result returned by the control server, the first storage server stores a first data write-in request which is sent by the service server and carries a data key value pair and writes a latest data version identifier;

s407, the first storage server synchronizes the stored key value pairs of the data to the second storage server and other storage servers;

s408, after receiving the result of successful data synchronization sent by the first storage server, the second storage server and other storage servers store the data key value pair sent by the first storage server and then return the result of successful data synchronization to the first storage server;

s409, the first storage server returns a data writing success result to the service server after receiving the data synchronization success result sent by the second storage server and other storage servers;

and S410, the service server returns a data writing success result to the terminal after receiving the data writing success result returned by the first storage server.

In this embodiment, the first storage server and the second storage server are any storage server in a storage system, and the storage servers in the storage system both have data writing and data reading functions.

Referring to fig. 5, a disaster recovery method of the storage system of the present application is described below, as shown in fig. 5, which is a flowchart of another disaster recovery method of the storage system provided in this application embodiment, and shows that the method for writing data in the case of a failure of the first storage server may be implemented based on the system architecture shown in fig. 5 or other architectures, and the method may include, but is not limited to, the following steps:

s501, the terminal sends a data writing request to a service server;

it should be noted that, the specific content may refer to step S201, and is not described herein again.

S502, the service server sends a first data writing request to a first storage server;

it should be noted that, the specific content may refer to step S202, and is not described herein again.

S503, the first storage server cannot write data due to faults, and cannot return results to the service server;

s504, the service server does not receive the result returned by the first storage server, and the service server initiates a first data writing request to the second storage server;

s505, after receiving the first data writing request, the second storage server sends a data version identification judgment request to the control server;

s506, after receiving a data version identification judgment request sent by a second storage server, the control server judges the data version identification stored on the second storage server and the data version identification stored on the control server to obtain a result that the data version identifications are consistent, and updates the data version identification by the control server in a mode of adding one;

it should be noted that, the specific updating manner may refer to step S404, which is not described herein again.

S507, the control server returns a first judgment result to the second storage server, wherein the first judgment result represents that the data version identification is consistent and carries the latest data version identification;

s508, after receiving the first judgment result sent by the control server, the second storage server stores the data key value pair sent by the service server and writes the latest data version identification;

s509, the third storage server and other storage servers store the data key value pairs sent by the first storage server and then return a successful data synchronization result to the second storage server;

s510, the second storage server returns a data writing success result to the service server after receiving the data synchronization success result sent by the third storage server and other storage servers;

s511, the service server returns a data writing success result to the terminal after receiving the writing success result returned by the second storage server method;

s512, the service server returns a data writing success result to the terminal after receiving the data writing success result returned by the second storage server.

It should be noted that, after the failure is repaired, the failed first storage server may synchronize the update data with other storage servers of the storage system.

In this embodiment, the first storage server, the second storage server, and the third storage server are any storage server in a storage system, and the storage servers in the storage system all have data writing and data reading functions. According to the embodiment of the application, a request that data cannot be written in a failure mode can be sent to one storage server of the storage system, and other storage servers in the storage system can provide a data writing function.

Referring to fig. 6, a disaster recovery method of the storage system of the present application is described below, as shown in fig. 6, which is a schematic flowchart of another disaster recovery method of the storage system provided in the embodiment of the present application, indicating that a data synchronization failure occurs when data is written, where the method may be implemented based on the system architecture shown in fig. 6 or other architectures, and the method may include, but is not limited to, the following steps:

s601, the terminal sends a data writing request to a service server;

it should be noted that, the specific content may refer to step S201, and is not described herein again.

S602, the service server sends a first data write-in request to a first storage server;

it should be noted that, the specific content may refer to step S202, and is not described herein again.

S603, after receiving the first data writing request, the first storage server sends a data version identification judgment request to the control server;

it should be noted that, the specific content of the data version identifier may refer to step S403, and is not described herein again.

S604, it should be noted that the specific content may refer to step S404, which is not described herein again.

S605, it should be noted that the specific content may refer to step S405, which is not described herein again.

S606, it should be noted that the specific contents refer to step S406, which is not described herein again.

S607, it should be noted that the specific contents may refer to step S407, which is not described herein again.

S608, after the second storage server and other storage servers in the storage system receive the synchronization request of the first storage server, the second storage server cannot perform data synchronization because of a fault and returns a data synchronization failure result to the first storage server or does not return a result to the first storage server; other storage servers return a successful data synchronization result to the first storage server;

s609, the first storage server returns a data writing success result to the service server after receiving the data synchronization failure result or the data synchronization failure result returned by the second storage server and the data synchronization success results returned by other storage servers in the storage system;

s610, the service server returns the successful data writing result to the terminal after receiving the successful data writing result returned by the first storage server.

It should be noted that the result of successful data writing may carry storage prompt information for prompting the service server to send the first data writing request to the third storage server, where the third storage server is a storage server with successful data synchronization, or for prompting the service server not to send the first data writing request to the second storage server, and the second storage server is a storage server with failed data synchronization.

It should be noted that, after the failure is repaired, the failed second storage server may synchronize the update data with other storage servers of the storage system.

In this embodiment, the first storage server and the second storage server are any storage server in a storage system, and the storage servers in the storage system both have data writing and data reading functions. Through the embodiment of the application, the situation that data synchronization fails to occur in a certain storage server in a storage system during data synchronization can be seen, and the storage server does not have the latest data version identification.

Referring to fig. 7, a disaster recovery method of the storage system of the present application is described below, and as described in fig. 7, it is a flowchart of another disaster recovery method of the storage system provided in this application embodiment, which shows how to write data in a case where a certain storage server of the storage system does not have a latest data version identifier and cannot write data, where the method may be implemented based on the system architecture shown in fig. 7 or other architectures, and the method may include, but is not limited to, the following steps:

s701, it should be noted that the specific content may refer to step S201, which is not described herein again.

S702, it should be noted that the specific content may refer to step S202, which is not described herein again.

S703, it should be noted that the specific contents may refer to step S403, which is not described herein again.

S704, after receiving the data version identification judgment request, the control server judges the data version identification stored on the second storage server and the data version identification stored on the control server to obtain the result that the data version identifications are inconsistent.

S705, the control server returns a second judgment result to the second storage server, and the second judgment result represents that the data version identifications are inconsistent;

s706, the second storage server receives a second judgment result sent by the control server, and the second storage server cannot store the data key value pair;

s707, the second storage server returns a data write failure result to the service server;

s708, the service server initiates a first data writing request to a first storage server except a second storage server in the storage system after receiving the result of the data writing failure;

s709, after receiving the first data writing request, the first storage server sends a data version identification judgment request to the control server, wherein the data version judgment request carries the data version identification stored in the first storage server;

s710, after receiving the data version identification judgment request, the control server judges the data version identification stored on the first storage server and the data version identification stored on the control server to obtain a result that the data version identifications are consistent, and the control server updates the data version identification in a mode of adding one;

it should be noted that, the specific updating manner may refer to step S405, and is not described herein again.

S711, the control server returns a first judgment result to the first storage server, wherein the first judgment result carries the representation data version identification and is consistent and carries the latest data version identification;

s712, the second storage server stores the data key value pair carried in the first data writing request sent by the service server and writes the latest data version identification after receiving the first judgment result returned by the control server;

s713, the second storage server synchronizes the stored data key value pairs to a third storage server and other storage servers;

s714, the third storage server and other storage servers return a successful data synchronization result to the second storage server after receiving the successful data synchronization result sent by the second storage server;

s715, the second storage server returns a data writing success result to the service server after receiving the data synchronization success result sent by the third storage server and the other storage servers;

and S716, the service server returns a data writing success result to the terminal after receiving the data writing success result sent by the second storage server.

In the embodiment of the application, the first storage server and the second storage server are any storage server in a storage system, and the storage servers in the storage system have data writing and data reading functions. According to the embodiment of the application, data writing is performed through other storage servers in the storage system under the condition that the latest data version identification is not stored in one storage server in the storage system and data cannot be written.

In one embodiment, the embodiment of the present application further provides a method for determining a data version identifier by using a storage server in a storage system, where after a first storage server receives a first data write request sent by a service server for the first time, the first data write request carries a data content and a key identifier, the first storage server writes the key identifier into a key field of a data key value pair, writes the data content carried by the first data write request into a value field of the data key value pair, allocates the data version identifier to the data content, and synchronizes the data version identifier to a control module in the first storage server; if the first storage server receives the first data writing request sent by the service server for the second time, the control unit in the first storage server judges the data version identification, if the data judgment identification is consistent, the control unit carries out updating operation on the data version identification and synchronizes the data version identification to the first storage server, and if the data judgment identification is inconsistent, the inconsistent result is synchronized to the first storage server.

It should be noted that, if the service server receives a data reading request sent by the terminal, the service server reads data in any storage server of the storage system according to the existing key value of the data in the data reading request.

In order to better implement the above-mentioned scheme of the embodiments of the present application, the present application also provides a disaster recovery device of a storage system, which is described in detail below with reference to the accompanying drawings.

As shown in fig. 8, an embodiment of the present application provides a schematic structural diagram of a disaster recovery device 80 of a storage system, including: a transmission unit 801, a storage unit 802, a generation unit 803, and a judgment update unit 804.

A sending unit 801, configured to send data to the service server after the first storage server receives the data write request sent by the service server; the system comprises a first storage server, a control server and a second storage server, wherein the first storage server is used for sending data version identification synchronization or judgment to the control server after receiving a first data write-in request sent by a business service; the data synchronization request is sent to the second storage server after the first storage server completes data writing according to the first data Hill request;

a storage unit 802, configured to store, by a first storage server, data content and a data key identifier carried in a first data write request sent by a service server and a latest version identifier carried in a first determination result sent by a control server;

a generating unit 803, configured to generate, by the first storage server, a data version identifier corresponding to the data content carried in the first data write request;

and the judgment and update unit 804 is used for the first storage server to judge and update the data version identification stored in the control unit in the storage server and the data version identification stored in the median domain in the storage server.

It should be noted that the disaster recovery device 80 of the storage system corresponds to the storage server in the method embodiment. The specific implementation and beneficial effects of the above operations may also correspond to the steps specifically executed by the storage server in the embodiments provided in fig. 1 to fig. 7 and possible embodiments thereof, and are not described herein again.

In order to better implement the above-mentioned scheme of the embodiments of the present application, the present application also provides a disaster recovery device of a storage system, which is described in detail below with reference to the accompanying drawings.

As shown in fig. 9, an embodiment of the present application provides a schematic structural diagram of a disaster recovery device 90 of a storage system, including: a transmitting unit 901, a storage unit 902 and a judgment updating unit 903.

A sending unit 901, configured to control the server to send a data version identifier determination result to the first storage server;

a storage unit 902, configured to control the server to store the data version identifier sent by the first storage server;

and a judgment and update unit 903, configured to judge and update the data version identifier carried in the received data version identifier judgment request and the data version identifier stored in the control server by the control server.

It should be noted that the disaster recovery device 90 of the storage system corresponds to the storage server in the method embodiment. The specific implementation and beneficial effects of the above operations may also correspond to the steps specifically executed by the storage server in the embodiments provided in fig. 1 to fig. 7 and possible embodiments thereof, and are not described herein again.

In order to better implement the above-mentioned scheme of the embodiments of the present application, the present application also provides a disaster recovery device of a storage system, which is described in detail below with reference to the accompanying drawings.

As shown in fig. 10, an embodiment of the present application provides a schematic structural diagram of a disaster recovery device 100 of a storage system, including: a transmitting unit 1001 and a receiving unit 1002.

A sending unit 1001, configured to send a data read and data write request to a storage server in a storage system by a service server;

a receiving unit 1002, configured to receive, by the service server, a service request sent by the terminal and receive a result returned by the storage server in the storage system.

Note that the disaster recovery device 100 of the storage system corresponds to the storage server in the method embodiment. The specific implementation and beneficial effects of the above operations may also correspond to the steps specifically executed by the storage server in the embodiments provided in fig. 1 to fig. 7 and possible embodiments thereof, and are not described herein again.

Fig. 11 is a schematic structural diagram of a disaster recovery device of a storage system according to an embodiment of the present application. For ease of understanding and illustration, shown in fig. 11 is a disaster recovery device 110 of a storage system, which device, corresponding to a storage server in an embodiment of the method, may include one or more of the following components: memory 1101, processor 1102, communication module 1103.

The memory 1101 may include one or more storage units, each of which may include one or more memories, which may be used to store programs and various data and enable access to the programs or data to be performed automatically and at high speed during the operation of the account login server 110. When the account login server 110 shown in fig. 11 executes the methods described in fig. 2-6, the memory may be used to store account information, target account identification information, other relevant data, and the like.

The communication module 1103, which may also be referred to as a transceiver, or transceiver, may include a unit for performing wireless, wired, or other communication. Alternatively, a device used for implementing a receiving function in the portion 1103 may be regarded as a receiving unit, and a device used for implementing a sending function may be regarded as a sending unit, that is, the portion 1103 includes a receiving unit and a sending unit.

The processor 1102, which may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc. The processor may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. When the storage server 110 shown in fig. 11 executes the steps in the method embodiments of step S203, step S204, step S208 in fig. 2, step S403 in the method embodiment of fig. 4, and step S503 in the method embodiment of fig. 5, the processor 1102 calls the computer program of the memory 1101 to execute the following steps:

receiving a first data writing request sent by a service server through a communication module 1103; the first storage server is one of the plurality of storage servers;

after the data writing is completed according to the first data writing request through the memory 1101, a data synchronization request is sent to the second storage server through the communication module 1103.

In one embodiment, the first data write request carries data content and a data key identifier; after receiving the first data write request sent by the service server through the communication module 1103 and before sending a data synchronization request to the second storage server, the method further includes:

judging whether the data key identification exists according to the first data writing request;

if the first storage server does not have the data key identification, the first storage server writes the key identification into a key domain of a data key value pair, writes data content carried by the first data write request into a value domain of the data key value pair, distributes a data version identification to the data content, and sends a data version identification synchronization request to a control server.

In one embodiment, if the first storage server has the data key identifier, the first storage server sends a determination request of the data version identifier to the control server through the communication module 1103, where the determination request carries the data version identifier corresponding to the data content stored in the first storage server;

in a case that the first storage server receives a first determination result sent by the control server through the communication module 1103, the first storage server updates the data content and the data version identifier in the data key value pair value field, where the first determination result represents that the data version identifiers are consistent.

Under the condition that the first storage server receives a second judgment result sent by the control server through the communication module 1103, the first storage server does not update the data key value pair and returns a data unwritable result to the service server, wherein the second judgment result represents that the data version identifiers are inconsistent.

In one embodiment, after sending the data synchronization request to the second storage server, the first storage server receives a result of successful data synchronization or unsuccessful data synchronization returned by the second storage server through the communication module 1103.

Fig. 12 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application. For ease of understanding and illustration, shown in fig. 12 is a disaster recovery device 120 of a storage system, said device corresponding to a control server in an embodiment of the method, and may comprise one or more of the following components: memory 1201, processor 1202, communication module 1203.

Memory 1201 may include one or more storage units, each of which may include one or more memories, which may be used to store programs and various data and may be used to perform access to the programs or data automatically and at a high speed during operation of disaster recovery device 120 of the storage system. When the storage server 120 shown in fig. 12 executes the methods of fig. 2-7, the storage may be used to store data version identifications and other related data, etc.

The communication module 1203, which may also be referred to as a transceiver, or transceiver, etc., may include a unit for wireless, wired, or other communication. Alternatively, a device for implementing a receiving function in part 1203 may be regarded as a receiving unit, and a device for implementing a transmitting function may be regarded as a transmitting unit, that is, part 1203 includes a receiving unit and a transmitting unit.

The processor 1202, which may also be referred to as a processing unit, processing board, processing module, processing device, etc. The processor may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. When the disaster recovery device 120 of the storage system shown in fig. 12 executes step S207 in the method embodiment in fig. 2, step S404 and step S405 in the method embodiment in fig. 4, and step S706 in the method embodiment in fig. 7, the processor 1202 calls the computer program of the memory 1201 to execute the following steps:

after receiving a data version identification judgment request sent by a first storage server through a communication module 1203, where the data version identification judgment request carries a data version identification corresponding to data content stored in the first storage server, judging a data version identification and a data version identification corresponding to a control server;

the result of the data version identification judgment is returned to the first storage server through the communication module 1203.

In one embodiment, determining, by the processor 1202, the data version identification and the corresponding data version identification on the control server, and returning the result of the data version identification determination to the first storage server includes:

judging whether the data version identification is consistent with the corresponding data version identification on the control server;

if the data version identification is consistent with the current data version identification, the control server updates the current data version identification and returns the result of consistency of the updated data version identification and the data version identification to the first storage server;

and if the data version identifications are inconsistent, the control server does not process the current data version identifications and returns the inconsistent result of the data version identifications to the first storage server.

Fig. 13 is a schematic structural diagram of a disaster recovery device of another storage system according to an embodiment of the present application. For ease of understanding and illustration, fig. 13 shows a disaster recovery device 130 of a storage system, which device, corresponding to a traffic server in an embodiment of the method, may include one or more of the following components: memory 1301, processor 1302, communication module 1303.

The memory 1301 may include one or more memory units, each of which may include one or more memories, which may be used to store programs and various data and enable high-speed, automated access to the programs or data during operation of the storage device 130 of the storage system. When the storage device 130 of the storage system shown in fig. 13 executes the steps in the method embodiments of fig. 2 to 6, the memory 1301 may be used to store a data write request, a data write success request, other related data, and the like.

The communication server 1303 may also be referred to as a transceiver, or the like, and may include a unit for performing wireless, wired, or other communication. Optionally, a device used for implementing the receiving function in the part 1303 may be regarded as a receiving unit, and a device used for implementing the transmitting function may be regarded as a transmitting unit, that is, the part 1303 includes a receiving unit and a transmitting unit.

Processor 1302, which may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc. The processor may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. When the disaster recovery device 130 of the storage system shown in fig. 13 executes step S202 in the method embodiment described in fig. 2 and executes step S708 in the method embodiment described in fig. 7, the processor 1302 calls the computer program in the memory 1301 to execute the following steps:

a first data writing request is sent to a first storage server after a data writing request of a terminal is received through a communication module 1303; the first storage server is one of a plurality of storage servers; the data writing request carries data content, and the first data writing request carries the data content and the data key identification;

and when receiving a data writing unsuccessful result returned by the first storage server through the communication module 1303, sending a first data writing request to any other storage server except the first storage server in the storage system.

In one embodiment, the method further comprises the following steps:

after the communication module 1303 sends the first data write-in request to the second storage server, the second storage server does not return a result indicating that the second storage server is failed, and sends the first data write-in request to any one of the other storage servers except the second storage server according to the communication module 1303.

It should be noted that, for specific implementation of each functional unit, reference may be made to relevant descriptions in each method embodiment described above, and details are not described in this embodiment of the application. The specific implementation and advantages of the above operations may also correspond to the corresponding descriptions provided in the embodiments and possible embodiments of fig. 1 to 6.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. And the aforementioned storage medium includes: a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

In this application, the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. While the present application has been described herein in conjunction with various embodiments, other variations to the disclosed embodiments may be understood and effected by those skilled in the art in practicing the present application as claimed herein.

Claims (13)

1. A disaster recovery method for a storage system, wherein the disaster recovery system includes a plurality of storage servers, and each of the plurality of storage servers has data reading and data writing functions, the method comprising:

a first storage server receives a first data write-in request sent by a service server; the first storage server is one of the plurality of storage servers; the data writing request carries data content;

after the first storage server completes data writing according to the first data writing request, sending a data synchronization request to a second storage server;

wherein the second storage server is a server other than the first storage server in the plurality of storage servers; and the data synchronization request is used for indicating the second storage server to complete data synchronization, and when the second storage server receives a first data writing request sent by a service server, completing data writing according to the data writing request.

2. The method of claim 1, wherein the first data write request carries data content and a data key identification; after the first storage server receives the first data write request sent by the service server and before the first storage server sends the data synchronization request to the second storage server, the method further includes:

the first storage server judges whether the data key identification exists according to the first data writing request;

if the first storage server does not have the data key identification, the first storage server writes the key identification into a key domain of a data key value pair, writes the data content into a value domain of the data key value pair, distributes a data version identification to the data content, and sends a data version identification synchronization request to a control server.

3. The method according to claim 2, wherein if the data key identifier exists in the first storage server, the first storage server sends a determination request of a data version identifier to the control server, wherein the determination request carries the data version identifier corresponding to the data content stored in the first storage server;

under the condition that the first storage server receives a first judgment result sent by the control server, wherein the first judgment result represents that the data version identification is consistent and carries the latest data version identification; the first storage server updates the data content and the data version identification in the data key value pair value field;

and under the condition that the first storage server receives a second judgment result sent by the control server, wherein the second judgment result represents that the data version identifications are inconsistent, the first storage server does not update the data key value pair and returns a data non-writable result to the service server.

4. The method of claim 1, wherein the storage server comprises a block-link point server;

after the data synchronization request is sent to the second storage server, the first storage server receives a result that the data synchronization returned by the second storage server is successful or unsuccessful.

5. A disaster recovery method for a storage system, wherein the disaster recovery system includes a control server, the method comprising:

after a judgment request of a data version identification sent by a first storage server is received, wherein the data version identification judgment request carries the data version identification which is stored by the first storage server and corresponds to data content, the data version identification and the data version identification which corresponds to the control server are judged, and a judgment result of the data version identification is returned to the first storage server.

6. The method of claim 5, wherein determining the data version identification and the corresponding data version identification on the control server and returning the result of the determination of the data version identification to the first storage server comprises:

judging whether the data version identification is consistent with the corresponding data version identification on the control server;

if the data version identification is consistent with the current data version identification, the control server updates the current data version identification and returns the result of consistency of the updated data version identification and the data version identification to the first storage server;

and if the data version identifications are inconsistent, the control server does not process the current data version identifications and returns the inconsistent result of the data version identifications to the first storage server.

7. A disaster recovery method of a storage system, wherein the disaster recovery system comprises a service server, the method comprising:

sending a first data writing request to a first storage server after receiving a data writing request of a terminal; the first storage server is one of a plurality of storage servers; the data writing request carries data content, and the first data writing request carries data content and a data key identifier;

and when receiving a data writing unsuccessful result returned by the first storage server, the service server sends a first data writing request to any storage server except the first storage server in the plurality of storage servers.

8. The method of claim 7, further comprising:

after the service server sends a first data write-in request to a second storage server, the second storage server does not return a result, which indicates that the second storage server fails, and the service server sends the first data write-in request to any other storage server except the second storage server.

9. A method for disaster recovery in a storage system, the method comprising:

the method comprises the steps that a service server sends a first data writing request to a first storage server after receiving a data writing request sent by a terminal, wherein the data writing request carries data content, and the first data writing request carries the data content and a data key identifier; the first storage server is one of the plurality of storage servers;

after the first storage server completes data writing according to the first data writing request, sending a data synchronization request to a second storage server;

wherein the second storage server is a server other than the first storage server in the plurality of storage servers; and the data synchronization request is used for indicating the second storage server to complete data synchronization, and when the second storage server receives a data writing request sent by a service server, completing data writing according to the data writing request.

10. A disaster recovery apparatus for a storage system, comprising:

a receiving unit, configured to receive a data write request sent by a service server;

and the sending unit is used for sending a data synchronization request to the second storage server after the first storage server completes data writing according to the data writing request.

11. A disaster recovery apparatus for a storage system, comprising:

a judging unit, configured to, after receiving a judgment request for a data version identifier sent by a first storage server, where the judgment request carries the data version identifier corresponding to the data content stored in the first storage server, judge the data version identifier and a data version identifier corresponding to the data content on the control server;

and the sending unit is used for returning the result of the judgment of the data version identification to the first storage server.

12. A disaster recovery apparatus for a storage system, comprising:

the sending unit is used for sending a first data writing request to the first storage server after receiving the data writing request of the terminal; the first storage server is one of the plurality of storage servers;

the sending unit is further configured to send, when receiving a result that data writing returned by the first storage server is unsuccessful, a first data writing request to any one of the other storage servers in the storage system except the first storage server by the service server.

13. A computer-readable storage medium, characterized in that the computer-readable storage medium stores program instructions that, when executed by a processor, cause the processor to perform the method of any of claims 1-8.