CN109508261B - Power grid data node backup method and system based on big data - Google Patents
Power grid data node backup method and system based on big data Download PDFInfo
- Publication number
- CN109508261B CN109508261B CN201811010693.7A CN201811010693A CN109508261B CN 109508261 B CN109508261 B CN 109508261B CN 201811010693 A CN201811010693 A CN 201811010693A CN 109508261 B CN109508261 B CN 109508261B
- Authority
- CN
- China
- Prior art keywords
- backup
- server
- backup server
- work
- normal
- 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
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000008569 process Effects 0.000 claims description 12
- 238000010586 diagram Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/008—Reliability or availability analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention relates to a power grid data node backup method and a system based on big data, wherein the system comprises a main server group and a backup server group, the main server group comprises N main servers which are not connected with each other and used for storing data and receiving read-write access operation of a client, the backup server group comprises N backup servers which are connected into an annular network and used for backing up the data of the corresponding main server and providing service for the client when the main server fails. The storage space of each backup server in the backup server group is divided into two parts, wherein the first part is used for carrying out hot backup on the corresponding main server, and the second part is an available storage part which can provide the storage space for the client to carry out data writing operation when the adjacent backup server cannot work.
Description
Technical Field
The invention relates to the technical field of server backup, in particular to a power grid data node backup method and a backup system based on big data.
Background
With the development of power services, the scale of power consumers is rapidly expanded, and a power grid system needs to use a large number of data nodes to store corresponding data for the client to perform operations such as read-write query and the like. In order to ensure the normal operation of the data node, the data node is generally backed up. In the prior art, a mode often adopted is dual-computer hot backup, that is, a main server and a backup server are directly connected and backup in real time, once the main server fails, the main server is immediately switched to the backup server, the backup server takes over the main server to provide corresponding services, meanwhile, operations such as repair, restart and the like are performed on the main server, and after the main server normally operates, the main server can be restored to a dual-computer hot backup mode.
However, in the current power communication network system, the main server and the backup server are most likely to have the same physical location of the machine room, for example, located in the same machine room, or located in different machine rooms in the same county and city, so when an undesirable condition occurs in the machine room environment, there is a possibility that the main server and the backup server fail simultaneously, which brings a significant impact on the continuity of network communication. Moreover, the primary server may fail due to sudden large data accesses, in which case the backup server may also fail in a short time to provide service to the client. In the prior art, for example, in patent ZL201710388516.1 issued to the present invention in china, an authentication server annular escape system and method are provided, which implement authentication and escape functions by providing three servers, and the number of servers used is large, and the cost is high.
Therefore, how to improve the current backup method to enable the grid data node to better cope with the occurrence of the extreme condition is a technical problem that needs to be solved by those skilled in the art at present.
Disclosure of Invention
In order to solve the above problems, the present invention provides a big data based grid data node backup system, which is characterized in that the system includes a main server group S ═ S1,S2……SNT and backup server set T ═ T1，T2……TNWherein the main server group S includes N (N is a natural number, N)>2) main servers S not connected to each other1,S2……SNThe backup server group T comprises N backup servers connected to a ring network, wherein Tiis corresponding to the main server SiI is a natural number between 1 and N; each backup server T in the backup server group TiIs divided into two parts L0And L1(ii) a Each backup server TiA status list is maintained in which the information of each backup server is kept.
The invention also provides a power grid data node backup system based on big data, which is characterized by comprising a main server group S ═ { S ═ S }1,S2……SNT and backup server set T ═ T1，T2……TNWherein the main server group S includes N (N is a natural number, N)>2) main servers S not connected to each other1,S2……SNThe backup server group T comprises N backup servers connected as a star network, wherein Tiis corresponding to the main server SiI is a natural number between 1 and N; each backup server T in the backup server group TiIs divided into two parts L0And L1(ii) a At the center of the star network is a network controller that is connected to each backup server, and the network controller maintains a status list in which the information of each backup server is kept.
The invention also provides a corresponding big data-based power grid data node backup method, wherein according to the first aspect of the invention, the method comprises the step S100 of judging the main server SiWhether the work is normal or not, if the work is normal, the process is ended; if the normal work can not be carried out, the main server S is switched toiCorresponding backup server TiFrom TiServing the client;
Step S200, judging a backup server TiWhether the work is normal or not, if the work is normal, the process is ended; if the system can not work normally, the backup server T adjacent to the system is determined according to the information in the state listi+1And/or Ti-1Serving the client;
Wherein each backup server updates the information in the status list in real time through the ring network.
Step S300, detecting the backup server T in real timei+1And/or Ti-1Whether the work is normal or not, if the work is normal, the process is ended; if at least one of the two can not work normally, the step S200 is executed repeatedly.
In step S400, when the primary server returns to normal, each backup server writes data back to the primary server.
According to a second aspect of the invention, the method comprises, step S100, determining a host server SiWhether the work is normal or not, if the work is normal, the process is ended; if the normal work can not be carried out, the main server S is switched toiCorresponding backup server TiFrom TiServing the client;
Step S200, judging a backup server TiWhether the work is normal or not, if the work is normal, the process is ended; if the client side can not work normally, under the control of the network controller, determining that other available backup servers provide services for the client side according to the information in the state list;
And the network controller updates the information in the state list in real time through the star network.
Step S300, detecting whether the backup server in use works normally in real time, and if the backup server works normally, ending the process; if at least one of them can not work normally, the step S200 is executed repeatedly.
In step S400, when the primary server returns to normal, each backup server writes data back to the primary server.
The grid data node backup method and system based on big data can more effectively cope with extreme conditions in the network on the premise of not increasing the number of backup servers and provide a more reliable backup scheme.
Drawings
Fig. 1 is a schematic block diagram of a big data based grid data node backup system according to a first aspect of the present invention;
Fig. 2 is a schematic block diagram of a big data based grid data node backup system according to a second aspect of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings. This description is made by way of example and not limitation to specific embodiments consistent with the principles of the invention, the description being in sufficient detail to enable those skilled in the art to practice the invention, other embodiments may be utilized and the structure of various elements may be changed and/or substituted without departing from the scope and spirit of the invention. The following detailed description is, therefore, not to be taken in a limiting sense.
As shown in fig. 1, according to a first aspect of the present invention, a method and a system for backing up a big data-based grid data node are provided, where the backup system includes a main server group S ═ { S ═ S1,S2……SNT and backup server set T ═ T1，T2……TNWherein the main server group S includes N (N is a natural number, N)>2) main servers S not connected to each other1,S2……SNUsed for storing data and receiving read-write access operation of a client,And the backup server group T comprises N backup servers which are connected into a ring network and used for backing up the data of the corresponding main server and providing service for the client when the main server fails, wherein TiIs corresponding to the main server SiI is a natural number between 1 and N.
In the schematic block diagram shown in fig. 1, each backup server T in the backup server group TiMay be divided into two parts, wherein the first part is used for the corresponding main server SiPerforming hot backup, the second part is available storage part, and the backup server T adjacent to the second parti-1Or Ti+1When the data writing device cannot work, the data writing device can provide storage space for a client to write data. To this end, each backup server TiA status list is maintained that includes information about each backup server including, but not limited to, the ID of each backup server, the current status of each backup server, the first portion of storage space of each backup server, the second portion of storage space of each backup server, the Mean Time Between Failure (MTBF) of each backup server, the time between failures (MTBF) of each backup server, the number of backup servers T, and the number of backup servers TiTo an adjacent backup server Ti-1And Ti+1Network connection time, etc. Those skilled in the art will appreciate that any parameters characterizing the state and connectability of the backup server may be maintained in the state list. Each backup server updates the status list in real time through the ring network.
According to a first aspect of the present invention, in the schematic configuration diagram shown in fig. 1, the entire backup system performs the following backup method: backup server TiIs divided into L0And L1Two parts; master server S of a master server group SiWith the backup server T in the backup server group TiPerforming one-to-one hot backup, wherein the hot backup is stored in a backup server TiL of0in the area; once a certain main server SiIf the failure occurs and the service cannot be provided, the corresponding backup server T is usediTo gueststhe user terminal provides service; master server SiDuring the fault, once the corresponding backup server TiAlso fails, the backup server TiAdjacent backup server T ofi-1And/or Ti+1Providing storage space L for writing data to client1. T may be selected according to the parameters characterizing the state and connectivity of the backup server as described abovei-1Or Ti+1One or both to provide a storage space L1. In particular, T is detected from parameters in the status listi-1And/or Ti+1If data is stored in one of L1, another L1 which does not store data is selected to provide a storage space; if both do not store data, L can be selected from the two1the larger area provides storage space for the client to write data, or the longer Mean Time Between Failures (MTBF) of the two provides storage space for the client to write data, or the shorter network connection time of the two provides storage space for the client to write data; if both store data, then according to both L1The size of the region is scaled so that the two share the required storage space according to the scale, and so on.
Depending on the situation that occurs in reality, a more extreme situation may be considered, i.e. a backup server T already providing storage spacei-1And/or Ti+1A processing method when at least one of them fails. In this case, the problem can be solved by only continuously and repeatedly executing the step of selecting the backup server. That is, since the current status of a backup server (whether the backup server is providing service, whether the backup server is operating normally, etc.) is indicated in the status list, and the status list is updated in real time, it is only necessary to continue to repeat the previous operations to select from the rest of the backup servers according to the same criteria when the backup server is not operating. Backup servers that serve in place of the primary server and their corresponding backup servers should write the stored data associated with them back to the primary server when they are newly availableThe server and the corresponding backup server.
Because different backup servers are located in different counties and cities, the physical distances are different, the conditions of machine rooms are different, the brands and the performances of the servers adopted by the backup servers in different counties and cities are different, and the probability of simultaneous failure is extremely low, the backup method can effectively solve the problem of interruption of power grid data communication when the main server and the backup server simultaneously fail on the premise of not increasing the backup servers.
As shown in fig. 2, according to a second aspect of the present invention, a method and a system for backing up a big data-based grid data node are provided, where the backup system includes a main server group S ═ { S ═ S1,S2……SNT and backup server set T ═ T1，T2……TNWherein the main server group S includes N (N is a natural number, N)>2) main servers S not connected to each other1,S2……SNThe backup server group T comprises N backup servers which are connected into a star network and used for backing up the data of the corresponding main server and providing service for the client when the main server fails, wherein TiIs corresponding to the main server Sii is a natural number between 1 and N. At the heart of the star network is a network controller that maintains a status list that keeps track of each backup server's various items of information, including, but not limited to, each backup server's ID, each backup server's current status, each backup server's first portion of storage space, each backup server's second portion of storage space, each backup server's Mean Time Between Failures (MTBF), each backup server TiTo other backup servers TjNetwork connection time, etc. Those skilled in the art will appreciate that any parameters characterizing the state and connectability of the backup server may be maintained in the state list. The network controller updates the status list in real time according to the communication condition with each backup serverTable (7). Those skilled in the art will appreciate that the network controller may be implemented in the form of a server.
According to a second aspect of the present invention, in the schematic configuration diagram shown in fig. 2, the entire backup system performs the following backup method: backup server TiIs divided into L0And L1Two parts; master server S of a master server group SiWith the backup server T in the backup server group TiPerforming one-to-one hot backup, wherein the hot backup is stored in a backup server TiL of0In the area; once a certain main server SiIf the failure occurs and the service cannot be provided, the corresponding backup server T is usediProviding a service to a client; master server SiDuring the fault, once the corresponding backup server TiIf a failure occurs, the other backup servers provide the storage space L for writing data to the client under the control of the network controller1. The selection of which backup server or backup servers to provide the storage space L may be based on the parameters characterizing the status and connectivity of the backup servers as described above1. Specifically, L can be selected from all backup servers capable of working normally1The larger area provides storage space for the client to write data, or the longer Mean Time Between Failures (MTBF) of all the backup servers capable of working normally provides storage space for the client to write data, or the shorter network connection time of all the backup servers capable of working normally provides storage space for the client to write data. In order to prevent one backup server from bearing excessive data traffic, the network controller may also determine, according to a certain algorithm, storage space provided by a plurality of backup servers for the client to write data. For example, the network controller may determine a fixed number of backup servers providing storage space based on the status list, which may be based on L1The size of the storage space, the duration of the mean time between failures MTBF, the length of the network connection time, etc. For example, the network controller selects L according to the parameters in the status list1The storage space is the mostAnd large M backup servers provide services, or the M backup servers with the longest Mean Time Between Failures (MTBF) or the M backup servers with the shortest network connection time are selected. In order to make the overall load of the network small and safe and controllable, the preferred value of M is 2 or 3. The network controller may also determine that all backup servers meeting a predetermined threshold provide storage space based on the status list, e.g., the network controller determines all L1Backup servers greater than 500TB provide storage space, or all backup servers with an average time to failure greater than one hundred thousand hours provide storage space, or all backup servers with a network connection time less than 50 microseconds provide storage space.
In the method, the network controller is in the position of central regulation control, is connected with each backup server through a network, and updates the information of the state list in real time through the network. Each backup server can be completely interconnected with each other through a network, and also can be only interconnected with adjacent backup servers or arbitrarily interconnected with each backup server under the condition of ensuring that at least two other backup servers are connected with each other due to the requirement of saving cost.
Likewise, consider a more extreme situation, i.e., a handling method when at least one of the M backup servers that provide storage space has failed. In this case, the problem can be solved by only continuously and repeatedly executing the step of selecting the backup server. That is, since the current status of a backup server (whether it is providing service, whether it is working normally, etc.) is indicated in the status list maintained by the network controller, and the status list is updated in real time, it is only necessary to continue to repeat the previous operations to select from the rest of the backup servers according to the same criteria when the backup server is not working. In this way, the number of backup servers providing services can be kept at M all the time until the number of available backup servers in the backup server group T is less than M. This is generally not possible or until the primary and other backup servers have been repaired or restarted to provide normal service. When the primary server and its corresponding backup server are re-available, the backup servers that serve in place of them should write the stored data associated with them back to the primary server and its corresponding backup server.
The disclosed method includes one or more steps for achieving the objectives of the present invention, and the method steps may be interchanged with one another without departing from the scope of the present invention. In other words, unless a specific order of steps is required for proper operation of the embodiment, the order of specific steps may be modified without departing from the spirit and scope of the present invention. While the invention has been described primarily in terms of specific embodiments and applications, those skilled in the art will recognize that the invention is not limited thereto. Various modifications, changes, and variations apparent to those skilled in the art in light of the disclosed methods and systems may be made without departing from the spirit and scope of the invention.
Claims (6)
1. The grid data node backup method based on big data is applied to a grid data node backup system and is characterized in that the system comprises a main server group S ═ S { (S) }1,S2……SNT and backup server set T ═ T1，T2……TNWherein, the main server group S comprises N main servers S which are not connected with each other1,S2……SNThe backup server group T comprises N backup servers connected to a ring network, wherein TiIs corresponding to the main server SiI is a natural number between 1 and N, N is a natural number>2; each backup server T in the backup server group TiIs divided into two parts L0And L1(ii) a Each backup server TiMaintaining a state list, wherein the state list is used for loading various information of each backup server, the various information of each backup server comprises an ID of each backup server, a current state of each backup server, and a first part storage space L of each backup server0A second part of storage space L of each backup server1Mean time between failures MTBF per backup server, T per backup serveriTo an adjacent backup server Ti-1And Ti+1Network connection time of (a); the method comprises the following steps:
Step S100, judging the main server Siwhether the work is normal or not, if the work is normal, the process is ended; if the normal work can not be carried out, the main server S is switched toiCorresponding backup server TiFrom TiServing the client;
Step S200, judging a backup server TiWhether the work is normal or not, if the work is normal, the process is ended; if the system can not work normally, the backup server T adjacent to the system is determined according to the information in the state listi+1And/or Ti-1Serving the client;
Wherein, each backup server updates the information in the state list in real time through a ring network;
Step S300, detecting the backup server T in real timei+1And/or Ti-1Whether the work is normal or not, if the work is normal, the process is ended; if at least one of the two can not work normally, the step S200 is executed repeatedly.
2. The backup method according to claim 1, further comprising a step S400 of writing back data to the primary server by each backup server when the primary server is restored to normal.
3. Backup method according to claim 1 or 2, characterized in that the backup server T determined by its neighbour is determined from the information in the status listi+1And/or Ti-1Servicing the client includes detecting T from parameters in the state listi-1and/or Ti+1If data is stored in one of the L1, another L1 that does not store data is selected to provide a service; if both do not store data, L in both1service provided by larger area, or average failure of bothThe service is provided by the longer MTBF or the shorter of the MTBF and the MTBF; if both store data, then according to Ti+1And Ti-1Both L1The size of the region is scaled to provide service by both together in that scale.
4. The grid data node backup method based on big data is applied to a grid data node backup system and is characterized in that the system comprises a main server group S ═ S { (S) }1,S2……SNT and backup server set T ═ T1，T2……TNWherein, the main server group S comprises N main servers S which are not connected with each other1,S2……SNThe backup server group T comprises N backup servers connected as a star network, wherein TiIs corresponding to the main server SiI is a natural number between 1 and N, N is a natural number>2; each backup server T in the backup server group TiIs divided into two parts L0And L1(ii) a The star network is centered on a network controller connected to each backup server, the network controller maintains a status list in which information of each backup server is specified, the information of each backup server includes an ID of each backup server, a current status of each backup server, and a first storage space L of each backup server0A second part of storage space L of each backup server1Mean time between failures MTBF per backup server, T per backup serveriTo other available backup servers TjNetwork connection time of (a); the method comprises the following steps:
Step S100, judging the main server SiWhether the work is normal or not, if the work is normal, the process is ended; if the normal work can not be carried out, the main server S is switched toicorresponding backup server TiFrom TiServing the client;
Step S200, judging a backup server TiWhether the work is normal or not, if the work is normal, the process is ended; if the client side can not work normally, under the control of the network controller, determining that other available backup servers provide services for the client side according to the information in the state list;
The network controller updates the information in the state list in real time through a star network;
Step S300, detecting whether the backup server in use works normally in real time, and if the backup server works normally, ending the process; if at least one of them can not work normally, the step S200 is executed repeatedly.
5. The backup method according to claim 4, further comprising a step S400 of writing back data to the primary server by each backup server when the primary server is restored to normal.
6. A backup method according to claim 4 or 5, characterized in that determining from the information in the status list that other available backup servers provide services to the client under the control of the network controller comprises the network controller providing services according to L1Determining that M backup servers provide services according to the size of the storage space, the time length of the Mean Time Between Failures (MTBF) and the length of the network connection time, wherein the value of M is 2 or 3; or comprises the network controller according to L1Determining all backup servers meeting the preset threshold value to provide services according to the size of the storage space, the time length of the Mean Time Between Failures (MTBF) and the length of the network connection time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811010693.7A CN109508261B (en) | 2018-08-31 | 2018-08-31 | Power grid data node backup method and system based on big data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811010693.7A CN109508261B (en) | 2018-08-31 | 2018-08-31 | Power grid data node backup method and system based on big data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109508261A CN109508261A (en) | 2019-03-22 |
| CN109508261B true CN109508261B (en) | 2019-12-13 |
Family
ID=65745669
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811010693.7A Active CN109508261B (en) | 2018-08-31 | 2018-08-31 | Power grid data node backup method and system based on big data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109508261B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111104266A (en) * | 2019-12-23 | 2020-05-05 | 北京大米科技有限公司 | Access resource allocation method and device, storage medium and electronic equipment |
| CN113778744B (en) * | 2021-01-05 | 2024-06-18 | 北京沃东天骏信息技术有限公司 | Task processing method, device, system and storage medium |
| CN113572837A (en) * | 2021-07-22 | 2021-10-29 | 南方电网数字电网研究院有限公司 | Power grid monitoring system data processing service scheduling method based on fragmentation technology |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101316274A (en) * | 2008-05-12 | 2008-12-03 | 华中科技大学 | Data disaster tolerance system suitable for WAN |
| CN102737127A (en) * | 2012-06-20 | 2012-10-17 | 厦门聚海源物联网络技术有限公司 | Massive data storage method |
| CN107066355A (en) * | 2017-05-15 | 2017-08-18 | 郑州云海信息技术有限公司 | The backup server system and its building method of a kind of High Availabitity |
| CN108089946A (en) * | 2017-12-15 | 2018-05-29 | 安徽长泰信息安全服务有限公司 | A kind of multinode Fast incremental backup method |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9652344B2 (en) * | 2015-06-11 | 2017-05-16 | International Business Machines Corporation | In-memory data store replication through remote memory sharing |
| CN106210151A (en) * | 2016-09-27 | 2016-12-07 | 深圳市彬讯科技有限公司 | A kind of zedis distributed caching and server cluster monitoring method |
| CN206498429U (en) * | 2016-11-11 | 2017-09-15 | 中华通信系统有限责任公司 | A kind of Core server group network system based on distributed heterogeneous network |
-
2018
- 2018-08-31 CN CN201811010693.7A patent/CN109508261B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101316274A (en) * | 2008-05-12 | 2008-12-03 | 华中科技大学 | Data disaster tolerance system suitable for WAN |
| CN102737127A (en) * | 2012-06-20 | 2012-10-17 | 厦门聚海源物联网络技术有限公司 | Massive data storage method |
| CN107066355A (en) * | 2017-05-15 | 2017-08-18 | 郑州云海信息技术有限公司 | The backup server system and its building method of a kind of High Availabitity |
| CN108089946A (en) * | 2017-12-15 | 2018-05-29 | 安徽长泰信息安全服务有限公司 | A kind of multinode Fast incremental backup method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109508261A (en) | 2019-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109729129B (en) | Configuration modification method of storage cluster system, storage cluster and computer system | |
| US7007144B2 (en) | Method, apparatus, and computer readable medium for managing back-up | |
| CN109508261B (en) | Power grid data node backup method and system based on big data | |
| CN106776130B (en) | Log recovery method, storage device and storage node | |
| US11892922B2 (en) | State management methods, methods for switching between master application server and backup application server, and electronic devices | |
| CN109446169B (en) | Double-control disk array shared file system | |
| CN106062717A (en) | Distributed storage replication system and method | |
| CN108984349B (en) | Method and device for electing master node, medium and computing equipment | |
| CN103299296B (en) | Partition management method, equipment and system in a kind of distributed memory system | |
| CN107817950B (en) | Data processing method and device | |
| CN107329859B (en) | Data protection method and storage device | |
| US20080082630A1 (en) | System and method of fault tolerant reconciliation for control card redundancy | |
| CN107038192B (en) | Database disaster tolerance method and device | |
| CN104753987B (en) | A kind of distributed conversation management method and system | |
| CN106201772A (en) | The backup of a kind of operating system based on data center, restoration methods and device | |
| CN113590049B (en) | Storage volume cross-node cloning method, device, equipment and readable medium | |
| CN107943615B (en) | Data processing method and system based on distributed cluster | |
| CN112749045B (en) | Database cluster switching method, device, storage medium and apparatus | |
| CN105323271B (en) | Cloud computing system and processing method and device thereof | |
| CN113051428B (en) | Method and device for back-up storage at front end of camera | |
| CN117312052A (en) | Recovery method, storage medium and equipment of database disaster recovery system | |
| CN115563028B (en) | Data caching method, device, equipment and storage medium | |
| CN114443057B (en) | Deployment of conversation model, conversation method, device, electronic equipment and storage medium | |
| CN115686368A (en) | Method, system, apparatus and medium for storage capacity expansion of nodes of block chain network | |
| CN110389863A (en) | A kind of data reconstruction method, device, equipment and computer readable storage medium |
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 |