CN112000515A - Method and assembly for recovering instance data in redis cluster - Google Patents
Method and assembly for recovering instance data in redis cluster Download PDFInfo
- Publication number
- CN112000515A CN112000515A CN202010790534.4A CN202010790534A CN112000515A CN 112000515 A CN112000515 A CN 112000515A CN 202010790534 A CN202010790534 A CN 202010790534A CN 112000515 A CN112000515 A CN 112000515A
- Authority
- CN
- China
- Prior art keywords
- redis cluster
- instance
- cluster
- target file
- redis
- 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.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/161—Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a method and a component for recovering instance data in a redis cluster. The method disclosed by the application comprises the following steps: if an instance data backup instruction is received, obtaining instance data corresponding to all instances in a first redis cluster before recovery; merging all the acquired example data, and converting the merged file into a target file with a preset format; and if the recovery instruction is received, after the target file is verified to pass, deploying the target file to the recovered first redis cluster and/or second redis cluster with any instance structure. According to the method and the device, the instance data in one redis cluster can be restored to the redis cluster with any instance structure, so that the limitation of the existing instance data restoration mode is broken, and a universal instance data restoration method is provided. Correspondingly, the instance data recovery component in the redis cluster also has the technical effect.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an assembly for restoring instance data in a redis cluster.
Background
Currently, a redis cluster stores all instance data therein in a cluster disk, so as to avoid instance data loss when the redis cluster fails or is abnormal. In the recovery process of the redis cluster, all the instance data in the redis cluster before the fault is loaded from the cluster disk, and then the instance data is deployed to the cluster node according to the instance structure of the redis cluster before the fault. At this time, it is required to ensure that the instance structures of the redis cluster recovered at the current time and the redis cluster before the failure are completely the same, otherwise, the loading will fail. Therefore, the existing instance data recovery mode has certain limitation, and only the instance data in one redis cluster can be recovered to the redis cluster with the same instance structure.
Therefore, how to provide a general instance data recovery method to break the limitation of instance data recovery in a redis cluster is a problem to be solved by those skilled in the art.
Disclosure of Invention
In view of this, an object of the present application is to provide an example data recovery method and component in a redis cluster, so as to break through the limitation of example data recovery in the redis cluster, and provide a general example data recovery method. The specific scheme is as follows:
in a first aspect, the present application provides a method for recovering instance data in a redis cluster, including:
if an instance data backup instruction is received, obtaining instance data corresponding to all instances in a first redis cluster before recovery;
merging all the acquired example data, and converting the merged file into a target file with a preset format;
if a recovery instruction is received, after the target file is verified to pass, deploying the target file to the recovered first redis cluster and/or second redis cluster;
wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
Preferably, the obtaining of the instance data corresponding to all instances in the first redis cluster before restoration includes:
loading the instance data corresponding to all instances in the first redis cluster before recovery to a buffer of the first redis cluster, so as to read all the instance data in the first redis cluster from the buffer.
Preferably, the converting the merged file into a target file in a preset format includes:
and converting the file obtained by merging into a target file in a JSON format.
Preferably, verifying the target file comprises:
judging whether each K value in the target file records a corresponding value or not;
if yes, the target file is verified to pass;
if not, verifying that the target file does not pass.
Preferably, the method further comprises the following steps:
and if the target file is not verified, generating and displaying a prompt message that the target file is not verified.
Preferably, the deploying the target file to the restored first redis cluster and/or second redis cluster includes:
acquiring instance interfaces of all instances in the recovered first redis cluster and/or the second redis cluster;
and deploying the target file to the recovered first redis cluster and/or the second redis cluster through the instance interface.
Preferably, the obtaining the instance interfaces of all instances in the recovered first redis cluster and/or the second redis cluster includes:
acquiring first cluster information of the first redis cluster and/or second cluster information of the second redis cluster after recovery;
and acquiring the recovered instance interfaces of all instances in the first redis cluster and/or the second redis cluster according to the first cluster information and/or the second cluster information.
In a second aspect, the present application provides an apparatus for restoring instance data in a redis cluster, including:
the obtaining module is used for obtaining the example data corresponding to all the examples in the first redis cluster before recovery if the example data backup instruction is received;
the analysis module is used for combining all the acquired example data and converting the combined file into a target file with a preset format;
the deployment module is used for deploying the target file to the recovered first redis cluster and/or second redis cluster after the target file is verified to pass if the recovery instruction is received;
wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
In a third aspect, the present application provides an instance data recovery device in a redis cluster, including:
a memory for storing a computer program;
a processor for executing the computer program to implement the example data recovery method in the redis cluster disclosed above.
In a fourth aspect, the present application provides a readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the example data recovery method in a redis cluster as disclosed in the foregoing.
By the above scheme, the present application provides an example data recovery method in a redis cluster, including: if an instance data backup instruction is received, obtaining instance data corresponding to all instances in a first redis cluster before recovery; merging all the acquired example data, and converting the merged file into a target file with a preset format; if a recovery instruction is received, after the target file is verified to pass, deploying the target file to the recovered first redis cluster and/or second redis cluster; wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
As can be seen, after receiving an instance data backup instruction, the method and the device for recovering instance data obtain the instance data corresponding to all instances in the first redis cluster before recovery, then merge all the obtained instance data, and convert the file obtained by the merging into a target file in a preset format; if the recovery instruction is received, after the target file is verified to pass, deploying the target file to the recovered first redis cluster and/or second redis cluster, and thus recovering all the instance data in the first redis cluster to the recovered first redis cluster and/or second redis cluster with any instance structure. After all the instance data are merged and recovered, the data can be distributed to any instance according to a brand-new rule without paying attention to the original instance structure, so that the situation of instance loading failure can be avoided. Moreover, it is generally difficult to ensure that the instance structures of the redis clusters before and after recovery are completely the same, so the conventional recovery method is difficult to implement. According to the method and the device, the instance structure of the redis cluster where the instance data are currently deployed and the instance structure of the redis cluster where the instance data are originally stored do not need to be concerned, the instance data in one redis cluster can be restored to the redis cluster of any instance structure, so that the limitation of the existing instance data restoration mode is broken, and a universal instance data restoration method is provided.
Accordingly, the example data recovery component (i.e., the apparatus, the device, and the readable storage medium) in the redis cluster provided by the present application also has the above technical effects.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flowchart of an example data recovery method in a redis cluster as disclosed herein;
FIG. 2 is a schematic diagram of an example data recovery system in a redis cluster as disclosed herein;
FIG. 3 is a schematic illustration of an example data merge disclosed herein;
FIG. 4 is a schematic diagram of an example data recovery disclosed herein;
FIG. 5 is a schematic diagram of an example data recovery apparatus in a redis cluster disclosed in the present application;
fig. 6 is a schematic diagram of an example data recovery device in a redis cluster disclosed in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
At present, an existing instance data recovery method has certain limitations, and the instance data in one redis cluster cannot be recovered to other redis clusters different from the instance structure of the instance data. Therefore, the application provides an instance data recovery scheme in the redis cluster, which can break through the limitation of the instance data recovery in the existing redis cluster and provide a universal instance data recovery method.
Referring to fig. 1, an embodiment of the present application discloses an example data recovery method in a redis cluster, including:
s101, if an instance data backup instruction is received, obtaining instance data corresponding to all instances in the first redis cluster before restoration.
It should be noted that the redis cluster can solve the requirement of the redis distribution aspect. When bottleneck problems such as single-machine memory, concurrency, flow and the like are met, the Redis cluster can play a good load balancing role. At least 6 nodes (such as three main nodes and three auxiliary nodes) are configured in the Redis cluster, the main node provides read-write operation, and the auxiliary nodes serve as standby nodes to be used as fault transfer. The instance data backup instructions may be autonomously input by a user or autonomously generated by the first redis cluster upon shutdown or failure.
In a specific embodiment, acquiring instance data corresponding to all instances in the first redis cluster before recovery includes: and loading the instance data corresponding to all the instances in the first redis cluster before recovery to a buffer of the first redis cluster, so as to read all the instance data in the first redis cluster from the buffer.
The redis cluster flushes the instance data from the buffer to the cluster disk according to a predetermined policy, and loads all the instance data in the cluster disk to the buffer for reading in order to facilitate backup of the instance data.
And S102, merging all the acquired example data, and converting the merged file into a target file in a preset format.
In a specific embodiment, converting the merged file into a target file in a preset format includes: and converting the file obtained by merging into a target file in a JSON format. Json (javascript object notification) is a lightweight data exchange format, is easy for human reading and writing, is also easy for machine parsing and generation, and can effectively improve network transmission efficiency. The preset format may also be XML or other format.
The data included in the merged file may not be uniform in format, so that the merged file is converted into a target file in a JSON format, and the formats of the data therein can be uniform for subsequent processing and reading.
It should be noted that before the first redis cluster is recovered, that is, before the first redis cluster is closed or failed, all instance data therein is acquired and merged into a target file with a preset format, which may provide help for the processes of recovery, cluster migration, cluster replication, and the like of the first redis cluster.
S103, if the recovery instruction is received, after the target file is verified to pass, the target file is deployed to the recovered first redis cluster and/or second redis cluster.
Wherein. The second redis cluster and the restored first redis cluster have arbitrary instance structures.
In one embodiment, verifying the target file includes: judging whether each K value in the target file records a corresponding value or not; if yes, checking that the target file passes; if not, the target file is verified to be not passed. Since the instance data is recorded in the K-value key value pair, it is determined whether each K value in the target file has a corresponding value recorded therein, and it is possible to check whether there is data modification or omission.
If the verification target file is not passed, a prompt message that the verification of the target file is not passed is generated and displayed, so that a technician can check and modify the target file, or input an instance data backup instruction to re-execute S101-S102 to obtain a new target file.
In a specific embodiment, deploying the target file to the restored first redis cluster and/or second redis cluster includes: acquiring instance interfaces of all instances in the recovered first redis cluster and/or second redis cluster; and deploying the target file to the recovered first redis cluster and/or second redis cluster through the instance interface.
Obtaining instance interfaces of all instances in the recovered first redis cluster and/or second redis cluster includes: acquiring first cluster information of a first redis cluster and/or second cluster information of a second redis cluster after recovery; and acquiring the instance interfaces of all instances in the recovered first redis cluster and/or second redis cluster according to the first cluster information and/or second cluster information.
According to the method and the device, attention does not need to be paid to the instance structure of the redis cluster where the instance data are currently deployed and the instance structure of the redis cluster where the instance data are originally stored, so that the instance structure of the second redis cluster and the instance structure of the first redis cluster before recovery can be the same or different; the instance structure of the recovered first redis cluster may be the same as or different from the instance structure of the first redis cluster before recovery.
It should be noted that, recovering the redis cluster may be performed by performing data recovery on the original redis cluster, by newly building a redis cluster to perform data recovery, or by performing data recovery in the above two manners. Therefore, all the instance data in the original redis cluster (e.g., the first redis cluster) can be deployed to the restored original redis cluster (i.e., the first redis cluster) and/or other redis clusters (i.e., the second redis cluster), thereby completing restoring the redis cluster.
Therefore, after all the instance data are merged and recovered, the data can be distributed to any instance according to the cluster rule without paying attention to the original instance structure, and therefore the situation of instance loading failure can be avoided. According to the method and the device, the instance structure of the redis cluster where the instance data are currently deployed and the instance structure of the redis cluster where the instance data are originally stored do not need to be concerned, the instance data in one redis cluster can be restored to the redis cluster of any instance structure, so that the limitation of the existing instance data restoration mode is broken, and a universal instance data restoration method is provided.
Referring to fig. 2, an embodiment of the present application discloses an example data recovery system in a redis cluster, where the system includes: the device comprises a data loading module, a data merging module, a data analyzing module, a cluster information loading module and a data recovery module.
When the backup service is started, corresponding data files of each instance are loaded according to a timing strategy and a backup strategy set by a user, then the data merging module is started, the loaded data files are merged, the backup data files are analyzed after merging, the backup files are analyzed and reconstructed into a file format which can be used for recovery in a heterogeneous cluster, during the data recovery process, the backup files are firstly verified and pass the verification, the data entering a redis cluster information loading module is used for loading new redis cluster information, and then the data are recovered into a new redis cluster by using the backup files. The new redis cluster may be a reconstructed redis cluster or a new redis cluster in which the original redis cluster is recovered from a failure.
The method comprises the following specific steps:
step 1, when a data backup task is started, a cluster driver is called to start a data loading module, so that data corresponding to each instance in a redis cluster are loaded by the data loading module, and then the data enters a data merging module;
step 2, the data merging module merges the data obtained in the step 1 to generate a backup file; the merging process may refer to fig. 3, where each "Redis cluster instance" in fig. 3 represents each instance in the original Redis cluster;
step 3, the data analysis module analyzes the backup file to obtain a file with a specific format;
step 4, if data recovery is needed, firstly checking the file, and then recovering the data after the file passes the check;
step 5, loading information of the new redis cluster, acquiring interfaces of all instances, and then entering a data recovery module; the information of the cluster generally includes: IP and port information of the redis cluster instance, etc. A redis cluster typically includes a plurality of nodes, each of which may have at least one instance thereon.
And 6, restoring the data to the designated redis cluster by the data restoring module, wherein the cluster can be heterogeneous with the original redis cluster.
Wherein, the steps 4-6 can be seen in fig. 4. In fig. 4, the data verifying device is configured to verify integrity of the file, the cluster information obtaining device is configured to obtain information of the new redis cluster, and the data restoring device is configured to deploy all data in the file to the new redis cluster.
Therefore, the data can be combined into a file with a specific format in a centralized manner, and the data can be recovered in the heterogeneous redis cluster by using the jie of me, so that the problem that the data cannot be recovered in the heterogeneous redis cluster due to the fact that the persistent data of the redis cluster are distributed on the machines where the instances are located is solved.
In the following, an example data recovery device in a redis cluster provided in an embodiment of the present application is introduced, and an example data recovery device in a redis cluster described below and an example data recovery method in a redis cluster described above may be referred to each other.
Referring to fig. 5, an embodiment of the present application discloses an example data recovery device in a redis cluster, including:
an obtaining module 501, configured to obtain, if an instance data backup instruction is received, instance data corresponding to all instances in a first redis cluster before recovery;
the parsing module 502 is configured to merge all the obtained instance data, and convert a file obtained by the merging into a target file in a preset format;
the deployment module 503 is configured to, if the recovery instruction is received, deploy the target file to the recovered first redis cluster and/or second redis cluster after the target file is verified to pass;
wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
In a specific embodiment, the obtaining module is specifically configured to:
and loading the instance data corresponding to all the instances in the first redis cluster before recovery to a buffer of the first redis cluster, so as to read all the instance data in the first redis cluster from the buffer.
In a specific embodiment, the parsing module is specifically configured to:
and converting the file obtained by merging into a target file in a JSON format.
In a specific embodiment, the deployment module includes a verification unit for verifying the target file, where the verification unit is specifically configured to:
judging whether each K value in the target file records a corresponding value or not; if yes, checking that the target file passes; if not, the target file is verified to be not passed.
In one embodiment, the verification unit is further configured to:
and if the verification target file is not passed, generating and displaying a prompt message that the verification of the target file is not passed.
In one embodiment, the deployment module comprises:
the acquisition unit is used for acquiring the instance interfaces of all instances in the recovered first redis cluster and/or second redis cluster;
and the deployment unit is used for deploying the target file to the recovered first redis cluster and/or second redis cluster through the instance interface.
In a specific embodiment, the instance structure of the second redis cluster may be different from the instance structure of the first redis cluster before restoration; the instance structure of the first redis cluster after restoration may be different from the instance structure of the first redis cluster before restoration.
For more specific working processes of each module and unit in this embodiment, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described here again.
It can be seen that this embodiment provides an apparatus for recovering instance data in a redis cluster, where the apparatus does not need to pay attention to the instance structure of the redis cluster where the instance data is currently deployed and the instance structure of the redis cluster where the instance data is originally stored, and can recover the instance data in a certain redis cluster to a redis cluster with any instance structure, thereby breaking the limitation of the existing instance data recovery method and providing a general instance data recovery method.
In the following, description is given of an example data recovery device in a redis cluster provided in an embodiment of the present application, and an example data recovery device in a redis cluster described below and an example data recovery method and apparatus in a redis cluster described above may refer to each other.
Referring to fig. 6, an embodiment of the present application discloses an example data recovery device in a redis cluster, including:
a memory 601 for storing a computer program;
a processor 602 for executing the computer program to implement the method disclosed in any of the embodiments above.
In the following, a readable storage medium provided by an embodiment of the present application is introduced, and a readable storage medium described below and an example data recovery method, apparatus, and device in a redis cluster described above may be mutually referred to.
A readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the example data recovery method in a redis cluster disclosed in the previous embodiments. For the specific steps of the method, reference may be made to the corresponding contents disclosed in the foregoing embodiments, which are not described herein again.
References in this application to "first," "second," "third," "fourth," etc., if any, are intended to distinguish between similar elements and not necessarily to describe a particular order or sequence. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises" and "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, or apparatus.
It should be noted that the descriptions in this application referring to "first", "second", etc. are for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present application.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of readable storage medium known in the art.
The principle and the implementation of the present application are explained herein by applying specific examples, and the above description of the embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. An example data recovery method in a redis cluster, comprising:
if an instance data backup instruction is received, obtaining instance data corresponding to all instances in a first redis cluster before recovery;
merging all the acquired example data, and converting the merged file into a target file with a preset format;
if a recovery instruction is received, after the target file is verified to pass, deploying the target file to the recovered first redis cluster and/or second redis cluster;
wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
2. The method according to claim 1, wherein the obtaining of the instance data corresponding to all instances in the first redis cluster before restoration comprises:
loading the instance data corresponding to all instances in the first redis cluster before recovery to a buffer of the first redis cluster, so as to read all the instance data in the first redis cluster from the buffer.
3. The method for recovering instance data in a redis cluster according to claim 1, wherein the converting the merged file into a target file in a preset format comprises:
and converting the file obtained by merging into a target file in a JSON format.
4. The method of instance data recovery in a redis cluster of claim 1, wherein verifying the target file comprises:
judging whether each K value in the target file records a corresponding value or not;
if yes, the target file is verified to pass;
if not, verifying that the target file does not pass.
5. The method of instance data recovery in a redis cluster of claim 4, further comprising:
and if the target file is not verified, generating and displaying a prompt message that the target file is not verified.
6. The method for instance data recovery in a redis cluster according to claim 1, wherein the deploying the target file to the first and/or second redis cluster after recovery comprises:
acquiring instance interfaces of all instances in the recovered first redis cluster and/or the second redis cluster;
and deploying the target file to the recovered first redis cluster and/or the second redis cluster through the instance interface.
7. The method for recovering instance data in a redis cluster according to claim 6, wherein the obtaining the recovered instance interfaces of all instances in the first redis cluster and/or the second redis cluster comprises:
acquiring first cluster information of the first redis cluster and/or second cluster information of the second redis cluster after recovery;
and acquiring the recovered instance interfaces of all instances in the first redis cluster and/or the second redis cluster according to the first cluster information and/or the second cluster information.
8. An apparatus for instance data recovery in a redis cluster, comprising:
the obtaining module is used for obtaining the example data corresponding to all the examples in the first redis cluster before recovery if the example data backup instruction is received;
the analysis module is used for combining all the acquired example data and converting the combined file into a target file with a preset format;
the deployment module is used for deploying the target file to the recovered first redis cluster and/or second redis cluster after the target file is verified to pass if the recovery instruction is received;
wherein the second redis cluster and the recovered first redis cluster have arbitrary instance structures.
9. An instance data recovery device in a redis cluster, comprising:
a memory for storing a computer program;
a processor for executing the computer program for implementing the method of instance data recovery in a redis cluster according to any of claims 1 to 7.
10. A readable storage medium for holding a computer program, wherein the computer program, when executed by a processor, implements an instance data recovery method in a redis cluster as claimed in any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010790534.4A CN112000515A (en) | 2020-08-07 | 2020-08-07 | Method and assembly for recovering instance data in redis cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010790534.4A CN112000515A (en) | 2020-08-07 | 2020-08-07 | Method and assembly for recovering instance data in redis cluster |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112000515A true CN112000515A (en) | 2020-11-27 |
Family
ID=73463877
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010790534.4A Withdrawn CN112000515A (en) | 2020-08-07 | 2020-08-07 | Method and assembly for recovering instance data in redis cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112000515A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120150815A1 (en) * | 2010-12-09 | 2012-06-14 | Ibm Corporation | Efficient backup and restore of virtual input/output server (vios) cluster |
| CN105610987A (en) * | 2016-03-18 | 2016-05-25 | 车智互联（北京）科技有限公司 | Method, application and system for managing server cluster |
| US20160378622A1 (en) * | 2015-06-29 | 2016-12-29 | Vmware, Inc. | Virtual Machine Recovery On Non-Shared Storage in a Single Virtual Infrastructure Management Instance |
| CN109862075A (en) * | 2018-12-29 | 2019-06-07 | 北京奥鹏远程教育中心有限公司 | A kind of method for routing of Redis Service Instance |
| CN110333986A (en) * | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | A method of ensureing redis cluster availability |
| CN110795257A (en) * | 2019-09-19 | 2020-02-14 | 平安科技（深圳）有限公司 | Method, device and equipment for processing multi-cluster operation records and storage medium |
| CN110825495A (en) * | 2019-11-08 | 2020-02-21 | 北京浪潮数据技术有限公司 | Container cloud platform recovery method, device, equipment and readable storage medium |
| CN111090543A (en) * | 2018-10-23 | 2020-05-01 | 广东亿迅科技有限公司 | Backup recovery method of Zookeeper, terminal and computer readable storage medium |
-
2020
- 2020-08-07 CN CN202010790534.4A patent/CN112000515A/en not_active Withdrawn
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120150815A1 (en) * | 2010-12-09 | 2012-06-14 | Ibm Corporation | Efficient backup and restore of virtual input/output server (vios) cluster |
| US20160378622A1 (en) * | 2015-06-29 | 2016-12-29 | Vmware, Inc. | Virtual Machine Recovery On Non-Shared Storage in a Single Virtual Infrastructure Management Instance |
| CN105610987A (en) * | 2016-03-18 | 2016-05-25 | 车智互联（北京）科技有限公司 | Method, application and system for managing server cluster |
| CN111090543A (en) * | 2018-10-23 | 2020-05-01 | 广东亿迅科技有限公司 | Backup recovery method of Zookeeper, terminal and computer readable storage medium |
| CN109862075A (en) * | 2018-12-29 | 2019-06-07 | 北京奥鹏远程教育中心有限公司 | A kind of method for routing of Redis Service Instance |
| CN110333986A (en) * | 2019-06-19 | 2019-10-15 | 上海二三四五网络科技有限公司 | A method of ensureing redis cluster availability |
| CN110795257A (en) * | 2019-09-19 | 2020-02-14 | 平安科技（深圳）有限公司 | Method, device and equipment for processing multi-cluster operation records and storage medium |
| CN110825495A (en) * | 2019-11-08 | 2020-02-21 | 北京浪潮数据技术有限公司 | Container cloud platform recovery method, device, equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 艾锟等: "集群环境下数据库的数据安全保护", 《电力信息化》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Hamilton | On Designing and Deploying Internet-Scale Services. | |
| CN106951559B (en) | Data recovery method in distributed file system and electronic equipment | |
| CN108710673B (en) | Method, system, computer device and storage medium for realizing high availability of database | |
| US20070220370A1 (en) | Mechanism to generate functional test cases for service oriented architecture (SOA) applications from errors encountered in development and runtime | |
| CN107241315B (en) | Access method and device of bank gateway interface and computer readable storage medium | |
| CN110909394A (en) | Configuration file monitoring method of server | |
| CN112214357B (en) | HDFS data backup and recovery system and backup and recovery method | |
| CN110659159A (en) | Service process operation monitoring method, device, equipment and storage medium | |
| CN111309524A (en) | Distributed storage system fault recovery method, device, terminal and storage medium | |
| CN107943617B (en) | Data restoration method and device and server cluster | |
| US20120166893A1 (en) | Recording and Preventing Crash in an Appliance | |
| CN110659083A (en) | Method and system for recovering memory data after program fault restart | |
| CN112000515A (en) | Method and assembly for recovering instance data in redis cluster | |
| CN116561743A (en) | Business process management method and device, storage medium and electronic equipment | |
| CN114138566B (en) | Data storage method and device of virtual machine, virtual machine and storage medium | |
| CN115168236A (en) | Automatic testing method, electronic device and storage medium | |
| CN115168103A (en) | Application copying method, device, equipment and readable storage medium | |
| CN111427718B (en) | File backup method, file recovery method and file recovery device | |
| JP2009266031A (en) | Computer system and computer | |
| CN110677469B (en) | Security disaster recovery system and disaster recovery implementation method | |
| CN110955443A (en) | Method, device, equipment and medium for updating cluster crontab in batch | |
| CN112269693A (en) | Node self-coordination method, device and computer readable storage medium | |
| JP2008112229A (en) | Update data application method for software product | |
| CN114356643B (en) | Automatic task discovery failure and recovery method in remote sensing satellite processing system | |
| CN113076228B (en) | Distributed system and management method and device thereof |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20201127 |