JP2014170448A - Replication system, job processing system, replication method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a replication system capable of surely executing replication even in the case where update logs are rapidly stagnated by fault occurrence or the like, while implementing high-speed transfer of update logs, a job processing system, a replication method and a program.SOLUTION: A replication system comprises: a job processing system 100; and a backup system 200. The job processing system 100 includes: a storage device 30a for storing update object data and its update log; a storage device 40b of which the read speed and the write speed are lower than the storage device 30a but the storage capacity is higher; an update log transmission section 7 for transmitting the update log on the storage device 30a to the backup system 200; and an update log retreat section 5 for creating an update log file 11 including a plurality of update logs on the storage device 30a under a preset condition, temporarily storing the update log file 11 in the storage device 40a and then transmitting the update log file 11 to the backup system 200.

Description

  The present invention relates to a replication system, a business processing system, a replication method, and a program for realizing them, for backing up a business processing system.

  Conventionally, replication is used as one of methods for backing up data. In replication, data on a business processing system that processes business online is replicated to a spare system at another site, and the content of the replicated data is always synchronized with the latest data (for example, patent literature). 1-3). In the present specification, hereinafter, a business processing system that processes business online is referred to as a “front system”, and a spare system is referred to as a “backup system”.

  By the way, when such replication is adopted, it is necessary to promptly reflect the update log in the front system to the backup system in order to suppress the influence on the business process when a failure occurs in the front system. For this reason, for example, in Patent Document 3, the front system divides the update log based on the key of the record in the database so that the update log with the same record becomes the same processing sequence, Transfer to backup system. Thereafter, the update log is immediately reflected in the backup system.

Japanese Patent Laid-Open No. 6-67959 Japanese Patent Laid-Open No. 10-49418 JP 2012-133417 A

  By the way, in the system disclosed in Patent Document 3, it is necessary to transfer and reflect the update log from the front system to the backup system at a high speed. Therefore, the update log is stored in the memory database of each system. .

  However, the memory database is superior to the database by the disk device in the above point, but since the capacity limit value is low, the update log is stored in the backup system 20 when the update log stagnates suddenly due to a failure or the like. There is a possibility that a state where the update log cannot be transmitted, that is, a state where the update log overflows. In such a case, there is a risk that replication cannot be executed.

  An example of an object of the present invention is a replication that solves the above problems and realizes high-speed transfer of update logs, and can reliably execute replication even when update logs are stagnant due to a failure or the like. A system, a business processing system, a replication method, and a program are provided.

To achieve the above object, a replication system according to an aspect of the present invention includes a business processing system for executing business processing, and a backup system for backing up the business processing system,
The business processing system includes:
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
It is characterized by having.

In order to achieve the above object, a business processing system according to an aspect of the present invention is a business processing system that performs replication in cooperation with a backup system,
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
It is characterized by having.

In order to achieve the above object, a replication method according to an aspect of the present invention is a replication method using a business processing system for executing business processing and a backup system for backing up the business processing system. And
(A) in the business processing system, storing data to be updated and an update log of the data in a first storage device;
(B) in the business processing system, sending an update log stored in the first storage device to the backup system;
(C) In the business processing system, when a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
It is characterized by having.

Furthermore, in order to achieve the above object, a program according to one aspect of the present invention is a program for causing a computer to execute replication in cooperation with a backup system,
In the computer,
(A) storing data to be updated and an update log of the data in a first storage device included in the computer;
(B) transmitting an update log stored in the first storage device to the backup system;
(C) When a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is provided in the computer; and Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
Is executed.

  As described above, according to the present invention, high-speed transfer of update logs can be realized, and replication can be reliably executed even when the update logs are steeply accumulated due to a failure or the like.

FIG. 1 is a diagram showing a schematic configuration of a replication system according to an embodiment of the present invention. FIG. 2 is a block diagram showing the configuration of the replication system according to the embodiment of the present invention. FIG. 3 is a diagram showing an example of an update log storage table stored in the front system in the present embodiment. FIG. 4 is a diagram showing an example of a serial number table stored in the front system and the backup system in the present embodiment. FIG. 5 is a diagram illustrating an example of a stay threshold used in the front system in the present embodiment. FIG. 6 is a diagram showing an example of an update log storage table stored in the backup system in the present embodiment. FIG. 7 is a flowchart showing an operation during update log transmission processing of the front system (business processing system) in the embodiment of the present invention. FIG. 8 is an explanatory diagram showing the flow of processing of the replication system during normal times. FIG. 9 is an explanatory diagram showing the flow of the update log of the replication system at the normal time. FIG. 10 is a diagram showing an example of an update log message used in the embodiment of the present invention. FIG. 11 is a flowchart showing the operation during update log saving processing of the front system (business processing system) in the embodiment of the present invention. FIG. 12 is an explanatory diagram showing the flow of processing of the replication system when the update log stays. FIG. 13 is an explanatory diagram showing the flow of the update log of the replication system when the update log stays. FIG. 14 is a diagram illustrating an example of an update log file created in the present embodiment. FIG. 15 is a diagram illustrating an example of a file transfer notification message used in the present embodiment. FIG. 16 is a flowchart showing an operation during update log reception processing of the backup system in the embodiment of the present invention. FIG. 17 is a flowchart showing an operation during update log reflection processing of the backup system in the embodiment of the present invention. FIG. 18 is a block diagram illustrating an example of a computer that implements the front system (business processing system) according to the embodiment of the present invention.

(Embodiment)
Hereinafter, a replication system, a business processing system, a replication method, and a program according to an embodiment of the present invention will be described with reference to FIGS.

[System configuration: Overall configuration]
First, the system configuration of the replication system according to this embodiment will be described with reference to FIG. FIG. 1 is a diagram showing a schematic configuration of a replication system according to an embodiment of the present invention.

  As shown in FIG. 1, the replication system 300 according to this embodiment includes a business processing system 100 for executing business processing and a backup system 200 for backing up the business processing system 100. In the present embodiment, the business processing system 100 and the backup system 200 are connected via a network. In the present embodiment, the business processing system is hereinafter referred to as “front system”.

  As shown in FIG. 1, the front system 100 includes a first storage device 30 a, a second storage device 40 a, an update log transmission unit 7, and an update log saving unit 5. Among these, the first storage device 30a stores data to be updated and an update log of this data. The second storage device 40a is a storage device having a lower storage speed and a higher storage capacity than the first storage device 30a.

  The update log transmission unit 7 transmits the update log stored in the first storage device 30 a to the backup system 200. Therefore, the update log generated in the business processing system 100 is backed up in the backup system 200.

  In addition, the update log saving unit 5 first includes an update including a plurality of update logs stored in the first storage device 30a when the set condition is satisfied, for example, when the update log increases rapidly. A log file 11 is created. Subsequently, the update log saving unit 5 temporarily stores the created update log file 11 in the second storage device 40a, and then transmits the stored update log file 11 to the backup system 200.

  As described above, in this embodiment, the update log is normally stored in the first storage device 30a having a high read speed and high write speed, so that high-speed transfer of the update log can be realized. When the update log stays due to the occurrence of a failure, a temporary increase in business processing, etc., the update log is collected into an update log file and stored in the second storage device having a large capacity before the backup system. 200. For this reason, occurrence of a situation where the update log overflows is avoided, and even in the above-described case, replication is reliably performed.

  Next, the configuration of the replication system according to the present embodiment will be described more specifically with reference to FIGS. FIG. 2 is a block diagram showing the configuration of the replication system according to the embodiment of the present invention.

[System configuration: Front system]
As shown in FIG. 2, in the present embodiment, the front system 100 includes a memory storage device as the first storage device 30a and a disk device as the second storage device 3040a. Further, data to be updated and an update log are stored in a memory database (hereinafter referred to as “memory DB”) constructed in the storage area of the memory storage device. In the following description, they will be referred to as memory DB 30a and disk device 40a.

  In the present embodiment, data to be updated is updated by an application program (hereinafter referred to as “AP”) 1 executed in the front system 100. Specifically, the data to be updated is the user table 2 stored in the memory DB 30a. The user table 2 is composed of a key (Key) representing a record in the memory DB 30a and a value (Value) representing the user.

  Further, when an update log is generated by updating the user table 2, AP1 calls the update log storage processing unit 3 included therein as an API. When called, the update log storage processing unit 3 assigns serial numbers to the generated update logs in the order of generation, and stores them in the memory DB 30a. Specifically, the update log to which the serial number is assigned is stored in the memory DB 30 a as the update log storage table 3 stored in the update log storage processing unit 3.

  As shown in FIG. 3, the update log storage table 4 registers, for each update log, its serial number, a flag indicating whether each update log is a transfer target as the update log file 11, and the contents of the update log. ing. FIG. 3 is a diagram showing an example of an update log storage table stored in the front system in the present embodiment. The “update log contents” includes the update contents of the user table 2.

  Further, the update log storage processing unit 3 registers the serial number of the stored update log in the serial number table 6 as “registered serial number”. As shown in FIG. 4, the serial number table 6 is serial number information that identifies processed serial numbers and registered serial numbers. FIG. 4 is a diagram showing an example of a serial number table stored in the front system and the backup system in the present embodiment.

  The processed serial number is the serial number of the update log that has been transmitted to the backup system 200. The registered serial number is a serial number registered by the update log storage processing unit 3, and is a serial number of an update log that has not been transmitted to the backup system 200.

  Further, in the present embodiment, the update log transmission unit 7 refers to the update log storage table 4 and the serial number table 6 on the memory DB 30a in normal times, and updates the update log message (see FIG. 10 described later). To the update log receiving unit 13 of the backup system 200. At this time, the update log transmission unit 7 updates the processed serial number of the serial number table 6 stored in the memory DB 30a. “Normal time” refers to a case where the above-described setting condition is not satisfied and the update log saving unit 5 is not performing processing.

  As described above, the update log saving unit 5 acquires a plurality of update logs from the update log storage table 4 when the set condition is satisfied, and collectively collects them as an update log file 11 (see FIG. 14 described later). Then, it is evacuated to the disk device 40a. Further, the update log saving unit 5 deletes the saved update log from the update log storage table 4 of the memory DB 30a.

  The update log file 11 stored in the disk device 40a is transferred to the backup system 200 by file transfer such as FTP (File Transfer Protocol) by the update log saving unit 5. If the file transfer is successful, the disk device 40a deletes the update log file 11.

  The update log saving unit 5 repeats saving and file transfer for all update logs that are subject to file transfer in the update log storage table 4 (see FIG. 3). After saving all update logs subject to file transfer and file transfer, the update log saving unit 5 notifies the update log receiving unit 13 of a file transfer notification message. In this file transfer notification message, the first serial number (start serial number) of a plurality of update logs that are file transfer targets and the last serial number (end serial number) of the update log are recorded (see FIG. 15 described later). ).

  In the present embodiment, the setting condition is that when the update log stays in the front system 100, specifically, when the staying number (= registered serial number−processed serial number) is equal to or greater than the retention threshold. It is. The stay threshold is stored as the stay threshold 9 in the memory DB 30a. FIG. 5 is a diagram illustrating an example of a stay threshold used in the front system in the present embodiment.

  Further, as shown in FIG. 2, the number of lots 10 is stored on the memory DB 30a. The lot number 10 is a set value of the number of update logs included in the update log file. In the present embodiment, the retention threshold 9 and the number of lots 10 are set by the setting unit 8. The setting unit 8 sets the stay threshold 9 and the lot number 10 according to an instruction from the administrator of the front system 100 or according to a preset rule.

[System configuration: Backup system]
As shown in FIG. 2, the backup system 200 stores replication data, that is, data to be updated and an update log in preparation for the occurrence of a failure in the front system 100. And a device 40b.

  Among these, the storage device 30b is a memory device in which the memory DB is constructed, like the memory DB 30a of the front system 100. The storage device 40b is a disk device, similar to the disk device 40a of the front system 100. In the following description, they are expressed as memory DB 30b and disk device 40b.

  The memory DB 30b stores a user table 17 similar to the user table 2 as backup data of data to be updated. Further, the memory DB 30 b also stores a sequence number table 15 similar to the sequence number table 6, and a start sequence number 19 and an end sequence number 20 in the file transfer notification message transmitted from the update log saving unit 5.

  In addition, the update log transmitted from the update log transmission unit 7 is stored in the memory DB 30b as the update log storage table 14. FIG. 6 is a diagram showing an example of an update log storage table stored in the backup system in the present embodiment. As shown in FIG. 6, the update log storage table 14 stores the serial number, the termination flag, and the contents of the update log for each update log.

  The end flag indicates a point when switching the reference destination of the update log during update log update processing (reflection) from the update log storage table 14 to the update log file 11 stored in the disk device 40b.

  The disk device 40b is a storage device that has a lower storage speed and a higher storage capacity than the memory DB 30b. Therefore, the update log file 11 transmitted by the update log saving unit 5 of the front system 100 is stored in the disk device 40b.

  As illustrated in FIG. 2, the backup system 200 includes an update log receiving unit 13 and an update log reflecting unit 16. Among these, when receiving the update log by the update log message, the update log receiving unit 13 stores the update log in the update log storage table 14 on the memory DB 30b and updates the registered serial number of the serial number table 15. Further, when receiving the file transfer notification message from the update log saving unit 5, the update log receiving unit 13 updates the start sequence number 19 and the end sequence number 20 on the memory DB 30b.

  When the update log file 11 is not stored in the disk device 40b, the update log reflection unit 16 updates the user table 17 based on the update log (update log storage table 14) stored in the memory DB 30b. The update log reflecting unit 16 updates the update log file 11 when the update log file 11 is stored in the disk device 40b, specifically, when the above-described termination flag is set to YES (see FIG. 6). The user table 17 is updated based on the file 11.

  Specifically, in the latter case, the update log reflecting unit 16 refers to the serial number table 15, the update log storage table 4, and the disk device 40 b on the memory DB 30 b, and based on the received update log file 11, the memory DB 30 b The above user table 17 is updated. Furthermore, in this case, the update log reflecting unit 16 also updates the processed serial number of the serial number table 15 on the memory DB 30b. The update log reflection unit 16 deletes the update log file 11 for which the update process has been completed when the update process is successful.

[System operation]
Next, the operation of the replication system 300 according to the embodiment of the present invention will be described with reference to FIGS. In the following description, FIGS. In this embodiment, the replication method is performed by operating the replication system 300. Therefore, the description of the replication method in the present embodiment is replaced with the following description of the operation of the replication system 300.

[System operation: Normal processing]
First, normal processing of the replication system 300 in normal time will be described with reference to FIGS.

Front system:
FIG. 7 is a flowchart showing an operation during update log transmission processing of the front system (business processing system) in the embodiment of the present invention. FIG. 8 is an explanatory diagram showing the flow of processing of the replication system during normal times. FIG. 9 is an explanatory diagram showing the flow of the update log of the replication system at the normal time. FIG. 10 is a diagram showing an example of an update log message used in the embodiment of the present invention.

  First, as shown in FIGS. 8 and 9, in the front system 100, when the AP 1 updates the user table 2 on the memory DB, the update log storage processing unit 3 is called as an API and is stored on the memory DB 30a. The update log is stored in the update log storage table 4. Further, the update log storage processing unit 3 updates the registered serial numbers in the serial number table 6 (see FIG. 4).

  Next, as shown in FIG. 7, in the front system 100, the update log transmission unit 7 monitors the update log storage table 4 at regular intervals, and the update log storage table 4 is unprocessed (processed serial number + 1). It is determined whether an update log exists (step A1).

  If there is no unprocessed update log as a result of the determination in step A1, the update log transmission unit 7 enters a standby state. On the other hand, if there is an unprocessed update log as a result of the determination in step A1, the update log transmission unit 7 reads the unprocessed update log and creates an update log message (step A2).

  Specifically, in step A2, the update log transmission unit 7 specifies a processed serial number from the serial number table 6, as shown in FIG. Then, the update log transmission unit 7 is given a serial number equal to or greater than the value obtained by adding 1 to the specified processed serial number from the update log storage table 4 (see FIG. 3), and the file transfer target is set as a non-target. Read a certain number of updated logs.

  And the update log transmission part 7 produces the update log message | telegram shown in FIG. 10 using the update log for the fixed number of read. As shown in FIG. 10, the update log message includes a serial number, a size, and the update log for each of a certain number of update logs. In the present embodiment, the “certain number” is set as a fixed value by the administrator of the front system 100 in advance.

  Next, the update log transmission unit 7 transmits the update log message created in step A2 to the update log reception unit 13 of the backup system 200 (step A3). Then, after the transmission, the update log transmission unit 7 increments the processed serial number in the serial number table 6 by a certain number (step A4).

  Thereafter, the update log transmission unit 7 deletes the transmitted update log from the update log storage table 4 (step A5). After execution of step A5, the update log transmission unit 7 executes step A1 again.

Backup system:
Further, when Steps A1 to A5 are executed, as shown in FIGS. 8 and 9, in the backup system 200, the update log receiving unit 13 receives the update log. Then, the update log receiving unit 13 stores the received update log in the update log storage table 14 on the memory DB 30b, and updates the registered serial number in the serial number table 15 (see FIG. 4).

  Thereafter, the update log reflection unit 16 monitors the update log storage table 14 at regular intervals, reads an unprocessed update log (serial number = processed serial number + 1) from the update log storage table 14, and reads the contents of the read update log. This is reflected in the user table 17. Further, the update log reflecting unit 16 updates the processed serial number in the serial number table 15 (see FIG. 4).

[System operation: Update log backup processing]
Next, the update log saving process of the replication system 300 when the update log is retained will be described with reference to FIGS.

Front system:
FIG. 11 is a flowchart showing the operation during update log saving processing of the front system (business processing system) in the embodiment of the present invention. FIG. 12 is an explanatory diagram showing the flow of processing of the replication system when the update log stays. FIG. 13 is an explanatory diagram showing the flow of the update log of the replication system when the update log stays. FIG. 14 is a diagram illustrating an example of an update log file created in the present embodiment. FIG. 15 is a diagram illustrating an example of a file transfer notification message used in the present embodiment.

  First, as shown in FIG. 12 and FIG. 13, it is assumed that business processing has increased from the normal state, and the number of update log retention has increased.

  As shown in FIG. 11, the update log saving unit 5 refers to the registered serial numbers and processed serial numbers in the serial number table 6 (see FIG. 4) at regular intervals to store the update log retention number (= registered serial number− (Processed serial number) is calculated, and it is determined whether the staying number is equal to or greater than the staying threshold (see FIG. 5) (step B1).

  As a result of the determination in step B1, if the staying number is not equal to or greater than the staying threshold value, the update log saving unit 5 enters a standby state. On the other hand, if the result of determination in step B1 is that the staying number is equal to or greater than the staying threshold, the update log saving unit 5 adds 1 to the current processed serial number in the update log storage table 4 (see FIG. 3). For the update log from the serial number of the value (processed serial number + 1) to the registered serial number, the file transfer target is changed to “target” (step B2).

  Next, the update log saving unit 5 determines whether there is an update log in which the file transfer target is set to “target” in the update log storage table 4 (step B3).

  As a result of the determination in step B 3, if there is an update log in which the file transfer target is set to “target” in the update log storage table 4, the update log saving unit 5 calculates the lot number 10 from the update log storage table 4. get. Then, the update log saving unit 5 combines the update logs for the number of lots into one file, which is set as the update log file 11, and stores the update log file 11 in the disk device 40a (step B4).

  In the present embodiment, the update log file 11 is composed of serial numbers, sizes, and update logs of the update files for the number of lots, as shown in FIG. Further, the file name of the update log file 11 is created with a start sequence number and an end sequence number.

  In step B4, if the update log with the file transfer target “target” is less than the number of lots in the update log storage table 4, the update log saving unit 5 stores the unprocessed log that exists in the update log storage table 4. An update log file 11 is created using all the update logs. Further, when creating the update log file 11, the update log saving unit 5 sequentially extracts from the update log storage table 4 the update log with the lowest serial number that has not been processed and registers it in the update log file 11.

  Next, when the update log saving unit 5 saves the update logs for the number of lots in the update log file 11, the update log saving unit 5 deletes the update logs saved from the update log storage table 4 (step B5).

  Next, the update log saving unit 5 transfers the update log file 11 saved on the disk device 40a to the disk device 40b on the backup system 200 side by executing file transfer such as FTP (step B6). Next, after the file transfer, the update log saving unit 5 deletes the update log file 11 on the disk device 40a (step B7).

  The update log saving unit 5 repeatedly executes this series of update log saving and file transfer processing (steps B4 to B7) as long as there is an update log whose file transfer target is “target” in the update log storage table 4. .

  If there is no update log in which the file transfer target is set to “target” in the update log storage table 4 as a result of the determination in step B3, the update log saving unit 5 saves the last update log saved. Is determined to be greater than the processed serial number (step B8).

  As a result of the determination in step B8, when the serial number of the last update log saved is larger than the processed serial number, the update log saving unit 5 updates the processed serial number in the serial number table 6 (step B9). Thereafter, the update log saving unit 5 executes Step B10.

  On the other hand, as a result of the determination in step B8, when the serial number of the last update log saved is not larger than the processed serial number, the processed serial number has already been updated by the update log transmission unit 7, and the processed serial number is The serial number of the last update log in the update log file 11 is greater than or equal to. Therefore, the update log saving unit 5 does not update in this case, and executes Step B10.

  In step B10, the update log saving unit 5 uses the file transfer notification message shown in FIG. 15 to indicate to the update log receiving unit 13 the first serial number of the update log whose file transfer target is “target”. And the last serial number is notified as the end serial number. Thereafter, the update log saving unit 5 executes Step B1 again.

  Further, in the present embodiment, while the steps B1 to B10 are being executed (file transfer is being executed), the update log transmission unit 7 executes the following processing in parallel with this processing. First, the update log transmission unit 7 reads a certain number of update logs whose file transfer target is “not applicable” from the update log storage table 4, and sends a message to the update log reception unit 13 of the backup system 200. To transfer a certain number of update logs.

  Next, after the transfer is completed, the update log transmission unit 7 increments the processed serial number in the serial number table 6 by a certain number. The “certain number” is set as a fixed value by the administrator of the front system 100 in advance, as in the case of step A2 described above.

Backup system:
FIG. 16 is a flowchart showing an operation during update log reception processing of the backup system in the embodiment of the present invention. FIG. 17 is a flowchart showing an operation during update log reflection processing of the backup system in the embodiment of the present invention.

  When Steps B1 to B10 shown in FIG. 11 are executed, the backup system executes the update log reception process shown in FIG. 16 and the update log reflection process shown in FIG. Hereinafter, these processes will be described.

  As shown in FIG. 16, the update log receiving unit 13 determines whether an update log message has been received from the update log transmitting unit 7 of the front system 100 (step C1).

  If the result of determination in step C1 is that an update log message has been received, the update log receiving unit 13 determines whether the update log sequence number included in the update log message is greater than or equal to the start sequence number 19 and the end sequence number 20 on the memory DB 30b. It is determined whether or not (step C2).

  As a result of the determination in step C2, if the update log sequence number is not less than the start sequence number 19 of the file transfer notification already received and the end sequence number 20 or less, the update log has already been received by the file transfer notification. The update log receiving unit 13 enters a standby state.

  On the other hand, as a result of step C2, if the update log sequence number is not greater than or equal to the start sequence number 19 and the end sequence number 20 of the already received file transfer notification, the update log receiving unit 13 is included in the received update log message. The update log is stored in the update log storage table 14 of the memory DB 30b (step C3).

  Next, after executing step C3, the update log receiving unit 13 determines whether the update log sequence number is greater than the end sequence number 20 on the memory DB 30b (step C4). As a result of the determination in step C4, if the update log sequence number is larger than the end sequence number 20, the update log receiving unit 13 updates the registered sequence number in the sequence number table 15 with the update log sequence number (step C5). Thereafter, the update log receiving unit 13 executes Step C1 again.

  On the other hand, as a result of the determination in step C4, when the update log sequence number is not greater than the end sequence number 20 (end sequence number 20 or less), the update log receiving unit 13 sets the update log sequence number from the start sequence number 19 to 1. It is determined whether or not a value (start serial number -1) is obtained by subtracting (step C6).

  As a result of the determination in step C6, when the update log sequence number is not a value obtained by subtracting 1 from the start sequence number 19, the update log receiving unit 13 executes step C5 again. On the other hand, if the result of the determination in step C6 is that the update log sequence number is a value obtained by subtracting 1 from the start sequence number, the update log receiving unit 13 uses the value of the end sequence number 20 on the memory DB 30b and the sequence number table 15 The registered serial number is updated (step C7). Thereafter, the update log receiving unit 13 executes Step C1 again.

  If the update log message has not been received as a result of the determination in step C1, the update log receiving unit 13 determines whether the file transfer notification message has been received from the update log saving unit 5 of the front system 100. (Step C8).

  As a result of the determination in step C8, when the file transfer notification message has not been received, the update log receiving unit 13 enters a standby state. On the other hand, when the file transfer notification message is received as a result of step C8, the update log receiving unit 13 updates the received start sequence number and end sequence number on the memory DB 30b (step C9).

  Next, the update log receiving unit 13 determines whether or not there is an update log in which the value obtained by subtracting 1 from the start sequence number 19 (start sequence number -1) is a sequence number in the update log storage table 14 on the memory DB 30b. Determine (step C10).

  As a result of the determination in step C10, when there is no update log in which the value obtained by subtracting 1 from the start sequence number 19 is a sequence number, the update log receiving unit 13 executes step C1 again.

  On the other hand, as a result of the determination in step C10, if there is an update log in which the value obtained by subtracting 1 from the start serial number 19 is a serial number, the update log receiving unit 13 updates the update log storage table 14 (see FIG. 6). , The end flag of the update log in which the serial number is a value obtained by subtracting 1 from the start serial number 19 is set to “YES” (step C11). Thereafter, the update log receiving unit 13 executes Step C1 again.

  The update log is updated in the backup system 200 by the above steps C1 to C11.

  As shown in FIG. 17, first, the update log reflecting unit 16 refers to the serial number table 15 (see FIG. 4) on the memory DB 30b to determine whether the registered serial number is larger than the processed serial number. (Step D1).

  If the registered serial number is not greater than the processed serial number as a result of the determination in step D1, the update log reflecting unit 16 enters a standby state. On the other hand, if the registered serial number is larger than the processed serial number as a result of the determination in step D1, the update log reflecting unit 16 refers to the update log storage table 14 on the memory DB 30b and adds 1 to the processed serial number. It is determined whether or not an update log having a value serial number exists (step D2).

  As a result of the determination in step D2, if there is no update log having a serial number obtained by adding 1 to the processed serial number, the update log reflecting unit 16 executes step D8 described later.

  On the other hand, as a result of the determination in step D2, if there is an update log having a serial number with a value obtained by adding 1 to the processed serial number, the update log reflecting unit 16 sets the value obtained by adding 1 to the processed serial number. A certain number of update logs are read from the serial number (step D3). Then, the update log reflecting unit 16 reflects the read update log in the user table 17 (step D4). In the present embodiment, the fixed number is preset as a fixed value.

  After execution of step D4, the update log reflecting unit 16 updates the processed serial number of the serial number table 15 (step D5), and further deletes the update log below the processed serial number from the update log storage table 14 (step D6). ).

  Next, the update log reflection unit 16 determines whether there is an update log in which the termination flag is set to YES or an update log having a serial number obtained by adding 1 to the processed serial number in the update log storage table 14. Is determined (step D7).

  If any update log does not exist as a result of the determination in step D7, the update log reflection unit 16 executes step D1 again.

  On the other hand, if one of the update logs exists as a result of the determination in step D7, the update log reflecting unit 16 has a serial number of a value obtained by adding 1 to the processed serial number on the disk device 40b or higher. It is determined whether or not the update log file 11 having an end sequence number or less exists (step D8).

  As a result of the determination in step D8, if the update log file 11 does not exist, the update log reflection unit 16 executes step D1 again.

  On the other hand, if the above-mentioned update log file 11 exists as a result of the determination in step D8, the update log reflection unit 16 further determines whether the processed serial number is smaller than the end serial number 20 (step D9). .

  If the processed sequence number is smaller than the end sequence number 20 as a result of the determination in step D9, the update log reflecting unit 16 reads a predetermined number of update logs from the update log file 11 on the disk device 40b (step D10). In this case, the fixed number is also set in advance as a fixed value in the same manner as in step D3 described above.

  Next, the update log reflection unit 16 reflects the read update logs for a certain number in the user table 17 (step D11), and updates the processed serial number in the serial number table 15 (step D12). Thereafter, the update log reflecting unit 16 executes Step D9 again. Steps D9 to D12 are repeatedly executed as long as the processed sequence number is smaller than the end sequence number, and the contents of the update log file 11 are reflected in the user table.

  If the processed serial number is not smaller than the processed serial number 20 (end serial number 20 or more) as a result of the determination in step D9 described above, the update log reflecting unit 16 stores the update log file 11 on the disk device 40b. It deletes as a processed file (step D13). Thereafter, the update log reflecting unit 16 executes Step D1 again.

  Through the above steps D1 to D13, the contents of the update log are reflected in the user table in the backup system 200, and the replication of the front system 100 is completed.

[Effects of the present embodiment]
As described above, in the present embodiment, the update log is stored in the memory DB having a high reading speed and writing speed, so that high-speed transfer of the update log is realized. If the update log stays due to the occurrence of a failure, a temporary increase in business processing, etc., the update log is temporarily stored in the disk device as an update log file and then transferred to the backup system. For this reason, occurrence of a situation where the update log overflows is avoided, and even in the above-described case, replication is reliably performed.

  The update log transferred from the memory DB of the front system 100 and the update log transferred by file transfer are managed by serial numbers assigned in the order of occurrence. Therefore, even when the update logs are transferred in duplicate, the backup system 200 reflects the data in the memory DB in a state in which the order is guaranteed, so that replication is realized.

[Modification]
In the above-described embodiment, the front system 100 sets the retention threshold value 9 and the number of lots 10 by the setting unit 8. However, the present embodiment is not limited to this, and in the front system 100, the default values for the retention threshold 9 and the number of lots 10 are preset, and the front system 100 does not include the setting unit 8. There may be.

  In the present embodiment, one backup system 200 may correspond to a plurality of front systems 100. In this aspect, in order to prevent processing stagnation, it is preferable that the read speed and write speed of each storage device in the backup system 200 be higher than the read speed and write speed of the corresponding storage device in each front system 100.

[program]
The program in the present embodiment may be a program that causes a computer to execute steps A1 to A5 shown in FIG. 7 and steps B1 to B10 shown in FIG. By installing and executing this program on a computer, the front system and the replication method in the present embodiment can be realized. In this case, a CPU (Central Processing Unit) of the computer functions as the update log saving unit 5 and the update log transmission unit 7 and performs processing.

  Here, a computer that realizes the front system 100 by executing the program according to the present embodiment will be described with reference to FIG. FIG. 18 is a block diagram illustrating an example of a computer that implements the front system (business processing system) according to the embodiment of the present invention.

  As shown in FIG. 18, the computer 110 includes a CPU 111, a main memory 112, a storage device 113, an input interface 114, a display controller 115, a data reader / writer 116, and a communication interface 117. These units are connected to each other via a bus 121 so that data communication is possible.

  The CPU 111 performs various calculations by developing the program (code) in the present embodiment stored in the storage device 113 in the main memory 112 and executing them in a predetermined order. The main memory 112 is typically a volatile storage device such as a DRAM (Dynamic Random Access Memory). Further, the program in the present embodiment is provided in a state of being stored in a computer-readable recording medium 120. Note that the program in the present embodiment may be distributed on the Internet connected via the communication interface 117.

  Specific examples of the storage device 113 include a hard disk drive and a semiconductor storage device such as a flash memory. The input interface 114 mediates data transmission between the CPU 111 and an input device 118 such as a keyboard and a mouse. The display controller 115 is connected to the display device 119 and controls display on the display device 119.

  The data reader / writer 116 mediates data transmission between the CPU 111 and the recording medium 120, and reads a program from the recording medium 120 and writes a processing result in the computer 110 to the recording medium 120. The communication interface 117 mediates data transmission between the CPU 111 and another computer.

  Specific examples of the recording medium 120 include general-purpose semiconductor storage devices such as CF (Compact Flash (registered trademark)) and SD (Secure Digital), magnetic storage media such as a flexible disk, or CD- An optical storage medium such as ROM (Compact Disk Read Only Memory) can be used.

  Part or all of the above-described embodiments can be expressed by (Appendix 1) to (Appendix 14) described below, but is not limited to the following description.

(Appendix 1)
A business processing system for executing business processing; and a backup system for backing up the business processing system;
The business processing system includes:
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
A replication system characterized by comprising:

(Appendix 2)
The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The replication system according to appendix 1.

(Appendix 3)
The backup system is
A third storage device for storing backup data of the data to be updated and the update log transmitted by the update log transmission unit;
A fourth storage device for storing the update log file transmitted by the update log saving unit;
When the update log file is not stored in the fourth storage device, the backup data is updated based on the update log stored in the third storage device, and the fourth storage device An update log reflection unit that updates the backup data based on the update log file when the update log file is stored in
The replication system according to appendix 1 or 2, comprising:

(Appendix 4)
A serial number is assigned to the update log in the order in which it occurs, and the first storage device, together with the update log, transmits the serial number of the update log that has been transmitted to the backup system and the transmission to the backup system. Stores serial number information that identifies serial numbers of update logs that have not been completed,
The update log transmission unit identifies an update log that has not been transmitted to the backup system based on the serial number information, transmits the identified update log to the backup system,
The update log saving unit identifies an update log that has not been transmitted to the backup system based on the serial number information when a set condition is satisfied, and uses the identified update log to identify the update log. Create a file,
The replication system according to any one of appendices 1 to 3.

(Appendix 5)
A business processing system that performs replication in conjunction with a backup system,
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
A business processing system characterized by comprising:

(Appendix 6)
The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The business processing system according to attachment 5.

(Appendix 7)
A serial number is assigned to the update log in the order in which it occurs, and the first storage device, together with the update log, transmits the serial number of the update log that has been transmitted to the backup system and the transmission to the backup system. Stores serial number information that identifies serial numbers of update logs that have not been completed,
The update log transmission unit identifies an update log that has not been transmitted to the backup system based on the serial number information, transmits the identified update log to the backup system,
The update log saving unit identifies an update log that has not been transmitted to the backup system based on the serial number information when a set condition is satisfied, and uses the identified update log to identify the update log. Create a file,
The business processing system according to appendix 5 or 6.

(Appendix 8)
A replication method using a business processing system for executing business processing and a backup system for backing up the business processing system,
(A) in the business processing system, storing data to be updated and an update log of the data in a first storage device;
(B) in the business processing system, sending an update log stored in the first storage device to the backup system;
(C) In the business processing system, when a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
A replication method characterized by comprising:

(Appendix 9)
The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The replication method according to appendix 8.

(Appendix 10)
(D) in the backup system, storing backup data of the data to be updated and the update log transmitted by the update log transmission unit in a third storage device;
(E) in the backup system, storing the update log file transmitted in the step (b) in a fourth storage device;
(F) updating the backup data based on the update log stored in the third storage device when the update log file is not stored in the fourth storage device;
(E) updating the backup data based on the update log file when the update log file is stored in the fourth storage device;
The replication method according to appendix 8 or 9, further comprising:

(Appendix 11)
Serial numbers are assigned to the update logs in the order in which they occurred, and in the step (a), the first storage device, together with the update logs, is the serial number of the update log that has been transmitted to the backup system. And serial number information that identifies the serial number of the update log that has not been transmitted to the backup system,
In the step (b), based on the serial number information, an update log that has not been transmitted to the backup system is identified, and the identified update log is transmitted to the backup system,
In the step (c), when a set condition is satisfied, an update log that has not been transmitted to the backup system is identified based on the serial number information, and the update log is identified using the identified update log. Create log files,
The replication method according to any one of appendices 8 to 10.

(Appendix 12)
A program that allows a computer to perform replication by linking with a backup system,
In the computer,
(A) storing data to be updated and an update log of the data in a first storage device included in the computer;
(B) transmitting an update log stored in the first storage device to the backup system;
(C) When a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is provided in the computer; and Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
A program that executes

(Appendix 13)
The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The program according to attachment 12.

(Appendix 14)
Serial numbers are assigned to the update logs in the order in which they occurred, and in the step (a), the first storage device, together with the update logs, is the serial number of the update log that has been transmitted to the backup system. And serial number information that identifies the serial number of the update log that has not been transmitted to the backup system,
In the step (b), based on the serial number information, an update log that has not been transmitted to the backup system is identified, and the identified update log is transmitted to the backup system,
In the step (c), when a set condition is satisfied, an update log that has not been transmitted to the backup system is identified based on the serial number information, and the update log is identified using the identified update log. Create log files,
The program according to appendix 12 or 13.

  As described above, according to the present invention, high-speed transfer of update logs can be realized, and replication can be reliably executed even when the update logs are steeply accumulated due to a failure or the like. The present invention is effective for various systems that require replication.

DESCRIPTION OF SYMBOLS 1 Application program 2 User table 3 Update log storage process part 4 Update log storage table 5 Update log saving part 6 Serial number table 7 Update log transmission part 8 Setting part 9 Stay threshold 10 Number of lots 11 Update log file 13 Update log reception part 14 Update Log storage table 15 Sequence number table 16 Update log reflection unit 17 User table 19 Start sequence number 20 End sequence number 30a Memory DB (front system)
30b Memory DB (backup system)
40a Disk unit (front system)
40b Disk unit (backup system)
100 Front system 110 Computer 111 CPU
112 Main Memory 113 Storage Device 114 Input Interface 115 Display Controller 116 Data Reader / Writer 117 Communication Interface 118 Input Device 119 Display Device 120 Recording Medium 121 Bus 200 Backup System 300 Replication System

Claims (9)

A business processing system for executing business processing; and a backup system for backing up the business processing system;
The business processing system includes:
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
A replication system characterized by comprising: The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The replication system according to claim 1. The backup system is
A third storage device for storing backup data of the data to be updated and the update log transmitted by the update log transmission unit;
A fourth storage device for storing the update log file transmitted by the update log saving unit;
When the update log file is not stored in the fourth storage device, the backup data is updated based on the update log stored in the third storage device, and the fourth storage device An update log reflection unit that updates the backup data based on the update log file when the update log file is stored in
The replication system according to claim 1, further comprising: A serial number is assigned to the update log in the order in which it occurs, and the first storage device, together with the update log, transmits the serial number of the update log that has been transmitted to the backup system and the transmission to the backup system. Stores serial number information that identifies serial numbers of update logs that have not been completed,
The update log transmission unit identifies an update log that has not been transmitted to the backup system based on the serial number information, transmits the identified update log to the backup system,
The update log saving unit identifies an update log that has not been transmitted to the backup system based on the serial number information when a set condition is satisfied, and uses the identified update log to identify the update log. Create a file,
The replication system according to claim 1. A business processing system that performs replication in conjunction with a backup system,
A first storage device for storing data to be updated and an update log of the data;
A second storage device having a lower storage speed and a higher storage capacity than the first storage device;
An update log transmission unit for transmitting an update log stored in the first storage device to the backup system;
After setting conditions are satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is temporarily stored in the second storage device An update log saving unit for transmitting the stored update log file to the backup system;
A business processing system characterized by comprising: The setting condition is that the number of update logs that have not been transmitted to the backup system exceeds a threshold.
The business processing system according to claim 5. A serial number is assigned to the update log in the order in which it occurs, and the first storage device, together with the update log, transmits the serial number of the update log that has been transmitted to the backup system and the transmission to the backup system. Stores serial number information that identifies serial numbers of update logs that have not been completed,
The update log transmission unit identifies an update log that has not been transmitted to the backup system based on the serial number information, transmits the identified update log to the backup system,
The update log saving unit identifies an update log that has not been transmitted to the backup system based on the serial number information when a set condition is satisfied, and uses the identified update log to identify the update log. Create a file,
The business processing system according to claim 5 or 6. A replication method using a business processing system for executing business processing and a backup system for backing up the business processing system,
(A) in the business processing system, storing data to be updated and an update log of the data in a first storage device;
(B) in the business processing system, sending an update log stored in the first storage device to the backup system;
(C) In the business processing system, when a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
A replication method characterized by comprising: A program that allows a computer to perform replication by linking with a backup system,
In the computer,
(A) storing data to be updated and an update log of the data in a first storage device included in the computer;
(B) transmitting an update log stored in the first storage device to the backup system;
(C) When a set condition is satisfied, an update log file including a plurality of update logs stored in the first storage device is created, and the created update log file is provided in the computer; and Transmitting the stored update log file to the backup system after temporarily storing it in the second storage device having a lower storage speed and a higher storage capacity than the first storage device;
A program that executes

Images