WO2012145963A1 - Data management system and method - Google Patents

Data management system and method Download PDF

Info

Publication number
WO2012145963A1
WO2012145963A1 PCT/CN2011/076322 CN2011076322W WO2012145963A1 WO 2012145963 A1 WO2012145963 A1 WO 2012145963A1 CN 2011076322 W CN2011076322 W CN 2011076322W WO 2012145963 A1 WO2012145963 A1 WO 2012145963A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
standby
database
primary
data management
Prior art date
Application number
PCT/CN2011/076322
Other languages
French (fr)
Chinese (zh)
Inventor
龚力
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012145963A1 publication Critical patent/WO2012145963A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error 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/202Error 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/2035Error 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 without idle spare hardware
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80Database-specific techniques

Definitions

  • the present invention relates to the field of communications, and in particular, to a data management system and method. Background technique
  • a dual server is often used to achieve high availability, wherein one standby server is in a standby state, and when the primary server is down, the standby server will Take over the business.
  • the present invention provides a data management system, the system comprising: Server and standby server;
  • the primary server includes a primary database for internal users to read and write data;
  • the standby server includes a standby database for external data read-only operations, and at least one of the standby databases is equivalent to the primary database. Switch the environment for switching.
  • the primary server is provided with a synchronization module for transmitting redo logs to the standby server for synchronizing data between the standby database and the primary database.
  • both the primary server and the standby server use Real Application Cluster (RAC) technology, and each RAC node shares a cache. When one of the nodes is down, the other node takes over the load.
  • RAC Real Application Cluster
  • the system further includes a plurality of sub-standby servers, the sub-standby servers including sub-standby databases, and only for read-only services of external users.
  • the primary server and the secondary server are divided into different network segments, separated by a firewall.
  • the primary server is provided with a user identification module for verifying identity information of the user.
  • the primary server and the standby server are respectively disposed at different locations, and the two are separated by a safe distance.
  • the invention also proposes a data management method, the method comprising the following steps:
  • the primary server transmits the redo log to the standby server for synchronizing the data between the standby database and the primary database.
  • both the primary server and the standby server use the real application cluster RAC technology, and each RAC node shares a cache. When one node is down, the other nodes take over the load.
  • the data management system and method proposed by the present invention through the design of the database architecture, the main number
  • the database provides read and write permissions for internal users.
  • Multiple standby databases only provide read-only access to external users to achieve read-write separation of data, improve security, and multiple standby servers share system load and achieve high availability. , the effective use of system resources, because of the lower cost of read-only database construction, but also improve the economics of the system.
  • FIG. 1 is a schematic structural diagram of a data management system according to an embodiment of the present invention.
  • FIG. 2 is a schematic flow chart of a data management method according to an embodiment of the present invention.
  • the system includes a primary server 1 and a standby server 2, wherein the primary server 1 runs a primary database 11, and the standby server 2 runs a set of standby databases 21, and the standby database 21 has a primary database 11
  • the primary server 1 and the standby server 2 can be located in different places far apart from each other, and separated by a safe distance, respectively, two or more sets of IT systems with the same function can be established, and health status monitoring and function switching can be performed between each other.
  • the primary server 1 and the secondary server 2 may be composed of a plurality of sub-server clusters, and the databases in each server adopt real application cluster (RAC) technology to achieve high availability.
  • RAC real application cluster
  • each node in the RAC shares a cache.
  • each node takes over the load, providing parallel processing capability and load sharing of the server runtime, and performing fault tolerance when one of the nodes fails.
  • Recovery processing can achieve node failover, to ensure that the database 7 * 24 hours of operation.
  • the standby database 21 provides a read-only interface to the external user, so that the external user can be in standby, because the backup server 2 is in a standby state and is not in use, and the system resources are wasted.
  • Server 2 queries and implements various capabilities such as data mining and statistics.
  • the access area is limited to the standby server 2, which does not affect the operation of the main server 1, and reduces the possibility of the user accessing the main server 1 tampering with the data, thereby improving the security of the system.
  • the main server 1 Since the main database 11 provides the read/write interface of the internal user, the user can have read and write permissions to the main server 1 for data update and maintenance.
  • the main server 1 is provided.
  • a user identification module configured to verify the identity information of the user. For example, the identification module can provide a login window and a login account to verify whether the user is an internal user.
  • the primary server 1 can be divided into internal network segments to provide read and write permissions for internal users
  • the secondary server 2 can be divided into external network segments. Only external users can read-only permissions, and internal network segments and external network segments can be used as firewalls. Separated to achieve read-write separation, since the external user does not directly operate the main server 1, but accesses through the standby server 2, thereby improving the security of the system.
  • the main server 1 is provided with a synchronization module for transmitting redo logs to the standby server 2 for synchronizing data between the standby database 21 and the main database 11.
  • the database in the primary server 1 and the secondary server 2 supports the application of redo logs in a read-only state, so that the standby database 21 and the primary data can be implemented.
  • the synchronization of the library 11 allows external users to indirectly access the data of the primary database 11 by accessing the standby database 21.
  • the system further includes a plurality of sub-backup servers 3 that are not equal to the main server 1.
  • the sub-backup server 3 there are a plurality of sub-standby databases 31 that are not equal to the main server 1 in the standby environment.
  • the standby database 31 is synchronized with the primary database 11 data on the primary server 1, but only provides read-only services to external users, and no handover is provided.
  • the distributed sub-backup servers 31 provide only read-only permissions to external users without function switching with the primary server 1. Therefore, the sub-standby server 3 can be lower in configuration and performance requirements than the primary server 1. Moreover, read-only database construction costs are lower, thus reducing the cost of the entire system.
  • FIG. 2 it is a flowchart of a data management method according to an embodiment of the present invention, and the method includes the following steps:
  • Step S1 Configure a primary database for internal users to perform data read and write operations on the primary server; for example, an identity module may be set by a software program to distinguish different users. Specifically, the login window and the login account can be set. When the user logs in successfully, the user is identified as an internal user, and the data in the primary database can be maintained or modified to improve data security.
  • Step S2 Configure an alternate database for the standby server to perform data read-only operations only for the external server, and the standby database has at least one switchable environment that is equivalent to the primary database for switching.
  • a read-only interface can be configured or the standby server can be set to read-only through a software program, and maintenance or modification cannot be performed.
  • the primary server can be divided into internal network segments to provide read and write permissions for internal users.
  • the standby server is divided into external network segments, and only external users are allowed read-only permissions.
  • the internal network segment is separated from the external network segment by a firewall. In order to achieve read-write separation, the external user does not directly operate on the primary server, but accesses through the standby server, thereby improving the security of the system.
  • the above-mentioned primary server and standby server can also be composed of several sub-server clusters, and the database in each server uses RAC (Real Application Clusters) technology for high availability. It is also possible to further set a shared cache between each node in the RAC. When one of the nodes is down, several other nodes take over the load, provide parallel processing capability and load sharing of the server runtime, and perform fault tolerance when one of the nodes fails. And recovery processing, can achieve node failover, to ensure that the database 7 * 24 hours of operation.
  • RAC Real Application Clusters
  • the standby server provides a large amount of time in the standby state, is not put into use, and wastes system resources.
  • the embodiment of the present invention provides a read-only standby database to the external user read-only interface, so that the external user can
  • the standby server queries and implements various capabilities such as data mining and statistics.
  • the external user only provides a read-only interface, and the accessed area is limited to the standby server, without affecting the operation of the primary server.
  • the embodiment further includes transmitting the redo log to the standby server by setting the synchronization module on the primary server to synchronize the data between the standby database and the primary database.
  • the database in the primary server and the standby server supports the application of redo logs in the read-only state, so that the synchronization between the standby database and the primary database can be realized, so that external users can indirectly access the data of the primary database by accessing the standby database.
  • the method for data management in this embodiment further includes configuring a plurality of sub-backup servers that are not equal to the primary server, and the server synchronizes with the sub-standby server data.
  • the standby environment has multiple sub-standby databases that are not equal to the primary server. They only provide read-only services to external users, and do not provide switching.
  • the distributed sub-backup servers 3 only provide read-only access to external users without function switching with the primary server 1, therefore, Alternate service
  • the configuration and performance requirements of the device 3 can be lower than that of the primary server 1, and the read-only database construction cost is lower, thereby reducing the cost of the entire system.
  • the present invention provides a data management system and method, which implements functions such as cluster computing, active/standby switchover, disaster tolerance, read and write separation, etc., and fully utilizes spare resources to ensure high availability of the system 7*24 hours. Capabilities, while providing the system's high economy and high security.

