METHOD AND SYSTEM FOR IMPLEMENTING BUSINESS LOGIC

• US 20120173490A1
• Filed: 12/30/2010
• Published: 07/05/2012
• Est. Priority Date: 12/30/2010
• Status: Abandoned Application

• Current Assignee: VeriSign, Inc.
• Original Assignee: VeriSign, Inc.
• Inventors: Gould, James Fred, Griffiths, Hui Xu
• Application Number:
  US12/982,041
• Publication Number:
  US 20120173490A1
• Time in Patent Office: Days
• US Class Current: 707/648
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence

Abstract

A method of recovering a database includes providing a computer having a processor and providing a backup database including a last change marker. The method also includes extracting, using the processor, the last change marker from the backup database and providing transaction logs. Each transaction of the transaction logs includes input data, processed data, and a change marker. The method further includes sorting, using the processor, the transactions of the transaction logs using the change markers, replaying, using the processor, one or more of the transactions of the transaction logs, and generating a recovered database.

Claims

1. A method of recovering a database, the method comprising:

providing a computer having a processor;

providing a backup database including a last change marker;

extracting, using the processor, the last change marker from the backup database;

providing transaction logs, wherein each transaction of the transaction logs includes input data, processed data, and a change marker;

sorting, using the processor, the transactions of the transaction logs using the change markers;

replaying, using the processor, one or more of the transactions of the transaction logs; and

generating a recovered database.

2. The method of claim 1 wherein the transactions are associated with operation classes annotated with an indicator associated with recovery.

3. The method of claim 1 wherein providing the backup database comprises recovering the backup database from the last good backup.

4. The method of claim 1 wherein providing transaction logs comprises copying transaction logs from a plurality of application servers.

5. The method of claim 4 wherein the transactions of the transaction logs comprise domain name registration transactions and dates associated with each of the domain name registration transactions.

6. The method of claim 1 further comprising filtering the transactions of the transaction logs to discard transactions having change markers following the last change marker.

7. The method of claim 1 wherein replaying the one or more transactions comprises serially replaying the one or more transactions.

8. A method of forming a transaction log, the method comprising:

providing a computer having a processor;

receiving one or more client inputs including a request;

processing, using the processor, the request using the processor to provide processed data;

merging, using the processor, at least one of the one or more client inputs and the processed data;

determining that the merged one or more client inputs and processed data is to be committed;

creating, using the processor, a transaction log entry using the merged one or more client inputs and processed data;

storing the transaction log entry in the transaction log; and

storing a change marker associated with the transaction log entry in the transaction log.

9. The method of claim 8 wherein the one or more client inputs relate to a domain name registration process.

10. The method of claim 9 wherein receiving the one or more client inputs including a request comprises receiving an EPP request.

11. The method of claim 10 wherein the transaction log entry comprises an expiration date associated with a domain name.

12. The method of claim 8 wherein the processed data is based on a transaction date associated with the request.

13. The method of claim 8 wherein determining that the merged one or more client inputs and processed data is not to be committed comprises detecting an error associated with processing the request.

14. A database recovery system comprising:

an input/output module;

a processor coupled to the input/output module;

a backup database coupled to the processor, wherein the backup database includes a last change marker;

a database of transaction logs, wherein each transaction of the transaction logs includes input data, processed data, and a change marker;

a sorting module coupled to the database of transaction logs and operable to sort the transactions of the transaction logs using the change markers;

a replay module operable replay one or more of the transactions of the transaction logs; and

a recovered database.

15. The system of claim 14 wherein the transactions are associated with operation classes annotated with an indicator associated with recovery.

16. The system of claim 14 wherein the backup database is generated based on a last good backup.

17. The system of claim 14 wherein the transaction logs are copied from a plurality of application servers.

18. The system of claim 17 wherein the transactions of the transaction logs comprise domain name registration transactions and dates associated with each of the domain name registration transactions.

19. The system of claim 14 further comprising a filtering module to filter the transactions of the transaction logs to discard transactions having change markers following the last change marker.

20. The system of claim 14 wherein replaying the one or more transactions comprises serially replaying the one or more transactions.