Data recovery in a cross domain environment

• US 8,533,523 B2
• Filed: 10/27/2010
• Issued: 09/10/2013
• Est. Priority Date: 10/27/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Tylutki, Marcus A.
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): KUDIRKA, JOSEPH R
• Application Number:
  US12/913,228
• Publication Number:
  US 20120110369A1
• Time in Patent Office: 1,049 Days
• Field of Search: 714/2, 714/3, 714/20, 714/4.1, 707/999.202
• US Class Current: 714/2
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40

Abstract

A method for recovering data when corrupted data from a source is detected includes identifying data corrupted as a result of using the corrupted data by tracing propagation of the corrupted data to provide identified corrupted data, and repairing the identified corrupted data to provide repaired data. The propagation of the corrupted data is traced from one domain to another. Data in both domains is repaired. A wrapper is provided for the source. Calls into and out of the source are intercepted by the wrapper. Calls of a plurality of different domains are intercepted by the wrapper. A wrapper is provided for a process. External service calls of the process are intercepted by the wrapper. The wrapper recreates a process flow followed by the process in accordance with the corrupted data. A wrapper is provided for a database. Accesses of the database are intercepted by the wrapper.

Claims

1. A computer-implemented method for recovering data when corrupted data from a source is detected, comprising:

tracing propagation of the corrupted data to provide identified corrupted data;

determining good data and a timestamp both corresponding to the corrupted data, wherein the good data and the timestamp are utilized to compile a list of accesses of the corrupted data; and

repairing the identified corrupted data in accordance with the list of accesses.

2. The method of claim 1, further comprising tracing the propagation of the corrupted data from a first domain to a second domain.

3. The method of claim 2, further comprising repairing the corrupted data in both the first domain and the second domain.

4. The method of claim 1, further comprising providing a wrapper for the source.

5. The method of claim 4, further comprising intercepting calls into and out of the source by the wrapper.

6. The method of claim 5, further comprising intercepting calls of a plurality of different domains by the wrapper.

7. The method of claim 4, further comprising providing the wrapper for a process.

8. The method of claim 7, further comprising intercepting external service calls of the process by the wrapper.

9. The method of claim 8, further comprising the wrapper recreating a process flow followed by the process in accordance with the corrupted data.

10. The method of claim 4, further comprising providing the wrapper for a database.

11. The method of claim 10, further comprising intercepting accesses of the database by the wrapper.

12. The method of claim 11, further comprising intercepting the accesses of the database in accordance with a time window defined by a bad write to the database and a good write to the database.

13. The method of claim 1, further comprising determining corrected data in accordance with the good data and the timestamp.

14. The method of claim 13, further comprising repairing corrupted data in accordance with the corrected data.

15. The method of claim 1, further comprising trimming the list in accordance with a good write.

16. The method of claim 1, further comprising marking the corrupted data as tainted.

17. The method of claim 16, further comprising marking the corrupted data as untainted after it is repaired.