JP6676352B2 - Data processing device - Google Patents

Description

  The present invention relates to a data processing device.

  In recent years, computer systems using IT have become increasingly important in business. Therefore, the HA system (High Availability technology) for duplicating the computer system into a production system and a disaster countermeasure system and switching to the disaster countermeasure system when a failure occurs in the production system to continue the service is important. Has become.

  In particular, attention has been paid to a D / R (Disaster Recover) technique for quickly restoring a computer system using services and IT even in a large-scale disaster. In the D / R technology, data is protected by copying data between computer systems that are duplexed into a production system and a disaster countermeasure system. Therefore, it is most important that there is no data loss.

  FIG. 15 is a block diagram showing a configuration of a conventional D / R system. The conventional D / R system (Disaster Recover System) includes a production system 730 and a disaster countermeasure system 750 at a remote place. The production system 730 performs tasks such as data recording and retrieval. On the other hand, the disaster countermeasure system 750 stores the same contents as the production system 730 and plays a role as a backup site for the production system 730.

  The production system 730 includes a production Web / application (AP) server 732 and a production database (DB) server 734. The disaster countermeasure system 750 includes a disaster countermeasure Web / application (AP) server 752 and a disaster countermeasure database (DB). ) Server 754. In contrast to the production system 730, the disaster countermeasure system 750 is installed at a remote location, and both systems are connected by a dedicated line.

  In normal times, when a request is transmitted from the client terminal 720a via the network 727, the request is transferred to the production Web / AP server 732. The production Web / AP server 732 that has received this executes a process according to the content of the request, and transmits the processing result to the production DB server 734. The production DB server updates the corresponding table based on the processing result data received from the production Web / AP server 732. The production system 730 transfers the data as the processing result to the disaster recovery database (DB) server 754 of the disaster recovery system 750 at some timing. The disaster countermeasure DB server 754 updates the corresponding table based on the data as the received processing result. When a failure occurs, the system is switched, and the disaster recovery system 750, which was the backup site, takes over and executes the business.

  By the way, data transfer between systems also uses copying by an inter-database network. In order to ensure complete identity between the data stored in the production DB server 734 and the data stored in the disaster recovery DB server 754, first, the processing result is transmitted from the production DB server to the disaster recovery DB server, Ideally, a synchronous mode is adopted in which the update to the production DB server is executed when the update completion notification is returned. However, due to the nature of the disaster countermeasure system, it is difficult to adopt the synchronous mode at a long distance because it is installed at a long distance from the production system due to the network delay. Therefore, at present, data in the production database is copied to the disaster recovery database in an asynchronous mode.

  However, when data in the production database 730 is copied to the disaster recovery database 750 in the asynchronous mode, a delay due to the data transfer processing occurs, and thus data loss may occur. For example, in the case of transferring data once a day after the work is completed, if the production system 730 fails before the data transfer, the failure occurs in the production system 730 after the last data transfer. The data reflected in the production DB server 734 of the production system 730 is lost by the time it occurs.

  Therefore, for example, as shown in FIG. 16, the database management system disclosed in Patent Literature 1 uses a backup data backed up on a daily basis or the like on a server after a backup when a database failure occurs. The server transaction log 834 that converts the determined transaction executed in the above into a SQL statement and holds the same, and the client transaction log 823 that converts the confirmed transaction executed by the client into a SQL statement and holds the client, are collected. The database is restored by reflecting it.

JP-A-2000-20369

  However, the conventional example disclosed in Patent Literature 1 has a problem that it is extremely difficult to collect logs from a client in a situation where an unspecified number of devices connected to a wide area network such as the Internet are connected. is there.

  The present invention seeks to solve the above-mentioned problems associated with the prior art, and aims to copy data of a production database server to a disaster recovery database server in an asynchronous mode in an ordinary mode. Even in this case, it is possible to prevent data loss due to delay due to data transfer processing without using the client terminal or the SQL statement or log information of the client.

  According to one embodiment of the present invention, a first receiving unit that receives a copy of a first message that a client sends to a server to request a database update, and the server updates the database from the first message. And a message storage unit that stores the message when the database has been successfully changed and a message for generating a database operation statement for the message is successfully provided.

  The server generates a message for generating a database operation statement for updating the database from the first message and receives a copy of a second message for returning a result of executing the operation of changing the database to the client. The data processing device may further include a second receiving unit that generates the message and a message generating unit that generates the message from the copy of the first message or the copy of the second message.

  According to one embodiment of the present invention, a first receiving unit that receives a copy of a first message that a client sends to a server to request a database update, and the server updates the database from the first message. And a copy storage unit for storing a copy of the first message when a message for generating a database operation statement is generated and the change of the database is successful.

  In another preferred aspect, the server generates a message for generating a database operation statement for updating the database from the first message, and returns a result of executing the operation of changing the database to the client. A second receiving unit that receives a copy of the second telegram, wherein the copy storage unit stores a copy of the first telegram or a second telegram when the copy of the second telegram indicates a successful operation of changing the database; May be a data processing device that stores a copy of the data.

  In another preferred aspect, a data process including a message generation unit that generates a message for generating a database operation statement generated by the server from a copy of a first message or a copy of a second message stored in the storage unit It may be a device.

  According to an embodiment of the present invention, a first receiving unit that receives a copy of a first message transmitted to a server by a client to request a database update, and a copy storage unit that stores a copy of the first message. The server generates a message for generating a database operation statement for updating the database from the first message, and when the change of the database is successful, a copy of the first message according to the success is added to the database. It is possible to provide a data processing device having a history management unit for adding control information indicating the success of the change operation.

  The server generates a message for generating a database operation statement for updating the database from the first message and receives a copy of a second message for returning a result of executing the operation of changing the database to the client. Having a second receiving unit, the copy storage unit stores a copy of a second message, the history management unit, when the copy of the second message indicates a successful operation of the change of the database, The data processing device may be characterized in that control information indicating a success of a database change operation is added to the copy of the first message and the copy of the second message.

  A message generation unit that generates a message for generating a database operation statement generated by the server from a copy of the first message or a copy of the second message to which the control information indicating the success has been added, and stores the message. The data processing device may further include a message storage unit.

  In another preferred aspect, the data processing device may include a detection unit that detects that a failure has occurred in the server.

  In another preferred aspect, the data processing device may include a switching unit that operates as the server when a failure occurs in the server.

  In another preferred aspect, the switching unit may be a data processing device that updates route information from the client to the server when a failure occurs in the server.

  In another preferred aspect, a first associating unit that associates a copy of the first message received by the first receiving unit with a transaction of the database by the first message, and a second message received by the second receiving unit And a first determination unit that determines which copy of the database is to return a result of executing a change operation in the database, wherein the copy storage unit is determined by the first determination unit. The data processing device may store a copy of the first message or a copy of the second message associated with the transaction of the copy of the second message.

  In another preferred aspect, a second associating unit that associates a copy of the first message received by the first receiving unit with an identifier of a client of a transmission source, and a destination of the second message received by the second receiving unit A second determining unit that determines the identifier of the client of the first message or the copy of the first message associated with the transaction of the copy of the second message determined by the second determining unit. The data processing device may store a copy of the second telegram.

  In another preferred aspect, the second associating unit further associates a time at which a copy of the first telegram is received, and the copy storage unit performs the second associating in addition to the determination by the second determining unit. The data processing device may store a copy of the first message or a copy of the second message based on a time associated with the second message and a time at which the copy of the second message is received.

  According to an embodiment of the present invention, a first receiving unit that receives a copy of a first message transmitted by a client to a server to request a database update, and a copy of session identification information transmitted from the server to the client , A copy storage unit that stores a copy of the first message and a copy of the session identification information, and a copy of the first message and the session identification information that are stored in the copy storage unit. A second message generating unit for generating a second message to be returned to the client from the copy of the message, and a detecting unit for detecting that a failure has occurred in the server, wherein the second message generating unit includes: It is possible to provide a data processing device that generates the second message after detecting that a failure has occurred in the server. That.

  The data processing device may return the second message and the session identification information to a client.

  A message generation unit that generates a message for generating a database operation statement generated by the server from a copy of the first message stored in the copy storage unit, wherein the message generation unit includes: The data processing device may be configured to generate the telegram when detecting that a failure has occurred in the server.

  The server may include a switching unit that operates as the server when a failure occurs in the server.

  According to an embodiment of the present invention, a first receiving unit that receives a first message transmitted by a client to request an update of a first database, a first message storage unit that stores the first message, A second message generator for generating a second message returned to the client; and a detector for detecting that a failure has occurred in the first database, wherein the second message generator is configured such that the detector has the second message. A data processing device may be provided that generates the second telegram after detecting that a failure has occurred in one database.

  A message generator for generating a message for generating a database operation statement from the first message stored in the first message storage unit, and a transmission for transmitting the message for generating the database operation statement to a second database; A data processing apparatus may be provided, further comprising a unit, wherein the message generation unit generates the message when the detection unit detects that a failure has occurred in the server.

  The information processing apparatus further includes a second receiving unit that receives information indicating that the change of the second database that has received the message is successful, wherein the second message generation unit indicates that the change of the second database is successful. A data processing device that generates the second telegram based on the information may be provided.

  According to an embodiment of the present invention, a basic information storage unit that stores information serving as a basis for generating a database operation statement, a receiving unit that receives an active system switching notification, and the switching notification that is received by the receiving unit And a transmission unit for transmitting information, which is stored in the basic information storage unit and is a basis for generating the database operation statement, to a database.

  The basic information storage unit may store only information on updating the database.

  The information processing apparatus may further include an extraction unit that extracts only information on updating the database from the basic information storage unit and transmits the information to the transmission unit.

  The basic information storage unit stores a second message that returns a result of the update processing of the database to the client, and a first message that is received from the client corresponding to the information on which the database operation statement is generated. And a collation unit for collating whether the first message and the second message are associated with each other.

  The transmitting unit may transmit, to the database, information serving as a basis for generating the database operation statement when the first message and the second message are not compared in the matching unit.

  According to an embodiment of the present invention, a relay unit that relays a message transmitted from a client to a server to request a database update to the server, and a database operation statement for the server to update the database from the message. And a generation unit that generates a copy of the message relayed by the relay unit when the database is successfully changed and the database is successfully changed.

  According to the present invention, even when the data of the production database server is normally copied to the disaster recovery database server in the asynchronous mode, the data transfer is performed without using the SQL statement or log information of the client terminal or the client. Data loss due to delay due to processing can be prevented from occurring.