Abstract

The present invention relates to a data management system and method. The system includes a main server and a standby server, the main server including a main database available for an internal user to perform data reading/writing operation, the standby server including a standby database only available for an external user to perform data read-only operation, and there is at least one switchable environment equivalent to the main database in the standby database for switching. The present invention can share the system burden, implement the high availability, and can also improve the economy of the system.

Description

数据管理系统及方法 技术领域  Data management system and method
本发明涉及通信领域, 尤其涉及一种数据管理系统及方法。 背景技术  The present invention relates to the field of communications, and in particular, to a data management system and method. Background technique
在通信系统中, 往往需要对海量的用户数据进行存储和管理。 特别是 在大容量的通信系统中, 由于用户数据总量非常大, 而且需要实现的功能 非常多, 有的甚至还需要提供用户接口, 对系统的安全性和健壮性要求较 高。 同时, 不同的应用对数据的要求不同, 例如, 话务应用要求数据库对 数据的响应快, 对系统的实时性要求高, 而查询统计应用则对数据库的大 规模查询和统计效率要求高, 这就要求数据应用需要同时具有联机事务处 理系统和联机分析处理系统的特性。  In communication systems, it is often necessary to store and manage a large amount of user data. Especially in a large-capacity communication system, since the total amount of user data is very large, and there are many functions that need to be implemented, some even need to provide a user interface, which requires high security and robustness of the system. At the same time, different applications have different requirements on data. For example, traffic applications require the database to respond quickly to data, and the real-time requirements of the system are high, while the query statistics application requires high-level query and statistical efficiency of the database. Data applications are required to have both on-line transaction processing systems and online analytical processing systems.
在现有的数据管理系统中, 为保证系统的在线时间和提高用户体验, 往往釆用双服务器的方式来实现高可用, 其中一台备用服务器处于待机状 态, 当主服务器出现宕机, 备用服务器将接管业务。  In the existing data management system, in order to ensure the online time of the system and improve the user experience, a dual server is often used to achieve high availability, wherein one standby server is in a standby state, and when the primary server is down, the standby server will Take over the business.
此种技术可以在一定程度上提高数据系统服务的高可用性, 但是这种 方法中外部用户和内部用户都在主服务器上进行操作, 没有实现数据物理 上的读和写分离, 降低了系统的安全性, 而且备用服务器大量的时间处于 待机状态, 不投入使用, 也浪费了系统资源。 发明内容  This kind of technology can improve the high availability of data system services to a certain extent, but in this method, external users and internal users operate on the main server, which does not realize physical read and write separation of data, which reduces system security. Sex, and the standby server spends a lot of time in standby, not putting it into use, and wasting system resources. Summary of the invention
本发明的主要目的在于提供一种数据管理系统及方法, 旨在减少资源 浪费。  It is a primary object of the present invention to provide a data management system and method for reducing resource waste.
为了达到上述目的, 本发明提出一种数据管理系统, 该系统包括: 主 服务器和备用服务器; 其中, In order to achieve the above object, the present invention provides a data management system, the system comprising: Server and standby server;
主服务器, 包含可供内部用户进行数据读写操作的主数据库; 备用服务器, 包含仅供外部用户进行数据只读操作的备用数据库, 该 备用数据库中存在至少一个和所述主数据库对等的可切换环境, 以供切换。  The primary server includes a primary database for internal users to read and write data; the standby server includes a standby database for external data read-only operations, and at least one of the standby databases is equivalent to the primary database. Switch the environment for switching.
优先的, 所述主服务器设有同步模块, 用于传送重做日志至备用服务 器, 以供备用数据库和主数据库同步数据。  Preferably, the primary server is provided with a synchronization module for transmitting redo logs to the standby server for synchronizing data between the standby database and the primary database.
优先的, 所述主服务器和备用服务器均釆用真正应用集群(RAC )技 术, 每个 RAC节点间共享緩存, 当其中一个节点宕机, 由其他节点接管负 荷。  Preferably, both the primary server and the standby server use Real Application Cluster (RAC) technology, and each RAC node shares a cache. When one of the nodes is down, the other node takes over the load.
优先的, 该系统还包括多个子备用服务器, 所述子备用服务器包含子 备用数据库, 仅用于外部用户的只读服务。  Preferably, the system further includes a plurality of sub-standby servers, the sub-standby servers including sub-standby databases, and only for read-only services of external users.
优先的, 所述主服务器和备用服务器被划分在不同的网段, 用防火墙 隔开。  Preferably, the primary server and the secondary server are divided into different network segments, separated by a firewall.
优先的, 所述主服务器设有用户识别模块, 用于验证用户的身份信息。 优先的, 所述主服务器与备用服务器分别设置在不同的场所, 两者相 隔一安全距离。  Preferably, the primary server is provided with a user identification module for verifying identity information of the user. Preferably, the primary server and the standby server are respectively disposed at different locations, and the two are separated by a safe distance.
本发明还提出一种数据管理的方法, 该方法包括以下步骤:  The invention also proposes a data management method, the method comprising the following steps:
对主服务器配置可供内部用户进行数据读写操作的主数据库; 对备用服务器配置仅供外部用户进行数据只读操作的备用数据库, 该 备用数据库中存在至少一个和所述主数据库对等的可切换环境, 以供切换。  Configuring a primary database for internal users to read and write data to the primary server; configuring a standby database for the standby server to perform read-only operations only for external users, and at least one of the standby databases is equivalent to the primary database. Switch the environment for switching.
优先的, 在执行所有步骤之后还包括: 主服务器传送重做日志至备用 服务器, 以供备用数据库和主数据库同步数据。  Preferably, after performing all the steps, the primary server transmits the redo log to the standby server for synchronizing the data between the standby database and the primary database.
优先的, 所述主服务器和备用服务器均釆用真正应用集群 RAC技术, 每个 RAC节点间共享緩存, 当其中一个节点宕机, 由其他节点接管负荷。 本发明提出的数据管理系统和方法, 通过对数据库架构的设计, 主数 据库提供内部用户的读写权限, 多个备用数据库只提供外部用户的只读权 限实现了对数据的读写分离, 提高了安全性, 而且多个备用服务器分担了 系统负荷, 实现了高可用, 有效利用了系统资源, 由于只读数据库搭建成 本较低, 也提高了系统的经济性。 Preferably, both the primary server and the standby server use the real application cluster RAC technology, and each RAC node shares a cache. When one node is down, the other nodes take over the load. The data management system and method proposed by the present invention, through the design of the database architecture, the main number The database provides read and write permissions for internal users. Multiple standby databases only provide read-only access to external users to achieve read-write separation of data, improve security, and multiple standby servers share system load and achieve high availability. , the effective use of system resources, because of the lower cost of read-only database construction, but also improve the economics of the system.
附图说明 DRAWINGS
图 1是本发明一实施例所述数据管理系统结构示意图;  1 is a schematic structural diagram of a data management system according to an embodiment of the present invention;
图 2是本发明一实施例所述数据管理方法流程示意图。 为了使本发明的技术方案更加清楚、 明了, 下面将结合附图作进一步 详述。  2 is a schematic flow chart of a data management method according to an embodiment of the present invention. In order to make the technical solutions of the present invention clearer and clearer, the following will be further described in detail with reference to the accompanying drawings.
具体实施方式 detailed description
应当理解, 此处所描述的具体实施例仅仅用以解释本发明, 并不用于 限定本发明。  It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
图 1是本发明一实施例数据管理系统结构示意图。 如图 1所示, 所述 系统包括主服务器 1和备用服务器 2, 其中主服务器 1上运行主数据库 11 , 备用服务器 2上运行一组备用数据库 21 ,在备用数据库 21中有一个与主数 据库 11对等的可切换环境, 当主数据库 11 出现故障, 即可将业务切换至 备用服务器 2以保证系统的安全性。 主服务器 1和备用服务器 2可处于相 隔较远的不同场所之中, 相隔一安全距离, 分别建立两套或多套功能相同 的 IT系统, 互相之间可以进行健康状态监视和功能切换, 当一处系统因意 外停止工作时, 整个数据库系统可以切换到另一处, 使得该系统功能可以 继续正常工作, 以实现容灾。 其中, 主服务器 1和备用服务器 2可由若干个子服务器集群组成, 每 个服务器中的数据库均釆用真正应用集群( RAC, Real Application Clusters ) 技术, 实现高可用性。 1 is a schematic structural diagram of a data management system according to an embodiment of the present invention. As shown in FIG. 1, the system includes a primary server 1 and a standby server 2, wherein the primary server 1 runs a primary database 11, and the standby server 2 runs a set of standby databases 21, and the standby database 21 has a primary database 11 In a peer-to-peer switchable environment, when the primary database 11 fails, the service can be switched to the standby server 2 to ensure the security of the system. The main server 1 and the standby server 2 can be located in different places far apart from each other, and separated by a safe distance, respectively, two or more sets of IT systems with the same function can be established, and health status monitoring and function switching can be performed between each other. When the system stops working unexpectedly, the entire database system can be switched to another location, so that the system function can continue to work normally to achieve disaster tolerance. The primary server 1 and the secondary server 2 may be composed of a plurality of sub-server clusters, and the databases in each server adopt real application cluster (RAC) technology to achieve high availability.
进一步地, RAC中的每个节点间共享緩存, 当其中一个节点宕机, 有 其他几个节点接管负荷, 提供服务器运行时的并行处理能力及均分负载, 当其中一个节点故障时进行容错和恢复处理, 可以实现节点的失败切换, 保证数据库 7*24小时运行。  Further, each node in the RAC shares a cache. When one of the nodes is down, several other nodes take over the load, providing parallel processing capability and load sharing of the server runtime, and performing fault tolerance when one of the nodes fails. Recovery processing, can achieve node failover, to ensure that the database 7 * 24 hours of operation.
由于备用服务器 2 大量的时间处于待机状态, 不投入使用, 浪费了系 统资源, 为了充分利用备用服务器 2的资源, 本发明实施例备用数据库 21 提供给外部用户只读接口, 使外部用户可以在备用服务器 2查询和实现数 据挖掘、 统计等多种能力。 同时, 由于对外部用户只提供只读接口, 访问 的区域局限在备用服务器 2, 不影响主服务器 1的运行, 减少了用户访问主 服务器 1篡改数据的可能, 提高了系统的安全性。  In the embodiment of the present invention, the standby database 21 provides a read-only interface to the external user, so that the external user can be in standby, because the backup server 2 is in a standby state and is not in use, and the system resources are wasted. Server 2 queries and implements various capabilities such as data mining and statistics. At the same time, since only the read-only interface is provided to the external user, the access area is limited to the standby server 2, which does not affect the operation of the main server 1, and reduces the possibility of the user accessing the main server 1 tampering with the data, thereby improving the security of the system.
由于主数据库 11提供内部用户的读写接口, 用户可对主服务器 1拥有 读写权限以进行数据的更新和维护, 在一实施例中, 为了保证数据的安全 性, 在主服务器 1上设有用户识别模块, 用于验证用户的身份信息。 例如, 该识别模块可提供登录窗口和登录账号, 以便验证用户是否为内部用户。 此外, 还可将主服务器 1 划分在内部网段, 提供内部用户的读写权限, 将 备用服务器 2划分在外部网段, 只提供外部用户只读权限, 将内部网段与 外部网段用防火墙隔开, 以实现读写分离, 由于外部用户不直接对主服务 器 1进行操作, 而是通过备用服务器 2进行访问, 从而提高了系统的安全 性。  Since the main database 11 provides the read/write interface of the internal user, the user can have read and write permissions to the main server 1 for data update and maintenance. In an embodiment, in order to ensure data security, the main server 1 is provided. A user identification module, configured to verify the identity information of the user. For example, the identification module can provide a login window and a login account to verify whether the user is an internal user. In addition, the primary server 1 can be divided into internal network segments to provide read and write permissions for internal users, and the secondary server 2 can be divided into external network segments. Only external users can read-only permissions, and internal network segments and external network segments can be used as firewalls. Separated to achieve read-write separation, since the external user does not directly operate the main server 1, but accesses through the standby server 2, thereby improving the security of the system.
主服务器 1设有同步模块, 用于传送重做日志至备用服务器 2, 以供备 用数据库 21和主数据库 11 同步数据。 主服务器 1和备用服务器 2中数据 库支持在只读状态下应用重做日志, 因此可以实现备用数据库 21和主数据 库 11的同步, 从而使外部用户可以通过访问备用数据库 21 间接的达到获 取主数据库 11数据信息的能力。 The main server 1 is provided with a synchronization module for transmitting redo logs to the standby server 2 for synchronizing data between the standby database 21 and the main database 11. The database in the primary server 1 and the secondary server 2 supports the application of redo logs in a read-only state, so that the standby database 21 and the primary data can be implemented. The synchronization of the library 11 allows external users to indirectly access the data of the primary database 11 by accessing the standby database 21.
在本实施例中, 系统还设有若干个与主服务器 1 不对等的子备用服务 器 3, 在子备用服务器 3中,备用环境存在多个与主服务器 1不对等的子备 用数据库 31 ,该子备用数据库 31与主服务器 1上的主数据库 11数据同步, 但仅提供对外部用户的只读服务, 不提供切换。 如图 1 所示, 分布的若干 个子备用服务器 31只提供给外部用户只读权限而不与主服务器 1进行功能 切换, 因此, 子备用服务器 3在配置和性能要求上可低于主服务器 1 , 而且 只读数据库搭建成本较低, 因而降低了整个系统的成本。 如图 2所示, 为本发明一实施例中数据管理方法的流程图, 该方法包 括以下步骤:  In this embodiment, the system further includes a plurality of sub-backup servers 3 that are not equal to the main server 1. In the sub-backup server 3, there are a plurality of sub-standby databases 31 that are not equal to the main server 1 in the standby environment. The standby database 31 is synchronized with the primary database 11 data on the primary server 1, but only provides read-only services to external users, and no handover is provided. As shown in FIG. 1, the distributed sub-backup servers 31 provide only read-only permissions to external users without function switching with the primary server 1. Therefore, the sub-standby server 3 can be lower in configuration and performance requirements than the primary server 1. Moreover, read-only database construction costs are lower, thus reducing the cost of the entire system. As shown in FIG. 2, it is a flowchart of a data management method according to an embodiment of the present invention, and the method includes the following steps:
步骤 S1:对主服务器配置可供内部用户进行数据读写操作的主数据库; 例如, 可通过软件程序设置身份识别模块, 以区别不同的用户。 具体 来说, 可设置登录窗口和登录账号, 在用户登录成功时, 识别其为内部用 户, 可对主数据库中的数据进行维护或修改等操作, 以提高数据的安全性。  Step S1: Configure a primary database for internal users to perform data read and write operations on the primary server; for example, an identity module may be set by a software program to distinguish different users. Specifically, the login window and the login account can be set. When the user logs in successfully, the user is identified as an internal user, and the data in the primary database can be maintained or modified to improve data security.
步骤 S2: 对备用服务器配置仅供外部用户进行数据只读操作的备用数 据库, 该备用数据库中存在至少一和所述主数据库对等的可切换环境, 以 供切换。  Step S2: Configure an alternate database for the standby server to perform data read-only operations only for the external server, and the standby database has at least one switchable environment that is equivalent to the primary database for switching.
本步骤中, 对于备用服务器, 可配置一只读接口或通过软件程序设置 其中的备用服务器只读, 而不能进行维护或修改等操作。  In this step, for the standby server, a read-only interface can be configured or the standby server can be set to read-only through a software program, and maintenance or modification cannot be performed.
此外, 还可将主服务器划分在内部网段, 提供内部用户的读写权限, 将备用服务器划分在外部网段, 只提供外部用户只读权限, 将内部网段与 外部网段用防火墙隔开, 以实现读写分离, 由于外部用户不直接对主服务 器进行操作, 而是通过备用服务器进行访问, 从而提高了系统的安全性。  In addition, the primary server can be divided into internal network segments to provide read and write permissions for internal users. The standby server is divided into external network segments, and only external users are allowed read-only permissions. The internal network segment is separated from the external network segment by a firewall. In order to achieve read-write separation, the external user does not directly operate on the primary server, but accesses through the standby server, thereby improving the security of the system.
为了进一步保障数据的安全性, 还可设置主服务器和备用服务器处于 相隔较远的不同场所之中, 相隔一安全距离, 分别建立两套或多套功能相 同的 IT系统, 互相之间可以进行健康状态监视和功能切换, 当一处系统因 意外停止工作时, 整个数据库系统可以切换到另一处, 使得该系统功能可 以继续正常工作, 以实现容灾。 To further secure data, you can also set the primary and standby servers to be in Two or more sets of IT systems with the same function are separated from each other in different places separated by a long distance. Health status monitoring and function switching can be performed between each other. When a system stops working due to an accident, the whole The database system can be switched to another location so that the system functions can continue to work properly to achieve disaster tolerance.
上述主服务器和备用服务器还可由若干个子服务器集群组成, 每个服 务器中的数据库均釆用 RAC ( Real Application Clusters, 真正应用集群)技 术, 实现高可用性。 还可进一步设置 RAC中的每个节点间共享緩存, 当其 中一个节点宕机, 有其他几个节点接管负荷, 提供服务器运行时的并行处 理能力及均分负载, 当其中一个节点故障时进行容错和恢复处理, 可以实 现节点的失败切换, 保证数据库 7*24小时运行。  The above-mentioned primary server and standby server can also be composed of several sub-server clusters, and the database in each server uses RAC (Real Application Clusters) technology for high availability. It is also possible to further set a shared cache between each node in the RAC. When one of the nodes is down, several other nodes take over the load, provide parallel processing capability and load sharing of the server runtime, and perform fault tolerance when one of the nodes fails. And recovery processing, can achieve node failover, to ensure that the database 7 * 24 hours of operation.
由于备用服务器大量的时间处于待机状态, 不投入使用, 浪费了系统 资源, 为了充分利用备用服务器的资源, 本发明实施例通过设置只读的备 用数据库提供给外部用户只读接口, 使外部用户可以在备用服务器查询和 实现数据挖掘、 统计等多种能力, 同时外部用户只提供只读接口, 访问的 区域局限在备用服务器, 从而不影响主服务器的运行。  The standby server provides a large amount of time in the standby state, is not put into use, and wastes system resources. In order to make full use of the resources of the standby server, the embodiment of the present invention provides a read-only standby database to the external user read-only interface, so that the external user can The standby server queries and implements various capabilities such as data mining and statistics. At the same time, the external user only provides a read-only interface, and the accessed area is limited to the standby server, without affecting the operation of the primary server.
本实施例还包括通过在主服务器设置同步模块, 传送重做日志至备用 服务器, 以供备用数据库和主数据库同步数据。 主服务器和备用服务器中 数据库支持在只读状态下应用重做日志, 因此可以实现备用数据库和主数 据库的同步, 从而使外部用户可以通过访问备用数据库间接的达到获取主 数据库数据信息的能力。  The embodiment further includes transmitting the redo log to the standby server by setting the synchronization module on the primary server to synchronize the data between the standby database and the primary database. The database in the primary server and the standby server supports the application of redo logs in the read-only state, so that the synchronization between the standby database and the primary database can be realized, so that external users can indirectly access the data of the primary database by accessing the standby database.
本实施例数据管理的方法还包括配置多个与主服务器不对等的子备用 服务器, 服务器与子备用服务器数据同步, 在子备用服务器中, 备用环境 存在多个与主服务器不对等的子备用数据库, 它们仅提供对外部用户的只 读服务, 不提供切换, 如图 1所示, 分布的若干个子备用服务器 3只提供 给外部用户只读权限而不与主服务器 1 进行功能切换, 因此, 子备用服务 器 3在配置和性能要求上可低于主服务器 1 ,而且只读数据库搭建成本较低, 因而降低了整个系统的成本。 The method for data management in this embodiment further includes configuring a plurality of sub-backup servers that are not equal to the primary server, and the server synchronizes with the sub-standby server data. In the sub-standby server, the standby environment has multiple sub-standby databases that are not equal to the primary server. They only provide read-only services to external users, and do not provide switching. As shown in Figure 1, the distributed sub-backup servers 3 only provide read-only access to external users without function switching with the primary server 1, therefore, Alternate service The configuration and performance requirements of the device 3 can be lower than that of the primary server 1, and the read-only database construction cost is lower, thereby reducing the cost of the entire system.
综上所述, 本发明提供的一种数据管理系统及方法, 实现了集群计算、 主备切换、 容灾、 读写分离等功能, 充分利用备用资源, 保证了系统 7*24 小时的高可用能力, 同时提供了系统的高经济性和高安全性。  In summary, the present invention provides a data management system and method, which implements functions such as cluster computing, active/standby switchover, disaster tolerance, read and write separation, etc., and fully utilizes spare resources to ensure high availability of the system 7*24 hours. Capabilities, while providing the system's high economy and high security.
以上所述仅为本发明的优选实施例, 并非因此限制本发明的专利范围, 凡是利用本发明说明书及附图内容所作的等效结构或流程变换, 或直接或 间接运用在其它相关的技术领域, 均同理包括在本发明的专利保护范围内。  The above is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention, and equivalent structural or process changes made by the present specification and drawings may be directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

权利要求书 Claim
1、 一种数据管理系统, 其特征在于, 该系统包括: 主服务器和备用服 务器; 其中,  A data management system, the system comprising: a primary server and a standby server; wherein
主服务器, 包含可供内部用户进行数据读写操作的主数据库; 备用服务器, 包含仅供外部用户进行数据只读操作的备用数据库, 所 述备用数据库中存在至少一个和所述主数据库对等的可切换环境。  a primary server, including a primary database for internal users to perform data read and write operations; an alternate server including a standby database for external data read-only operations, wherein at least one of the standby databases is peered with the primary database Switchable environment.
2、 根据权利要求 1所述的数据管理系统, 其特征在于, 所述主服务器 设有同步模块, 用于传送重做日志至备用服务器, 供备用数据库和主数据 库同步数据。  2. The data management system according to claim 1, wherein the primary server is provided with a synchronization module for transmitting redo logs to the standby server for synchronizing data between the standby database and the primary database.
3、 根据权利要求 1或 2所述的数据管理系统, 其特征在于, 所述主服 务器和备用服务器均釆用真正应用集群(RAC )技术, 每个 RAC节点间共 享緩存, 当其中一个节点宕机, 由其他节点接管负荷。  3. The data management system according to claim 1 or 2, wherein the primary server and the standby server both use a real application cluster (RAC) technology, and each of the RAC nodes shares a cache, and one of the nodes 宕Machine, taking over the load by other nodes.
4、 根据权利要求 3所述的数据管理系统, 其特征在于, 该系统还包括 多个子备用服务器, 所述子备用服务器包含子备用数据库, 仅用于外部用 户的只读服务。  4. The data management system according to claim 3, wherein the system further comprises a plurality of sub-backup servers, the sub-standby servers comprising sub-standby databases, and only for read-only services of external users.
5、 根据权利要求 4所述的数据管理系统, 其特征在于, 所述主服务器 和备用服务器被划分在不同的网段, 用防火墙隔开。  The data management system according to claim 4, wherein the primary server and the standby server are divided into different network segments and are separated by a firewall.
6、 根据权利要求 5所述的数据管理系统, 其特征在于, 所述主服务器 设有用户识别模块, 用于验证用户的身份信息。  The data management system according to claim 5, wherein the main server is provided with a user identification module for verifying identity information of the user.
7、 根据权利要求 6所述的数据管理系统, 其特征在于, 所述主服务器 与备用服务器分别设置在不同的场所, 两者相隔一安全距离。  7. The data management system according to claim 6, wherein the primary server and the standby server are respectively disposed at different locations, and the two are separated by a safe distance.
8、 一种数据管理方法, 其特征在于, 该方法包括以下步骤: 对主服务器配置可供内部用户进行数据读写操作的主数据库; 对备用服务器配置仅供外部用户进行数据只读操作的备用数据库, 所 述备用数据库中存在至少一个和所述主数据库对等的可切换环境。 8. A data management method, characterized in that the method comprises the steps of: configuring a primary database for an internal user to perform data read and write operations on the primary server; and configuring the standby server for an external user only for data read-only operations. a database, wherein at least one switchable environment that is peered with the primary database exists in the standby database.
9、 根据权利要求 8所述的数据管理方法, 其特征在于, 在执行所有步 骤之后还包括: 主服务器传送重做日志至备用服务器, 供备用数据库和主 数据库同步数据。 9. The data management method according to claim 8, wherein after performing all the steps, the method further comprises: the primary server transmitting the redo log to the standby server, and synchronizing the data with the standby database and the primary database.
10、 根据权利要求 8所述的数据管理方法, 其特征在于, 所述主服务 器和备用服务器均釆用真正应用集群 RAC技术, 每个 RAC节点间共享緩 存, 当其中一个节点宕机, 由其他节点接管负荷。  10. The data management method according to claim 8, wherein the primary server and the standby server both use a real application cluster RAC technology, and each of the RAC nodes shares a cache, and when one of the nodes is down, the other The node takes over the load.
PCT/CN2011/076322 2011-04-28 2011-06-24 Data management system and method WO2012145963A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110108949XA CN102761528A (en) 2011-04-28 2011-04-28 System and method for data management
CN201110108949.X 2011-04-28

Publications (1)

Publication Number Publication Date
WO2012145963A1 true WO2012145963A1 (en) 2012-11-01

Family

ID=47055850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/076322 WO2012145963A1 (en) 2011-04-28 2011-06-24 Data management system and method

Country Status (2)

Country Link
CN (1) CN102761528A (en)
WO (1) WO2012145963A1 (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103019875B (en) * 2012-12-19 2015-12-09 北京世纪家天下科技发展有限公司 The method of the two main transformation of a kind of fulfillment database and device
CN103152381B (en) * 2013-01-07 2016-06-29 北京奇虎科技有限公司 A kind of method that browser crash data is processed and server system
CN104348842B (en) * 2013-07-23 2019-03-15 腾讯科技(深圳)有限公司 Distributed memory system method for routing, routing management server and system
CN104426968B (en) * 2013-08-30 2019-05-24 腾讯科技(深圳)有限公司 Data managing method and device
JP6327001B2 (en) * 2014-06-19 2018-05-23 富士ゼロックス株式会社 Image processing apparatus and program
CN104537046B (en) * 2014-12-24 2018-09-11 北京奇虎科技有限公司 Supplementing Data method and apparatus
CN105991565B (en) * 2015-02-05 2019-01-25 阿里巴巴集团控股有限公司 Method, system and the database proxy server of read and write abruption
CN106469166B (en) * 2015-08-18 2019-09-06 阿里巴巴集团控股有限公司 A kind of information processing method and device
CN106651483A (en) * 2015-10-30 2017-05-10 宁波轩悦行电动汽车服务有限公司 Master-slave copy configuration database and electric car periodic leasing system and method
CN105607969A (en) * 2015-12-18 2016-05-25 深圳市金蝶友商电子商务服务有限公司 Failure period data access recovery system and method
CN106383861A (en) * 2016-08-31 2017-02-08 网易(杭州)网络有限公司 Data synchronization method and apparatus used for databases
CN108241656A (en) * 2016-12-23 2018-07-03 深圳市优朋普乐传媒发展有限公司 A kind of data read-write method and device
CN107066354B (en) * 2017-04-18 2021-01-05 中国银联股份有限公司 Database switching method, master server and slave server
CN107273419B (en) * 2017-05-11 2021-04-23 深圳市博世创兴科技有限公司 System data reading method and device
CN109145053B (en) 2018-08-01 2021-03-23 创新先进技术有限公司 Data processing method and device, client and server
CN109032803B (en) 2018-08-01 2021-02-12 创新先进技术有限公司 Data processing method and device and client
CN109981569B (en) * 2019-02-18 2022-01-11 平安科技(深圳)有限公司 Network system access method, device, computer equipment and readable storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141282A (en) * 2006-09-07 2008-03-12 中兴通讯股份有限公司 Network management system and its management method
CN101753608A (en) * 2008-12-09 2010-06-23 中国移动通信集团公司 Dispatching method and system of distributed system
CN102033912A (en) * 2010-11-25 2011-04-27 北京北纬点易信息技术有限公司 Distributed-type database access method and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101141282A (en) * 2006-09-07 2008-03-12 中兴通讯股份有限公司 Network management system and its management method
CN101753608A (en) * 2008-12-09 2010-06-23 中国移动通信集团公司 Dispatching method and system of distributed system
CN102033912A (en) * 2010-11-25 2011-04-27 北京北纬点易信息技术有限公司 Distributed-type database access method and system

Also Published As

Publication number Publication date
CN102761528A (en) 2012-10-31

Similar Documents

Publication Publication Date Title
WO2012145963A1 (en) Data management system and method
US11899684B2 (en) System and method for maintaining a master replica for reads and writes in a data store
US11894972B2 (en) System and method for data replication using a single master failover protocol
US10929428B1 (en) Adaptive database replication for database copies
US10929240B2 (en) System and method for adjusting membership of a data replication group
CN106341454B (en) Across computer room distributed data base management system (DDBMS) mostly living and method
US6421688B1 (en) Method and apparatus for database fault tolerance with instant transaction replication using off-the-shelf database servers and low bandwidth networks
US10248704B2 (en) System and method for log conflict detection and resolution in a data store
EP2281240B1 (en) Maintaining data integrity in data servers across data centers
CN107465721B (en) Global load balancing method and system based on double-active architecture and scheduling server
US9489434B1 (en) System and method for replication log branching avoidance using post-failover rejoin
US9450700B1 (en) Efficient network fleet monitoring
CN110083662B (en) Double-living framework construction method based on platform system
US8984328B2 (en) Fault tolerance in a parallel database system
US20150120658A1 (en) System and method for splitting a replicated data partition
CN110224871A (en) A kind of high availability method and device of Redis cluster
US9258363B2 (en) Data cube high availability
US10708379B1 (en) Dynamic proxy for databases
CN106254161A (en) The quickly detection of node failure based on HDFS and restoration methods and system
Anderson et al. Local recovery for high availability in strongly consistent cloud services
US11921699B1 (en) Lease-based consistency management for handling failover in a database
KR101610048B1 (en) Method, apparatus and computer program for managing repository of software defined network controller
CN111831743B (en) Block chain data storage system and method based on cloud storage
US7509302B2 (en) Device, method and program for providing a high-performance storage access environment while issuing a volume access request including an address of a volume to access
CN114760302B (en) Private cloud platform architecture suitable for wisdom power plant

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11864531

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11864531

Country of ref document: EP

Kind code of ref document: A1