技术领域technical field
本发明涉及服务器集群及数据库容灾技术领域，特别是涉及一种集群数据库容灾方法及装置。The invention relates to the technical field of server cluster and database disaster recovery, in particular to a cluster database disaster recovery method and device.
背景技术Background technique
传统的集群数据库容灾方案都采用双机互备，或者额外配置磁带库进行数据库数据备份，大型企业更需要采用远程异地数据库备份。其数据库容灾都比较固定，或者需要投入额外的资金。其中，磁带库需要投入大量资金进行购买，还需要投入额外的磁带库维护。双机热备则存在隐患，需要保证备机使用时，主机能尽快修复，否则数据库无法保证其安全。异地灾备中心则会涉及传输速度以及网络使用成本等问题。Traditional cluster database disaster recovery solutions use dual-machine mutual backup, or additionally configure tape libraries for database data backup, and large enterprises need to use remote off-site database backup. Its database disaster recovery is relatively fixed, or requires additional investment. Among them, the tape library needs to invest a lot of money for purchase, and additional tape library maintenance needs to be invested. There are hidden dangers in dual-machine hot backup. It is necessary to ensure that when the standby machine is in use, the main machine can be repaired as soon as possible, otherwise the database cannot guarantee its security. The remote disaster recovery center will involve issues such as transmission speed and network usage costs.
因此，提供一种能够减少额外资源投入的数据库容灾方法及装置是非常有必要的。Therefore, it is very necessary to provide a database disaster recovery method and device capable of reducing additional resource investment.
发明内容Contents of the invention
本发明的目的是提供一种集群数据库容灾方法及装置，目的在于解决现有数据库容灾方案中资源消耗较大的问题。The purpose of the present invention is to provide a cluster database disaster recovery method and device, aiming at solving the problem of large resource consumption in the existing database disaster recovery scheme.
为解决上述技术问题，本发明提供一种集群数据库容灾方法，包括：In order to solve the above technical problems, the present invention provides a cluster database disaster recovery method, including:
在服务器集群的N个节点上分别部署数据库，并将所述数据库初始化到同一状态，所述N为大于2的正整数；Deploying databases on N nodes of the server cluster respectively, and initializing the databases to the same state, where N is a positive integer greater than 2;
从所述节点中选择两个节点分别作为主节点、从节点，位于所述主节点的数据库为主数据库，位于所述从节点的数据库为保持与所述主数据库数据同步的从数据库；Select two nodes from the nodes as master node and slave node respectively, the database positioned at the master node is the master database, and the database positioned at the slave node is a slave database that maintains data synchronization with the master database;
检测所述主节点的健康状态；Detect the health status of the master node;
当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。When the master node is down, the slave node is used as the current master node, and other nodes in the server cluster are selected as the current slave nodes.
可选地，所述当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点包括：Optionally, when the master node goes down, using the slave node as the current master node, and selecting other nodes in the server cluster as the current slave node includes:
当所述主节点发生宕机时，检测所述从节点的健康状态；When the master node goes down, detect the health status of the slave node;
当所述从节点为正常状态时，将所述从节点作为当前主节点，并选择所述服务器集群中的其他节点作为当前从节点。When the slave node is in a normal state, take the slave node as the current master node, and select other nodes in the server cluster as the current slave nodes.
可选地，所述当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点包括：Optionally, when the master node goes down, using the slave node as the current master node, and selecting other nodes in the server cluster as the current slave node includes:
当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务区集群中其他存活节点作为当前从节点。When the master node is down, the slave node is used as the current master node, and other surviving nodes in the service area cluster are selected as the current slave nodes.
可选地，还包括：Optionally, also include:
向用户提示所述当前主节点以及所述当前从节点的信息。Prompting the user with information about the current master node and the current slave node.
本发明还提供了一种集群数据库容灾装置，包括：The present invention also provides a cluster database disaster recovery device, including:
设置模块，用于在服务器集群的N个节点上分别部署数据库，并将所述数据库初始化到同一状态，所述N为大于2的正整数；A setting module is used to deploy databases on N nodes of the server cluster respectively, and initialize the databases to the same state, where N is a positive integer greater than 2;
选择模块，用于从所述节点中选择两个节点分别作为主节点、从节点，位于所述主节点的数据库为主数据库，位于所述从节点的数据库为保持与所述主数据库数据同步的从数据库；The selection module is used to select two nodes from the nodes as a master node and a slave node respectively, the database located at the master node is the master database, and the database located at the slave node is a database that keeps data synchronization with the master database from the database;
检测模块，用于检测所述主节点的健康状态；A detection module, configured to detect the health status of the master node;
容灾模块，用于当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。The disaster recovery module is configured to use the slave node as the current master node when the master node goes down, and select other nodes in the server cluster as the current slave nodes.
可选地，所述容灾模块用于当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点包括：Optionally, the disaster recovery module is configured to use the slave node as the current master node when the master node goes down, and selecting other nodes in the server cluster as the current slave node includes:
所述容灾模块具体用于当所述主节点发生宕机时，检测所述从节点的健康状态；当所述从节点为正常状态时，将所述从节点作为当前主节点，并选择所述服务器集群中的其他节点作为当前从节点。The disaster recovery module is specifically used to detect the health status of the slave node when the master node is down; when the slave node is in a normal state, use the slave node as the current master node, and select the other nodes in the above server cluster as the current slave nodes.
可选地，所述容灾模块用于当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点包括：Optionally, the disaster recovery module is configured to use the slave node as the current master node when the master node goes down, and selecting other nodes in the server cluster as the current slave node includes:
所述容灾模块具体用于当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务区集群中其他存活节点作为当前从节点。The disaster recovery module is specifically configured to use the slave node as the current master node when the master node fails, and select other surviving nodes in the service area cluster as the current slave nodes.
可选地，还包括：Optionally, also include:
提示模块，用于向用户提示所述当前主节点以及所述当前从节点的信息。A prompt module, configured to prompt the user with information about the current master node and the current slave node.
本发明所提供的集群数据库容灾方法及装置，通过在服务器集群的N个节点上分别部署数据库，并将数据库初始化到同一状态；在节点中选择两个节点分别作为主节点、从节点，位于主节点的数据库为主数据库，位于从节点的数据库为保持与主数据库数据同步的从数据库；后台检测主节点的健康状态；当所述主节点发生宕机时，将从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。本发明所提供的集群数据库容灾方法及装置，充分利用了集群环境的特殊性，将数据库的容灾方案变为1+1+N的模式。能够在保证数据库数据安全的同时，节省了额外的资源投入。另外，在同一时刻，仅需要保持主节点与从节点的数据同步即可，大大减少了数据库同步数据流。The cluster database disaster recovery method and device provided by the present invention deploy the databases on the N nodes of the server cluster respectively, and initialize the databases to the same state; select two nodes in the nodes as the master node and the slave node respectively, located in The database of the master node is the master database, and the database located at the slave node is a slave database that maintains data synchronization with the master database; the background detects the health status of the master node; when the master node is down, the slave node is used as the current master node, And select other nodes in the server cluster as the current slave nodes. The cluster database disaster recovery method and device provided by the present invention make full use of the particularity of the cluster environment, and change the database disaster recovery scheme into a 1+1+N mode. It can save additional resource investment while ensuring the security of database data. In addition, at the same time, it is only necessary to keep the data synchronization between the master node and the slave node, which greatly reduces the database synchronization data flow.
附图说明Description of drawings
图1为本发明所提供的集群数据库容灾方法的一种具体实施方式的方法流程图；Fig. 1 is a method flowchart of a specific embodiment of the cluster database disaster recovery method provided by the present invention;
图2为本发明所提供的集群数据库容灾方法的另一种具体实施方式的方法流程图；Fig. 2 is a method flowchart of another specific embodiment of the cluster database disaster recovery method provided by the present invention;
图3为本发明所提供的集群数据库容灾装置的一种具体实施方式的结构框图。FIG. 3 is a structural block diagram of a specific embodiment of the cluster database disaster recovery device provided by the present invention.
具体实施方式Detailed ways
为了使本技术领域的人员更好地理解本发明方案，下面结合附图和具体实施方式对本发明作进一步的详细说明。显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. Apparently, the described embodiments are only some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.
本发明所提供的集群数据库容灾方法的一种具体实施方式的方法流程图如图1所示，该方法包括：A method flowchart of a specific embodiment of the cluster database disaster recovery method provided by the present invention is shown in Figure 1, the method includes:
步骤S101：在服务器集群的N个节点上分别部署数据库，并将所述数据库初始化到同一状态，所述N为大于2的正整数；Step S101: Deploy databases on N nodes of the server cluster respectively, and initialize the databases to the same state, where N is a positive integer greater than 2;
步骤S102：从所述节点中选择两个节点分别作为主节点、从节点，位于所述主节点的数据库为主数据库，位于所述从节点的数据库为保持与所述主数据库数据同步的从数据库；Step S102: Select two nodes from the nodes as the master node and the slave node respectively, the database located at the master node is the master database, and the database located at the slave node is the slave database keeping data synchronization with the master database ;
步骤S103：检测所述主节点的健康状态；Step S103: Detect the health status of the master node;
步骤S104：当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。Step S104: When the master node is down, use the slave node as the current master node, and select other nodes in the server cluster as the current slave nodes.
本发明所提供的集群数据库容灾方法，通过在服务器集群的N个节点上分别部署数据库，并将数据库初始化到同一状态；在节点中选择两个节点分别作为主节点、从节点，位于主节点的数据库为主数据库，位于从节点的数据库为保持与主数据库数据同步的从数据库；检测主节点的健康状态；当所述主节点发生宕机时，将从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。本发明所提供的集群数据库容灾方法，充分利用了集群环境的特殊性，将数据库的容灾方案变为1+1+N的模式。能够在保证数据库数据安全的同时，节省了额外的资源投入。另外，在同一时刻，仅需要保持主节点与从节点的数据同步即可，大大减少了数据库同步数据流。In the cluster database disaster recovery method provided by the present invention, the databases are respectively deployed on the N nodes of the server cluster, and the databases are initialized to the same state; two nodes are selected in the nodes as the master node and the slave node respectively, and are located at the master node The database at the slave node is the master database, and the database at the slave node is a slave database that keeps data synchronization with the master database; detect the health status of the master node; when the master node is down, take the slave node as the current master node, and select the other nodes in the above server cluster as the current slave nodes. The cluster database disaster recovery method provided by the present invention makes full use of the particularity of the cluster environment, and changes the database disaster recovery scheme into a 1+1+N mode. It can save additional resource investment while ensuring the security of database data. In addition, at the same time, it is only necessary to keep the data synchronization between the master node and the slave node, which greatly reduces the database synchronization data flow.
本发明所提供的集群数据库容灾方法的另一种具体实施方式的方法流程图如图2所示，该方法包括：The method flowchart of another specific embodiment of the cluster database disaster recovery method provided by the present invention is shown in Figure 2, the method includes:
步骤S201：在服务器集群的N个节点上分别部署数据库，并将所述数据库初始化到同一状态，所述N为大于2的正整数；Step S201: Deploy databases on N nodes of the server cluster respectively, and initialize the databases to the same state, where N is a positive integer greater than 2;
具体地，由于本发明所提供的集群数据容灾方法的硬件环境是处在集群环境中，因此，在集群环境搭建完成后，由使用者评估，在集群的N个节点上同时部署数据库，并初始化到同一状态。Specifically, since the hardware environment of the cluster data disaster recovery method provided by the present invention is in a cluster environment, after the cluster environment is set up, the user evaluates and deploys the database on the N nodes of the cluster at the same time, and initialized to the same state.
步骤S202：从所述节点中选择两个节点分别作为主节点、从节点，位于所述主节点的数据库为主数据库，位于所述从节点的数据库为保持与所述主数据库数据同步的从数据库；Step S202: Select two nodes from the nodes as the master node and the slave node respectively, the database located at the master node is the master database, and the database located at the slave node is the slave database keeping data synchronization with the master database ;
在集群使用过程中，将数据保存到主数据库中，同时根据用户设置的数据库备份策略，将从节点中的数据库与主节点的数据库同步。During the use of the cluster, the data is saved in the master database, and at the same time, the database in the slave node is synchronized with the database of the master node according to the database backup policy set by the user.
步骤S203：检测所述主节点的健康状态；Step S203: Detect the health status of the master node;
步骤S204：当所述主节点发生宕机时，检测所述从节点的健康状态；Step S204: When the master node is down, detect the health status of the slave node;
步骤S205：当所述从节点为正常状态时，将所述从节点作为当前主节点，并选择所述服务器集群中的其他存活节点作为当前从节点。Step S205: When the slave node is in a normal state, take the slave node as the current master node, and select other surviving nodes in the server cluster as the current slave node.
步骤S206：向用户提示所述当前主节点以及所述当前从节点的信息，并提示用户立即进行数据库同步。Step S206: Prompt the user for the information of the current master node and the current slave node, and prompt the user to perform database synchronization immediately.
此外，本发明所提供的集群数据库容灾方法还可以进一步包括：In addition, the cluster database disaster recovery method provided by the present invention may further include:
在从节点宕机情况下，选择其他任意节点作为从节点，并提示用于立即进行数据库同步。In the case of a slave node failure, select any other node as a slave node and prompt for immediate database synchronization.
本发明所提供的集群数据库容灾方法，打破了固定的数据库模式，考虑了集群环境的特殊性，将数据库的容灾方法变为1+1+N的模式，提高了数据库容灾的灵活性。可以在保证数据库数据安全的同时，节省了额外的资源投入以及避免了额外的数据流资源消耗。The cluster database disaster recovery method provided by the present invention breaks the fixed database mode, considers the particularity of the cluster environment, changes the database disaster recovery method into a 1+1+N mode, and improves the flexibility of database disaster recovery . While ensuring the security of database data, it saves additional resource investment and avoids additional data flow resource consumption.
本发明所提供的集群数据库容灾装置的一种具体实施方式的结构框图如图3所示，该装置包括：A structural block diagram of a specific embodiment of the cluster database disaster recovery device provided by the present invention is shown in Figure 3, the device includes:
设置模块100，用于在服务器集群的N个节点上分别部署数据库，并将所述数据库初始化到同一状态，所述N为大于2的正整数；The setting module 100 is used to deploy the database on the N nodes of the server cluster respectively, and initialize the database to the same state, and the N is a positive integer greater than 2;
选择模块200，用于从所述节点中选择两个节点分别作为主节点、从节点，位于所述主节点的数据库为主数据库，位于所述从节点的数据库为保持与所述主数据库数据同步的从数据库；The selection module 200 is used to select two nodes from the nodes as the master node and the slave node respectively, the database located at the master node is the master database, and the database located at the slave node maintains data synchronization with the master database from the database;
检测模块300，用于检测所述主节点的健康状态；A detection module 300, configured to detect the health status of the master node;
容灾模块400，用于当所述主节点发生宕机时，将所述从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。The disaster recovery module 400 is configured to use the slave node as the current master node when the master node goes down, and select other nodes in the server cluster as the current slave nodes.
本发明所提供的集群数据库容灾装置，通过在服务器集群的N个节点上分别部署数据库，并将数据库初始化到同一状态；从节点中选择两个节点分别作为主节点、从节点，位于主节点的数据库为主数据库，位于从节点的数据库为保持与主数据库数据同步的从数据库；后台检测主节点的健康状态；当所述主节点发生宕机时，将从节点作为当前主节点，并选择所述服务器集群中其他节点作为当前从节点。The cluster database disaster recovery device provided by the present invention deploys the database on the N nodes of the server cluster respectively, and initializes the database to the same state; two nodes are selected as the master node and the slave node respectively from the slave nodes, and are located at the master node The database located in the slave node is the master database, and the database located in the slave node is a slave database that maintains data synchronization with the master database; the background detects the health status of the master node; when the master node is down, the slave node is used as the current master node, and select Other nodes in the server cluster serve as current slave nodes.
本发明所提供的集群数据库容灾装置，充分利用了集群环境的特殊性，将数据库的容灾方案变为1+1+N的模式，提高了数据库容灾的灵活性。能够在保证数据库数据安全的同时，减少数据库容灾的整体投入，减少了数据流的资源消耗。The cluster database disaster recovery device provided by the present invention makes full use of the particularity of the cluster environment, changes the database disaster recovery scheme into a 1+1+N mode, and improves the flexibility of the database disaster recovery. While ensuring the security of database data, it can reduce the overall investment in database disaster recovery and reduce the resource consumption of data flow.
作为一种优选实施方式，本发明所提供的集群数据库容灾装置还可以进一步包括：As a preferred embodiment, the cluster database disaster recovery device provided by the present invention may further include:
提示模块500，用于向用户提示所述当前主节点以及所述当前从节点的信息，提示用户立即进行数据库同步。The prompt module 500 is configured to prompt the user with the information of the current master node and the current slave node, and prompt the user to perform database synchronization immediately.
本发明所提供的集群数据库容灾装置与上述集群数据库容灾方法相对应，在此不再赘述。The cluster database disaster recovery device provided by the present invention corresponds to the cluster database disaster recovery method described above, and will not be repeated here.
本说明书中各个实施例采用递进的方式描述，每个实施例重点说明的都是与其它实施例的不同之处，各个实施例之间相同或相似部分互相参见即可。Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other.
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本发明。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510505439.4ACN105095486A (en) | 2015-08-17 | 2015-08-17 | Cluster database disaster recovery method and device |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510505439.4ACN105095486A (en) | 2015-08-17 | 2015-08-17 | Cluster database disaster recovery method and device |
| Publication Number | Publication Date |
|---|---|
| CN105095486Atrue CN105095486A (en) | 2015-11-25 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510505439.4APendingCN105095486A (en) | 2015-08-17 | 2015-08-17 | Cluster database disaster recovery method and device |
| Country | Link |
|---|---|
| CN (1) | CN105095486A (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106021030A (en)* | 2016-05-30 | 2016-10-12 | 浪潮电子信息产业股份有限公司 | Database system and database fault processing method and device |
| CN106301938A (en)* | 2016-08-25 | 2017-01-04 | 成都索贝数码科技股份有限公司 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| CN106407264A (en)* | 2016-08-25 | 2017-02-15 | 成都索贝数码科技股份有限公司 | High-availability and high-consistency database cluster system and command processing method thereof |
| CN106452864A (en)* | 2016-09-30 | 2017-02-22 | 北京悦畅科技有限公司 | Parking lot fault protection method, apparatus and system thereof |
| CN109582509A (en)* | 2017-09-29 | 2019-04-05 | 中兴通讯股份有限公司 | Distributed file system disaster tolerance configuration method, device and readable storage medium storing program for executing |
| CN110389961A (en)* | 2019-07-26 | 2019-10-29 | 苏州浪潮智能科技有限公司 | Timed task processing method, device, equipment and computer readable storage medium |
| CN110399207A (en)* | 2019-06-29 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Timing task processing method, system and storage medium in distributed storage system |
| CN111459909A (en)* | 2020-03-13 | 2020-07-28 | 北京许继电气有限公司 | Method for constructing PostgreSQL L database cluster |
| CN112653734A (en)* | 2020-12-11 | 2021-04-13 | 邦彦技术股份有限公司 | Server cluster real-time master-slave control and data synchronization system and method |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070156781A1 (en)* | 2006-01-05 | 2007-07-05 | Aditya Kapoor | Detecting failover in a database mirroring environment |
| CN101309167A (en)* | 2008-06-27 | 2008-11-19 | 华中科技大学 | Disaster recovery system and method based on cluster backup |
| CN101667181A (en)* | 2008-09-05 | 2010-03-10 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| CN103034697A (en)* | 2012-12-06 | 2013-04-10 | 江苏引跑网络科技有限公司 | Method for realizing high availability of distributed database |
| CN103209091A (en)* | 2013-01-18 | 2013-07-17 | 中兴通讯股份有限公司 | Hot backup method and system for clustering system |
| CN104516966A (en)* | 2014-12-24 | 2015-04-15 | 北京奇虎科技有限公司 | High-availability solving method and device of database cluster |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070156781A1 (en)* | 2006-01-05 | 2007-07-05 | Aditya Kapoor | Detecting failover in a database mirroring environment |
| CN101309167A (en)* | 2008-06-27 | 2008-11-19 | 华中科技大学 | Disaster recovery system and method based on cluster backup |
| CN101667181A (en)* | 2008-09-05 | 2010-03-10 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| CN103034697A (en)* | 2012-12-06 | 2013-04-10 | 江苏引跑网络科技有限公司 | Method for realizing high availability of distributed database |
| CN103209091A (en)* | 2013-01-18 | 2013-07-17 | 中兴通讯股份有限公司 | Hot backup method and system for clustering system |
| CN104516966A (en)* | 2014-12-24 | 2015-04-15 | 北京奇虎科技有限公司 | High-availability solving method and device of database cluster |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106021030A (en)* | 2016-05-30 | 2016-10-12 | 浪潮电子信息产业股份有限公司 | Database system and database fault processing method and device |
| CN106301938A (en)* | 2016-08-25 | 2017-01-04 | 成都索贝数码科技股份有限公司 | A kind of high availability and the data base cluster system of strong consistency and node administration method thereof |
| CN106407264A (en)* | 2016-08-25 | 2017-02-15 | 成都索贝数码科技股份有限公司 | High-availability and high-consistency database cluster system and command processing method thereof |
| CN106452864A (en)* | 2016-09-30 | 2017-02-22 | 北京悦畅科技有限公司 | Parking lot fault protection method, apparatus and system thereof |
| CN109582509A (en)* | 2017-09-29 | 2019-04-05 | 中兴通讯股份有限公司 | Distributed file system disaster tolerance configuration method, device and readable storage medium storing program for executing |
| CN110399207A (en)* | 2019-06-29 | 2019-11-01 | 苏州浪潮智能科技有限公司 | Timing task processing method, system and storage medium in distributed storage system |
| CN110389961A (en)* | 2019-07-26 | 2019-10-29 | 苏州浪潮智能科技有限公司 | Timed task processing method, device, equipment and computer readable storage medium |
| CN111459909A (en)* | 2020-03-13 | 2020-07-28 | 北京许继电气有限公司 | Method for constructing PostgreSQL L database cluster |
| CN112653734A (en)* | 2020-12-11 | 2021-04-13 | 邦彦技术股份有限公司 | Server cluster real-time master-slave control and data synchronization system and method |
| CN112653734B (en)* | 2020-12-11 | 2023-09-19 | 邦彦技术股份有限公司 | Real-time master-slave control and data synchronization system and method for server cluster |
| Publication | Publication Date | Title |
|---|---|---|
| CN105095486A (en) | Cluster database disaster recovery method and device | |
| EP3832578A1 (en) | Electronic invoice identifier allocation method, and electronic ticket generating method, device and system | |
| CN103902617B (en) | Distributed data base synchronous method and system | |
| CN104537046B (en) | Supplementing Data method and apparatus | |
| CN102142008B (en) | Method and system for implementing distributed memory database, token controller and memory database | |
| US20210182153A1 (en) | System and method for performing an incremental backup for a persistent storage system that stores data for a node cluster | |
| CN110502340A (en) | A kind of resource dynamic regulation method, device, equipment and storage medium | |
| CN103299296B (en) | Partition management method, equipment and system in a kind of distributed memory system | |
| CN105446827A (en) | Data storage method and device for database at failure | |
| CN104503722B (en) | The method, device and mobile terminal of compatible display screen | |
| CN111651275A (en) | MySQL cluster automatic deployment system and method | |
| CN103647830A (en) | Dynamic management method for multilevel configuration files in cluster management system | |
| US9104609B2 (en) | Information processing apparatus, system time synchronization method and computer readable medium | |
| CN103905220B (en) | Data synchronizing processing method and system | |
| CN107729515B (en) | Data synchronization method, device and storage medium | |
| CN102523257A (en) | A Virtual Machine Fault Tolerance Method Based on IAAS Cloud Platform | |
| WO2015154525A1 (en) | Method and device for protecting hqos using multiple board cards | |
| CN101888683A (en) | Tolerant Device Licensing in Distributed Environments | |
| CN105719414A (en) | POS terminal invoicing method and device, and invoicing server terminal | |
| CN105373450A (en) | Data backup method and apparatus | |
| US10684875B2 (en) | Synchronization of a virtual machine across mobile devices | |
| CN111078352A (en) | Dual-computer hot standby deployment method and system based on KVM virtualization system | |
| CN111813854B (en) | Synchronization of metering networks | |
| CN117395263B (en) | Data synchronization method, device, equipment and storage medium | |
| CN109376037A (en) | A data backup method and related device |
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | Application publication date:20151125 | |
| WD01 | Invention patent application deemed withdrawn after publication |