It is a block diagram showing an example of composition of a D / R system concerning one embodiment of the present invention. 1 is a block diagram illustrating an example of a configuration of a data processing device according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a header table of request data and response data according to an embodiment of the present invention. It is a figure showing an example of a statement sentence and list data concerning one embodiment of the present invention. 1 is a block diagram illustrating an example of a configuration of a data processing device according to an embodiment of the present invention. It is a figure showing that control information which shows success of operation of database change was added to request data and response data concerning one embodiment of the present invention. It is a block diagram showing an example of the composition of the D / R system concerning other embodiments of the present invention. It is a block diagram showing an example of the composition of the D / R system concerning other embodiments of the present invention. It is a block diagram showing an example of the relation between each system concerning one embodiment of the present invention. FIG. 11 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. It is a block diagram showing an example of the composition of the D / R system concerning other embodiments of the present invention. FIG. 11 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. FIG. 11 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. FIG. 11 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. FIG. 11 is a block diagram illustrating an example of a configuration of a conventional D / R system. It is a block diagram showing an example of a conventional database management system.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The embodiments described below are examples of the embodiments of the present invention, and the present invention is not limited to these embodiments. In the drawings referred to in the present embodiment, the same portions or portions having similar functions are denoted by the same reference numerals or similar reference numerals (reference numerals in which A, B, etc. are added after numerals). May be omitted. On the other hand, even when the same portion or a portion having a similar function is provided with a similar code (a code obtained by adding A, B, or the like after a number), a distinction is made between the portions provided with the similar code. Is unnecessary, similar symbols are omitted. For example, when there is no need to distinguish client terminals, they are simply described as “client terminals”.

<First embodiment>
[Configuration of D / R system]
An outline of a D / R system (Disaster Recover System) will be described with reference to FIG. FIG. 1 is a block diagram illustrating an example of a configuration of a D / R system according to an embodiment of the present invention. The D / R system includes a production system 30 and a disaster countermeasure system 50 at a remote location. The production system 30 performs tasks such as data recording and retrieval. On the other hand, the disaster countermeasure system 50 stores the same contents as the production system 30, and plays a role as a backup of the production system 30. Note that both the production system 30 and the disaster countermeasure system 50 are composed of a primary system and a secondary system (not shown). For example, when the main system of the production system stops due to a failure, the operation is performed such that the system is switched to the sub system of the production system. On the other hand, when both the primary system and the secondary system of the production system 30 stop due to a large-scale disaster or the like, that is, when the production system 30 stops, the system switches to the disaster countermeasure system 50. In the following, a case where the production system 30 stops and switches to the disaster countermeasure system 50 will be described.

  The production system 30 includes a production Web / application (AP) server 32 and a production database (DB) server 34, and the disaster countermeasure system 50 includes a disaster countermeasure Web / application (AP) server 52 and a disaster countermeasure database (DB). ) Server 54. In contrast to the production system 30, the disaster countermeasure system 50 is installed at a remote location, and both systems are connected by a dedicated line. In this example, both the production system and the disaster countermeasure system are Web / AP servers and a DB server, and are not limited to this. However, the present invention is not limited to this, and Web / AP servers and a DB server are used. Alternatively, it may be a one-layer system in which a Web server, an AP server, and a DB server are integrated into one.

  In normal times, when a request is transmitted from the client terminal 20a via the network 27, the request is transferred to the production Web / AP server 32. The production Web / AP server 32 that has received this executes a process according to the content of the request, and transmits the processing result to the production DB server 34. The production DB server updates the corresponding table based on the processing result data received from the production Web / AP server 32. The production system 30 transfers data as a processing result to the disaster recovery database (DB) server 54 of the disaster recovery system 50 at some timing. The disaster countermeasure DB server 54 updates the corresponding table based on the data as the received processing result. If a failure occurs, the system is switched, and the disaster recovery system 50, which was the backup site, takes over and executes the business. This is the same as the conventional technology.

  In the production system 30, each of the client terminals 20 connects to the production server 32 via a network. The production server 32 receives data from the client terminal 20 and updates the production database 34 via the network 27.

  The network 27 is a network such as a LAN (local area network), a WAN (wide area network), or the Internet, and is a network environment in which the client terminal 20 can connect to the production server 32 regardless of a wireless / wired line, a dedicated line, or the like. Is applied.

  The client terminal 20 includes a multifunctional mobile phone, a mobile communication terminal such as a mobile phone and a PDA (Personal Digital Assistant), an information processing terminal having a communication function and an arithmetic function such as a personal computer, and the like. In addition, a browser is provided as a display control function for displaying a screen provided by the production server 32, and includes a CPU, a memory, a communication control unit that performs communication control with the production server, and the like. Furthermore, an operation input device such as a mouse, a keyboard, and a touch panel and a display device can be provided.

