CN116450417A - Bank payment system disaster backup switching platform and method based on DevOps - Google Patents
Bank payment system disaster backup switching platform and method based on DevOps Download PDFInfo
- Publication number
- CN116450417A CN116450417A CN202310658308.4A CN202310658308A CN116450417A CN 116450417 A CN116450417 A CN 116450417A CN 202310658308 A CN202310658308 A CN 202310658308A CN 116450417 A CN116450417 A CN 116450417A
- Authority
- CN
- China
- Prior art keywords
- switching
- application
- checking
- database
- script
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000013515 script Methods 0.000 claims abstract description 99
- 238000011084 recovery Methods 0.000 claims abstract description 63
- 238000007689 inspection Methods 0.000 claims abstract description 9
- 230000002159 abnormal effect Effects 0.000 claims description 3
- 230000006855 networking Effects 0.000 claims 1
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 238000000275 quality assurance Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- Quality & Reliability (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Data Mining & Analysis (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Computing Systems (AREA)
- Technology Law (AREA)
- General Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a disaster recovery switching platform and a disaster recovery switching method for a bank payment system based on DevOps, and belongs to the technical field of digitization of bank payment systems. The switching platform comprises various bank payment systems which are divided into application nodes, database nodes and network nodes, and the starting and stopping sequences of the nodes are arranged in the same disaster recovery switching pipeline; all application nodes are deployed with inspection scripts before application stopping, application starting and inspection scripts after application starting; all database nodes are provided with checking scripts before database switching, checking scripts after database switching and checking scripts after database switching; all network nodes are provided with checking script before network switching, checking script after network switching and checking script after network switching. The invention can reduce the complexity of disaster recovery switching environment, reduce the requirement on the professional degree of disaster recovery switching personnel, improve the disaster recovery switching efficiency and success rate and ensure the RTO and RPO indexes of disaster recovery of the payment system.
Description
Technical Field
The invention relates to the technical field of digitization of bank payment systems, in particular to a disaster recovery switching platform and method of a bank payment system based on DevOps.
Background
The digitization and informatization of the current bank payment system develop rapidly, and the specificity of the bank industry determines the high timeliness, the high reliability and the high availability of the payment system. In the development of bank payment systems, various payment systems such as a dockee-size system, a super bank system, a banking system, an internet connection system, etc. have appeared. The bank establishes a local disaster backup (disaster backup) center and a different place according to the supervision requirement, and periodically develops various forms of disaster backup switching exercises to ensure the availability of disaster backup environments and the effectiveness of disaster switching, and improve the processing capacity of related personnel for handling emergency events.
However, there are a number of problems in the disaster recovery switching exercise of the payment system: the related architecture is complex, the servers are numerous, and the application types are different; the related professionals are more, including application operation and maintenance administrators, database administrators, developers and the like; RTO (Recovery TIME Objective, recovery time objective, mainly the longest time that a service can be tolerated to stop service, that is, the shortest time period required from the disaster to the service system recovery of service functions) and RPO (Recovery Point Objective, recovery data objective, mainly the amount of data loss that a service system can tolerate) indexes that need to rely on the skill level and proficiency of operators to achieve disaster recovery; lack of tools or system support, rely solely on manual operation to ensure handoff success.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides the following technical scheme.
The invention provides a bank payment system disaster recovery switching platform based on DevOps, which comprises various bank payment systems, wherein the various bank payment systems are divided into application nodes, database nodes and network nodes, and the starting and stopping sequences of the application nodes, the database nodes and the network nodes of the various bank payment systems are arranged in the same disaster recovery switching pipeline of the bank payment system disaster recovery switching platform; during operation, an operator clicks the disaster backup switching pipeline to finish disaster backup switching of the bank payment system;
the method comprises the steps that an inspection script before application stopping, an application stopping script, an application starting script and an inspection script after application starting are deployed in all application nodes;
arranging a checking script before database switching, a checking script after database switching and a checking script after database switching in all the database nodes;
a checking script before network switching, a checking script after network switching and a checking script after network switching are deployed in all network nodes;
all of the pre-application stop checking script, the application stop script, the application start script, the post-application start checking script, the pre-database switching checking script, the post-database switching checking script, the pre-network switching checking script, the network switching checking script and the post-network switching checking script comprise the execution script and the operation script of the DevOps.
Preferably, the starting and stopping sequence of each application node, database node and network node of the various bank payment systems comprises: the method comprises the steps of firstly performing pre-application stop checking and application stop operation of an application node before disaster recovery switching, then performing pre-database switching checking, database switching and post-database switching checking operation of a database node, performing pre-network switching checking, network switching and post-network switching checking operation of a network node, and finally performing application starting and post-application starting checking operation of the application node after disaster recovery switching.
Preferably, the various bank payment systems include a size system, a super bank system, a banking system, and an internet system for interfacing with a people's bank.
Preferably, the database nodes perform master-slave copy switching in a semi-synchronous mode, namely, the bank payment system reads and writes the master database node of a master center and synchronizes logs to the backup database node of a backup center in real time.
The second aspect of the present invention provides a bank payment system disaster recovery switching method, the method is implemented by using a bank payment system disaster recovery switching platform based on DevOps according to the first aspect, the method includes: an operator logs in a disaster recovery switching platform of a bank payment system, firstly opens a disaster recovery switching pipeline, and then sequentially performs application operation before switching, database switching operation, network switching operation and application operation after switching.
Preferably, the pre-switch application operation includes an application pre-stop check operation and an application stop operation; the database switching operation comprises a checking operation before database switching, a database switching operation and a checking operation after database switching; the network switching operation comprises a checking operation before network switching, a network switching operation and a checking operation after network switching; the post-switch application operation comprises an application starting operation and an application post-start checking operation.
Preferably, the method further comprises:
checking whether the application stopping requirement is met in the current state, if so, performing application stopping operation, and returning to a normal stopping log after the completion;
checking whether the database node meets the switching condition, if so, using a database switching script to perform database switching operation, after the database switching is completed, checking whether the database node is successfully switched, and checking whether a background log has error reporting logs or abnormal information that the switching is unsuccessful;
checking IP information corresponding to the bank APP connection domain name by using a checking script before network switching, executing a network switching script to switch the IP information corresponding to the bank APP connection domain name, and checking whether the IP information corresponding to the bank APP domain name is successfully switched after the network switching is completed;
after the database node and the network node are successfully switched, the application is started, whether the switching state is normal is checked after the application is started, and if the switching state is normal, the switching is completed.
Preferably, the method further comprises:
after the operator completes the disaster backup switching of the bank payment system, the tester verifies the disaster backup switching result by logging in the bank APP.
The beneficial effects of the invention are as follows: the invention provides a disaster recovery switching platform and a disaster recovery switching method for a bank payment system based on DevOps. The platform and the method provided by the invention can reduce the complexity of the disaster recovery switching environment, reduce the professional requirements of disaster recovery switching personnel, improve the disaster recovery switching efficiency and success rate, and ensure the RTO and RPO indexes of the payment system.
Drawings
FIG. 1 is a bottom layer architecture diagram of a bank payment system disaster recovery switching platform of the present invention;
fig. 2 is a flowchart of a script execution method of each node of the bank payment system according to the present invention.
Detailed Description
In order to better understand the above technical solutions, the following detailed description will be given with reference to the accompanying drawings and specific embodiments.
In order to solve the problems in the prior art, the invention provides a bank payment system disaster recovery switching platform and a bank payment system disaster recovery switching method based on a DevOps technology, which are used for reducing the complexity of a disaster recovery switching environment, reducing the requirements on the expertise of disaster recovery switching personnel, improving the disaster recovery switching efficiency and success rate and ensuring the RTO and RPO indexes of the payment system disaster recovery.
DevOps (Development and operation) is a collective term for a set of processes, methods and systems used to facilitate communication, collaboration and integration between Development (application/software engineering), technical Operations and Quality Assurance (QA) departments.
Example 1
As shown in fig. 1, the embodiment of the invention provides a bank payment system disaster recovery switching platform based on a DevOps technology, which comprises various bank payment systems, wherein the various bank payment systems are divided into application nodes, database nodes and network nodes, and the starting and stopping sequences of the application nodes, the database nodes and the network nodes of the various bank payment systems are arranged in the same disaster recovery switching pipeline of the bank payment system disaster recovery switching platform. And when the operation is performed, an operator clicks the disaster recovery backup switching pipeline to finish the disaster recovery backup switching of the bank payment system, and a script used in the switching process is called.
As shown in fig. 2, a pre-application stop check script, an application stop script, an application start script, and an post-application start check script are deployed in all application nodes; arranging a checking script before database switching, a checking script after database switching and a checking script after database switching in all the database nodes; a checking script before network switching, a checking script after network switching and a checking script after network switching are deployed in all network nodes; all of the pre-application stop checking script, the application stop script, the application start checking script, the pre-database switching checking script, the post-database switching checking script, the pre-network switching checking script, the network switching checking script and the post-network switching checking script comprise execution scripts and operation scripts based on the DevOps switching platform.
The starting and stopping sequence of each node of each bank payment system comprises the following steps: the method comprises the steps of firstly performing pre-application stop checking and application stop operation of an application node before disaster recovery switching, then performing pre-database switching checking, database switching and post-database switching checking operation of a database node, performing pre-network switching checking, network switching and post-network switching checking operation of a network node, and finally performing application starting and post-application starting checking operation of the application node after disaster recovery switching.
In the present invention, various bank payment systems may include a payment clearing system for interfacing with a size system, a super bank system, a banking system, an internet connection system, etc. of a people's bank.
In the embodiment of the invention, the database nodes perform master-slave copy switching in a semi-synchronous mode, namely a bank payment system reads and writes a master database node of a master center and synchronizes logs to a backup database node of a backup center in real time.
In one embodiment of the present invention, the start and stop sequences of the nodes of the various bank payment systems are all arranged in the same disaster backup switching pipeline of the disaster backup switching platform. As one example, such as: the network system architecture, the application of the network system comprises three micro services of zuul (gateway micro service), app (main application micro service) and host (core micro service), the database of the network system is a set of Mysql-master-slave database architecture, and the application connection database is connected with the Mysql master database (master database) and the slave database (slave database) through the network domain name by IP.
In another embodiment of the present invention, such as in a networked system, the pre-application check script may be formulated as follows: the application of the network system comprises three micro services of zuul (gateway micro service), app (main application micro service) and host (core micro service), and the checking script before stopping the application simultaneously issues checking commands to the three micro services, and when the three micro services simultaneously feed back that the application service is normal, the next operation can be continued; the application stop script may be formulated as follows: the network system application comprises three micro services of zuul (gateway micro service), app (main application micro service) and host (core micro service), an application stopping script issues a stopping command to the three micro services according to the sequence of stopping the application micro service, the application micro service is stopped in series, and the application service is stopped to finish the next operation; the pre-database switch check script may be formulated as follows: the network system database is a Mysql-master-slave database architecture, and the checking script checks whether the Mysql database master and slave meet the switching conditions or not, and the next operation can be continued after the switching conditions are met; the database switch script may be formulated as follows: the network system database is a Mysql-master-slave database architecture, and the database switching script executes Mysql master-slave switching commands to switch master-slave roles; the database post-switch check script may be formulated as follows: after the network system Mysql database master library and the slave library are switched, the checking script checks whether the states of the new master library and the new slave library are normal or not, and the next operation can be continued when the states of the databases are in the normal states; the pre-network-switch check script may be formulated as follows: the network system application connection database is connected with the IP of the Mysql master library and the slave library through the network domain name, and the IP connected before the network system switching is checked; the network switch script may be formulated as follows: the network switching script modifies the domain name of the corresponding network connection database on the DNS from the master library IP to the slave library IP; the post-network-switch check script may be formulated as follows: the network system application connection database is connected with the IP of the Mysql master library and the IP of the slave library through the network domain name, whether the IP connected after the network system is switched is the IP of the slave library or not is checked, and if so, the next operation can be continued; the application start script may be formulated as follows: the network system is applied with three micro services of zuul (gateway micro service), app (main application micro service) and host (core micro service), an application start script issues a stop command to the three micro services according to the sequence of stopping the application micro service, the application micro service is started in series, and the application micro service is started to be completed before the next operation can be continued; the post-application inspection script may be formulated as follows: the network system is applied with three micro-services of zuul (gateway micro-service), app (main application micro-service) and host (core micro-service), after the application is started, the inspection script issues inspection commands to the three micro-services at the same time, and when the three micro-services feed back the application services normally, the next operation can be continued.
Example two
The invention also provides a bank payment system disaster recovery switching method, which uses the bank payment system disaster recovery switching platform based on the DevOps technology as described in the first embodiment, and the method comprises the following steps: an operator logs in a disaster recovery switching platform of a bank payment system, firstly opens a disaster recovery switching pipeline, and then sequentially performs application operation before switching, database switching operation, network switching operation and application operation after switching.
Wherein, as shown in fig. 2, the pre-switch application operation includes an application pre-stop check operation and an application stop operation; the database switching operation comprises a checking operation before database switching, a database switching operation and a checking operation after database switching; the network switching operation comprises a checking operation before network switching, a network switching operation and a checking operation after network switching; the post-switch application operation comprises an application starting operation and an application post-start checking operation.
The specific operation process can be as follows: checking whether the application stopping requirement is met in the current state, if so, performing application stopping operation, and returning to a normal stopping log after the completion; checking whether the database node meets the switching condition, if so, using a database switching script to perform database switching operation, after the database switching is completed, checking whether the database node is successfully switched, and checking whether a background log has error reporting logs or abnormal information that the switching is unsuccessful; checking IP information corresponding to the bank APP connection domain name by using a checking script before network switching, executing a network switching script to switch the IP information corresponding to the bank APP connection domain name, and checking whether the IP information corresponding to the bank APP domain name is successfully switched after the network switching is completed; after the database node and the network node are successfully switched, the application is started, whether the switching state is normal is checked after the application is started, and if the switching state is normal, the switching is completed.
In a preferred embodiment of the invention, after the operator completes the disaster recovery switching of the bank payment system, the tester verifies the disaster recovery switching result by logging in the bank APP.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention. It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (8)
1. The bank payment system disaster recovery switching platform based on the DevOps is characterized by comprising various bank payment systems, wherein the various bank payment systems are divided into application nodes, database nodes and network nodes, and the starting and stopping sequences of the application nodes, the database nodes and the network nodes of the various bank payment systems are arranged in the same disaster recovery switching pipeline of the bank payment system disaster recovery switching platform; during operation, an operator clicks the disaster backup switching pipeline to finish disaster backup switching of the bank payment system;
the method comprises the steps that an inspection script before application stopping, an application stopping script, an application starting script and an inspection script after application starting are deployed in all application nodes;
arranging a checking script before database switching, a checking script after database switching and a checking script after database switching in all the database nodes;
a checking script before network switching, a checking script after network switching and a checking script after network switching are deployed in all network nodes;
all of the pre-application stop checking script, the application stop script, the application start script, the post-application start checking script, the pre-database switching checking script, the post-database switching checking script, the pre-network switching checking script, the network switching checking script and the post-network switching checking script comprise the execution script and the operation script of the DevOps.
2. The bank payment system disaster recovery switching platform based on DevOps according to claim 1, wherein the starting and stopping sequence of each application node, database node and network node of each bank payment system comprises: the method comprises the steps of firstly performing pre-application stop checking and application stop operation of an application node before disaster recovery switching, then performing pre-database switching checking, database switching and post-database switching checking operation of a database node, performing pre-network switching checking, network switching and post-network switching checking operation of a network node, and finally performing application starting and post-application starting checking operation of the application node after disaster recovery switching.
3. The bank payment system disaster recovery switching platform based on DevOps according to claim 1, wherein the various bank payment systems include a size system, a super internet banking system, a banking system and an internet networking system for interfacing with a people's bank.
4. The bank payment system disaster backup switching platform based on DevOps according to claim 1, wherein the database nodes perform master-slave copy switching in a semi-synchronous mode, that is, the bank payment system reads and writes a master database node of a master center and synchronizes logs to a backup database node of a backup center in real time.
5. A bank payment system disaster recovery switching method, wherein the method is implemented by using a bank payment system disaster recovery switching platform based on DevOps according to any one of claims 1-4, the method comprising: an operator logs in a disaster recovery switching platform of a bank payment system, firstly opens a disaster recovery switching pipeline, and then sequentially performs application operation before switching, database switching operation, network switching operation and application operation after switching.
6. The bank payment system disaster recovery switching method according to claim 5, wherein the pre-switch application operation includes an application pre-stop check operation and an application stop operation; the database switching operation comprises a checking operation before database switching, a database switching operation and a checking operation after database switching; the network switching operation comprises a checking operation before network switching, a network switching operation and a checking operation after network switching; the post-switch application operation comprises an application starting operation and an application post-start checking operation.
7. The bank payment system disaster recovery switching method according to claim 6, wherein the method further comprises:
checking whether the application stopping requirement is met in the current state, if so, performing application stopping operation, and returning to a normal stopping log after the completion;
checking whether the database node meets the switching condition, if so, using a database switching script to perform database switching operation, after the database switching is completed, checking whether the database node is successfully switched, and checking whether a background log has error reporting logs or abnormal information that the switching is unsuccessful;
checking IP information corresponding to the bank APP connection domain name by using a checking script before network switching, executing a network switching script to switch the IP information corresponding to the bank APP connection domain name, and checking whether the IP information corresponding to the bank APP domain name is successfully switched after the network switching is completed;
after the database node and the network node are successfully switched, the application is started, whether the switching state is normal is checked after the application is started, and if the switching state is normal, the switching is completed.
8. The bank payment system disaster recovery switching method according to claim 7, wherein the method further comprises:
after the operator completes the disaster backup switching of the bank payment system, the tester verifies the disaster backup switching result by logging in the bank APP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310658308.4A CN116450417B (en) | 2023-06-05 | 2023-06-05 | Bank payment system disaster backup switching platform and method based on DevOps |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310658308.4A CN116450417B (en) | 2023-06-05 | 2023-06-05 | Bank payment system disaster backup switching platform and method based on DevOps |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116450417A true CN116450417A (en) | 2023-07-18 |
| CN116450417B CN116450417B (en) | 2023-08-25 |
Family
ID=87125860
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310658308.4A Active CN116450417B (en) | 2023-06-05 | 2023-06-05 | Bank payment system disaster backup switching platform and method based on DevOps |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116450417B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040206A1 (en) * | 2012-08-02 | 2014-02-06 | Kadangode K. Ramakrishnan | Pipelined data replication for disaster recovery |
| CN104468244A (en) * | 2014-12-31 | 2015-03-25 | 北京奇虎科技有限公司 | Domain name resolution system disaster recovery construction method and device |
| US20170371636A1 (en) * | 2016-06-27 | 2017-12-28 | Vmware, Inc. | Methods and systems to optimize cost and automate a development and operations deployment pipeline |
| US20180074887A1 (en) * | 2016-09-15 | 2018-03-15 | International Business Machines Corporation | Using Predictive Analytics of Natural Disaster to Cost and Proactively Invoke High-Availability Preparedness Functions in a Computing Environment |
| CN110633174A (en) * | 2018-06-22 | 2019-12-31 | 中兴通讯股份有限公司 | Disaster recovery switching method, device and computer readable storage medium |
| CN112463440A (en) * | 2020-11-13 | 2021-03-09 | 中国建设银行股份有限公司 | Disaster recovery switching method, system, storage medium and computer equipment |
| US20220121477A1 (en) * | 2020-10-21 | 2022-04-21 | Opsera Inc | DevOps Declarative Domain Based Pipelines |
| CN116149722A (en) * | 2022-12-27 | 2023-05-23 | 启赟数字科技(上海)有限公司 | Devops automatic release system |
-
2023
- 2023-06-05 CN CN202310658308.4A patent/CN116450417B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140040206A1 (en) * | 2012-08-02 | 2014-02-06 | Kadangode K. Ramakrishnan | Pipelined data replication for disaster recovery |
| CN104468244A (en) * | 2014-12-31 | 2015-03-25 | 北京奇虎科技有限公司 | Domain name resolution system disaster recovery construction method and device |
| US20170371636A1 (en) * | 2016-06-27 | 2017-12-28 | Vmware, Inc. | Methods and systems to optimize cost and automate a development and operations deployment pipeline |
| US20180074887A1 (en) * | 2016-09-15 | 2018-03-15 | International Business Machines Corporation | Using Predictive Analytics of Natural Disaster to Cost and Proactively Invoke High-Availability Preparedness Functions in a Computing Environment |
| CN110633174A (en) * | 2018-06-22 | 2019-12-31 | 中兴通讯股份有限公司 | Disaster recovery switching method, device and computer readable storage medium |
| US20220121477A1 (en) * | 2020-10-21 | 2022-04-21 | Opsera Inc | DevOps Declarative Domain Based Pipelines |
| CN112463440A (en) * | 2020-11-13 | 2021-03-09 | 中国建设银行股份有限公司 | Disaster recovery switching method, system, storage medium and computer equipment |
| CN116149722A (en) * | 2022-12-27 | 2023-05-23 | 启赟数字科技(上海)有限公司 | Devops automatic release system |
Non-Patent Citations (1)
| Title |
|---|
| 刘方洲: "工商银行数据中心智能运维的探索与实践", 《中国金融电脑》, pages 8 - 12 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116450417B (en) | 2023-08-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107766502B (en) | Oracle RAC database disaster recovery switching drilling method | |
| CN110262972B (en) | Failure testing tool and method for micro-service application | |
| CN100461130C (en) | Method for testing a software application | |
| US7475275B2 (en) | Method for fault handling in a co-operative workflow environment | |
| ZA200400131B (en) | Method and system for correlating and determining root causes of system and enterprise events. | |
| CN101026494A (en) | Method and system for facilitating event management and analysis within a communications environment | |
| JP4239989B2 (en) | Fault recovery system, fault recovery device, rule creation method, and fault recovery program | |
| CN116450417B (en) | Bank payment system disaster backup switching platform and method based on DevOps | |
| US7260184B1 (en) | Test system and method for scheduling and running multiple tests on a single system residing in a single test environment | |
| CN105528259B (en) | A kind of application redundancy automation switching control design method | |
| WO2023124366A1 (en) | Shadow system-based feature comparison method and apparatus, and electronic device | |
| CN115599600A (en) | Disaster recovery switching method and device, storage medium and electronic equipment | |
| CN111737130B (en) | Public cloud multi-tenant authentication service testing method, device, equipment and storage medium | |
| CN114996039A (en) | Cloud native system joint debugging method, system and medium based on third-party system docking | |
| TWI733261B (en) | Method and system for configuring cloud service | |
| CN113342650A (en) | Chaos engineering method and device for distributed system | |
| CN113065001A (en) | Fault loss stopping method and device | |
| CN107145570B (en) | Method and system for maintaining server based on database service architecture | |
| TWI841390B (en) | Decentralized task cooperation control system | |
| CN114443296B (en) | Method, device, equipment and readable medium for returning high-availability event | |
| JP7189085B2 (en) | Abnormal location estimation device and method | |
| CN116185723B (en) | Database disaster recovery switching exercise method, device, computer equipment and storage medium | |
| CN103905241A (en) | Troubleshooting method and device | |
| JPH06250953A (en) | Computer network monitor and support system | |
| WO2023032116A1 (en) | Script identification device, script identification method, and script identification system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |