WO2018113543A1 - 主备数据库的管理方法、系统及其设备 - Google Patents

主备数据库的管理方法、系统及其设备 Download PDF

Info

Publication number
WO2018113543A1
WO2018113543A1 PCT/CN2017/115392 CN2017115392W WO2018113543A1 WO 2018113543 A1 WO2018113543 A1 WO 2018113543A1 CN 2017115392 W CN2017115392 W CN 2017115392W WO 2018113543 A1 WO2018113543 A1 WO 2018113543A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
lock
primary
primary database
backup
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.)
Ceased
Application number
PCT/CN2017/115392
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
阳振坤
黄贵
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to MYPI2019003464A priority Critical patent/MY199572A/en
Priority to EP17884001.3A priority patent/EP3561694B1/en
Priority to JP2019533442A priority patent/JP6905161B2/ja
Priority to KR1020197021325A priority patent/KR102142233B1/ko
Publication of WO2018113543A1 publication Critical patent/WO2018113543A1/zh
Priority to US16/394,315 priority patent/US10592361B2/en
Priority to PH12019501392A priority patent/PH12019501392A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/2041—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 with more than one idle spare processing component
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/142—Reconfiguring to eliminate the error
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/2025—Failover techniques using centralised failover control functionality
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/2033—Failover techniques switching over of hardware resources
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/2043—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 where the redundant components share a common memory address space
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21—Design, administration or maintenance of databases
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2308—Concurrency control
    • G06F16/2336—Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
    • G06F16/2343—Locking methods, e.g. distributed locking or locking implementation details
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80—Database-specific techniques
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/825—Indexing scheme relating to error detection, to error correction, and to monitoring the problem or solution involving locking

Definitions

  • the present application relates to the field of information security technologies, and in particular, to a method, system, and device for managing a primary and secondary database.
  • the database is a key infrastructure in the fields of finance, commerce, transportation, and the whole society.
  • the continuous availability of the database is a guarantee for the sustainable service to users in the fields of finance and commerce.
  • the database In order to avoid the failure of a single database and improve the availability of the database, the database usually adopts the primary and backup configurations. When the primary database fails, it switches to the backup database to continue the service.
  • the active and standby databases can be switched by means of automatic switching, that is, the monitoring system is deployed to the primary database, and once the primary data path is found to be abnormal, an alarm is issued and a command is issued to switch the primary and secondary databases.
  • the primary database may be switched when there is no failure due to misjudgment, or the primary database fails but does not switch, thereby affecting the normal service for the user.
  • the purpose of the present application is to solve at least one of the above technical problems to some extent.
  • the first object of the present application is to propose a management method for a primary and secondary database, which determines the lock held by the primary database before the primary database does not send a renewal request before the lock held by the primary database expires. If it fails, the user cannot be served normally, so that a backup data is selected as the new primary database, which improves the switching rate and accuracy of the primary and secondary databases.
  • a second object of the present application is to propose a lock arbitration server.
  • a third object of the present application is to propose a primary database server.
  • a fourth object of the present application is to propose a backup database server.
  • the fifth object of the present application is to propose a management system for a primary and secondary database.
  • the method for managing the primary and secondary databases of the first aspect of the present application includes: determining whether the lock held by the primary database expires, wherein the primary database and the backup database share the lock; If the lock held by the primary database has expired, it is determined whether a renewal request of the primary database is received; if the renewal request of the primary database is not received, one of the backup databases is selected as a new one. The primary database and control the primary database to switch to the backup database.
  • the management method of the primary and secondary databases in the embodiment of the present application determines whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, it is determined whether the primary database renewal request is received, if not Upon receiving the renewal request, a new primary database is selected from the backup database and the primary database is controlled to be switched to the backup database. The method does not send a renewal request before the primary database expires the lock held by the primary database, and then determines that the lock held by the primary database is invalid, and cannot provide services to the user normally, thereby selecting a backup data to become a new primary database, thereby improving The switching rate and accuracy of the primary and secondary databases.
  • management method of the primary and secondary databases in the embodiment of the present application further has the following additional technical features:
  • the method further includes: sending a lock expiration notification to the backup database; receiving the backup data according to the lock to
  • selecting one of the backup databases as the primary database is further used to: select a backup database with the earliest reception time as the primary database.
  • the primary database has a higher priority than the backup database.
  • the update period of the lock is T1, wherein the primary database sends a lock request for querying the state of the lock in a period T2, and the backup database sends the query for the lock in a period T3.
  • the backup database includes a hot standby database and a disaster recovery database, wherein the primary database and the hot standby database are located in the same data center, and the primary database and the disaster recovery database are located. Different data centers.
  • the method further includes: receiving a lock request sent by the original primary database, and controlling the lock to be held by the original primary database after the lock expires
  • the original primary database is restored to the primary database, and the current primary database is restored to the backup database.
  • the method further includes: continuing to determine whether the lock held by the current primary database is expired; if the current primary database holds If the lock has expired, it is determined whether the lock request of the original primary database, the current primary database, and other backup databases is received; if the lock request of the original primary database is received, the original primary database is restored to the primary database.
  • Recovering the current database as a backup database if the lock request of the original primary database is not received, and receiving a lock request of the current primary database and other backup databases, maintaining the current primary database as a primary database; If the lock request of the original primary database and the current primary database is not received, and a lock request of another backup database is received, one of the other backup databases is selected as a primary database, and the current primary data is restored to
  • the lock arbitration server of the second aspect of the present application includes: a first determining module, configured to determine whether a lock held by the primary database is expired, wherein the primary database and the backup database share the a second determining module, configured to determine, when the lock held by the primary database has expired, whether to receive a renewal request of the primary database; the first processing module, configured to not receive the When the primary database is renewed, one of the backup databases is selected as the new primary database, and the primary database is controlled to be switched to the backup database.
  • the lock arbitration server of the embodiment of the present application it is determined whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, it is determined whether the persistent lock request of the primary database is received, if not received. To renew the lock request, select a new primary database from the backup database and control the primary database to switch to the backup database. The server does not send a renewal request before the lock of the primary database expires, and then determines that the lock held by the primary database is invalid, and cannot provide services for the user, thereby selecting a backup data to become a new primary database, thereby improving The switching rate and accuracy of the primary and secondary databases.
  • lock arbitration server of the embodiment of the present application has the following additional distinguishing technical features:
  • the first processing module is configured to: select a backup database with the earliest receiving time as the primary database.
  • the primary database has a higher priority than the backup database.
  • the update period of the lock is T1
  • the primary database sends a lock request for querying the state of the lock in a period T2
  • the backup database sends a status of querying the lock in a period T3.
  • Lock request where T2 is less than T1 and T3 is greater than or equal to T1.
  • the backup database includes a hot standby database and a disaster recovery database, wherein the primary database and the hot standby database are located in the same data center, and the primary database and the disaster recovery database are located. Different data centers.
  • the method further includes: a first receiving module, configured to receive, after the original primary database is restored, a lock request sent by the original primary database; the first processing module is further configured to: After the period, the lock is controlled by the original primary database to restore the original primary database to the primary database, and the current primary database is restored to the backup database.
  • the first determining module is further configured to continue to determine whether a lock held by the current primary database is expired; and the second determining module is further configured to be in the current primary database.
  • the held lock has expired, it is judged whether the lock request of the original primary database, the current primary database and other backup databases is received; and the second processing module is configured to: when receiving the lock request of the original primary database, The original primary database is restored to the primary database, and the current database is restored to the backup database.
  • the third processing module is configured to receive the lock request of the original primary database and receive the current primary database and other backup databases.
  • the current primary database is maintained as a primary database; and a fourth processing module is configured to: when the lock request of the original primary database and the current primary database is not received, and a lock request of another backup database is received, Select one of the other backup databases as the primary database and restore the current primary data to the backup database.
  • the primary database server of the third aspect of the present application includes: a second sending module, configured to send a renewal request to the lock arbitration server when the held lock expires, so that the lock arbitration server When the renewal request is not received, one of the backup databases is selected as the new primary database; and the switching module is configured to control the primary database to be switched to the backup database.
  • the primary data server sends a renewal request to the lock arbitration server when the held lock expires, so that when the lock arbitration server does not receive the renewal request, one of the backup databases is selected as the new database.
  • the primary database is switched to the backup database.
  • the primary database is switched to the backup database, and a backup data is selected to become the new primary database, which improves the switching rate and accuracy of the primary and secondary databases, and ensures the database. Normally providing services to users, improving the user experience.
  • the primary data server of the embodiment of the present application has the following additional technical features:
  • the primary database has a higher priority than the backup database.
  • the update period of the lock is T1, wherein the primary database server sends a lock request for querying the state of the lock in a period T2, and the backup database sends the query according to the period T3.
  • the backup database includes a hot standby database and a disaster recovery database, wherein the primary database and the hot standby database are located in the same data center, and the primary database and the disaster recovery database are located. Different data centers.
  • the primary database server further includes:
  • a third sending module configured to send a lock request to the lock arbitration server after the original primary database is restored, so that the lock arbitration server receives the lock request sent by the original primary database, and controls the lock after the lock expires
  • the lock is held by the original primary database to restore the original primary database to the primary database, and the current primary database is restored to the backup database.
  • the backup database server of the fourth aspect of the present application includes: a fourth sending module, configured to send a lock request to the lock arbitration server; and a second receiving module, configured to receive the lock sent by the lock arbitration server a confirmation message; a fifth processing module, configured to switch to a new primary database according to the lock confirmation message.
  • the lock request is sent to the lock arbitration server, and the lock confirmation message sent by the lock arbitration server is received, and the new primary database is switched according to the lock confirmation message.
  • the backup database server selects a backup data to become the new primary database, and switches the primary database to the backup database, thereby improving the switching rate and accuracy of the primary and secondary databases, and ensuring the guarantee.
  • the database normally provides services to users, which improves the user experience.
  • the backup database server includes: a third receiving module, configured to receive a lock expiration notification sent by the lock arbitration server after determining that the lock held by the primary database has expired,
  • the fourth sending module sends a lock request to the lock arbitration server according to the lock request sent by the lock expiration notification.
  • the primary database has a higher priority than the backup database.
  • the backup database includes a hot standby database and a disaster recovery database, wherein the primary database and the hot standby database are located in the same data center, and the primary database and the disaster recovery database are located. Different data centers.
  • the backup database server further includes: a sixth processing module, configured to receive, by the lock arbitration server, a lock request sent by the original primary database, and control the After the lock is held by the original primary database to restore the original primary database to the primary database, the current primary database is controlled to be restored to the backup database.
  • a sixth processing module configured to receive, by the lock arbitration server, a lock request sent by the original primary database, and control the After the lock is held by the original primary database to restore the original primary database to the primary database, the current primary database is controlled to be restored to the backup database.
  • the management system of the primary and secondary databases of the fifth aspect of the present application includes the lock arbitration server according to the second embodiment of the present application, and the primary database server of the third aspect of the present application, Applying to the backup database server described in the fourth aspect of the embodiment.
  • FIG. 1 is a flowchart of a method for managing a primary and secondary database according to an embodiment of the present application
  • FIGS. 2(a) to 2(c) are diagrams of deployment of a primary and secondary database according to an embodiment of the present application
  • FIG. 3 is a flowchart of a method for managing a primary and secondary database according to another embodiment of the present application.
  • FIG. 4 is a flowchart of a method for managing a primary and secondary database according to still another embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a lock arbitration server according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a lock arbitration server according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a lock arbitration server according to another embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a lock arbitration server according to still another embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a primary database server according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a primary database server according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a backup database according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a backup database server according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a backup database server according to another embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a management system of a primary and secondary database according to an embodiment of the present application.
  • FIG. 1 is a flowchart of a method for managing a primary and secondary database according to an embodiment of the present application. As shown in FIG. 1, the management method of the primary and secondary databases includes:
  • S110 Determine whether the lock held by the primary database expires, wherein the primary database and the backup database share the lock.
  • the switching between the active and standby databases for example, the switching of the primary database without failure or the failure of the primary data is not switched.
  • an external arbitration mechanism is introduced, and the arbitration mechanism is used to accurately determine whether the primary database has failed, thereby accurately controlling the switching between the primary and secondary databases.
  • the foregoing external arbitration mechanism may be various according to the specific application scenario.
  • the embodiment of the present application describes the lock service in detail by using the arbitration mechanism.
  • the primary data and the backup database share a lock
  • both the primary database and the backup database compete for the ownership of the lock
  • the database that acquires the lock is the primary database, and since the lock has a mutually exclusive feature, only one database can be available at a time.
  • the main database since the lock has a mutually exclusive feature, only one database can be available at a time.
  • the primary database needs to constantly update the lock to extend its validity before the expiration of the validity period (usually tens of seconds). If the primary database fails or is upgraded and maintained during the validity period, the validity period of the extended lock for the lock cannot be completed, so that other backup databases grab the lock and upgrade to the primary database, and the primary database is demoted to the backup database. .
  • the primary database in order to protect the primary database from being changed, it is prevented from being switched to the backup database when there is no failure or upgrade and maintenance operations, and the priority of the primary database is higher than the priority of the backup database. Ensure that the database holding the lock is the primary database without the failure of the primary database or the operation of upgrading and maintaining.
  • the configuration of the active/standby database may be multiple, for example, a primary-to-standby deployment mode, or a primary-to-standby deployment mode.
  • the deployment mode of the active and standby databases is described as an example of the two sites in the two places, that is, the backup database includes a hot standby database and a disaster recovery database, where the primary database and the hot standby database are located.
  • the primary database and the disaster recovery database are located in different data centers.
  • the re-locking request of the primary database is not received, it indicates that the primary database network or power is faulty, and the update of the lock cannot be completed, so that in order to provide services for the user normally, one of the backup databases is selected as the new primary.
  • one of the backup databases may be selected as the primary database in different manners.
  • the backup database can actively query the primary database when the lock expires, whether to issue a renewal request to extend the validity of the lock. If not, the backup database issues a lock request, so that the lock can be quickly acquired and switched. Become the master database.
  • FIG. 2(a)-FIG. 2(b) in the database deployment manner, that is, FIG. 2
  • two databases are deployed at the same time in the same room and the hot standby room.
  • a separate database is deployed in the remote disaster recovery room.
  • the external arbitration mechanism service GOS itself can be deployed across the ground, can accommodate the complete failure of the equipment room and the layout area, or the network failure, and can always provide uninterrupted lock service.
  • FIG. 2(b) is a schematic diagram of a master-slave database switch according to an embodiment of the present application.
  • the hot standby machine room After the validity period of the lock expires, the hot standby machine room will obtain a new lock, so that the hot standby database will become the new primary database.
  • the original primary data path is automatically downgraded to the backup database, and the hot standby database serves as the new primary database to serve the user.
  • the disaster recovery room obtains the latest data from the new primary database and synchronizes it to the local.
  • the management method of the primary and secondary databases in the embodiment of the present application determines whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, it is determined whether the primary database is received.
  • the lock request if no renewal request is received, selects a new primary database from the backup database and controls the primary database to switch to the backup database.
  • the method does not send a renewal request before the primary database expires the lock held by the primary database, and then determines that the lock held by the primary database is invalid, and cannot provide services to the user normally, thereby selecting a backup data to become a new primary database, thereby improving The switching rate and accuracy of the primary and secondary databases.
  • the switching modes of the active and standby databases can be classified into active switching and passive switching.
  • the details are as follows:
  • the backup database actively sends a lock request for querying the state of the lock in a relatively long period, so that when the lock of the primary database fails, the lock can be quickly acquired, and then actively switched to become a new primary database without affecting the service for the user.
  • the primary database sends a lock request for querying the state of the lock with the period T2
  • the backup database sends a lock request for querying the state of the lock with the period T3, where T2 is less than T1, and T3 is greater than or equal to T1.
  • the backup database is not always actively sending a lock request for the state of the query lock in a certain period
  • the lock expiration notification is actively sent to other backup databases for backup.
  • the database sends a lock request based on the lock expiration notification, and the acquire lock becomes the new primary database.
  • FIG. 3 is a flowchart of a method for managing a primary and secondary database according to another embodiment of the present application, as shown in FIG. 3,
  • the data between the primary database and the backup database is quasi-real-time synchronized.
  • the speed of synchronization depends on the backup speed of the database.
  • the delay in the same room is several milliseconds, and the delay in the remote room is several hundred milliseconds.
  • the hot standby database can The synchronous update completes all the data, so in general, the data of the hot standby database is relatively complete, so the hot standby database is limited as the next primary database.
  • a backup database that is closer to the primary database is determined. That is, because different backup databases may have different distances from the current primary database, for example, the hot standby database is generally closer to the primary database, and the disaster recovery database is generally far away from the primary data, so the time for receiving the lock request is different, and the hot standby database is different. The request was received earlier.
  • the backup database with the earliest reception time is selected as the primary database.
  • the management method of the primary and secondary databases in the embodiments of the present application can still be implemented when a catastrophic failure occurs in the primary database and the hot standby database of the same data center, such as an earthquake.
  • the backup database when the lock of the primary database expires, the backup database quickly acquires the lock and becomes the new primary database, ensuring that the user continues to be normal in a short period of time. Providing services that enhance the user experience.
  • the management method of the primary and secondary databases in the embodiment of the present application further includes receiving the original primary database after the original primary database is restored. Lock request to switch it to the primary database.
  • the validity of the lock of the current primary database and the lock request of the original primary data are always detected, and when the current primary database lock fails, again Select a new primary database in the other backup database, or after receiving the lock request from the original primary database, because the original primary database has a higher priority, the original primary database is switched to the primary database, and the current primary database is demoted to the backup database.
  • FIG. 4 is a flowchart of a method for managing a primary and secondary database according to another embodiment of the present application. As shown in FIG. 4, the management method of the primary and secondary databases includes:
  • the lock request is sent. Because the priority of the original primary database is high, after receiving the lock request, the original primary database is restored to the primary database, and the current primary database is restored to the backup database.
  • the current primary database is continuously maintained as the primary database.
  • the lock request of the original primary database and the current primary database is not received, it indicates that the original primary database does not return to the normal state, and the current primary database also fails or needs to be upgraded, etc., so in order to provide normal services for the user, Select one of the other backup databases from which the lock request was sent as the primary database and restore the current primary data to the backup database.
  • the method for managing the primary and secondary databases in the embodiment of the present application continues to determine whether the current primary database receives the lock request of the original primary database after selecting a new primary database from the backup database, and whether the current primary database is The update of the lock is performed.
  • the lock request of the original primary database is received, the original primary database is restored to the current primary database, and the current primary database is restored to the backup database. If the lock request of the original primary database is not received, it is determined whether the primary primary database is valid. Update the lock. If not, select one of the other backup databases as the primary database and restore the current primary data to the backup database.
  • the method ensures that after the original primary database is restored, it is restored to the primary database, which can better provide services for the user, and improves the practicability of the management method of the primary and secondary databases of the present application.
  • FIG. 5 is a schematic structural diagram of a lock arbitration server according to an embodiment of the present application.
  • the lock arbitration server includes:
  • the first determining module 510 is configured to determine whether the lock held by the primary database expires, wherein the primary database and the backup database share the lock.
  • the second determining module 520 is configured to determine, when the lock held by the primary database has expired, whether to receive the renewal request of the primary database.
  • the first processing module 530 is configured to select one of the backup databases as the new primary database and not control the primary database to switch to the backup database when the primary database renewal request is not received.
  • the primary database in order to protect the primary database from being changed, it is prevented from being switched to the backup database when there is no failure or upgrade and maintenance operations, and the priority of the primary database is higher than the priority of the backup database. Ensure that the database holding the lock is the primary database without the failure of the primary database or the operation of upgrading and maintaining.
  • the configuration of the active/standby database may be multiple, for example, a primary-to-standby deployment mode, or a primary-to-standby deployment mode.
  • the deployment mode of the active and standby databases is described as an example of the two sites in the two places, that is, the backup database includes a hot standby database and a disaster recovery database, where the primary database and the hot standby database are located.
  • the primary database and the disaster recovery database are located in different data centers.
  • the first determining module 510 determines whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, the second determining module 520 determines whether a renewal request of the primary database is received.
  • the renewal request of the primary database is not received, it indicates that the primary database network or the power is faulty, and the update of the lock cannot be completed, so that the first processing module 530 selects one from the backup database in order to normally provide the service to the user.
  • the new primary database and control the primary database to switch to the backup database.
  • the first processing module 530 may select one of the backup databases as the primary database in different manners.
  • the backup database can actively query the primary database when the lock expires, whether to issue a renewal request to extend the validity of the lock. If not, the backup database issues a lock request, so that the lock can be quickly acquired and switched. Become the master database.
  • the lock arbitration server determines whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, it is determined whether the persistent lock request of the primary database is received. If no resound request is received, a new primary database is selected from the backup database and the primary database is controlled to be switched to the backup database.
  • the lock arbitration server determines that the lock held by the primary database is invalid before the primary database expires the lock held by the primary database, and cannot correctly provide services for the user, thereby selecting a backup data to become the new primary database. Improve the switching rate and accuracy of the primary and secondary databases.
  • the switching modes of the active and standby databases can be classified into active switching and passive switching.
  • the details are as follows:
  • the backup database actively sends a lock request for querying the state of the lock in a relatively long period, so that when the lock of the primary database fails, the lock can be quickly acquired, and then actively switched to become a new primary database without affecting the service for the user.
  • the primary database sends a lock request for querying the state of the lock with the period T2
  • the backup database sends a lock request for querying the state of the lock with the period T3, where T2 is less than T1, and T3 is greater than or equal to T1.
  • the backup database is not always actively sending a lock request for the state of the query lock in a certain period
  • the lock expiration notification is actively sent to other backup databases for backup.
  • the database sends a lock request based on the lock expiration notification, and the acquire lock becomes the new primary database.
  • FIG. 6 is a schematic structural diagram of a lock arbitration server according to an embodiment of the present application.
  • the lock arbitration server further includes: a first sending module 540. And recording module 550.
  • the first sending module sends a lock expiration notification to the backup database
  • the recording module 550 receives the lock request sent by the backup data according to the lock expiration notification. And record the receipt time of the lock request.
  • the first processing module 530 selects the backup database with the earliest receiving time as the primary database. .
  • the backup database quickly acquires the lock to become a new primary database, and ensures that the user continues to provide services in a relatively short period of time. , improved user experience.
  • the lock arbitration server in the embodiment of the present application is further configured to receive the lock of the original primary database after the original primary database is restored. Request to switch it to the primary database.
  • FIG. 7 is a schematic structural diagram of a lock arbitration server according to another embodiment of the present application.
  • the lock arbitration server further includes: a first receiving module 560, as shown in FIG. Specifically, in the present example, after the first processing module 530 selects one of the backup databases as the new primary database, the first receiving module 560 always receives the lock request of the original primary data, and receives the original primary at the first receiving module 560. After the lock request of the database, because the priority of the original primary database is high, the first processing module 530 switches the original primary database to the primary database, and demotes the current primary database to the backup database.
  • FIG. 8 is a schematic structural diagram of a lock arbitration server according to still another embodiment of the present application.
  • the lock arbitration server further includes a second processing module 570, a third processing module 580, and a fourth processing module 590, as shown in FIG.
  • the first determining module 510 continues to determine whether the lock held by the current primary database is expired, and the second determining module 520 holds the current primary database. When the lock has expired, it is judged whether the lock request of the original primary database, the current primary database, and other backup databases is received.
  • the second processing module 570 restores the original primary database to the primary database and restores the current database to the backup database.
  • the lock request is sent. Because the priority of the original primary database is high, after receiving the lock request, the original primary database is restored to the primary database, and the second processing module 570 will be the current primary database. Revert to the backup database.
  • the third processing module 580 maintains the current primary database as the primary database.
  • the third processing module 580 continues to maintain the current primary database as the primary database.
  • the fourth processing module 590 selects one of the other backup databases as the primary database, and restores the current primary data to the backup database. .
  • the four processing module 590 needs to select one of the other backup databases that send the lock request as the primary database, and restore the current primary data to the backup database.
  • the lock arbitration server in the embodiment of the present application selects one as the new primary database from the backup database, it continues to determine whether the current primary database receives the lock request of the original primary database, and whether the current primary database is locked. Update, when receiving the lock request of the original primary database, the original primary database is restored to the current primary database, and the current primary database is restored to the backup database. If the lock request of the original primary database is not received, it is determined whether the previous primary database is valid for locking. Update, if not, select one of the other backup databases as the primary database and restore the current primary data to the backup database.
  • the lock arbitration server ensures that after the original primary database is restored, it is restored to the primary database, which can better serve the user, and improves the practicability of the management method of the primary and secondary databases of the present application.
  • the present application also proposes a primary database server.
  • FIG. 9 is a schematic structural diagram of a primary database server according to an embodiment of the present application. As shown in FIG. 9, the primary database server includes:
  • the second sending module 910 is configured to send a renewal request to the lock arbitration server when the held lock expires, so that the lock arbitration server selects one of the backup databases from the backup database as the new primary database.
  • the switching module 920 is configured to control the primary database to switch to the backup database.
  • the primary database in order to protect the primary database from being changed, it is prevented from being switched to the backup database when there is no failure or upgrade and maintenance operations, and the priority of the primary database is higher than the priority of the backup database. Ensure that the database holding the lock is the primary database without the failure of the primary database or the operation of upgrading and maintaining.
  • the configuration of the active/standby database may be multiple, for example, a primary-to-standby deployment mode, or a primary-to-standby deployment mode.
  • the deployment mode of the active and standby databases is described as an example of the two sites in the two places, that is, the backup database includes a hot standby database and a disaster recovery database, where the primary database and the hot standby database are located.
  • the primary database and the disaster recovery database are located in different data centers.
  • the second sending module 910 sends a lock request to the lock arbitration server when the held lock expires. If the lock arbitration server does not receive the lock request, it indicates that the current primary database is performing an upgrade update or a failure, etc.
  • the server is normally provided to the user, so that the lock arbitration server selects one from the backup database as the new primary database to provide normal service for the user as soon as possible, and the switching module 920 controls the primary database to switch to the backup database.
  • the backup database actively sends a lock request for querying the state of the lock in a relatively long period, so that when the lock of the primary database fails, the lock can be quickly acquired, and then actively switched to become a new primary database without affecting the service for the user.
  • the primary database sends a lock request for querying the state of the lock with the period T2
  • the backup database sends a lock request for querying the state of the lock with the period T3, where T2 is less than T1, and T3 is greater than or equal to T1.
  • the primary data server sends a renewal request to the lock arbitration server when the held lock expires, so that the lock arbitration server does not receive the renewal request, and selects from the backup database.
  • One as a new database while switching the primary database to a backup database.
  • the primary database is switched to the backup database, and a backup data is selected to become the new primary database, which improves the switching rate and accuracy of the primary and secondary databases, and ensures the database. Normally providing services to users, improving the user experience.
  • the primary and secondary database servers in the embodiment of the present application are also used to receive the original primary database after the original primary database is restored. Lock the request to switch it to the primary database.
  • FIG. 10 is a schematic structural diagram of a primary database server according to an embodiment of the present application. As shown in FIG. 10, the primary data server further includes: a third sending module 930.
  • the lock request is sent by the third sending module 930. Because the priority of the original primary database is high, after receiving the lock request, the lock arbitration server receives the lock request sent by the original primary database, and After the lock expires, the control lock is held by the original primary database to restore the original primary database to the primary database, and the current primary database is restored to the backup database.
  • the primary and secondary database servers in the embodiment of the present application ensure that after the original primary database is restored, the primary database is restored to the primary database, which can better serve the user and improve the user experience.
  • FIG. 11 is a schematic structural diagram of a backup database according to an embodiment of the present application. As shown in FIG. 11, the backup database includes:
  • the fourth sending module 1010 is configured to send a lock request to the lock arbitration server.
  • the second receiving module 1020 is configured to receive a lock confirmation message sent by the lock arbitration server.
  • the fifth processing module 1030 is configured to switch to a new primary database according to the lock confirmation message.
  • the fourth sending module 1010 sends a lock request to the lock arbitration server, so that when the primary database cannot effectively update the lock, the lock is quickly grabbed, and the second receiving module 1020 receives the lock confirmation message sent by the lock arbitration server, so that the fifth The processing module 1030 switches to the primary database according to the confirmation message of the lock.
  • the configuration of the active/standby database may be multiple, for example, a primary-to-standby deployment mode, or a primary-to-standby deployment mode.
  • the deployment mode of the active and standby databases is described as an example of the two sites in the two places, that is, the backup database includes a hot standby database and a disaster recovery database, where the primary database and the hot standby database are located.
  • the primary database and the disaster recovery database are located in different data centers.
  • the backup database server in the embodiment of the present application sends a lock request to the lock arbitration server.
  • the switch is changed to the new primary database, thereby improving the main
  • the switching rate and accuracy of the standby database ensure that the user can provide normal services and improve the user experience.
  • the backup database server does not always actively send a lock request for the state of the query lock in a certain period, when the lock held by the primary database fails, the lock expiration notification is actively sent to other backup databases for backup.
  • the database server sends a lock request based on the lock expiration notification, and acquires the lock to become the new primary database.
  • FIG. 12 is a schematic structural diagram of a backup database server according to an embodiment of the present application.
  • the backup database server includes: a third receiving module 1040.
  • the third receiving module 1040 receives the lock expiration notification sent after the lock arbitration server determines that the lock held by the primary database has expired, wherein the fourth sending module 1010 arbitrates to the lock according to the lock request sent by the lock expiration notification.
  • the server sends a lock request.
  • the lock arbitration server selects the receiving time.
  • the earliest backup database is used as the primary database.
  • the backup database server of the embodiment of the present application when the lock of the primary database expires, the backup database quickly acquires the lock and becomes a new primary database, ensuring that the user continues to provide services in a relatively short period of time. , improved user experience.
  • the backup data server in the embodiment of the present application is also used to switch to the backup database after the original primary database is restored.
  • FIG. 13 is a schematic structural diagram of a backup database server according to another embodiment of the present application. As shown in FIG. 13, the backup database server includes: a sixth processing module 1050.
  • the lock arbitration server restores the original primary database to the primary database after receiving the lock request, and the sixth processing module 1050 Restore the current primary database to a backup database.
  • the backup database server in the embodiment of the present application restores the original primary database to the backup database after the original primary database is restored, and the arbitration server restores the original primary database to the primary database, which can better serve the user and improve the user.
  • the backup database server in the embodiment of the present application restores the original primary database to the backup database after the original primary database is restored, and the arbitration server restores the original primary database to the primary database, which can better serve the user and improve the user.
  • FIG. 14 is a schematic structural diagram of a management system for the primary and secondary databases according to an embodiment of the present application. As shown in FIG. 14, the primary and secondary databases are shown.
  • the management system includes: a lock arbitration server 1000, a primary database server 2000, and a backup database server 3000.
  • lock arbitration server 1000 the primary database server 2000, and the backup database server 3000 in the present application refer to the foregoing descriptions of the lock arbitration server, the primary database server, and the backup database server, and are not described herein again.
  • the management system of the primary and secondary databases in the embodiment of the present application determines whether the lock held by the primary database is expired. If it is determined that the lock held by the primary database has expired, it is determined whether the primary database is received.
  • the lock request if no renewal request is received, selects a new primary database from the backup database and controls the primary database to switch to the backup database.
  • the system does not send a renewal request before the primary database expires before the lock held by the primary database, and then judges that the lock held by the primary database is invalid, and cannot provide services to the user normally, thereby selecting a backup data to become a new primary database, thereby improving The switching rate and accuracy of the primary and secondary databases.
  • first and second are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated.
  • features defining “first” or “second” may include at least one of the features, either explicitly or implicitly.
  • the meaning of "a plurality” is at least two, such as two, three, etc., unless specifically defined otherwise.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Hardware Redundancy (AREA)
PCT/CN2017/115392 2016-12-20 2017-12-11 主备数据库的管理方法、系统及其设备 Ceased WO2018113543A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
MYPI2019003464A MY199572A (en) 2016-12-20 2017-12-11 Method, system and apparatus for managing primary and secondary databases
EP17884001.3A EP3561694B1 (en) 2016-12-20 2017-12-11 Management method, system, and device for master and standby databases
JP2019533442A JP6905161B2 (ja) 2016-12-20 2017-12-11 マスタおよびスタンバイデータベースのための管理方法、システム、およびデバイス
KR1020197021325A KR102142233B1 (ko) 2016-12-20 2017-12-11 기본 및 보조 데이터베이스를 관리하기 위한 방법, 시스템 및 장치
US16/394,315 US10592361B2 (en) 2016-12-20 2019-04-25 Method, system and apparatus for managing primary and secondary databases
PH12019501392A PH12019501392A1 (en) 2016-12-20 2019-06-18 Method, system and apparatus for managing primary and secondary databases

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611183638.9A CN107066480B (zh) 2016-12-20 2016-12-20 主备数据库的管理方法、系统及其设备
CN201611183638.9 2016-12-20

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/394,315 Continuation US10592361B2 (en) 2016-12-20 2019-04-25 Method, system and apparatus for managing primary and secondary databases

Publications (1)

Publication Number Publication Date
WO2018113543A1 true WO2018113543A1 (zh) 2018-06-28

Family

ID=59619184

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/115392 Ceased WO2018113543A1 (zh) 2016-12-20 2017-12-11 主备数据库的管理方法、系统及其设备

Country Status (10)

Country Link
US (1) US10592361B2 (https=)
EP (1) EP3561694B1 (https=)
JP (1) JP6905161B2 (https=)
KR (1) KR102142233B1 (https=)
CN (1) CN107066480B (https=)
MY (1) MY199572A (https=)
PH (1) PH12019501392A1 (https=)
SG (2) SG10201913120SA (https=)
TW (1) TWI677797B (https=)
WO (1) WO2018113543A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3702936A1 (en) * 2019-03-01 2020-09-02 Accenture Global Solutions Limited Message recovery system for computing nodes with replicated databases

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107066480B (zh) * 2016-12-20 2020-08-11 创新先进技术有限公司 主备数据库的管理方法、系统及其设备
CN110442650A (zh) * 2019-08-09 2019-11-12 中国工商银行股份有限公司 数据库切换方法、装置、系统、电子设备及存储介质
CN110765143B (zh) * 2019-10-10 2022-08-02 腾讯科技（深圳）有限公司 数据处理方法、装置、服务器和存储介质
CN111159156B (zh) * 2019-12-31 2023-04-28 杭州迪普科技股份有限公司 SQLite数据库的备份方法和装置
US11379477B2 (en) 2020-03-31 2022-07-05 Sap Se Efficient workload balancing in replicated databases based on result lag computation
CN114490231A (zh) * 2020-11-11 2022-05-13 网联清算有限公司 一种数据库仲裁服务调度方法及系统
CN115168322A (zh) * 2022-07-08 2022-10-11 北京奥星贝斯科技有限公司 数据库系统、主库选举方法及装置
CN116048886A (zh) * 2022-12-30 2023-05-02 蚂蚁区块链科技(上海)有限公司 一种进行区块链节点主备切换的方法和装置
US20240406060A1 (en) * 2023-05-31 2024-12-05 Rakuten Symphony, Inc. Communication network failure detection and restoration

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102831038A (zh) * 2011-06-17 2012-12-19 中兴通讯股份有限公司 Enum-dns的容灾方法及enum-dns
CN103593266A (zh) * 2013-11-12 2014-02-19 浪潮(北京)电子信息产业有限公司 一种基于仲裁盘机制的双机热备方法
CN104778102A (zh) * 2015-03-27 2015-07-15 深圳市创梦天地科技有限公司 一种主备切换方法及系统
CN106202075A (zh) * 2015-04-29 2016-12-07 中兴通讯股份有限公司 一种数据库主备切换的方法及装置
CN107066480A (zh) * 2016-12-20 2017-08-18 阿里巴巴集团控股有限公司 主备数据库的管理方法、系统及其设备

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3572928B2 (ja) * 1998-03-18 2004-10-06 富士通株式会社 バックアップ機能付オンラインデータベース情報処理システム
US6957251B2 (en) * 2001-05-07 2005-10-18 Genworth Financial, Inc. System and method for providing network services using redundant resources
WO2003005245A2 (en) * 2001-07-06 2003-01-16 Computer Associates Think, Inc. Systems and methods of information backup
US20040003317A1 (en) * 2002-06-27 2004-01-01 Atul Kwatra Method and apparatus for implementing fault detection and correction in a computer system that requires high reliability and system manageability
US7254736B2 (en) * 2002-12-18 2007-08-07 Veritas Operating Corporation Systems and method providing input/output fencing in shared storage environments
US7284151B2 (en) * 2003-07-21 2007-10-16 Oracle International Corporation Conditional data access after database system failure
TWI306241B (en) * 2004-07-12 2009-02-11 Infortrend Technology Inc A controller capable of self-monitoring, a redundant storage system having the same, and its method
US7496701B2 (en) * 2004-11-18 2009-02-24 International Business Machines Corporation Managing virtual server control of computer support systems with heartbeat message
CN100362482C (zh) * 2005-07-21 2008-01-16 上海华为技术有限公司 一种双机备份实现方法及系统
CN100449548C (zh) * 2007-04-11 2009-01-07 华为技术有限公司 数据库同步方法及系统
JP5199464B2 (ja) * 2009-01-20 2013-05-15 株式会社日立製作所 ストレージシステム及びストレージシステムの制御方法
JP5625243B2 (ja) * 2009-02-26 2014-11-19 日本電気株式会社 情報処理システム、ディザスタリカバリ方法及びディザスタリカバリプログラム
JP2011076512A (ja) * 2009-10-01 2011-04-14 Hitachi Solutions Ltd ジョブ管理サーバーの統合管理システム
US9575985B2 (en) * 2009-12-07 2017-02-21 Novell, Inc. Distributed lock administration
US8984328B2 (en) * 2011-03-11 2015-03-17 Microsoft Technology Licensing, Llc Fault tolerance in a parallel database system
US9348883B2 (en) * 2011-06-01 2016-05-24 Clustrix, Inc. Systems and methods for replication replay in a relational database
US8719225B1 (en) * 2012-01-17 2014-05-06 Amazon Technologies, Inc. System and method for log conflict detection and resolution in a data store
US9116862B1 (en) * 2012-01-17 2015-08-25 Amazon Technologies, Inc. System and method for data replication using a single master failover protocol
JP2013161252A (ja) * 2012-02-03 2013-08-19 Fujitsu Ltd 冗長コンピュータ制御プログラム、方法、及び装置
CN102739451B (zh) * 2012-06-29 2014-12-03 华为技术有限公司 一种主备切换条件更新方法、装置、服务器及系统
CN102891849B (zh) * 2012-09-25 2015-07-22 北京星网锐捷网络技术有限公司 业务数据同步方法、恢复方法及装置和网络设备
US9009444B1 (en) * 2012-09-29 2015-04-14 Emc Corporation System and method for LUN control management
CN102945195B (zh) * 2012-11-26 2015-11-18 国电南瑞科技股份有限公司 一种基于SQLite数据库的主备冗余复制方法
US9667490B1 (en) * 2013-06-05 2017-05-30 Parallels IP Holdings GmbH Method for high availability of services in cloud computing systems
US9274902B1 (en) * 2013-08-07 2016-03-01 Amazon Technologies, Inc. Distributed computing fault management
US20150339200A1 (en) * 2014-05-20 2015-11-26 Cohesity, Inc. Intelligent disaster recovery
TWI529624B (zh) * 2015-03-19 2016-04-11 Univ Nat Central Method and system of fault tolerance for multiple servers
JP2017102834A (ja) * 2015-12-04 2017-06-08 日本電気株式会社 バックアップシステム
CN105933379B (zh) * 2016-04-01 2018-10-09 浪潮电子信息产业股份有限公司 一种业务处理方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102831038A (zh) * 2011-06-17 2012-12-19 中兴通讯股份有限公司 Enum-dns的容灾方法及enum-dns
CN103593266A (zh) * 2013-11-12 2014-02-19 浪潮(北京)电子信息产业有限公司 一种基于仲裁盘机制的双机热备方法
CN104778102A (zh) * 2015-03-27 2015-07-15 深圳市创梦天地科技有限公司 一种主备切换方法及系统
CN106202075A (zh) * 2015-04-29 2016-12-07 中兴通讯股份有限公司 一种数据库主备切换的方法及装置
CN107066480A (zh) * 2016-12-20 2017-08-18 阿里巴巴集团控股有限公司 主备数据库的管理方法、系统及其设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3702936A1 (en) * 2019-03-01 2020-09-02 Accenture Global Solutions Limited Message recovery system for computing nodes with replicated databases
US10999392B2 (en) 2019-03-01 2021-05-04 Accenture Global Solutions Limited Message recovery system for computing nodes with replicated databases

Also Published As

Publication number Publication date
PH12019501392A1 (en) 2020-02-10
JP6905161B2 (ja) 2021-07-21
EP3561694B1 (en) 2022-06-22
EP3561694A4 (en) 2019-12-18
US10592361B2 (en) 2020-03-17
SG10202012899PA (en) 2021-01-28
CN107066480B (zh) 2020-08-11
JP2020502686A (ja) 2020-01-23
CN107066480A (zh) 2017-08-18
KR20190095443A (ko) 2019-08-14
MY199572A (en) 2023-11-07
KR102142233B1 (ko) 2020-08-07
US20190251008A1 (en) 2019-08-15
SG10201913120SA (en) 2020-03-30
TW201824030A (zh) 2018-07-01
TWI677797B (zh) 2019-11-21
EP3561694A1 (en) 2019-10-30

Similar Documents

Publication Publication Date Title
WO2018113543A1 (zh) 主备数据库的管理方法、系统及其设备
US8169856B2 (en) Time synchronization in cluster systems
JP6382454B2 (ja) 分散ストレージ及びレプリケーションシステム、並びに方法
US8538923B2 (en) Method, node and system for controlling version in distributed system
CN107291787B (zh) 主备数据库切换方法和装置
US8630985B2 (en) Automatic failover configuration with lightweight observer
CN103117901B (zh) 一种分布式心跳检测方法、装置及系统
CN103795553B (zh) 基于监控的主、备服务器切换
WO2018019023A1 (zh) 一种数据容灾方法、装置和系统
US20070124348A1 (en) Database system configured for automatic failover with no data loss
WO2012071920A1 (zh) 分布式内存数据库的实现方法、系统、令牌控制器及内存数据库
JP2019219954A (ja) クラスタストレージシステム、データ管理制御方法、データ管理制御プログラム
CN112783694B (zh) 一种高可用Redis的异地灾备方法
CN106156318B (zh) 一种实现多节点数据库高可用的系统及方法
US20110161724A1 (en) Data management apparatus, monitoring apparatus, replica apparatus, cluster system, control method and computer-readable medium
CN102013997B (zh) 电信网管系统中的双机数据备份方法和系统
WO2011103763A1 (zh) 数据容灾的方法、装置及系统
CN104767794A (zh) 一种分布式系统中的节点选举方法及节点
CN116346582A (zh) 一种实现主备双网冗余方法、装置、设备及存储介质
US20210326224A1 (en) Method and system for processing device failure
CN108009045B (zh) 一种主备数据库故障处理方法及装置
CN109189854B (zh) 提供持续业务的方法及节点设备
CN102841895B (zh) 一种处理数据库状态转移的方法和系统
CN106250048A (zh) 管理存储阵列的方法及装置
CN112256484A (zh) 一种数据备份的方法、装置和系统

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: 17884001

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019533442

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197021325

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017884001

Country of ref document: EP

Effective date: 20190722