Disaster recovery data processing method, device and system

Abstract

The embodiment of the invention discloses a disaster recovery data processing method, device and system, and the method comprises the steps: after a disaster recovery database obtains a first serviceprocessing request sent by a service requester, judging whether the type of the first service processing request is an inflow type, and obtaining a first judgment result; if the first judgment resultis yes, determining a corresponding gateway account according to the user information in the first service processing request, performing gateway accounting on the transaction in the first service processing request according to the gateway account, and listing the corresponding user into a gateway blacklist; determining a real blacklist generated asynchronously, and combining the real blacklist with the gateway blacklist to obtain a total blacklist; and locking the users who do not belong to the real blacklist in the total blacklist, and carrying out merging and updating processing on the gateway account data corresponding to the locked users. By means of the embodiments of the present specification, normal transactions can be performed on the user accounts except the real blacklist in the disaster recovery period.

Description

technical field [0001] The embodiments of this specification relate to the technical field of computer data processing, and in particular, to a disaster recovery data processing method, device, and system. Background technique [0002] A network failure or unexpected termination of the database may cause some or all services to be unavailable, which is called database failover (FO for short, disaster recovery) in the industry. A general database has a master database and a standby database, and database failover usually occurs on the master database. When the main database is unavailable, it takes a certain amount of time to pull up the backup database. During this period, in order to ensure the business, the account data is usually written into the FO database (or disaster recovery database). After the standby database is pulled up or the main database is repaired, the data in the disaster recovery database is written to the main database or the standby database. [0003]...

AI Technical Summary

Problems solved by technology

[0003] However, when the disaster recovery database is used for accounting data processing, the instant the main database goes down, the data status of the main database and other real-time synchronous databases may be inconsistent, making it impossible to accurately know the accurate accounting data of the users in the main database during the disaster recovery period, for example The user's accurate balance limits the user's normal transactions and brings a bad experience to the user

At the same time, in the process of process switching, there may be inconsistencies in the status of some distributed servers, which leads to the risk of simultaneous accounting in the main library and disaster recovery inventory

Images