[Configuration of data processing device]
The data processing device 52 will be described with reference to FIG. FIG. 2 is a block diagram illustrating an example of a configuration of a data processing device according to an embodiment of the present invention. The data processing device (disaster countermeasure server) includes a first receiving unit 521, a second receiving unit 522, a collating unit 523, a message generating unit 525, a detecting unit 526, a switching unit 527, a temporary table 541, a transaction execution table 543, and a recovery table. 545.

  The first receiving unit 521 receives all copies of the request data (first message) transmitted from the client terminal 20 to the production Web / AP server 34 in order to request the update of the production DB server 34. Specifically, when the client transmits, for example, request data for fund transfer by screen input of a browser or the like of the client terminal 20, the transmitted request data is transmitted to the production Web of the production system 30 via the network 27. / AP server 32. At this time, a copy of the fund transfer request data is transferred from the network 27, and the first receiving unit 521 of the data processing device 52 receives the copy. The details of the request data will be described later.

  The second receiving unit 522 generates a message (statement statement) for the production Web / AP server 32 to generate an SQL statement (database operation statement) for updating the production DB server 34 from the request data (first message). Then, a copy of the response data (second message) for returning the result of executing the operation of changing the production DB 34 to the client terminal 20 is received via the network 27. Specifically, for example, when a request for fund transfer is made from the client terminal 20, the production Web / AP server 32 generates a statement sentence and list data from the request data. Then, the statement statement and the list data are transmitted from the production Web / AP server 32 to the production DB server 34, and the production DB server 34 generates and executes an SQL statement from the statement statement and the list data. When the SQL statement is executed, the corresponding table of the production DB server 34 is updated for the fund transfer. Thereafter, the production Web / AP server 32 receives the result updated by the production DB server 34 and transmits response data to the client terminal 20. The details of the response data, statement statement, and list data will be described later.

  The transaction execution table (copy storage unit) 543 includes a statement sentence for the production Web / AP server 32 to generate an SQL statement (database operation statement) for updating the production DB server 34 from the request data (first telegram). When the list data is generated and the change of the production DB server 34 is successful, a copy of the request data (first message) is stored. Specifically, the transaction execution table 543 stores a copy of the request data (first message) when the copy of the response data (second message) indicates that the operation of changing the production DB server 34 is successful.

  Here, a copy of request data and a copy of response data will be described with reference to FIG. FIG. 3 is a diagram showing an example of a table for copying request data and copying response data according to an embodiment of the present invention. When the first receiving unit 521 receives the copy of the request data, the temporary table 541 stores the copy of the request data in chronological order. Further, when the second receiving unit 522 receives the copy of the response data, the temporary table 541 stores the copy of the response data in chronological order. FIG. 3A shows a table in which copies of request data are classified in time series, and FIG. 3B shows a table in which copies of request data are classified in time series. All the copies of the request data are stored in the table in which the copies of the request data are classified in time series, and all of the copies of the response data are stored in the table in which the copies of the response data are classified in time series. Each copy of data is composed of a header and a body, but FIG. 3 shows only the header.

  As shown in FIG. 3, the request header table 110 includes a time 111, an IP address 112, request contents 113, a user name (client name) 114, and a user ID (client ID) 115. Looking at the request header table 121, the user name “A” and the user ID “23451022” request the “transfer approval screen” from the IP address “192.168.236.61” at the time “9:01”. You can see that it is doing. Looking at the request header table 122, the user name “Taro Yamada” and the user ID “98765432” request “balance inquiry” from the IP address “192.168.1.70” at the time “9:02”. You can see that it is doing.

  On the other hand, the response header table 130 includes a time 131, an IP address 132, a status 133, a user name 134, and a user ID 135. Looking at the response header table 141, at time “9:02”, “Status = 200” for the user name “A”, the user ID “23451022”, and the IP address “192.168.236.61” It can be seen that the response has been made. This means that the status code is returned from the production server to the browser or the like. If the status code is in the 200s, it means that normal processing has been performed. However, even if the transfer is completed or the balance is insufficient, the process is still normal even if the process fails. Therefore, it cannot be determined from the status code 200 that the fund transfer has succeeded. In order to determine whether or not the fund transfer has succeeded, it is determined based on a transaction name or a processing ID indicating the completion of the transfer.

  The configuration of the data processing device 52 will be described again with reference to FIG. The collating unit 523 includes a first associating unit 531, a first determining unit 533, a second associating unit 535, and a second determining unit 537.

  The first associating unit 531 associates a copy of the request data (first message) received by the first receiving unit 521 with a transaction of the production DB server 34 by the request data. Specifically, for example, if the content of the request in the copy of the request data is “transfer approval screen”, the transaction of the production DB server by the request data is also associated with the “transfer approval screen”.

  The first determining unit 533 determines which copy of the response data (second telegram) received by the second receiving unit 522 returns the result of executing a change operation in a transaction of the production database 34. Specifically, as described above, the response header table includes a user name and a user ID. For example, the user name “A” and the user ID “23451022” request the “transfer approval screen” at the time “9:01” from the IP address “192.168.236.61”. If the response header includes the user name “A Co., Ltd.” and the user ID “23451022”, it can be determined that the result of executing the change operation in the transaction “transfer approval screen” is returned.

  Then, when the change of the production DB server is successful, the transaction execution table 543 stores the request data (first message) associated with the copy transaction of the response data (second message) determined by the first determination unit 533. A copy or a copy of the response data is stored. More specifically, a copy of the request data is extracted from a table in which the copies of the request data are classified in time series, updated, and in this example, whether or not the request is a fund transfer request is analyzed. In the case of a copy of the fund transfer request, if the copy of the response data corresponding to the request has a transaction name or a processing ID indicating the completion of the transfer, it is determined that the fund transfer has been completed, and the transaction execution table 543 indicates Then, a copy of the fund transfer request data or a copy of the response data corresponding to the fund transfer request data is stored in the table. On the other hand, whether the request is a fund transfer request is analyzed and a copy of the request data determined to be not a fund transfer request and a copy of the corresponding response data are deleted from the temporary table (table in FIG. 3) 541. . Here, it is called a temporary table because it is temporarily stored.

  The second associating unit 535 associates the copy of the request data (first message) received by the first receiving unit 521 with the identifier of the client terminal 20 of the transmission source. Specifically, as described above, the request header table 110 includes an IP address (identifier of a client terminal) and browser information (not shown). For example, the user name “A” and the user ID “23451022” request the “transfer approval screen” at the time “9:01” from the IP address “192.168.236.61”. Therefore, the second associating unit 535 associates the IP address “192.168.236.61” with the copy of the request data received by the first receiving unit 521.

  The second associating unit 535 further associates the time at which the copy of the request data (first message) was received. Specifically, the request header table 110 includes time data. For example, the user name “A” and the user ID “23451022” request the “transfer approval screen” at the time “9:01” from the IP address “192.168.236.61”. Therefore, the second associating unit 535 associates the time “9:01” with the copy of the request data received by the first receiving unit.

  The second determination unit 537 determines the identifier of the client terminal 20 to which the response data (second message) received by the second reception unit 522 is transmitted. Specifically, the response header table 130 includes the IP address (identifier) of the client terminal 20 to which the response is sent. For example, in the response header table 141, at time “9:02”, a response “Status = 200” is made to the IP address “192.168.236.61”, and the IP address “192” .168.236.61 ". The second determining unit determines the IP address “192.168.236.61”.

  The transaction execution table 543 stores the copy of the request data or the copy of the response data associated with the transaction of the copy of the response data determined by the determination by the second determination unit 537 when the change of the production DB server is successful. I do. For example, the second determination unit 537 determines the IP address “192.168.236.61” and the user ID of the response header. A copy of the request data is extracted from a table in which the copy of the request data is classified in time series, and is updated. In this example, whether or not the request is a fund transfer request is analyzed. In the case of a copy of the fund transfer request, if the copy of the response data corresponding to the request includes a transaction name or a processing ID indicating the completion of the transfer, it is determined that the fund transfer has been completed, and the transaction execution table 543 is determined. Stores a copy of the fund transfer request data or a copy of the response data corresponding to the fund transfer request data in a table. On the other hand, whether the request is a fund transfer request is analyzed and a copy of the request data determined to be not a fund transfer request and a copy of the corresponding response data are deleted from the temporary table (table in FIG. 3) 541. .

  When the change of the production DB server is successful, the transaction execution table 543 indicates the time when the copy of the request data and the time when the copy of the response data are received in addition to the above-described determination by the second determination unit 537. And a copy of the request data or a copy of the response data may be stored. Specifically, as shown in the request header table 121, the user name “A” and the user ID “23451022” are changed from the IP address “192.168.236.61” at time “9:01” to “ Transfer approval screen ". On the other hand, as indicated by the response header table 141, at time “9:02”, “Status” for the user name “A”, the user ID “23451022”, and the IP address “192.168.236.61”. = 200 ”.

  When the request header table 121 and the response header table 141 are compared, since the same user name “A Co., Ltd.”, user ID “23451022”, and IP address “192.168.236.61” exist, the user name “stock” It can be understood that the fund transfer request by the “company A” and the user ID “23451022” was successfully processed. The transaction execution table 543 may store a copy of the request data or a copy of the response data when the copy of the response data indicates the success of the operation of changing the production database, as in this example.

  The statement sentence and the list data will be described with reference to FIG. FIG. 4 is a diagram illustrating an example of a statement sentence and list data according to an embodiment of the present invention. The message generation unit 525 generates an SQL statement generated by the production Web / AP server 32 from a copy of the request data (first message) or a copy of the response data (second message) stored in the transaction execution table 543. To generate a statement statement and list data. As shown in FIG. 4, the statement sentence and the list data include data “YOFFKFKM0601P”, which is data indicating a transfer. 4A and 4B, the statement statement and the list data include the same “2015 08/26 15:44:26 7800067760admin001 YOFFKFKM0601P 5171318f-9eba-4226-ae67-063dfe1370c2”. There is data, and this data makes it possible to link the statement sentence with the list data.

  When the statement statement and the list data are created from the copy of the request data, specifically, the program obtains the destination information, the destination information, and the amount information from the transaction execution table 543, calls the transfer service program, and calls the destination information. Then, the destination information and the money amount information are passed as parameters and executed. Here, the same service program is used in the production system as the transfer service program. However, in this embodiment, unlike the production system, the data processing device (Web server / disaster countermeasure server) is connected to the disaster recovery DB server. Not connected. Therefore, the transfer service program stops before connecting to the disaster recovery DB server, and outputs a processing result at the time of the stop. The result of this processing is a statement sentence and list data as shown in FIG. Then, the recovery table (message storage unit) 545 stores the statement statement and the list data, respectively. As shown in FIG. 4A, since the processing result is obtained at the time of stopping before connection to the disaster recovery DB server, the statement sentence includes “?” As in “CRP_NO =?”. , Are not SQL statements.

  When creating a statement and list data from a copy of the response data, the copy of the response data contains destination information, destination information, amount information, and transfer completion information. As in the case of creating the list data, the program acquires the destination information, the destination information, and the amount information from the transaction execution table 543, calls the transfer service program, and sets the destination information, the destination information, and the amount information as parameters. And run. As a result, a statement and list data are obtained, and the recovery table 545 stores the statement and list data, respectively.

  The detection unit 526 detects that a failure (disaster) has occurred in the production system including the production Web / AP server. Specifically, the detection unit 526 of the data processing device 52 of the disaster countermeasure system 50 always transmits a signal to the production system 30, and the production system 30 responds to the detection unit 526 with a response signal. When the response signal disappears, the detection unit 526 regards that a disaster has occurred.

  When the detection unit 526 detects that a failure (disaster) has occurred in the production Web / AP server 32, the switching unit 527 operates the data processing device (disaster recovery Web / AP server) 52 as the production Web / AP server 32. Switch to that. When a failure occurs in the production Web / AP server 32, the switching unit 527 updates the route information from the client terminal 20 to the production Web / AP server 32. That is, the connection destination of the client terminal 20 is switched to the disaster countermeasure Web / AP server by changing the setting of the DNS server (not shown). Further, when a failure occurs in the production Web / AP server 32, the data of the production DB server 34 is stopped from being asynchronously copied to the disaster recovery DB server 54.

  Here, when the statement and list data are transferred from the recovery table 545 to the disaster recovery DB server 54 after the above switching, the statement and list data to be transferred are limited. That is, in normal times, since the data is asynchronously transferred from the production DB server 34 to the disaster recovery DB server 54, only the statement sentence and the list data corresponding to the data not yet transferred need to be transferred. Therefore, the data in the recovery table 545 and the data in the disaster recovery DB server 54 are compared, and statement statements and list data corresponding to data that has not been transferred yet are transferred to the disaster recovery DB server 54. Specifically, the time information of the recovery table 545, the information of the user name or the user ID, the time information of the disaster recovery DB server 54, and the information of the user name or the user ID are compared to transfer data that has not been transferred yet. It is. The following method can be considered as a method of transferring data that has not been transferred yet. That is, at the timing when data is asynchronously transferred from the production DB server 34 to the disaster recovery DB server 54 in normal times, a signal indicating that the transfer is completed is transmitted to the data processing device. Then, the data processing device receiving this signal discards the data stored in the recovery table 545. After that, since the data stored in the recovery table 545 has not been transferred yet by the time the detecting unit 526 detects that a disaster has occurred, the data is transferred to the disaster recovery DB server 54.

  In the related art, the data processing device (disaster countermeasure Web / AP server) 52 is not particularly used in normal times. On the other hand, according to the present embodiment, in normal times, the temporary table 541 of the data processing device (disaster countermeasure Web / AP server) stores a copy of request data and a copy of response data as described above. When the request data is a fund transfer request, the transaction execution table 543 determines that the fund transfer has been completed if the copy of the response data includes a transaction name or a process ID indicating the completion of the transfer, and A copy of the request data and a copy of the response data are stored. Specific data is acquired from the transaction execution table 543, a transfer service program is executed, a statement statement and list data are created, and stored in the recovery table 545. Thereafter, the statement sentence and the list data corresponding to the data not yet transferred to the disaster recovery DB server 54 are effectively used such as being used for updating the disaster recovery DB server.

  In this embodiment, there are a plurality of types of transactions. For example, "transfer approval screen", "balance inquiry", "file upload", "TOP", and the like. In the case of the “transfer approval screen” of this transaction, since the request data is a fund transfer, the data of the production DB server 34 is updated. On the other hand, if the transaction is “balance inquiry”, the data of the production DB server 34 is not updated. In the present embodiment, the transaction execution table 543 stores a copy of the request data or a copy of the response data when the copy of the response data indicates the success of the operation of changing the production database 34, for example, in the case of a fund transfer. I do. Therefore, there is an effect that only an update such as a fund transfer can be restored as data from one of the request data copy and the response data copy.

  Further, according to the conventional technology, a person manually recognizes that a disaster has occurred, and manually switches the data processing device (disaster countermeasure Web / AP server) 52 to operate as the production Web / AP server 32. I was going. In addition, it takes time to manually perform this switching. On the other hand, according to the present embodiment, when the detection unit detects that a failure (disaster) has occurred in the production system including the production Web / AP server, the switching unit sets the data processing device (disaster recovery Web / AP server). 52 is automatically switched to operate as the production Web / AP server 32. Therefore, according to the present embodiment, there is an effect that the time required to switch the data processing device (disaster countermeasure Web / AP server) 52 to operate as the production Web / AP server 32 is reduced.

  Further, according to the present embodiment, as described above, the data processing device (disaster countermeasure Web / AP server) 52 uses the statement statement and the list from the copy of the request data or the copy of the response data stored in the transaction execution table 543 as described above. The data is generated, and the recovery table 545 stores the statement sentence and the list data. Then, when a failure (disaster) occurs in the production system including the production Web / AP server 32, the data processing device 52 outputs a statement sentence corresponding to data that was not normally transferred among the statement sentence and the list data. The list data is transferred to the disaster recovery DB server 54. Then, the disaster countermeasure DB server 54 generates and executes an SQL statement from the transferred statement statement and list data, and updates the data of the disaster countermeasure DB server. Therefore, even in a case where the data of the production DB server 34 is normally asynchronously copied to the disaster recovery DB server 54, the data transfer processing is performed without using the SQL statement or log information of the client terminal 20 or the client. Data loss due to the delay can be prevented from occurring.

  Further, the request data also includes, for example, client ID and password data (not shown in FIG. 3). For example, there is request data such as a fund transfer, and the production DB server is updated. After that, a failure occurs in the production DB server, and the request data such as the fund transfer is transferred from the production DB server to the disaster recovery DB server. Is not transferred, the client ID and password data can be used. Specifically, by generating a dummy client from the data of the client ID and the password, logging in, and performing a transaction such as a transfer of funds, the transaction can be restored and the disaster recovery DB server can be updated.

<Second embodiment>
A data processing device including a history management unit will be described with reference to FIGS. FIG. 5 is a block diagram illustrating an example of a configuration of a data processing device according to an embodiment of the present invention. FIG. 6 is a diagram showing that request information and response data according to an embodiment of the present invention are added with control information indicating the success of a database change operation. This embodiment is substantially the same as the first embodiment. Therefore, the description of the overlapping part will be omitted, and different points will be described. The data processing device 52C according to the present embodiment includes a history management unit 530 unlike the first embodiment. The copy storage unit 551 of the data processing device 52C according to the present embodiment stores a copy of all request data (first message) and a copy of response data (second message).

  The history management unit 530 generates a statement statement and a list data for the production Web / AP server to generate an SQL statement (database operation statement) for updating the production DB server from the request data, and generates the statement statement and the list data. When the change of the production DB server is successful based on the above, control information indicating the success of the change of the production DB server is added to the copy of the request data relating to the success. As shown in FIG. 6, the control information 116 of the request header table 121 is input with control information indicating that the change of the production DB server was successful. On the other hand, such control information is not input to the request header tables 122 to 124. This is because the production DB server is not changed in the balance inquiry, the TOP screen, and the file upload.

  In addition, when the response data copy succeeds in changing the production DB server, the history management unit 530 adds control information indicating the success in changing the production DB server to the request data copy and the response data copy. Good. As shown in FIG. 6, the control information 116 of the request header table 121 and the control information 137 of the response header table 141 are input with control information indicating that the change of the production DB server has been successful.

  The message generator 525 generates a SQL statement generated by the production Web / AP server from a copy of the request data or the copy of the response data to which the control information indicating the success of the change of the production DB server has been added. Generate list data. That is, the message generation unit 525 adds control information indicating the success of the change of the production DB server as shown in FIG. 6 among all the copy of the request data or the copy of the response data stored in the copy storage unit 551. The statement text and the list data are generated only from the copy of the request data or the copy of the response data.

  The message storage unit 553 stores the statement sentence and the request data generated by the message generation unit 525.

  In the present embodiment, similarly to the first embodiment, there is an effect that in a normal time, a data processing device (disaster countermeasure Web / AP server) that is not particularly used can be effectively used. Also, in the present embodiment, similarly to the first embodiment, there is an effect that the time required to switch the data processing device to operate as the production Web / AP server is reduced. Further, in the present embodiment, as in the first embodiment, even in the case where data of the production DB server is asynchronously copied to the disaster recovery DB server in normal times, the SQL statement and log information of the client terminal and the client are used. Can be prevented without causing data loss due to a delay due to the data transfer process.

  Also in this embodiment, as in the first embodiment, only an update such as a fund transfer can be restored as data from either one of the request data copy and the response data copy.

  Further, in the present embodiment, as in the first embodiment, a dummy client is generated from the client ID and password data in the request data, and the transaction is restored by logging in and performing a transaction such as a transfer of funds. Then, the disaster countermeasure database can be updated.

<Third embodiment>
FIG. 7 is a block diagram illustrating an example of a configuration of a D / R system according to another embodiment of the present invention. This embodiment is substantially the same as the first embodiment. Therefore, the description of the overlapping part will be omitted, and different points will be described. In the present embodiment, the detection unit 526 of the first embodiment is not inside the data processing device (disaster countermeasure Web / AP server) 52, and the detection unit 36 is outside. The detection unit 36 detects a disaster and transmits a signal indicating the disaster to the data processing device 52. The data processing device according to the present embodiment includes a disaster information data receiving unit (not shown) that receives data transmitted by the detecting unit 36, unlike the data processing device according to the first embodiment.

  As an example, the production system 30 includes a primary system 30a and a secondary system 30b, the primary system 30a and the secondary system 30b monitor each other, and the detection unit 36 performs integrated monitoring. When the monitoring of the main system 30a and the monitoring of the sub system 30b are stopped, there is no communication. At that timing, the detection unit 36 outputs data indicating that a disaster has occurred to the disaster information data receiving unit of the data processing device 52. Send to When the disaster information data receiving unit receives this data, the switching unit automatically switches the data processing device 52 to operate as the production Web / AP server 32. It should be noted that a seismometer may be used together to detect an earthquake.

  As another example, when the detection unit 36 performs system integrated monitoring for monitoring the primary system 30a and the secondary system 30b of the production system 30, and it is determined that all of the production systems 30 have been stopped by the integrated monitoring. Then, the detecting unit 36 may transmit a signal indicating that the disaster is present to the disaster information data receiving unit of the data processing device 52. In this case, since the detection unit 36 detects and operates before an earthquake occurs before the earthquake occurs, it transmits a signal indicating a disaster to the disaster information data reception unit before the detection unit 36 stops. It is possible to do. It should be noted that a seismometer may be used together to detect an earthquake.

  Further, as still another example, the detection unit 36 performs system integrated monitoring for monitoring the primary system 30a and the secondary system 30b of the production system 30, and all or a part of the production system 30 is stopped by the integrated monitoring. If the determination is successful, the detection unit 36 may transmit a signal indicating a disaster to the disaster information data receiving unit of the data processing device 52.

  In the present embodiment, similarly to the first embodiment and the second embodiment, there is an effect that a data processing device (disaster countermeasure Web / AP server) that is not particularly used can be effectively used in normal times. . Also in the present embodiment, similarly to the first embodiment and the second embodiment, there is an effect that the time required to switch the data processing device to operate as a production Web / AP server is reduced. Further, in the present embodiment, similarly to the first and second embodiments, even when the data of the production DB server is normally asynchronously copied to the disaster recovery DB server, the client terminal and the Without using an SQL statement or log information, it is possible to prevent data loss due to delay due to data transfer processing.

  Also, in the present embodiment, as in the first and second embodiments, only an update such as a fund transfer is restored as data from one of the request data copy and the response data copy. Can be.

  Further, in the present embodiment, similarly to the first and second embodiments, a dummy client is generated from the client ID and password data in the request data, logged in, and a transaction such as a transfer of funds is performed. Thus, the transaction can be restored and the disaster recovery database can be updated.

<Fourth embodiment>
The case where the data relay device 60 is located in the middle of the client terminal 20 and the network 27 will be described with reference to FIG. FIG. 8 is a block diagram illustrating an example of a configuration of a D / R system according to another embodiment of the present invention. The data relay device 60 includes a relay unit 601 and a generation unit 603.

  The relay unit 601 relays, to the production Web / AP server 32, request data transmitted from the client terminal 20 to the production Web / AP server 32 to request an update of the production database 34. The relay unit 601 is, for example, an Internet service provider.

  The generation unit 603 generates a statement statement and list data for the production Web / AP server 32 to generate an SQL statement (database operation statement) for updating the production DB server 34 from the request data, and changes the production database 32. If successful, a copy of the request data relayed by the relay unit 601 is generated.

  According to the present embodiment, it is possible to generate a copy of the request data using the data relay device 60. Then, similar to the first to third embodiments, a dummy client is generated from the client ID and password data in the request data, and the transaction is restored by logging in and performing a transaction such as a transfer of funds. Then, the disaster countermeasure DB server can be updated. According to the present embodiment, it is possible to provide a service for transferring and analyzing customer data with a contract company using a data relay device such as an Internet service provider.

<Fifth embodiment>
In the above embodiment, the case where the production system is constituted by a single system has been described. However, the production system may be constituted by a plurality of systems or a plurality of services, and each system may cooperate. This case is also substantially the same as the above embodiment, and is partially different. Therefore, the description of the overlapping portions is omitted here.

  In the case of a single system, the disaster recovery Web / AP server transfers the stored statement statement and list data to the disaster recovery DB server, generates and executes an SQL statement from the statement statement and list data, Although the data stored in the disaster recovery DB server will be updated, not all of the stored statement statements and list data are transferred. Because, in the above embodiment, since data is transferred asynchronously from the production DB server to the disaster recovery DB server, only the statement statement and the list data corresponding to the data not transferred to the disaster recovery DB server are transferred. This is because the data stored in the disaster recovery DB server may be updated.

  As shown in FIG. 9, even when the production system is composed of a plurality of systems or a plurality of services, and each system is linked, all of the statement statements and list data stored in the disaster countermeasure Web / AP server Is not transferred to the disaster recovery DB server and the data stored in the disaster recovery DB server is not updated. However, if the production system is composed of a plurality of systems or a plurality of services, and each system is linked, after reconciling statement statements and list data not transferred to the disaster recovery DB server in each system, Match between systems.

  Specifically, a front system other than the back system 70 matches the back system 70. In this example, the front system is a system that has a contact point with a customer, for example, an Internet banking system. The back system is a system that records executed transactions and reflects the contents of the transactions in a ledger or the like, and is, for example, an account management system. For example, if the client completes the transfer from the client terminal using Internet banking, the transfer from the client is recognized as having been completed. However, a disaster may occur in the account management system without completing the transfer of the client. In this case, it is necessary to collate between the front system and the back system and reflect the completion of the transfer in the table of the disaster recovery DB server.

  Also in the present embodiment, similarly to the first to third embodiments, there is an effect that a data processing device (disaster countermeasure Web / AP server) that is not particularly used can be effectively used in normal times. . Also in the present embodiment, as in the first to third embodiments, the time required to switch the data processing device (disaster countermeasure Web / AP server) to operate as the production Web / AP server is reduced. This has the effect. Further, in the present embodiment, similarly to the first to third embodiments, even in a case where data of the production DB server is asynchronously copied to the disaster recovery DB server in normal times, the client terminal and the Without using an SQL statement or log information, it is possible to prevent data loss due to delay due to data transfer processing.

  Also in the present embodiment, as in the first to third embodiments, only an update such as a fund transfer is restored as data from one of the request data copy and the response data copy. Can be.

  Further, in the present embodiment, similarly to the first to fourth embodiments, a dummy client is generated from the data of the client ID and the password in the request data, logged in, and a transaction such as a transfer of funds is performed. Thus, the transaction can be restored and the disaster recovery database can be updated.

<Sixth embodiment>
FIG. 10 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. This embodiment is substantially the same as the first embodiment. Therefore, the description of the overlapping part will be omitted, and different points will be described. The data processing device 52D according to the present embodiment includes a session identification information receiving unit 528 in addition to the configuration of the data processing device (disaster countermeasure Web / AP server) 52 of the first embodiment.

  The session identification information receiving unit 528 receives the session identification information from the production Web / AP server 32. Here, the session identification information refers to information for identifying a session. In this example, when the client terminal 20 opens a login screen when the client terminal 20 uses a certain service (for example, a service for performing a transfer via the Internet), the production Web / AP server returns the login screen. Then, when the client terminal 20 logs in, the production Web / AP server 32 issues session identification information, and includes the session identification information in the response when returning the next screen. Subsequently, when the client terminal 20 transmits request data (for example, data of fund transfer) to the production Web / AP server 32, the passed session identification information is included. The session identification information receiving unit 528 receives a copy of the session identification information when the production Web / AP server 32 returns a response to the client terminal 20. However, the present invention is not limited to this. May be received to the production Web / AP server 32, a copy of the session identification information may be received.

  In the prior art, the request data (first message) from the client terminal is processed by the production Web / AP server. However, if a failure occurs in the production system before the database is updated by the production DB server, However, there is a problem that the database is not updated and a problem that the client terminal cannot receive the response data (second message).

  On the other hand, according to the present embodiment, when the client terminal 20 transmits request data to the production Web / AP server 32 to request updating of the database of the production DB server 34, the first receiving unit of the data processing device 52D 521 receives a copy of the request data, and the copy storage unit 561 stores the copy of the request data. Also, the session information receiving unit 528 receives a copy of the session identification information, and the copy storage unit 561 stores a copy of the session identification information. If the request data (first message) from the client terminal is processed by the production Web / AP server, but the production system fails before the database is updated by the production DB server, the detection unit 526 is activated. Upon detecting this failure, the switching unit 527 switches the data processing device 52D to operate as a production Web / AP server. Then, when the detection unit 526 detects a failure, the message generation unit 525 generates a statement sentence and list data. Then, an SQL statement is generated and executed from the statement statement and the list data, and the database of the disaster recovery DB server 54 is updated. Thereafter, a response data (second message) and a copy of the session identification information are returned to the client terminal 20. Without the copy of the session identification information, the client terminal 20 cannot receive the response data. As described above, in the present embodiment, the request data from the client terminal is processed by the production Web / AP server, but before the production DB server updates the database, the production system fails. Even if there is, there is an effect that the database of the disaster recovery DB server is updated, and the client terminal can receive the response data.

  Further, in the related art, although the request data is processed by the production Web / AP server 32 and the database is updated by the production DB server 34, the failure occurs in the production system 30 before the client terminal 20 receives the response data. If this occurs, there is a problem that the client terminal 20 cannot receive the response data. This problem occurs when the database is updated in the production DB server 34 and the database in the disaster recovery DB server 54 is not updated, or when the database is updated in the production DB server 34 and the disaster occurs. The database of the countermeasure DB server 54 may be updated.

  On the other hand, in the present embodiment, the database is updated in the production DB server 34 and the database of the disaster recovery DB server 54 is not updated, and the database is updated in the production DB server 34 and the disaster recovery DB server In any case where the database 54 is updated, the above-described problem does not occur.

  First, when the database is updated in the production DB server 34 and the database of the disaster recovery DB server 54 is not updated, before the client terminal 20 receives the response data from the production Web / AP server 32, the production system When a failure occurs in the copy 30, the copy of the request data and the copy of the response data stored in the copy storage unit 561 are compared. That is, when the user name, user ID, IP address, and the like of the copy of the request data and the copy of the response data match, it is determined that the copy of the request data does not have a corresponding copy of the response data. It can be seen that the response data corresponding to the request data has not been returned to the client terminal 20. Therefore, the message generation unit 525C generates a statement sentence and list data from the copy of the request data, and these are transferred to the disaster recovery DB server 54. Then, the disaster countermeasure DB server 54 generates an SQL statement from the statement statement and the list data, updates the database, and transmits response data to the client terminal 20.

  Next, when the database is updated in the production DB server 34 and the database of the disaster recovery DB server 54 is updated, before the client terminal 20 receives the response data from the production Web / AP server 32, the production If a copy of the request data stored in the copy storage unit 561 matches a copy of the response data when a failure occurs in the system 30, a copy of the request data for which no corresponding copy of the response data exists is found. However, even for request data for which no corresponding copy of response data exists, the database itself of the disaster recovery DB server 54 has been updated. Therefore, if statement text and list data are generated from request data for which a copy of the corresponding response data does not exist, and these are transferred to the disaster recovery DB server 54, they are updated twice. There is. Therefore, of the data that has already been updated, data for which no response data has been returned is extracted from the database, and the second message generating unit 529 generates response data. Specifically, the request data for which there is no copy of the corresponding response data includes information such as a user name, a user ID, an IP address, and a time. Data that matches the user name, user ID, IP address, etc. of the request data for which no copy exists is extracted. Since the extracted data includes data such as destination information, destination information, amount information, and time, the second message generator 529 generates response data from these data.

  Also in the present embodiment, similarly to the first to third embodiments, there is an effect that a data processing device (disaster countermeasure Web / AP server) that is not particularly used can be effectively used in normal times. . Also in the present embodiment, similarly to the first to third embodiments, there is an effect that the time required to switch the data processing device to operate as a production Web / AP server is reduced. Further, in the present embodiment, similarly to the first to third embodiments, even in a case where data of the production DB server is asynchronously copied to the disaster recovery DB server in normal times, the client terminal and the Without using an SQL statement or log information, it is possible to prevent data loss due to delay due to data transfer processing.

  Also in this embodiment, as in the first to third embodiments, only an update such as a fund transfer can be restored as data from a copy of the request data.

  Further, in the present embodiment, similarly to the first to fourth embodiments, a dummy client is generated from the data of the client ID and the password in the request data, logged in, and transactions such as transfer of funds are performed. Thus, the transaction can be restored and the disaster recovery database can be updated.

<Seventh embodiment>
A case where the production Web / AP server functions as a data processing device will be described with reference to FIGS. FIG. 11 is a block diagram illustrating an example of a configuration of a D / R system according to another embodiment of the present invention. FIG. 12 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. In the sixth embodiment, the case where a failure has occurred in the entire production system has been described. However, in the seventh embodiment, only the production DB server 34c has a failure and the production Web / AP server 32c has no failure. explain.

  In the present embodiment, as shown in FIG. 11, the production Web / AP server 32c is a data processing device. The production Web / AP server 32c and the disaster recovery DB server 54 are connected by a network 43.

  The data processing device (production Web / AP server) 32c includes a first reception unit 321, a second reception unit 322, a first message storage unit 324, a message generation unit 325, a detection unit 326, a transmission unit 328, and a second message generation unit. 329.

  The first receiving unit 321 receives request data (first message) transmitted by the client to request an update of the production DB server 34c (first database). The first message storage unit 324 stores the request data.

  The detection unit 326 detects that a failure has occurred in the production DB server 34c. Specifically, when the detection unit 326 always transmits a signal to the production DB server 34c, and the production DB server 34c transmits a response signal to the detection unit 326, When the response signal disappears, the detection unit 326 determines that a disaster has occurred.

  The message generation unit 325 generates a statement sentence for generating an SQL sentence and list data from the request data stored in the first message storage unit 324. Specifically, the message generation unit 325 generates a statement sentence and a list data only for the data of which the response data has not yet been returned to the client among the request data stored in the first message storage unit 324.

  The transmission unit 328 transmits the statement sentence and the list data generated by the message generation unit 325 to the disaster recovery DB server 54 (second database) via the network 43. The disaster countermeasure DB server 54 that has received the statement statement and the list data generates and executes an SQL statement based on the statement statement and the list data, and transmits the result to the data processing device 32c.

  The second receiving unit 322 receives information indicating that the change of the disaster recovery DB server 54 has been successful.

  The second message generator 329 generates response data (second message) to be returned to the client. The second message generation unit 329 generates response data after the detection unit 326 detects that a failure has occurred in the production DB server 34c. The second message generator 329 generates response data based on information indicating that the change of the disaster recovery DB server 54 has been successful.

  According to the conventional technology, if a failure occurs in the production DB server 34c after the client transmits the request data, no response data is returned. However, in the present embodiment, even if a failure occurs in the production DB server 34c after the client has transmitted the request data, a statement statement and list data are generated from the request data stored in the first message storage unit 324, and Is transmitted to the disaster recovery DB server 54, and after the SQL statement is generated and executed by the disaster recovery DB server 54, information indicating that the change of the disaster recovery DB server 54 is successful is returned. Based on the information, the response data is returned. Is generated and returned to the client. Therefore, there is an effect that a useful service can be provided to the client.

<Eighth embodiment>
FIG. 13 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. The data processing device 62 includes a receiving unit 621, a collating unit 623, a basic information storage unit 624, and a transmitting unit 625.

  The basic information storage unit 624 stores request data (first message) transmitted from a client to a production Web / Ap server (not shown), and returns an update processing result in the database of the production DB server to the client. The response data (second message) is stored.

  Further, the basic information storage unit 624 stores information serving as a basis for generating an SQL statement generated from request data or response data. Specifically, the basic information storage unit 624 stores a statement sentence and list data. In this example, the basic information storage unit 624 stores only information related to updating the database of the disaster recovery DB server 54. The information on the update of the database is, for example, data on a fund transfer. Therefore, the basic information storage unit 624 stores the statement statement and the list data of the data related to the fund transfer.

  The receiving unit 621 receives the active system switching notification. For example, when a failure occurs in a production Web / AP server or a production DB server of a production system (not shown) due to a disaster or the like, the receiving unit 621 receives a notification for switching from the production system.

  The matching unit 623 checks whether the request data and the response data are associated with each other. Specifically, when request data and response data stored in the basic information storage unit 624 are compared, request data for which no corresponding response data exists is found. The case where the request data and the response data do not match means that there is request data for which there is no corresponding response data.

  Based on the switching notification received by the receiving unit 621, when the request data and the response data are not collated, the transmission unit 625 stores information serving as a basis for generating an SQL statement stored in the basic information storage unit 624. For example, the statement statement and the list data of the data relating to the fund transfer are transmitted to the database of the disaster recovery DB server 54. That is, the statement sentence and the list data generated from the request data for which there is no corresponding response data are transmitted to the database of the disaster recovery DB server 54.

  In the related art, the data processing device (disaster countermeasure Web / Ap server) is not particularly used in normal times. On the other hand, according to the present embodiment, the basic information storage unit 624 of the data processing device stores the statement statement and the list data of the data relating to the fund transfer, and from this fund transfer table, the data is still transferred from the production DB server to the disaster recovery DB server. The statement statement and the list data corresponding to the data that has not been transferred are created and stored, and then the statement statement and the list data are effectively used, such as being used to update the disaster recovery DB. . Further, according to the present embodiment, only the statement statement and the list data of the data related to the fund transfer stored in the basic information storage unit 624 of the data processing device are triggered by the reception of the switching notification as a trigger. This has the effect of being transmitted and the SQL statement being generated and executed.

<Ninth embodiment>
FIG. 14 is a block diagram illustrating an example of a configuration of a data processing device according to another embodiment of the present invention. This embodiment is substantially the same as the eighth embodiment, but is partially different. Therefore, the description of the overlapping part will be omitted, and different points will be described. The data processing device 62a according to the present embodiment includes an extraction unit 626 in addition to the configuration of the data processing device 62 according to the eighth embodiment.

  The basic information storage unit 624 stores request data (first message) transmitted from a client to a production Web / Ap server (not shown), and returns an update processing result in the database of the production DB server to the client. The response data (second message) is stored. Then, it generates and stores information serving as a basis for generating an SQL statement from the request data or the response data. Specifically, the storage unit 624 stores a statement sentence and list data.

  The extracting unit 626 extracts information related to the update of the database, that is, the statement sentence and the list data of the data related to the fund transfer, from the statement sentence and the list data stored in the basic information storage unit 624.

  Then, based on the switching notification received by the receiving unit 621, if the request data and the response data are not collated, the transmitting unit 625 determines the basics of the generation of the SQL statement stored in the basic information storage unit 624. For example, a statement sentence and list data of data relating to fund transfer are transmitted to the database of the disaster recovery DB server 54.

  In the present embodiment, similarly to the eighth embodiment, the basic information storage unit 624 of the data processing device stores the statement sentence and the list data, and thereafter, the statement sentence and the list data are used to update the disaster recovery DB. It has the effect of being used effectively, such as being used. Further, according to the present embodiment, only the statement statement and the list data of the data related to the fund transfer stored in the basic information storage unit 624 of the data processing device are triggered by the reception of the switching notification as a trigger. This has the effect of being transmitted and the SQL statement being generated and executed.

  The above description has been given on the assumption that a financial institution, such as a transfer of funds or a balance inquiry, is a specific example. However, the present invention is not limited to a system in a financial institution, and may be a system in another company or institution. In this case, the transactions that require updating of the production database differ depending on each company or institution.

  Further, the present invention is not limited to the above-described embodiment, and can be appropriately changed without departing from the gist.

20: Client terminal 27: Network 30: Production system 30a: Primary system of production system 30b: Subsystem of production system 32: Production Web / AP server
34: Production database server 36: Detector
42: Network between servers 43: Network 44: Network between database servers 50: Disaster countermeasure system 50a: Primary system of disaster countermeasure system 50b: Secondary system of disaster countermeasure system
52: Disaster Countermeasures Web / AP Server
54: Disaster recovery database server 60: Relay device 70: Back system 72: Web / AP server of the back system
74: Database server for back system 80: Front system 82: Web / AP server for front system
84: Front system database server 110: Request table 111: Time 112: IP address 113: POST data 113: Content of request
114: User name 115: User ID
121, 122, 123, 124: request header table 130: response header table 131: time 132: IP address 133: Status 134: user name 135: user ID
141, 142, 143, 144: response header table 321: first receiving unit 322: second receiving unit 324: first message storage unit
325: Message generation unit 326: Detection unit
Transmission unit: 328 329: second message generation unit 521: first reception unit 522: second reception unit 523: collation unit 525: message generation unit 526: detection unit 527: switching unit 531: first association unit
533: first determination unit 535: second association unit 537: second determination unit 541: temporary table 543: transaction execution table 545: recovery table 551: copy storage unit 553: message storage unit 561: copy storage unit
601: relay unit 603: generation unit 621: reception unit 623: collation unit 624: basic information storage unit 625: transmission unit 626: extraction unit 720: client terminal 727: network 730: production system 732: production Web / AP server
734: Production database server 742: Inter-server network 744: Inter-database network 750: Disaster countermeasure system 752: Disaster countermeasure Web / AP server
754: Disaster recovery database server 820: Client terminal 827: Network 823: Client transaction log 832: Server 834: Server transaction log 836: Backup data 838: DBMS

Claims (26)

A first receiving unit that receives a copy of a first message that the client sends to the server to request a database update;
A message generator for generating a message for generating a database manipulation statements for the server from a copy of the first message updates the previous SL database,
When the server has successfully changed the database, a message storage unit that stores the message,
A data processing device having: A first receiving unit that receives a copy of a first message that the client sends to the server to request a database update;
A second receiving unit that receives a copy of a second message that returns a result of performing the operation of changing the database to the client;
Claims, characterized in that the copy or copies of the second message of the first message, having a message generating unit for generating a message for generating a database manipulation statements for the server to update the database Item 2. The data processing device according to item 1. A first receiving unit that receives a copy of a first message that the client sends to the server to request a database update;
A message generation unit that generates a message for generating a database operation statement for the server to update the database from a copy of the first message ;
When the server has successfully changed the database, the data processing device having a copy storage unit for storing a copy of the first message according to the success. The result of executing the operation changes from the previous SL database has a second receiving unit to receive a copy of the second message to reply to the client,
The copy storage unit stores a copy of the first message or a copy of the second message related to the success when the copy of the second message indicates the success of the operation of changing the database. Item 4. The data processing device according to item 3. The message generation unit, from said first message copy or second message copy of which is stored in the copy storage unit, that generates the message, the data processing device according to 請 Motomeko 3 or 4. A first receiving unit that receives a copy of a first message that the client sends to the server to request a database update;
A copy storage unit that stores a copy of the first message;
A message generator for generating a message for generating a database manipulation statements for the server from a copy of the first message updates the previous SL database,
When the server has successfully changed the database, and history management section for adding the control information indicative of the successful operation of the database changes to the copy of the first message according to the success,
A data processing device having: A second receiving unit that receives a copy of a second message that returns a result of the server performing an operation of changing the database to the client,
The copy storage unit stores a copy of the second message,
When the copy of the second message indicates the success of the operation of changing the database, the history management unit controls the copy of the first message and the copy of the second message to indicate the success of the operation of changing the database The data processing apparatus according to claim 6, wherein information is added. The message generation unit generates a message for generating a database operation statement generated by the server from a copy of the first message or a copy of the second message to which the control information indicating the success is added ,
The data processing device according to claim 6, further comprising a message storage unit that stores the message.   The data processing device according to claim 2, further comprising a detection unit configured to detect that a failure has occurred in the server.   10. The data processing device according to claim 5, further comprising a switching unit that operates as the server when a failure occurs in the server.   The data processing device according to claim 10, wherein when a failure occurs in the server, the switching unit updates route information from the client to the server. A first associating unit that associates a copy of the first message received by the first receiving unit with a transaction of the database according to the first message;
A first determination unit configured to determine whether a copy of the second message received by the second reception unit is to return a result of performing a change operation in which transaction of the database,
Said copy storage unit stores a copy or copies of the second message of the first message associated with the transaction of the said discriminated by the first discriminating unit second message copy, data according to claim 4 or 7 Processing equipment. A second associating unit for associating the copy of the first message received by the first receiving unit with the identifier of the client of the transmission source;
A second determining unit that determines an identifier of a client of a transmission destination of the second message received by the second receiving unit;
Has,
Said copy storage unit stores a copy or copies of the second message of the first message associated with the transaction of the said discriminated by the second discriminating section second message copy, data according to claim 4 or 7 Processing equipment. The second associating unit further associates a time at which a copy of the first message was received,
The copy storage unit copies the first message based on the time associated with the second association unit and the time at which the copy of the second message was received, in addition to the determination by the second determination unit. 14. The data processing device according to claim 13, wherein a copy of the second telegram is stored. A first receiving unit that receives a copy of a first message that the client sends to the server to request a database update;
A session identification information receiving unit that receives a copy of the session identification information transmitted from the server to the client;
A copy storage unit that stores a copy of the first message and a copy of the session identification information;
A second message generation unit that generates a second message to be returned to the client from the copy of the first message and the copy of the session identification information stored in the copy storage unit;
A detection unit that detects that a failure has occurred in the server ;
A message generation unit that generates a message for generating a database operation statement generated by the server from a copy of the first message stored in the copy storage unit ;
The data processing device according to claim 2, wherein the second message generation unit generates the second message after the detection unit detects that a failure has occurred in the server. The data processing device according to claim 15, wherein the second message and the session identification information are returned to a client. Before SL message generator, said when the detection unit detects that the failure to the server is generated, the data processing apparatus according to claim 15 you and generating the message.   18. The data processing device according to claim 15, further comprising a switching unit that operates as the server when a failure occurs in the server. A first receiving unit that receives a first message transmitted by the client to request an update of the first database;
A first message storage unit for storing the first message;
A second message generator for generating a second message to be returned to the client;
A detection unit that detects that a failure has occurred in the first database ;
A message generation unit that generates a message for generating a database operation statement from the first message stored in the first message storage unit ;
The data processing device according to claim 2, wherein the second message generation unit generates the second message after the detection unit detects that a failure has occurred in the first database. Further comprising a transmitter for transmitting message for generating a pre-SL database manipulation statements in the second database,
20. The data processing device according to claim 19, wherein the message generation unit generates the message when the detection unit detects that a failure has occurred in the first database . A second receiving unit that receives information indicating that the change of the second database that has received the message is successful;
21. The data processing apparatus according to claim 20, wherein the second message generating unit generates the second message based on information indicating that the change of the second database has been successful. A basic information storage unit that stores a first message that is received from a client and a second message that returns a database update processing result to the client, corresponding to information serving as a basis for generating a database operation statement;
A receiving unit that receives an active system switching notification;
Based on the switching notification received by the receiving unit, a transmission unit for transmitting the underlying information of generation of the database manipulation statements stored in the basic information memory unit to the database,
A matching unit that checks whether or not the first message and the second message are associated with each other;
A data processing device comprising:   23. The data processing device according to claim 22, wherein the basic information storage unit stores only information related to updating of a database.   23. The data processing device according to claim 22, further comprising an extraction unit that extracts only information related to updating of a database from the basic information storage unit and transmits the information to the transmission unit. And the transmission unit, in the matching unit and the first message and the second message is if was not matching, and transmits the information as a basis for generation of the database operation statement against the database, according to claim 22 A data processing device according to claim 1. A relay unit that relays, to the server, a first message transmitted to the server by the client to request a database update;
The server generates a message for generating a database operation statement for updating the database from the first message, and when the change of the database is successful, copies the first message relayed by the relay unit. A data relay device having a generation unit that generates the data.

Images