JP2013178685A - Data processing system with asynchronous backup function, front system, backup method and program therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an asynchronous backup method with which cost-reduced and short-time backup can be performed in a distributed database.SOLUTION: A data processing system comprises a front system which carries out ordinary jobs and a backup system which performs data backup. In the case where a record is overlapped in an update log of a database in the front system, whether the record can be overwrite-updated or not is imparted to the update log and if it can be overwrite-updated, before transmission to the backup system, the overlapped record of the update log is overwrite-updated with the latest record, thereby reducing a transmission data amount. The similar processing is also performed after backup system reception, and the time for reflecting the database in the backup system with the update log is also shortened.

Description

  The present invention relates to a data processing system having an asynchronous backup function, a front system used in the system, a backup method, and a program therefor.

  A technique for performing asynchronous backup in a distributed database is known. This technology is a system that permits an update of the database of the front system without waiting for the update of the database of the backup system when the database of the front system is updated. While the non-updatable time of the front system database is minimized, if the data size of the update log sent to the backup system is large, the time required to update the backup system becomes long, and inconsistencies between databases tend to occur. There's a problem.

  An example of the asynchronous backup technique is described in Patent Document 1. In the asynchronous backup technology described in Patent Document 1, the front system performs a transaction log (T log) that is an update log, an image log before update (B log), and an image log after update (A log) at the time of backup. To the secondary system, which is the backup system, to keep the data synchronized. As a result, the backup can be performed at a low cost for a short time compared to the case of backing up the entire file.

JP 2001-356945 A

  However, the technique described in the above-mentioned patent document 1 has three points of a transaction log (T log), an image log before update (B log), and an image log after update (A log) every time the front system is updated. Must be sent to backup system. Therefore, while the front system is being updated, data is always transmitted from the front system to the backup system. Therefore, the technology described in the technical document 1 has an enormous amount of backup data communication between the front system and the backup system, and cannot be backed up in a short time. Further, there is a problem that the communication amount increases due to the enormous amount of communication and cannot be said to be low.

  An object of the present invention is to provide a data processing system having an asynchronous backup function, a backup method, and a program therefor that can solve the above-described problems.

The first asynchronous backup system according to one aspect of the present invention is:
A front system that performs normal operations;
A backup system for performing data backup of the front system;
A front system database updated at any time in the front system;
A backup system database for backing up the front system database in the backup system;
When sending an update log of the front system database to the backup system, an update log reduction target management unit that stores and manages an update log reduction target management table that records whether or not it is a target to be overwritten and updated with a later record with respect to duplicate records;
An update log table storage unit that stores an update log of the front system database as an update log table until an application that has updated the front system database commits an update;
Organize the update log of the front system database into record keys and record contents, and refer to the management table of the update log reduction target management unit, add to the update log whether or not it is an overwrite update target record, and overwrite update target If it is a record, the duplicate record is overwritten with a later record and output to the update log table storage unit, and the update log is sent to the update log transmission control unit when the application that updated the front system database commits the update. A database update controller to send;
A front system update log storage table storage unit for storing an update log transmitted from the database update control unit as an update log storage table;
If there is an update of the update log sent from the database update control unit, it is put together in the unit to be sent to the backup system, and if it is an overwrite update target record, the duplicate record is overwritten with the later record, and in advance by the system administrator An update log transmission control unit that transmits an update log to the backup system at a set transmission timing;
A backup system update log storage table storage unit for storing the update log transmitted from the front system as an update log storage table;
When there is an update of the update log transmitted from the update log transmission control unit, if it is an overwrite update target record, the duplicate record is overwritten with a later record, and the backup system database is set at a timing set by the system administrator And an update log reception control unit that updates the contents of the update log in the update log storage table.

Asynchronous backup method in the first distributed arrangement database in one aspect of the present invention,
The database update control unit organizes the update log of the front system database into record keys and record contents,
The database update control unit refers to the management table of the update log reduction target management unit, adds to the update log whether or not it is a record for overwrite update, and adds it to the update log table.
If it is an overwrite update target record, the database update control unit overwrites the duplicate record with a later record, updates the update log table,
When the application that has updated the front system database commits the update, the database update control unit transmits the update log of the update log table to the update log transmission control unit,
The update logs received by the update log transmission control unit are grouped into units for transmission to the backup system, added to the update log storage table of the front system update log storage table storage unit,
If it is an overwrite update target record, the update log transmission control unit overwrites the duplicate record with a later record and updates the update log storage table,
Send the update log with the contents of the update log storage table to the backup system at the timing set by the system administrator,
The update log reception control unit receives the update log,
If it is an overwrite update target record, the update log reception control unit overwrites the duplicate record with a later record, updates the update log storage table,
The backup system database is updated with the contents of the update log in the update log storage table at a timing set by a system administrator.

An asynchronous backup program in the first distributed arrangement database according to one aspect of the present invention is stored in a computer.
The database update control unit organizes the update log of the front system database into record keys and record contents,
The database update control unit refers to the management table of the update log reduction target management unit, adds to the update log whether or not it is a record for overwrite update, and adds it to the update log table.
If it is an overwrite update target record, the database update control unit overwrites the duplicate record with a later record, updates the update log table,
When the application that has updated the front system database commits the update, the database update control unit transmits the update log of the update log table to the update log transmission control unit,
The update logs received by the update log transmission control unit are grouped into units for transmission to the backup system, added to the update log storage table of the front system update log storage table storage unit,
If it is an overwrite update target record, the update log transmission control unit overwrites the duplicate record with a later record and updates the update log storage table,
Send the update log with the contents of the update log storage table to the backup system at the timing set by the system administrator,
The update log reception control unit receives the update log,
If it is an overwrite update target record, the update log reception control unit overwrites the duplicate record with a later record, updates the update log storage table,
A process of updating the backup system database with the contents of the update log in the update log storage table at a timing set by a system administrator is executed.

  According to the present invention, the amount of data transferred from the front system to the backup system is reduced and the cost is reduced. In addition, since the transfer data becomes small, the time required for backup is shortened, and the time when data cannot be synchronized between the front system and the backup system can be shortened.

FIG. 1 is a block diagram showing the configuration of the data processing system according to the first embodiment of this invention. FIG. 2 is a diagram illustrating a hardware configuration in which the data processing system according to the first embodiment is realized by a computer device and its peripheral devices. FIG. 3 is a diagram illustrating an example of the update log reduction target management table 1030 stored in the update log reduction target management unit 103 according to the first embodiment. FIG. 4 is a diagram illustrating an example of the update log tables 1040 and 1041 stored in the update log table storage unit 104 according to the first embodiment. FIG. 5 is a diagram illustrating an example of the update log storage tables 1050 and 1051 stored in the front system update log storage table storage unit 105 according to the first embodiment. FIG. 6 is a flowchart showing an operation of generating an update log in the database update control unit 101 in the first embodiment. FIG. 7 is a flowchart showing an operation of transmitting the update log to the backup system 2 in the update log transmission control unit 102 according to the first embodiment. FIG. 8 is a flowchart illustrating an operation of reflecting the update log in the backup system database 200 in the update log reception control unit 201 according to the first embodiment. FIG. 9 is a diagram illustrating a hardware configuration in which the data processing system according to the second embodiment is realized by a computer device and its peripheral devices.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing a configuration of a data processing system according to the first embodiment of the present invention. Referring to FIG. 1, a data processing system 1000 includes a front system 1 that executes data processing and a backup system 2 for backing up the data. The front system 1 is connected to the backup system 2 via the network 3. The front system 1 includes a front system database 100, a database update control unit 101, an update log transmission control unit 102, an update log reduction target management unit 103, an update log table storage unit 104, and a front system update log storage table storage. Part 105 is provided. The backup system 2 also includes a backup system database 200, an update log reception control unit 201, and a backup system update log storage table storage unit 202.

  The front system 1 and the backup system 2 are each a computer device or a server in a distributed database, but may be a computer device in another data processing system. The distributed arrangement database is a system in which an update destination database is determined for each key of a record to be updated. Each part of the front system 1 may exist for each processing sequence, and reflection of the backup update log may be processed in parallel.

  Next, the configuration of the front system 1 will be described.

  The front system database 100 is a collection of data called from various applications, and is shared by a plurality of users. The data processing system 1000 of the present embodiment performs backup of the front system database. The backup destination is the backup system database 200.

  When the data in the front system database 100 is updated by executing the application, the database update control unit 101 generates a record key and a record content of an update log of the front system database 100 according to the data update. Further, the database update control unit 101 refers to a management table (to be described later) of the update log reduction target management unit 103 and determines whether or not the update log record is a record to be overwritten. Furthermore, the database update control unit 101 adds information of the determination result to the update log, and additionally registers it in an update log table 1040 (described later) of the update log table storage unit 104. In this case, if the record is an overwrite update target record, the database update control unit 101 overwrites the duplicate record in the update log with a later record, thereby updating the update log table 1040 after the update. Update to (described later). Furthermore, the database update control unit 101 transmits the update log in the updated update log table 1041 to the update log transmission control unit 102 when the application that has updated the data in the front system database 100 commits the update.

  The update log transmission control unit 102 receives the update log from the database update control unit 101, integrates the update log into a unit (transaction unit that can be reflected at the backup destination) to be transmitted to the backup system 2, and stores the front system update log storage table. Stored in the update log storage table 1050 of the unit 105. In this case, if the received update log is an overwrite update target record, the update log transmission control unit 102 stores the update log storage table 1050 by overwriting a duplicate record in the update log with a later record. Update to table 1051 and register. Further, the update log transmission control unit 102 reads the update log from the update log storage table 105 and transmits the update log to the update log reception control unit 201 of the backup system 2 at a timing set by the system administrator.

  When sending the update log of the front system database 100 to the backup system 2, the update log reduction target management unit 103 records an update log reduction management table 1030 that records information about whether or not duplicate records are overwritten and updated with later records. Save and manage.

  The update log table storage unit 104 stores the update logs of the front system database 100 as update log tables 1040 and 1041 until an application that has updated the front system database 100 commits the update.

  The front system update log storage table storage unit 105 stores the update logs received from the database update control unit 101 as update log storage tables 1050 and 1051.

  Next, the configuration of the backup system 2 will be described.

  The update log reception control unit 201 receives the update log from the update log transmission control unit 102. In addition, the update log reception control unit 201 adds the received update log to the update log storage table 1050 of the backup system update log storage table storage unit 202. In this case, when the update log is updated, the update log reception control unit 201 overwrites the duplicate record with the later record if it is an overwrite update target record and updates the update log storage table 1051. The backup system database 200 is updated with the contents of the update log at the set timing.

  The backup system update log storage table storage unit 202 stores the update logs received from the front system 1 as update log storage tables 1050 and 1051.

  Next, data stored in the update log reduction target management unit 103, the update log table storage unit 104, the front system update log storage table storage unit 105, and the backup system update log storage table storage unit 202 will be described.

  FIG. 3 is a diagram showing an example of the update log reduction target management table 1030 stored in the update log reduction target management unit 103 according to the present embodiment.

  The update log reduction target management table 1030 shown in FIG. 3 is composed of a table name and update log reduction target column data, and is storage data indicating which table of the update log is a reduction target (overwrite target). The update log of the table indicated as “target” is processed by the database update control unit 101, the update log transmission control unit 102, and the update log reception control unit 201 as follows. That is, duplicate records in the update log are overwritten by later records. As a result, duplicate records before overwriting are reduced. In the following description, this deletion is also referred to as overwrite deletion.

  FIG. 4 is a diagram illustrating an example of the update log tables 1040 and 1041 stored in the update log table storage unit 104 according to the present embodiment.

  The update log tables 1040 and 1041 shown in FIG. 4 include columns of record keys, table names, overwrite update targets, and record contents. The update log table 1040 stores a plurality of records generated by the database update control unit 101 in which the update log is organized by record key and record content. Each record is also added with information (overwrite update target) as to whether or not each record is a record to be overwritten by the database update control unit 101. In contrast to the update log table 1040, the database update control unit 101 outputs the update log table 1041 by overwriting and reducing the duplicate records in the later records if they are overwrite update target records.

  FIG. 5 is a diagram showing an example of the update log storage tables 1050 and 1051 stored in the front system update log storage table storage unit 105 according to the present embodiment.

  The update log storage tables 1050 and 1051 shown in FIG. 5 include data of serial numbers, update serial numbers, record keys, overwrite update targets, and record content columns. The update log storage table 1050 is data in which an update sequence number is newly added each time the database update control unit 101 receives a new update log. For the update log storage table 1050, the update log transmission control unit 102 integrates the update log into a unit to be transmitted to the backup system 2 when the update log is updated. Reduce overwriting with records. The update log storage table 1051 shows the update log storage table after overwriting deletion.

  FIG. 2 is a diagram showing a hardware configuration in which the front system 1 and the backup system 2 in the first embodiment of the present invention are realized by a computer and its peripheral devices. As shown in FIG. 2, the front system 1 and the backup system 2 include CPUs 11 and 21, output devices 12 and 22, input devices 13 and 23, main storage devices 14 and 24, and secondary storage devices 15 and 25, respectively. . Further, the front system 1 and the backup system 2 are connected to the network 3 via network interfaces 10 and 20, respectively.

  The CPUs 11 and 21 operate the operating system to control the entire front system 1 and backup system 2 according to the first embodiment of the present invention. Further, the CPUs 11 and 21 read programs and data from the secondary storage devices 15 and 25 to the main storage devices 14 and 24, for example, and the database update control unit 101, the update log transmission control unit 102 in the first embodiment, and The update log reception control unit 201 executes various processes.

  The secondary storage devices 15 and 25 are, for example, an optical disk, a flexible disk, a magnetic optical disk, an external hard disk, or a semiconductor memory, and record a computer program so that the computer program can be read. The computer program may be downloaded from an external computer (not shown) connected to the communication network.

  The input devices 13 and 23 are realized by, for example, a mouse, a keyboard, a built-in key button, and the like, and are used for input operations. The input devices 13 and 23 are not limited to a mouse, a keyboard, and built-in key buttons, but may be a touch panel, for example.

  The output devices 12 and 22 are realized by a display, for example, and are used to check the output.

  Note that the block diagram (FIG. 1) used in the description of the first embodiment shows functional unit blocks, not hardware unit configurations. These functional blocks are realized by the hardware configuration shown in FIG. However, the means for realizing each unit included in the front system 1 and the backup system 2 is not particularly limited. That is, the front system 1 and the backup system 2 may be realized by one physically coupled device, or two or more physically separated devices are connected by wire or wirelessly, and these plural devices are used. It may be realized.

  The CPUs 11 and 21 read computer programs recorded in the secondary storage devices 15 and 25, and as the database update control unit 101, update log transmission control unit 102, and update log reception control unit 201 according to the programs. It may work.

  A recording medium (or storage medium) in which the program code is recorded is supplied to the front system 1 and the backup system 2, and the front system 1 and the backup system 2 read and execute the program code stored in the recording medium. May be. That is, the present invention temporarily stores the software (asynchronous backup program in the distributed arrangement database) to be executed by the front system 1 and the backup system 2 in the first embodiment, or the secondary that stores the software temporarily. Storage devices 15 and 25 are also included.

  Operations of the front system 1 and the backup system 2 configured as described above will be described with reference to the flowcharts of FIGS. 6, 7, and 8.

  FIG. 6 is a flowchart showing an outline of an operation of generating an update log in the database update control unit 101 in the first embodiment. Note that the processing according to this flowchart may be executed based on the above-described program control by the CPU.

  As shown in FIG. 6, first, the database update control unit 101 monitors the front system database 100 to confirm whether it has been updated (step S101). If not updated, continue monitoring.

  When the front system database 100 is updated, an update log of the front system database 100 is obtained (referred to as reading) (step S102).

  Next, the database update control unit 101 obtains the update log reduction target management table 1030 from the update log reduction target management unit 103 (step S103).

  Next, the database update control unit 101 adds information (target / non-target) indicating whether or not the record is an overwrite update target record to the update log of the front system database 100 based on the information in the update log reduction target management table 1030. Then, it is added to the update log table 1040 of the update log table storage unit 104 (step S104).

  Furthermore, if there is a duplicate overwrite update target record, the database update control unit 101 overwrites it with the latest record and updates it as the update log table 1041 (step S104).

  When the front system database 100 has not been committed by the application being updated (step S106), the database update control unit 101 monitors the front system database 100 again and has been committed (step S106) or whether there is further update. Confirm (Step S107). Continue monitoring if no further updates or commits have been made. If there is further update, the database update control unit 101 returns to step S102 to execute the process. If committed, finally, the database update control unit 101 transmits the update log of the update log table 1041 to the update log transmission control unit 102 (step S108).

  As described above, the database update control unit 101 ends the update log generation operation.

  FIG. 7 is a flowchart showing an outline of an operation of transmitting the update log to the backup system 2 in the update log transmission control unit 102 according to the first embodiment. Note that the processing according to this flowchart may be executed based on the above-described program control by the CPU.

  As illustrated in FIG. 7, first, the update log transmission control unit 102 confirms whether an update log is received from the database update control unit 101 (step S201). If not, wait until it is received.

  When the update log is received, the update log transmission control unit 102 integrates it into a unit to be transmitted to the backup system 2 and adds it to the update log storage table 1050 of the front system update log storage table storage unit 105 (step S202).

  Furthermore, if there is a duplicate overwrite update target record, the update log transmission control unit 102 overwrites it with the latest record and updates it as the update log storage table 1051 (step S203).

  If the transmission timing set by the system administrator has not been reached (step S204), the update log transmission control unit 102 has received another update log from the database update control unit 101 again (step S205) or the transmission timing. (Step S204) is confirmed. Monitoring is continued if the timing of further update log reception or transmission has not been reached. If there is further update log reception, the process returns to step S202 to execute processing. When the transmission timing is reached, finally, the update log transmission control unit 102 transmits the update log in the update log storage table 1051 to the update log reception control unit 201 of the backup system 2 (step S206).

  Thus, the update log transmission control unit 102 ends the operation of transmitting the update log to the backup system 2.

  FIG. 8 is a flowchart showing an outline of the operation of reflecting the update log in the backup system database 200 in the update log reception control unit 201 in the first embodiment. Note that the processing according to this flowchart may be executed based on the above-described program control by the CPU.

  As shown in FIG. 8, first, the update log reception control unit 201 confirms whether an update log is received from the update log transmission control unit 102 of the front system 1 (step S301). If not, wait until it is received.

  When the update log is received, the update log reception control unit 201 adds the update log to the update log storage table 1050 of the backup system update log storage table storage unit 202 (step S302).

  Furthermore, if there is a duplicate overwrite update target record, it is overwritten with the latest record and updated as the update log storage table 1051 (step S303).

  If the backup system database update timing set by the system administrator has not been reached (step S204), has the update log reception control unit 201 received another update log from the update log transmission control unit 102 of the front system 1 again? It is confirmed whether (Step S305) or database update timing has come (Step S304). Monitoring is continued if the timing of further update log reception or database update has not been reached. If there is further update log reception, the process returns to step S302 to execute the process. When the database update timing is reached, finally, the update log reception control unit 201 updates the backup system database 200 with the contents of the update log in the update log storage table 1051 (step S306).

  As described above, the update log reception control unit 201 ends the operation of reflecting the update log in the backup system database 200.

  Next, effects of the first exemplary embodiment of the present invention will be described.

  The front system and backup system in the present embodiment described above can perform asynchronous backup for a short time at low cost.

This is because the following configuration is included. That is, first, the update log reduction target management unit stores as a management table which table of the update log is the reduction target (overwrite target). Second, the database update control unit, the update log transmission control unit, and the update log reception control unit, in accordance with the instructions in the management table of the update log reduction target management unit, if there are duplicate overwrite update target records, Overwrite. As a result, since the redundant data is always sent to the backup system database after reducing redundant data, the amount of data transferred from the front system to the backup system is reduced and the cost is reduced. In addition, since the transfer data becomes small, the time required for backup is shortened, and the time when data cannot be synchronized between the front system and the backup system can be shortened.

[Second Embodiment]
In the first embodiment, a method of asynchronous backup of a database system using a single CPU has been described. In this embodiment, consider the case of a distributed database system in which a plurality of CPUs perform parallel processing. Note that a description similar to that of the first embodiment is omitted.

  FIG. 9 is a diagram showing a hardware configuration in which the front system 1 and the backup system 2 according to the second embodiment of the present invention are realized by a computer and its peripheral devices. Note that peripheral devices that are not involved in the explanation are omitted because they are the same as those in FIG.

  In the front system 1, a plurality of CPUs 11a to 11d are connected to a secondary storage device 15 that is a database. Although four units are connected in FIG. 9, the number of connections is arbitrary. Network interfaces 10a to 10d are connected to the respective CPUs 11a to 11d. The backup system 2 has the same hardware configuration. As in FIG. 2, the front system 1 and the backup system 2 are connected by a network 3. Others are the same as those in the first embodiment. Further, the functional configuration of the front system 1 and the backup system 2 in the second embodiment of the present invention includes each component shown in FIG. Therefore, in the following description, each component in FIG. 1 will be described in combination with FIG. 9, and further with reference to FIGS.

  In the operation of transmitting the update log to the backup system 2 in the update log transmission control unit 102 in the second embodiment, when the update log transmission control unit 102 receives the update log, the update log transmission control unit 102 transmits the update log to the backup system 2 in units. They are integrated and added to the update log storage table 1050 of the front system update log storage table storage unit 105 (step S202 in FIG. 7). Furthermore, if there is a duplicate overwrite update target record, it is overwritten with the latest record and updated as the update log storage table 1051 (step S203). At this time, different CPUs 11a to 11d are assigned to the keys of the updated records in the update log. This is because the record overwrite update is performed only for the record with the same key in step S203, and the overwrite update process between different keys does not interfere with each other. For this reason, the update log transmission control unit 102 can perform parallel processing by a plurality of CPUs by assigning a CPU to each key.

  Next, the update log transmission control unit 102 transmits the update log in the update log storage table 1051 to the update log reception control unit 201 of the backup system 2 through the network interfaces 10a to 10d connected to the CPUs 11a to 11d (step S206). .

  The receiving backup system 2 side has the same hardware configuration as that of the front system 1, and the CPUs 21a to 21d and the network interfaces 20a to 20d that perform processing for each key are determined. The update log transmitted by the front system 1 is received by the backup system 2 via the network interfaces 20a to 20d for each key. As with the front system 1, the CPUs 21 a to 21 d execute steps S 302 to S 306 for each key of the update record for the received update log, and overwrite the update log and reflect it in the backup system database 200.

  The front system and backup system in the present embodiment described above can further perform asynchronous backup in a short time by distributing processing.

  Each component in each embodiment of the present invention described above can be realized by a computer apparatus and firmware based on program control as well as by realizing the function in hardware. The program is provided by being recorded on a computer-readable recording medium such as a magnetic disk or a semiconductor memory, and is read by the computer when the computer is started up. The read program causes the computer to function as a component in each of the embodiments described above by controlling the operation of the computer.

  Although the present invention has been described with reference to each embodiment, the present invention is not limited to the above embodiment. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

  For example, each component described in each of the above embodiments does not necessarily have to be individually independent. For example, for each component, a plurality of components may be realized as one module, or one component may be realized as a plurality of modules. Each component is configured such that a component is a part of another component, or a part of a component overlaps a part of another component. Also good.

  Further, in each of the embodiments described above, a plurality of operations are described in order in the form of a flowchart, but the described order does not limit the order in which the plurality of operations are executed. For this reason, when each embodiment is implemented, the order of the plurality of operations can be changed within a range that does not hinder the contents.

  Furthermore, in each embodiment described above, a plurality of operations are not limited to being executed at different timings. For example, another operation may occur during the execution of a certain operation, or the execution timing of a certain operation and another operation may partially or entirely overlap.

  Furthermore, in each of the embodiments described above, a certain operation is described as a trigger for another operation, but the description does not limit all relationships between the certain operation and the other operations. For this reason, when each embodiment is implemented, the relationship between the plurality of operations can be changed within a range that does not hinder the contents. The specific description of each operation of each component does not limit each operation of each component. For this reason, each specific operation | movement of each component may be changed in the range which does not cause trouble with respect to a functional, performance, and other characteristic in implementing each embodiment.

DESCRIPTION OF SYMBOLS 1 Front system 2 Backup system 3 Network 10, 20, 10a, 10b, 10c, 10d, 20a, 20b, 20c, 20d Network interface 11, 21, 11a, 11b, 11c, 11d, 21a, 21b, 21c, 21d CPU
12, 22 Output device 13, 23 Input device 14, 24 Main storage device 15, 25 Secondary storage device 100 Front system database 101 Database update control unit 102 Update log transmission control unit 103 Update log reduction target management unit 104 Update log table storage Unit 105 front system update log storage table storage unit 200 backup system database 201 update log reception control unit 202 backup system update log storage table storage unit

Claims (5)

A front system that performs data processing;
A backup system for performing data backup of the front system;
Including
The front system is
A front system database updated at any time in the front system;
A backup system database for backing up the front system database in the backup system;
When sending an update log of the front system database to the backup system, an update log reduction target management unit that stores and manages an update log reduction target management table that records whether or not it is a target to be overwritten and updated with a later record with respect to duplicate records;
An update log table storage unit for storing an update log of the front system database as an update log table;
Organize the update log of the front system database into record keys and record contents, and refer to the management table of the update log reduction target management unit, add to the update log whether or not it is an overwrite update target record, and overwrite update target If it is a record, the duplicate record is overwritten with a later record and output to the update log table storage unit, and the update log is sent to the update log transmission control unit when the application that updated the front system database commits the update. A database update controller to send;
A front system update log storage table storage unit for storing an update log transmitted from the database update control unit as an update log storage table;
When the update log sent from the database update control unit is updated, it is collected in the unit to be sent to the backup system, and if it is an overwrite update target record, the duplicate record is overwritten with the later record and updated to the backup system An update log transmission control unit for transmitting logs;
Including
The backup system is
A backup system update log storage table storage unit for storing the update log transmitted from the front system as an update log storage table;
When there is an update of the update log transmitted from the update log transmission control unit, if it is an overwrite update target record, the duplicate record is overwritten with a later record, and the backup system database is set at a timing set by the system administrator An asynchronous backup system that includes an update log reception control unit that updates the file with the update log contents of the update log storage table.   The asynchronous backup system according to claim 1, wherein the front system and the backup system are configured by a distributed database, and perform parallel processing using a record key of the update log. A front system that performs data processing;
A backup system for performing data backup of the front system;
The front system in a data processing system comprising:
A front system database updated at any time in the front system;
When sending an update log of the front system database to the backup system, an update log reduction target management unit that stores and manages an update log reduction target management table that records whether or not it is a target to be overwritten and updated with a later record with respect to duplicate records;
An update log table storage unit for storing an update log of the front system database as an update log table;
Organize the update log of the front system database into record keys and record contents, and refer to the management table of the update log reduction target management unit, add to the update log whether or not it is an overwrite update target record, and overwrite update target If it is a record, the duplicate record is overwritten with a later record and output to the update log table storage unit, and the update log is sent to the update log transmission control unit when the application that updated the front system database commits the update. A database update controller to send;
A front system update log storage table storage unit for storing an update log transmitted from the database update control unit as an update log storage table;
When the update log sent from the database update control unit is updated, it is collected in the unit to be sent to the backup system, and if it is an overwrite update target record, the duplicate record is overwritten with the later record and updated to the backup system An update log transmission control unit for transmitting logs;
Including front system. The database update control unit organizes the update log of the front system database into record keys and record contents,
The database update control unit refers to the management table of the update log reduction target management unit, adds to the update log whether or not the record is an overwrite update target record,
If it is an overwrite update target record, the database update control unit overwrites the duplicate record with a later record, updates the update log table,
When the application that has updated the front system database commits the update, the database update control unit sends the update log of the update log table to the update log transmission control unit,
The update log received by the update log transmission control unit is added to the update log storage table of the front system update log storage table storage unit in a unit to be transmitted to the backup system,
If it is an overwrite update target record, the update log transmission control unit overwrites the duplicate record with a later record and updates the update log storage table,
Sending the update log with the contents of the update log storage table to the backup system;
The update log reception control unit receives the update log, adds it to the update log storage table of the backup system update log storage table storage unit,
If it is an overwrite update target record, the update log reception control unit duplicates the record that is duplicated with a later record and updates the update log storage table of the backup system update log storage table storage unit,
An asynchronous backup method for updating the backup system database with the contents of the update log in the update log storage table. The database update control unit organizes the update log of the front system database into record keys and record contents,
The database update control unit refers to the management table of the update log reduction target management unit, adds to the update log whether or not the record is an overwrite update target record,
If it is an overwrite update target record, the database update control unit overwrites the duplicate record with a later record, updates the update log table,
When the application that has updated the front system database commits the update, the database update control unit sends the update log of the update log table to the update log transmission control unit,
The update log received by the update log transmission control unit is added to the update log storage table of the front system update log storage table storage unit in a unit to be transmitted to the backup system,
If it is an overwrite update target record, the update log transmission control unit overwrites the duplicate record with a later record and updates the update log storage table,
Sending the update log with the contents of the update log storage table to the backup system;
The update log reception control unit receives the update log, adds it to the update log storage table of the backup system update log storage table storage unit,
If it is an overwrite update target record, the update log reception control unit duplicates the record that is duplicated with a later record and updates the update log storage table of the backup system update log storage table storage unit,
A program that causes a computer to execute processing for updating the backup system database with the contents of the update log in the update log storage table.

Images