CN109561151B - Data storage method, device, server and storage medium - Google Patents
Data storage method, device, server and storage medium Download PDFInfo
- Publication number
- CN109561151B CN109561151B CN201811519676.6A CN201811519676A CN109561151B CN 109561151 B CN109561151 B CN 109561151B CN 201811519676 A CN201811519676 A CN 201811519676A CN 109561151 B CN109561151 B CN 109561151B
- Authority
- CN
- China
- Prior art keywords
- server cluster
- data
- database
- server
- storage
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
Abstract
The disclosure relates to a data storage method, a data storage device, a server and a storage medium, and relates to the technical field of data processing, wherein the method comprises the following steps: when the server stores the service data in the storage database of the first server cluster, the server may backup the service data to the storage database of the second server cluster, and when the service data is not backed up to the storage database of the second server cluster, store the data identifier of the service data to the corresponding partition of the target disaster recovery database, and then backup the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database. The first server cluster and the second server cluster are respectively located in different machine rooms, so that a cross-machine-room data storage process is realized, and the stability and reliability of data storage are improved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data storage method, an apparatus, a server, and a storage medium.
Background
With the development of the information age, the traffic volume in the network is increasing day by day, and data caching is an indispensable part in the process of realizing business processing. In the process of service processing, data related to a service generally needs to be cached through a server cluster.
At present, the data caching method generally comprises: in the service processing process, the service data related in the service processing process is cached in a server cluster in the same machine room in real time, and is generally stored in a Redis database of the server cluster, so as to facilitate subsequent reading and use in the service processing process.
However, in the data caching method, when any server used for storing the service data in the computer room crashes in the service processing process, the service processing process is also affected to interrupt the processing, so that the stability and reliability of the data storage are poor.
Disclosure of Invention
The present disclosure provides a data storage method, apparatus, server and storage medium. The problem of poor stability and reliability of data storage in the related art can be overcome.
According to a first aspect of the embodiments of the present disclosure, a data storage method is provided, where the method is applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different computer rooms, respectively, and the method includes:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identification of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is a disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
In a possible implementation manner, when the server does not backup the service data to the storage database of the second server cluster, storing the data identifier of the service data to the corresponding partition of the target disaster recovery database includes:
when the server does not back up the service data to the storage database of the second server cluster, determining a corresponding partition of the data identifier in a plurality of partitions of the target disaster recovery database according to the characteristic value of the data identifier of the service data;
and storing the data identification into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the storing the data identifier to the corresponding partition of the target disaster recovery database includes:
determining a backup path of the business data, wherein the backup path is used for indicating a source server cluster and a destination server cluster when the business data is backed up;
and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the storing, according to the data identifier in the corresponding partition of the target disaster recovery database, the service data in the storage database of the first server cluster to the storage database of the second server cluster includes:
when the target also comprises the backup path of the service data in the corresponding partition of the database, screening out a target server cluster as a target data identifier of a server cluster where the server is located from a plurality of data identifiers of the corresponding partition of the target disaster backup database according to the backup path of the service data in the corresponding partition of the target disaster backup database;
and acquiring target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
In a possible implementation manner, the storing the service data corresponding to the data identifier in the storage database of the second server cluster includes:
and when the storage database of the second server cluster comprises the data identifier, updating the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
In a possible implementation manner, before storing the data identifier of the service data in the corresponding partition of the target disaster recovery database when the service data is not backed up in the storage database of the second server cluster, the method further includes:
when the business data is unsuccessfully stored in the available space of the storage database of the second server cluster, or the available space of the storage database of the second server cluster is smaller than a preset threshold value, it is determined that the server does not back up the business data to the storage database of the second server cluster.
In a possible implementation manner, the first server cluster is a master server cluster, and the second server cluster is a slave server cluster.
According to a second aspect of the embodiments of the present disclosure, there is provided a data storage apparatus, which is applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different machine rooms, respectively, the apparatus including:
the first storage module is configured to backup business data to a storage database of a second server cluster when the server stores the business data in the storage database of the first server cluster, wherein the storage database of the second server cluster is used for backing up the business data in the storage database of the first server cluster;
the second storage module is configured to store the data identifier of the service data into a corresponding partition of a target disaster recovery database when the server does not back up the service data into a storage database of the second server cluster, where the target disaster recovery database is a disaster recovery database of a server cluster where the server is located;
and the third storage module is configured to store the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
In a possible implementation manner, the second storage module is further configured to determine, when the server does not back up the service data to the storage database of the second server cluster, a corresponding partition of a data identifier in a plurality of partitions of the target disaster recovery database according to a characteristic value of the data identifier of the service data; and storing the data identification into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the second storage module is further configured to determine a backup path of the service data, where the backup path is used to indicate a source server cluster and a destination server cluster when backing up the service data; and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the third storage module is further configured to, when the target further includes the backup path of the service data in the corresponding partition of the database to be searched, screen out, from the plurality of data identifiers of the corresponding partition of the target disaster recovery database, a target server cluster as the target data identifier of the server cluster where the server is located according to the backup path of the service data in the corresponding partition of the target disaster recovery database; and acquiring target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
In a possible implementation manner, the updating module is configured to, when the storage database of the second server cluster includes the data identifier, update the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
In one possible implementation, the apparatus further includes:
the determining module is configured to determine that the business data is not backed up in the storage database of the second server cluster when the business data is not successfully stored in the available space of the storage database of the second server cluster or the available space of the storage database of the second server cluster is smaller than a preset threshold.
In a possible implementation manner, the first server cluster is a master server cluster, and the second server cluster is a slave server cluster.
According to a third aspect of the embodiments of the present disclosure, there is provided a data storage server, including:
one or more processors;
one or more memories for storing the one or more processor-executable instructions;
wherein the data storage server is a server of any one of a first server cluster or a second server cluster, the first server cluster and the second server cluster are respectively located in different computer rooms, and the one or more processors are configured to:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identification of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is a disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium, wherein instructions, when executed by a processor of a mobile terminal, enable the mobile terminal to execute a data storage method applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different rooms, respectively, the method including:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identification of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is a disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
According to a fifth aspect of the embodiments of the present disclosure, there is provided an application program, including one or more instructions, which when executed by a processor of a server, enable the server to execute a data storage method, where the method is applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different rooms, respectively, and the method includes:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
if the server does not backup the service data into the storage database of the second server cluster, storing the data identification of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is the disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
in this disclosure, when the server stores the service data in the storage database of the first server cluster, the server may backup the service data to the storage database of the second server cluster, and when the service data is not backed up to the storage database of the second server cluster, the server may also synchronously store the data identifier of the service data to the corresponding partition of the target disaster recovery database, and then backup the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database. The first server cluster and the second server cluster are respectively located in different machine rooms, and the service data in the first server cluster can be accurately and reliably backed up to the second server cluster, so that a cross-machine-room data storage process is realized, and the stability and reliability of data storage are improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow chart illustrating a method of data storage according to an exemplary embodiment.
FIG. 2 is a schematic diagram of an implementation environment of a data storage method according to an example embodiment.
FIG. 3 is a flow chart illustrating a method of data storage according to an exemplary embodiment.
FIG. 4 is an architectural diagram illustrating a data storage method according to an exemplary embodiment.
FIG. 5 is a block diagram illustrating a data storage device according to an exemplary embodiment.
FIG. 6 is a block diagram illustrating a server in accordance with an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a flowchart illustrating a data storage method according to an exemplary embodiment, where as shown in fig. 1, the data storage method is applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different rooms respectively, and includes the following steps.
101. When the server stores the service data in the storage database of the first server cluster, backing up the service data to the storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
102. when the server does not backup the service data into the storage database of the second server cluster, storing the data identifier of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is the disaster recovery database of the server cluster where the server is located;
103. and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
In a possible implementation manner, when the server does not backup the service data to the storage database of the second server cluster, storing the data identifier of the service data to the corresponding partition of the target disaster recovery database includes:
when the server does not back up the service data to the storage database of the second server cluster, determining a corresponding partition of the data identifier in the multiple partitions of the target disaster recovery database according to the characteristic value of the data identifier of the service data;
and storing the data identification into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the storing the data identifier to the corresponding partition of the target disaster recovery database includes:
determining a backup path of the service data, wherein the backup path is used for indicating a source server cluster and a destination server cluster when the service data is backed up;
and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the storing the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database includes:
when the target also comprises the backup path of the service data in the corresponding partition of the database, screening out a target server cluster as a target data identifier of a server cluster where the server is located from a plurality of data identifiers of the corresponding partition of the target disaster backup database according to the backup path of the service data in the corresponding partition of the target disaster backup database;
and acquiring the target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
In a possible implementation manner, the storing the service data corresponding to the data identifier in the storage database of the second server cluster includes:
and when the storage database of the second server cluster comprises the data identifier, updating the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
In a possible implementation manner, before the storing the data identifier of the service data into the corresponding partition of the target disaster recovery database when the server does not back up the service data to the storage database of the second server cluster, the method further includes:
and when the business data is not successfully stored in the available space of the storage database of the second server cluster, or the available space of the storage database of the second server cluster is smaller than a preset threshold value, determining that the server does not back up the business data to the storage database of the second server cluster.
In one possible implementation, the first server cluster is a master server cluster, and the second server cluster is a slave server cluster.
In this disclosure, when the server stores the service data in the storage database of the first server cluster, the server may backup the service data to the storage database of the second server cluster, and when the service data is not backed up to the storage database of the second server cluster, the server may also synchronously store the data identifier of the service data to the corresponding partition of the target disaster recovery database, and then backup the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database. The first server cluster and the second server cluster are respectively located in different machine rooms, and the service data in the first server cluster can be accurately and reliably backed up to the second server cluster, so that a cross-machine-room data storage process is realized, and the stability and reliability of data storage are improved.
Fig. 2 is a schematic diagram of an implementation environment of a data storage method according to an exemplary embodiment, and as shown in fig. 2, the implementation environment includes a first server cluster 201 and a second server cluster 202, and a storage layer and a logic layer are deployed in the first server cluster 201 and the second server cluster 202. The storage tiers of the first server cluster 201 and the second server cluster 202 are respectively provided with a storage database and a disaster recovery database. The logic layer comprises business processing logic used for providing business processing service. The first server cluster 201 and the second server cluster 202 are respectively located in different rooms, for example, the first server cluster 201 is located in a room a, and the second server cluster is located in a room B.
The first server cluster 201 and the second server cluster 202 may both receive the service processing request, for example, a plurality of service processing requests may be uniformly distributed to the first server cluster 101 and the second server cluster 102 in real time, and a logic layer of the first server cluster 101 or the second server cluster 102 executes a service processing process. The storage database is used for storing service data related to the service in the service processing process. In the service processing process, the service data may be stored in the storage database of the first server cluster 101 in real time, and the service data is backed up in the storage database of the second server cluster 202, so as to backup the storage database of the first server cluster 201. When the service data is not backed up to the second server cluster 202, the data identifier of the service data may be stored in the corresponding partition of the disaster recovery database; and then, according to the data identifier in the corresponding partition based on the disaster recovery database, storing the service data corresponding to the data identifier in the storage database of the first server cluster 201 to the storage database of the second server cluster 202.
It should be noted that the first server cluster 201 and the second server cluster 202 are server clusters in a storage system, the storage system may include a plurality of server clusters, the plurality of server clusters are respectively located in a plurality of different computer rooms, the first server cluster 201 may be any main server cluster in the storage system, and the second server cluster 202 may be any slave server cluster in the storage system. The embodiment of the present disclosure is not particularly limited to this.
It should be noted that the above-mentioned process is described only with the first server cluster 201 as a master server cluster, and the second server cluster 202 as a slave server cluster. Of course, the first server cluster 201 may be switched to a slave server cluster at any time, and the second server cluster 202 may be switched to a master server cluster at any time. For example, in the current service processing process, the first server cluster 201 serves as a master server cluster, and the second server cluster 202 serves as a slave server cluster; in the next service processing process, the first server cluster 201 may be switched to a slave server cluster, and the second server cluster 202 may also be switched to a master server cluster. In a possible implementation manner, when the backup of the slave server cluster fails, the data identifier and the backup path of the service data may also be stored in the disaster recovery database, where the backup path is used to indicate the source server cluster and the destination server cluster at the time of backing up the service data, so that the service data in the storage database of the master server cluster is backed up in the storage database of the destination server cluster based on the destination server cluster.
Fig. 3 is a flowchart illustrating a data storage method according to an exemplary embodiment, where the method is applied to a server of any one of a first server cluster or a second server cluster, and the first server cluster and the second server cluster are respectively located in different rooms, as shown in fig. 3, including the following steps.
301. When the server stores the service data in the storage database of the first server cluster, the server backs up the service data to the storage database of the second server cluster.
The storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster; in the embodiment of the disclosure, when receiving the service data to be cached, the server stores the service data into the storage database of the first server cluster, and when the first server cluster is successfully stored, the server stores the service data into the storage database of the second server cluster.
The first server cluster may be a master server cluster, and the second server cluster may be a slave server cluster. The storage database may be any database that can store data in the server cluster, and in a possible implementation manner, the storage database may be a cache database in the server cluster, where the cache database refers to a server that supports real-time storage and real-time reading of service data in a service processing process. In the embodiment of the present disclosure, the storage database of the server cluster may include one or more servers in the server cluster for providing storage services. In one possible implementation, the storage database may be a Redis database in a server cluster. In the Redis database, the server may store the service data in the form of key-value (key value) into a queue of the Redis database. The key is used for storing the data identifier of the service data, and the value is used for storing the service data and information such as the data version and the expiration time of the service data.
The logical layers of the first server cluster and the second server cluster are configured with data storage addresses, and the data storage addresses refer to storage addresses of service data related in a service processing process. The data storage address may be an IP (internet Protocol) address of a server in the main server cluster, and the server IP address may be an IP address of a server where the storage database is located. And the server writes the service data into a storage database of the first server cluster, and when the server successfully writes the service data into the storage database of the first server cluster, the server determines that the service data in the service processing process is successfully stored. The server asynchronously writes the service data into a storage database of a second server cluster by adopting an asynchronous storage mode.
The server may store a first server identifier of a server in which the database is stored in the first server cluster, and a second server identifier of a server in which the database is stored in the second server cluster, so that the server may asynchronously backup the service data after storing the service data based on the first server identifier and the second server identifier. The server may be any one of the first server cluster and the second server cluster for providing data storage services.
In the embodiment of the disclosure, the server can asynchronously backup the service data to the slave server cluster when the service data is successfully written into the master server cluster, so that cross-machine-room storage can be realized when caching is possible, and the reliability of the data caching process in the service processing process is improved.
302. When the server fails to store the service data in the available space of the storage database of the second server cluster, or the available space of the storage database of the second server cluster is smaller than a preset threshold value, the server determines that the server does not back up the service data in the storage database of the second server cluster.
In the backup process, the server can also judge whether to backup the service number to the storage database of the second server cluster in real time based on the storage state. The available space of the storage database refers to the remaining space in the storage database that can be currently used for storing business data.
In the process of backing up the service data by the server, if the server does not successfully store the service data into the available space of the storage database of the second server cluster, that is, the service data does not exist in the available space of the storage database of the second server cluster, the server determines that the service data is not backed up into the storage database of the second server cluster. Or, when the available space of the storage database of the second server cluster is smaller than the preset threshold, it indicates that the storage database is full or is about to be full, and the server determines that the service data is not backed up in the storage database of the second server cluster, that is, the backup of the second server cluster fails. Otherwise, the server determines that the second server cluster storage is successful. And (6) ending.
The preset threshold may be set based on needs, and this is not particularly limited in the embodiments of the present disclosure. For example, the preset threshold may be 0 byte, 1 byte, etc.
In the embodiment of the present disclosure, the server may determine whether the server successfully backs up the service data based on the size of the available space of the storage database and whether the storage is successful in the backup process, so that when the backup fails, the disaster recovery backup may be performed based on the subsequent step 303 and 304, thereby further improving the reliability of the cross-machine-room cache and ensuring the stability of the service processing process.
303. And when the server does not back up the service data to the storage database of the second server cluster, the server stores the data identifier of the service data to the corresponding partition of the target disaster recovery database.
And disaster recovery databases are configured in the first server cluster and the second server cluster. The disaster recovery database is used for storing the data identification of the service data when the storage of the second server cluster fails. When the server does not back up the service data to the storage database of the second server cluster, the server may change the storage address of the service data, and change the data identifier of the service data to be stored in the target disaster recovery database. The server may determine, according to the characteristic value of the data identifier of the service data, a corresponding partition of the data identifier in the plurality of partitions of the target disaster recovery database, and store the data identifier in the corresponding partition of the target disaster recovery database. The target disaster recovery database is a disaster recovery database of a server cluster where the server is located. In addition, the disaster recovery database of the server cluster may include a plurality of partitions, and each partition is used to store service data with the same characteristic value.
In a possible implementation manner, the server may further store the backup path of the service data in the target disaster recovery database. The backup path is used for indicating a source server cluster and a destination server cluster when the business data is backed up. The process of storing the data identifier in the partition of the target disaster recovery data by the server may be: the server determines a backup path of the business data, wherein the backup path is used for indicating a source server cluster and a destination server cluster when the business data is backed up; and the server stores the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
In this embodiment of the present disclosure, the first server cluster is used as a master server cluster in a current backup process, the second server cluster is used as a slave server cluster in the current backup process, the destination server cluster is the second server cluster, and the source server cluster is the first server cluster. In a possible embodiment, the disaster recovery database may be a kafka database in a server cluster, the partitions are partitions included in the kafka database, and the characteristic value of the data identifier of the service data may be a hash value of the data identifier, in this step, the server calculates the hash value of the data identifier of each service data, and stores the data identifier and the backup path of the service data into a corresponding partition of the partitions according to the hash value of the data identifier of the service data. Each partition is used for storing one or more data identifications with the same hash value.
For each data identifier, the server may perform modulo operation between the hash value and the total number of partitions in the disaster recovery database, and determine a partition corresponding to the data identifier according to a result of the modulo operation. For example, the hash value of the data identifier, that is, the key, may be 123 in 3 partitions included in the kafka database, modulo operations are performed on 123 and 3, and the computation result of the modulo operation is the remainder obtained by dividing 123 by 3, that is, 123% 3 is 0 and% is the sign of the modulo operation, and the data identifier is stored to the 0 th partition. In addition, in the kafka database, the backup path may be stored in a form of from/to, and then the storage form of the backup path may be { from: origin server cluster, to: destination server cluster }.
In a possible embodiment, the first server cluster and the second server cluster may perform switching between master and slave server clusters, for example, in a current service processing process, the first server cluster serves as a master server cluster, and the second server cluster serves as a slave server cluster; in the next service processing process, the first server cluster can be switched to a slave server cluster, and the second server cluster can also be switched to a master server cluster. And if the first server cluster is switched to a slave server cluster and the second server cluster is switched to a master server cluster, the source server cluster is the second server cluster, and the destination server cluster is the first server cluster. According to the embodiment of the disclosure, the data identifier and the backup path are stored in the disaster recovery database, so that switching between the master server cluster and the slave server cluster can be supported, and the accuracy of data storage is ensured.
In addition, in order to synchronously store the service data when the backup fails in the disaster recovery database of the server cluster where the server is located, namely the disaster recovery database of the service data storage initiator, because only the data identification is stored, the data volume is small, the data identification is stored in different partitions based on the characteristic values and is stored in the server cluster where the initiator is located, the storage path is short, the storage efficiency of the data identification in the disaster recovery process is greatly improved by reducing the stored data volume and the storage path as much as possible, and the data identification with different characteristic values is stored in different partitions according to the characteristic values, so that the storage accuracy of the data identification in the disaster recovery process is improved, the problem that the data are repeatedly read in the subsequent reading process is avoided, the backup efficiency of the data storage is further improved, and the backup accuracy of the backup is ensured.
304. And the server stores the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the disaster recovery database.
In this step, the server may obtain, according to the data identifier of the partition corresponding to the disaster recovery database, the service data corresponding to the data identifier from the storage database of the first server cluster, and store the service data corresponding to the data identifier in the storage database of the second server cluster.
When the target also comprises the backup path of the service data in the corresponding partition of the database, the server screens out a target server cluster as a target data identifier of the server cluster where the server is located from a plurality of data identifiers of the corresponding partition of the target disaster backup database according to the backup path of the service data in the corresponding partition of the target disaster backup database; and the server acquires the target service data corresponding to the target data identifier from the storage database of the first server cluster, and stores the target service data into the storage database of the second server cluster.
The server may monitor the disaster recovery database of the first server cluster and the disaster recovery database of the second server cluster, filter the data identifiers stored in all the disaster recovery databases according to the backup path, and screen out the data identifier of the service data that needs to be stored in the cluster where the server is located when monitoring that the storage destination server cluster in the disaster recovery database of the first server cluster and the disaster recovery database of the second server cluster is the data identifier of the service data of the server cluster where the server is located, and store the service data based on the data identifier.
The storage database of the first server cluster may further store information such as a data version and expiration time of the service data, so that the server may obtain the service data and information such as the data version and expiration time of the service data from the storage database of the first server cluster according to the data identifier. Taking the storage database as a Redis database and the disaster recovery database as a kafka database as an example, if data is stored in the Redis database in the form of key-value, the server may screen out the value corresponding to the key from the Redis database according to the key value in the kafka database, so as to obtain the key-value, and store the key-value in the Redis database of the second server cluster.
The first server cluster and the second server cluster may switch between master and slave server clusters, for example, the storage database is a Redis database, the disaster recovery database is a kafka database, the kafka database may further include a kafka consumer, and the server may listen to the kafka database in the first server cluster and the second server cluster through the kafka consumer at the same time, and based on { from: origin server cluster, to: and a target server cluster }, screening, when the data identifier of the server cluster where the target server cluster is located is monitored, acquiring the service data corresponding to the data identifier from the master server cluster based on the data identifier, and storing the service data into a Redis database of the slave server cluster.
In a possible embodiment, the second server cluster may include the service data corresponding to the data identifier, however, the service data may not be the latest data, and the server may further update the service data in the second server cluster according to the data version of the service data corresponding to the data identifier from the first server cluster. And when the storage database of the second server cluster comprises the data identifier, the server updates the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
And the server acquires first service data corresponding to the data identifier in the storage database of the first server cluster according to the data identifier, and acquires second service data corresponding to the data identifier in the storage database of the second server cluster. The server judges according to the data version (version) of the first service data and the data version of the second service data, if the data version of the first service data is later than the data version of the second service data, the version of the second service data is older, the server deletes the second service data in the storage database of the second server cluster, and stores the first service data in the storage database of the second server cluster; and if the data version of the first service data is earlier than the data version of the second service data, which indicates that the version of the second service data is newer, the server discards the first service data.
For a clearer explanation of the data storage process, the embodiment of the present disclosure further describes the data storage process with a framework shown in fig. 4. As shown in fig. 4, taking the storage database as a Redis database and the disaster recovery database as a kafka database as an example, the a server cluster of the room a is a main server cluster, and the B server cluster of the room B is a main server cluster. And the server cluster A and the server cluster B process the service request based on the logic layers of the server cluster A and the server cluster B respectively, and in the processing process, the server writes the service data into a Redis database of the server cluster A and asynchronously stores the service data into the Redis database of the server cluster B. When the asynchronous writing of the service number into the Redis database of the server cluster B by the server cluster A fails, the synchronous writing of the service number into the kafka database of the server cluster A by the server cluster A; similarly, when the B server cluster fails to asynchronously write the service number into the Redis database of the B server cluster, the B server cluster synchronously writes the service number into the kafka database of the server cluster. Meanwhile, the consumers in the kafka database of the A, B server cluster all listen to the kafka database of the A, B server cluster. When a kafka consumer of a B server cluster monitors two kafka databases, and a target server cluster is a key corresponding to the business data of the B server cluster, the business data corresponding to the key, namely value, is obtained from a hot Redis database of the A server cluster, and is stored in a Redis database of the B server cluster, namely the business data is dropped back to the Redis database of the B server cluster by the consumer of the B server cluster. In the kafka consumer monitoring process of the A server cluster, because the destination server cluster is the slave server cluster and the A server cluster is the master server cluster, the consumer of the A server cluster cannot monitor the data identifier of which the destination server cluster is the A server cluster, and therefore, the consumer of the A server cluster cannot fall back data. Of course, the A, B server cluster may perform switching between the master server cluster and the slave server cluster, and at this time, when the kafka consumer of the a server cluster monitors that the destination server cluster is a key corresponding to the service data of the a server cluster, the service data corresponding to the key in the Redis database of the master server cluster is stored in the Redis database of the a server cluster, thereby implementing asynchronous backup of the service data to the slave server cluster across the computer room, and being capable of synchronously dropping the service data from the disaster recovery database to the slave server cluster when the backup fails, thereby improving reliability and stability of data storage.
In this disclosure, when the server stores the service data in the storage database of the first server cluster, the server may backup the service data to the storage database of the second server cluster, and when the service data is not backed up to the storage database of the second server cluster, the server may also synchronously store the data identifier of the service data to the corresponding partition of the target disaster recovery database, and then backup the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database. The first server cluster and the second server cluster are respectively located in different machine rooms, and the service data in the first server cluster can be accurately and reliably backed up to the second server cluster, so that a cross-machine-room data storage process is realized, and the stability and reliability of data storage are improved.
FIG. 5 is a block diagram illustrating a data storage device according to an example embodiment. Referring to fig. 5, the apparatus is applied to a server of any one of a first server cluster or a second server cluster, where the first server cluster and the second server cluster are located in different rooms respectively, and the apparatus includes a first storage module 501, a second storage module 502, and a second storage module 502.
A first storage module 501, configured to, when the server stores service data in the storage database of the first server cluster, backup the service data to a storage database of a second server cluster, where the storage database of the second server cluster is used to backup the service data in the storage database of the first server cluster;
a second storage module 502, configured to store the data identifier of the service data in a corresponding partition of a target disaster recovery database when the server does not backup the service data in the storage database of the second server cluster, where the target disaster recovery database is a disaster recovery database of a server cluster where the server is located;
the third storage module 503 is configured to store the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
In a possible implementation manner, the second storage module is further configured to determine, when the server does not back up the service data to the storage database of the second server cluster, a corresponding partition of the data identifier in the multiple partitions of the target disaster recovery database according to a characteristic value of the data identifier of the service data; and storing the data identification into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the second storage module is further configured to determine a backup path of the service data, where the backup path is used to indicate a source server cluster and a destination server cluster when the service data is backed up; and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
In a possible implementation manner, the third storage module is further configured to, when the target further includes the backup path of the service data in the corresponding partition of the database to be searched, screen out, from the plurality of data identifiers of the corresponding partition of the target disaster recovery database, a target server cluster as the target data identifier of the server cluster where the server is located according to the backup path of the service data in the corresponding partition of the target disaster recovery database; and acquiring the target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
In a possible implementation manner, the updating module is configured to, when the storage database of the second server cluster includes the data identifier, update the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
In one possible implementation, the apparatus further includes:
the determining module is configured to determine that the service data is not backed up in the storage database of the second server cluster when the service data is not successfully stored in the available space of the storage database of the second server cluster or the available space of the storage database of the second server cluster is smaller than a preset threshold.
In one possible implementation, the first server cluster is a master server cluster, and the second server cluster is a slave server cluster.
In this disclosure, when the server stores the service data in the storage database of the first server cluster, the server may backup the service data to the storage database of the second server cluster, and when the service data is not backed up to the storage database of the second server cluster, the server may also synchronously store the data identifier of the service data to the corresponding partition of the target disaster recovery database, and then backup the service data in the storage database of the first server cluster to the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database. The first server cluster and the second server cluster are respectively located in different machine rooms, and the service data in the first server cluster can be accurately and reliably backed up to the second server cluster, so that a cross-machine-room data storage process is realized, and the stability and reliability of data storage are improved.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
It should be noted that: in the data storage device provided in the above embodiment, when storing data, only the division of the above functional modules is taken as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above described functions. In addition, the data storage device provided by the above embodiment and the data storage method embodiment belong to the same concept, and specific implementation processes thereof are detailed in the method embodiment and are not described herein again.
Fig. 6 is a schematic structural diagram of a server according to an embodiment of the present disclosure, where the server 600 may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 601 and one or more memories 602, where the memory 602 stores at least one instruction, the server is a server of any one of a first server cluster or a second server cluster, and the first server cluster and the second server cluster are located in different rooms, and the at least one instruction is loaded and executed by the processor 601 to implement the data storage method provided by each method embodiment:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to the storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identifier of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is the disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.
In an exemplary embodiment, there is also provided a computer-readable storage medium, such as a memory, including instructions executable by a processor in a terminal to perform the data storage methods in the embodiments described below.
The method is applied to a server of any one of a first server cluster or a second server cluster, wherein the first server cluster and the second server cluster are respectively located in different machine rooms, and the method comprises the following steps:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to the storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identifier of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is the disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
For example, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, there is also provided an application program including one or more instructions which, when executed by a processor of a server, enable the server to perform a data storage method applied to a server of any one of a first server cluster or a second server cluster, the first server cluster and the second server cluster being located in different rooms, respectively, the method including:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to the storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not backup the service data into the storage database of the second server cluster, storing the data identifier of the service data into a corresponding partition of a target disaster recovery database, wherein the target disaster recovery database is the disaster recovery database of the server cluster where the server is located;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (14)
1. A data storage method is applied to a server of any one of a first server cluster or a second server cluster, wherein the first server cluster and the second server cluster are respectively located in different machine rooms, and the method comprises the following steps:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not back up the service data to the storage database of the second server cluster, determining a corresponding partition of the data identifier in a plurality of partitions of a target disaster recovery database according to a characteristic value of the data identifier of the service data, wherein the characteristic value of the data identifier is a hash value of the data identifier, each partition is used for storing one or more data identifiers with the same hash value, and the target disaster recovery database is a disaster recovery database of the server cluster where the server is located; storing the data identification into a corresponding partition of the target disaster recovery database;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
2. The data storage method according to claim 1, wherein the storing the data identifier into the corresponding partition of the target disaster recovery database comprises:
determining a backup path of the business data, wherein the backup path is used for indicating a source server cluster and a destination server cluster when the business data is backed up;
and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
3. The data storage method according to claim 1, wherein the storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database comprises:
when the corresponding partition of the target disaster backup database also comprises the backup path of the service data, screening out a target data identifier of a target server cluster as a server cluster where the server is located from a plurality of data identifiers of the corresponding partition of the target disaster backup database according to the backup path of the service data in the corresponding partition of the target disaster backup database;
and acquiring target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
4. The data storage method according to claim 1, wherein the storing the service data in the storage database of the first server cluster into the storage database of the second server cluster comprises:
and when the storage database of the second server cluster comprises the data identifier, updating the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster.
5. The data storage method according to claim 1, wherein when the server does not backup the service data in the storage database of the second server cluster, the method further includes, before determining, according to a characteristic value of a data identifier of the service data, that the data identifier is in a corresponding partition of a plurality of partitions of a target disaster recovery database, the method further includes:
when the business data is unsuccessfully stored in the available space of the storage database of the second server cluster, or the available space of the storage database of the second server cluster is smaller than a preset threshold value, it is determined that the server does not back up the business data to the storage database of the second server cluster.
6. The data storage method of claim 1, wherein the first server cluster is a master server cluster and the second server cluster is a slave server cluster.
7. A data storage device, wherein the device is applied to a server of any one of a first server cluster or a second server cluster, and the first server cluster and the second server cluster are respectively located in different machine rooms, the device comprising:
the first storage module is configured to backup business data to a storage database of a second server cluster when the server stores the business data in the storage database of the first server cluster, wherein the storage database of the second server cluster is used for backing up the business data in the storage database of the first server cluster;
a second storage module, configured to, when the server does not backup the service data to the storage database of the second server cluster, determine, according to a feature value of a data identifier of the service data, a corresponding partition of the data identifier in multiple partitions of a target disaster recovery database, where the feature value of the data identifier is a hash value of the data identifier, each partition is used to store one or more data identifiers having the same hash value, and the target disaster recovery database is a disaster recovery database of a server cluster where the server is located; storing the data identification into a corresponding partition of the target disaster recovery database;
and the third storage module is configured to store the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
8. The data storage device of claim 7,
the second storage module is further configured to determine a backup path of the service data, where the backup path is used to indicate a source server cluster and a destination server cluster when the service data is backed up; and storing the data identifier and the backup path of the service data into a corresponding partition of the target disaster recovery database.
9. The data storage device of claim 7,
the third storage module is further configured to, when the corresponding partition of the target disaster recovery database further includes the backup path of the service data, screen out a target data identifier of a server cluster where a target server cluster is located from a plurality of data identifiers of the corresponding partition of the target disaster recovery database according to the backup path of the service data in the corresponding partition of the target disaster recovery database; and acquiring target service data corresponding to the target data identifier from the storage database of the first server cluster, and storing the target service data into the storage database of the second server cluster.
10. The data storage device of claim 7,
and the updating module is configured to update the service data corresponding to the data identifier in the storage database of the second server cluster according to the data version of the service data in the storage database of the first server cluster when the storage database of the second server cluster includes the data identifier.
11. The data storage device of claim 7, wherein the device further comprises:
the determining module is configured to determine that the server does not backup the service data into the storage database of the second server cluster when the service data is not successfully stored into the available space of the storage database of the second server cluster or the available space of the storage database of the second server cluster is smaller than a preset threshold.
12. The data storage device of claim 7, wherein the first server cluster is a master server cluster and the second server cluster is a slave server cluster.
13. A data storage server, comprising:
one or more processors;
one or more memories for storing the one or more processor-executable instructions;
wherein the data storage server is a server of any one of a first server cluster or a second server cluster, the first server cluster and the second server cluster are respectively located in different computer rooms, and the one or more processors are configured to:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not back up the service data to the storage database of the second server cluster, determining a corresponding partition of the data identifier in a plurality of partitions of a target disaster recovery database according to a characteristic value of the data identifier of the service data, wherein the characteristic value of the data identifier is a hash value of the data identifier, each partition is used for storing one or more data identifiers with the same hash value, and the target disaster recovery database is a disaster recovery database of the server cluster where the server is located; storing the data identification into a corresponding partition of the target disaster recovery database;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
14. A non-transitory computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of a mobile terminal, enable the mobile terminal to perform a data storage method applied to a server of any one of a first server cluster or a second server cluster, the first server cluster and the second server cluster being respectively located in different rooms, the method comprising:
when the server stores the service data in the storage database of the first server cluster, backing up the service data to a storage database of a second server cluster, wherein the storage database of the second server cluster is used for backing up the service data in the storage database of the first server cluster;
when the server does not back up the service data to the storage database of the second server cluster, determining a corresponding partition of the data identifier in a plurality of partitions of a target disaster recovery database according to a characteristic value of the data identifier of the service data, wherein the characteristic value of the data identifier is a hash value of the data identifier, each partition is used for storing one or more data identifiers with the same hash value, and the target disaster recovery database is a disaster recovery database of the server cluster where the server is located; storing the data identification into a corresponding partition of the target disaster recovery database;
and storing the service data in the storage database of the first server cluster into the storage database of the second server cluster according to the data identifier in the corresponding partition of the target disaster recovery database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811519676.6A CN109561151B (en) | 2018-12-12 | 2018-12-12 | Data storage method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811519676.6A CN109561151B (en) | 2018-12-12 | 2018-12-12 | Data storage method, device, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109561151A CN109561151A (en) | 2019-04-02 |
| CN109561151B true CN109561151B (en) | 2021-09-17 |
Family
ID=65869646
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811519676.6A Active CN109561151B (en) | 2018-12-12 | 2018-12-12 | Data storage method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109561151B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111381987A (en) * | 2020-03-13 | 2020-07-07 | 北京金山云网络技术有限公司 | Message processing method and device, electronic equipment and medium |
| CN113297159B (en) * | 2021-02-08 | 2024-03-08 | 阿里巴巴集团控股有限公司 | Data storage method and device |
| CN113810456A (en) * | 2021-02-09 | 2021-12-17 | 京东科技信息技术有限公司 | Data acquisition method, device, system, computer equipment and storage medium |
| CN113064766A (en) * | 2021-05-07 | 2021-07-02 | 数字广东网络建设有限公司 | Data backup method, device, equipment and storage medium |
| CN113726877A (en) * | 2021-08-26 | 2021-11-30 | 湖南快乐阳光互动娱乐传媒有限公司 | Method and system for storing data across machine room cluster |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103064760A (en) * | 2012-12-19 | 2013-04-24 | 华为技术有限公司 | Backup method and backup device |
| CN103516667A (en) * | 2012-06-20 | 2014-01-15 | 中国银联股份有限公司 | System, method and apparatus used for safety information data disaster recovery backup |
| CN103973727A (en) * | 2013-01-28 | 2014-08-06 | 深圳市腾讯计算机系统有限公司 | Data synchronizing method and device |
| CN104468548A (en) * | 2014-11-28 | 2015-03-25 | 华为技术有限公司 | Data verification method, disaster recovery storage and production storage |
| CN104503864A (en) * | 2014-11-20 | 2015-04-08 | 北京世纪高蓝科技有限公司 | Method and device for file backup based on local area network |
| CN104618127A (en) * | 2013-11-01 | 2015-05-13 | 深圳市腾讯计算机系统有限公司 | Master and standby storage node switching method and system |
| CN105224418A (en) * | 2015-09-06 | 2016-01-06 | 福建三元达通讯股份有限公司 | A kind of data back up method and device |
| CN105282253A (en) * | 2015-11-04 | 2016-01-27 | 湖南御家科技有限公司 | Data document synchronization method and system |
| CN105302675A (en) * | 2015-11-25 | 2016-02-03 | 上海爱数信息技术股份有限公司 | Method and device for data backup |
| CN107346271A (en) * | 2016-05-05 | 2017-11-14 | 华为技术有限公司 | The method and calamity of Backup Data block are for end equipment |
| CN108228397A (en) * | 2016-12-22 | 2018-06-29 | 深圳市优朋普乐传媒发展有限公司 | The method and apparatus that a kind of cluster span computer room synchronizes |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030005350A1 (en) * | 2001-06-29 | 2003-01-02 | Maarten Koning | Failover management system |
| US7441092B2 (en) * | 2006-04-20 | 2008-10-21 | Microsoft Corporation | Multi-client cluster-based backup and restore |
| CN101309167B (en) * | 2008-06-27 | 2011-04-20 | 华中科技大学 | Disaster allowable system and method based on cluster backup |
| CN103902617B (en) * | 2012-12-28 | 2017-06-09 | 华为技术有限公司 | Distributed data base synchronous method and system |
| CN105187464B (en) * | 2014-06-19 | 2019-11-05 | 南京中兴软件有限责任公司 | Method of data synchronization, apparatus and system in a kind of distributed memory system |
| CN104935654B (en) * | 2015-06-10 | 2018-08-21 | 华为技术有限公司 | Caching method, write-in point client in a kind of server cluster system and read client |
| CN106341454B (en) * | 2016-08-23 | 2019-09-24 | 世纪龙信息网络有限责任公司 | Across computer room distributed data base management system (DDBMS) mostly living and method |
| CN106487936A (en) * | 2016-12-29 | 2017-03-08 | 深圳市优必选科技有限公司 | Data transmission method and equipment, distributed memory system |
| CN108259613B (en) * | 2018-01-24 | 2019-12-24 | 平安科技（深圳）有限公司 | Disaster recovery data online synchronization device, method and computer readable storage medium |
-
2018
- 2018-12-12 CN CN201811519676.6A patent/CN109561151B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103516667A (en) * | 2012-06-20 | 2014-01-15 | 中国银联股份有限公司 | System, method and apparatus used for safety information data disaster recovery backup |
| CN103064760A (en) * | 2012-12-19 | 2013-04-24 | 华为技术有限公司 | Backup method and backup device |
| CN103973727A (en) * | 2013-01-28 | 2014-08-06 | 深圳市腾讯计算机系统有限公司 | Data synchronizing method and device |
| CN104618127A (en) * | 2013-11-01 | 2015-05-13 | 深圳市腾讯计算机系统有限公司 | Master and standby storage node switching method and system |
| CN104503864A (en) * | 2014-11-20 | 2015-04-08 | 北京世纪高蓝科技有限公司 | Method and device for file backup based on local area network |
| CN104468548A (en) * | 2014-11-28 | 2015-03-25 | 华为技术有限公司 | Data verification method, disaster recovery storage and production storage |
| CN105224418A (en) * | 2015-09-06 | 2016-01-06 | 福建三元达通讯股份有限公司 | A kind of data back up method and device |
| CN105282253A (en) * | 2015-11-04 | 2016-01-27 | 湖南御家科技有限公司 | Data document synchronization method and system |
| CN105302675A (en) * | 2015-11-25 | 2016-02-03 | 上海爱数信息技术股份有限公司 | Method and device for data backup |
| CN107346271A (en) * | 2016-05-05 | 2017-11-14 | 华为技术有限公司 | The method and calamity of Backup Data block are for end equipment |
| CN108228397A (en) * | 2016-12-22 | 2018-06-29 | 深圳市优朋普乐传媒发展有限公司 | The method and apparatus that a kind of cluster span computer room synchronizes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109561151A (en) | 2019-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109561151B (en) | Data storage method, device, server and storage medium | |
| CN111078147B (en) | Processing method, device and equipment for cache data and storage medium | |
| US9367598B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| CN110247984B (en) | Service processing method, device and storage medium | |
| CN107402722B (en) | Data migration method and storage device | |
| WO2017143905A1 (en) | Online upgrade method, device and system | |
| JP5686034B2 (en) | Cluster system, synchronization control method, server device, and synchronization control program | |
| CN112636992B (en) | Dynamic routing method, device, equipment and storage medium | |
| CN111399764B (en) | Data storage method, data reading device, data storage equipment and data storage medium | |
| CN107817950B (en) | Data processing method and device | |
| CN113094430B (en) | Data processing method, device, equipment and storage medium | |
| CN107025257B (en) | Transaction processing method and device | |
| CN111338834B (en) | Data storage method and device | |
| CN110532123B (en) | Fault transfer method and device of HBase system | |
| CN109726211B (en) | Distributed time sequence database | |
| CN113064919B (en) | Data processing method, data storage system, computer device and storage medium | |
| CN113467719A (en) | Data writing method and device | |
| CN105511808B (en) | Data operation method, system and related device | |
| CN112000850A (en) | Method, device, system and equipment for data processing | |
| CN109992447B (en) | Data copying method, device and storage medium | |
| CN114500289B (en) | Control plane recovery method, device, control node and storage medium | |
| JP2012053795A (en) | Information processing system | |
| CN115292408A (en) | Master-slave synchronization method, device, equipment and medium for MySQL database | |
| CN113806309A (en) | Metadata deleting method, system, terminal and storage medium based on distributed lock | |
| US8429136B2 (en) | Information processing method and information processing apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |