Method for mirroring a log file by threshold driven synchronization

• US 9,201,746 B2
• Filed: 06/29/2012
• Issued: 12/01/2015
• Est. Priority Date: 03/11/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Fashchik, Ran, Gordon, Eyal, Valentin, Gary
• Primary Examiner(s): Hwa, Shyue Jiunn
• Application Number:
  US13/538,623
• Publication Number:
  US 20120330897A1
• Time in Patent Office: 1,250 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 11/2074 Asynchronous techniques
• CPC Class Codes: G06F 11/2076 Synchronous techniques
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27

Abstract

A method for of accelerating database log hardening using specific per block data protection and damage control is provided. A per write specification is implemented to determine when database log data is mirrored synchronously or asynchronously. Synchronous mirroring is performed upon reaching a predetermined threshold, based on one or more parameters such as transaction value, both individual and cumulative, and the quantity of data written since the last synchronous mirroring. As data is added to the database log, it is written specifying asynchronous mirroring to the primary log file. Once a threshold is met, a write specifying synchronous mirroring is performed to both the primary and secondary log files, thereby hardening the log file in both primary and secondary storage subsystem.

Claims

1. A method of mirroring log data from a primary storage subsystem to a secondary storage subsystem, the method comprising:

initiating a transaction in response to receiving a write instruction;

determining a value of the transaction;

adding the value of the transaction to a cumulative value of transaction values since a most recent synchronous mirroring;

performing an asynchronous mirroring of the log data when the cumulative value does not exceed a damage threshold, and

performing a synchronous mirroring of the log data when the cumulative value exceeds the damage threshold, and

wherein the value of the transaction is an indicator of one or more of a monetary value of the transaction and a transaction data quantity.

2. The method according to claim 1, the primary storage subsystem comprising a primary write logic subsystem configured to decode data protection metadata to determine what type of write is to be performed.

3. The method according to claim 1, wherein the cumulative value is an indicator of one or more of a cumulative monetary value of the transaction values and a cumulative transacted data quantity.

4. The method according to claim 1, wherein the damage threshold is an indicator of one or more of an acceptable financial exposure and an acceptable data quantity loss risk.

5. The method according to claim 1, wherein the cumulative value is determined by incrementing a counter according to the value of the transaction, and wherein incrementing the counter comprises:

receiving the log data; and

updating the counter with information derived from the received log data, and wherein the counter is reset after performing the synchronous mirroring.

6. The method according to claim 1, the primary storage subsystem comprising a primary communication subsystem, a primary write logic subsystem, a primary storage controller, and a primary disk subsystem.

7. The method according to claim 1, wherein the write instruction comprises write opcode, a data address, and data protection metadata.

8. The method according to claim 1, wherein the performing the synchronous mirroring comprises updating the secondary storage subsystem with log data received by the primary storage subsystem after a most recent mirroring.

9. A computer program product for mirroring log data from a primary storage subsystem to a secondary storage subsystem, comprising:

a non-transitory computer usable medium having computer usable code embodied therewith, the computer program product comprising;

computer usable code configured for initiating a plurality of transactions of a mirroring operation;

computer usable code configured for determining a value of each transaction;

computer usable code configured for adding the value of each transaction to a cumulative value of transaction values since a most recent synchronous mirroring;

computer usable code configured for asynchronously mirroring of the log data when the cumulative value does not exceed a damage threshold for at least one of the transactions; and

computer usable code configured for synchronously mirroring the log data when the cumulative value exceeds the damage threshold for at least a different one of the transactions,

wherein the value of the transaction is an indicator of one or more of a monetary value of the transaction and a transaction data quantity.

10. The computer program product according to claim 9, wherein the log data is stored in a sequential database log file.

11. The computer program product according to claim 9, further comprising, in response to opening a log file comprising the log data:

initializing a damage counter; and

setting the damage threshold, and

wherein the log data comprises one or more database transactions.

12. The computer program product according to claim 9, wherein the value of the transaction is selected from a group consisting of a monetary value of the transaction and a quantity of data in the transaction.

13. The computer program product according to claim 12, further comprising computer usable code configured to:

receive the log data; and

update one or more of a damage counter and a physical data counter based on information derived from the received log data.

14. The computer program product according to claim 9, further comprising computer usable code configured to:

determine whether there are additional transactions to process in response to executing the computer usable code configured to perform one or more of the asynchronous mirroring and the synchronous mirroring; and

in response to determining there are not additional transactions to process, mirror any non-mirrored data to a secondary log file.

15. The computer program product according to claim 9, wherein the computer usable code configured for synchronously mirroring the log data is configured to update the secondary storage subsystem with log data received by the primary storage subsystem after a most recent synchronous mirroring.

16. A method of mirroring database transaction log data from a primary storage subsystem to a secondary storage subsystem, the method comprising:

receiving database transaction log data from a log hardening module configured to determine whether a write instruction to the primary storage subsystem specifies either asynchronous or synchronous mirroring;

initializing a damage counter in response to receiving the log data from the log hardening module;

initiating several transactions;

upon initiating each transaction, determining a value of the transaction;

upon determining the value of each transaction, updating the damage counter based on the value of the transaction to a cumulative value of the transactions processed after a most recent synchronous mirroring;

performing a synchronous mirroring of the database transaction log data in response to determining that a value of the damage counter for the transaction is greater than a damage threshold; and

performing an asynchronous mirroring of the log data when the cumulative value does not exceed a damage threshold.

17. The method according to claim 16, wherein the log data comprises a plurality of data blocks of a single data track, the method further comprising:

determining a track position of each data block prior to mirroring the data block, and

performing an asynchronous mirroring of each data block for which

the data block is determined not to be the last data block of the data track; and

the data block is not part of a transaction for which the value of the damage counter is greater than the damage threshold, and

wherein the database transaction log data is stored in a sequential file.

18. The method according to claim 16, wherein the value of the transaction is based on a quantity of the database transaction log data, wherein the updating the damage counter comprises:

the receiving the database transaction log data;

determining a quantity of the received database transaction log data; and

updating the damage counter with the quantity of the received database transaction log data.

19. The method according to claim 16, wherein the log hardening module receives the log data from a log update module configured to receive the database transaction log data from a database system.

20. The method according to claim 16, further comprising reinitializing the damage counter in response to determining the value of the damage counter is greater than the damage threshold.

21. A method of mirroring log data from a primary storage subsystem to a secondary storage subsystem, the method comprising:

opening a log file comprising the log data;

setting a physical data threshold in response to opening the log file;

initiating a transaction;

determining whether the physical data threshold is reached;

performing an asynchronous mirroring of the log data in response to determining the physical data threshold is not yet reached; and

performing a synchronous mirroring of the log data in response to determining the physical data threshold is reached; and

initializing a physical data threshold counter in response to opening the log file, the physical data threshold counter indicates a cumulative quantity of data transferred since a most recent synchronous mirroring,

wherein the step of performing the synchronous mirroring comprises the step of updating the secondary storage subsystem with log data received after the most recent synchronous mirroring.

22. The method according to claim 21, wherein the physical data threshold corresponds to a capacity of a single data track, and

wherein the log data is stored in a sequential file.

23. The method according to claim 21, wherein physical data threshold comprises one or more data tracks, each of the tracks comprising a circular segment of a fixed disk comprising a consecutive set of sectors, and

wherein the one or more data tracks are copied during the synchronous mirroring.

24. The method according to claim 23, further comprising:

determining whether there are additional transactions to process in response to performing one or more of the asynchronous mirroring and the synchronous mirroring; and

in response to determining there are not additional transactions to process;

mirroring any non-mirrored data to a secondary log file; and

closing the log file.