Method and apparatus for aligning a restored parent environment to its child environments with minimal data loss

• US 5,274,803 A
• Filed: 04/26/1991
• Issued: 12/28/1993
• Est. Priority Date: 04/26/1991
• Status: Expired due to Term

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Stevens, Peter H., Dubin, Bennett S.
• Primary Examiner(s): Heckler, Thomas M.
• Application Number:
  US07/692,144
• Time in Patent Office: 977 Days
• Field of Search: 364/DIG. 1 MS File, 364/, 395/600, 395/650
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A method and apparatus for aligning a restored parent environment to its child environments with minimal data loss is disclosed. The method and apparatus achieve the alignment by re-executing the transactions affecting the objects in the child environments and the revisions of the objects in the parent environment in their order of execution, thereby, allowing the restored parent to further recover loss data from its child environments. The transactions are enhanced to facilitate collection of information regarding the transactions during normal operation, and to adjust their actions during their re-execution based on the information collected. As a result of further data recovery by the restored parent environment, alignment may be achieved with substantially less data loss.

Claims

1. In a network of computer systems comprising a parent environment and a plurality of child environments, wherein said parent and child environments logically comprise a plurality of objects, a method for aligning said parent environment to said child environments with minimal data loss after restoring said parent environment, said method comprising the steps of:

logging all transactions affecting revisions of objects in said parent environment and their corresponding objects in said child environments when said transactions are executed;

identifying said transactions logged between a first time t₀ and a second time t₁ where t₁ is greater than t₀, said parent environment being damaged at said second time t₁ and restored to its last back up time which is said first time t₀ ;

sorting said identified transactions into a chronological order in accordance to their time of execution; and

performing repair action for each of said sorted transactions in said chronological order.

2. The method as set forth in claim 1, wherein said transactions, logging, identifying and sorting, are performed by means logically organized as methods of a first class defining a root environment, which is a super class to a second class defining said parent environment, which in turn is a super class to a third and fourth classes defining a first and a second child environment.

3. The method as set forth in claim 1, wherein said transactions are logged in command log files of said child environments.

4. The method as set forth in claim 3, wherein said command log files are logically organized as class instance variables of classes defining said child environments.

5. The method as set forth in claim 1, wherein if a transaction is reconciling a revision of an object in said parent environment to one of its corresponding objects in one of said child environments, said corresponding object affected by said reconciling transaction is repaired by reexecuting said reconcile transaction with said corresponding object, said re-executed reconcile transaction handling said corresponding object in accordance to a plurality of timing parameters extracted for said revision and said corresponding object.

6. The method as set forth in claim 5, wherein said reconcile transaction being re-executed extracts a third and fourth time, t₃ and t₄, from a directory structure and a transaction database in said child environment of said corresponding object, and a fifth time t₅ from a revision database in said parent environment, said corresponding object being last modified in said re-reconciling child environment at said third time t₃, said corresponding object being last involved in a transaction between said re-reconciling child environment and said parent environment at said third time t₄, and said corresponding object being last revised in said parent environment at said fifth time t₅.

7. The method as set forth in claim 6, wherein,

said directory is logically organized as a class directory of a first class defining said child environment of said corresponding object;

said transaction database is logically organized as a first class instance variable of said first class defining said child environment of said corresponding object; and

said revision database is logically organized as a second class instance variable of a second class defining said parent environment, which is a super class to said first class defining said child environment of said corresponding object.

8. The method as set forth in claim 6, wherein if said time t₃ equals said time t₄ and equals a non-zero value, and said time t₅ equals a value zero, said reconcile transaction being reexecuted resets said corresponding object in said child environment of said corresponding object, and updates said parent environment handling said corresponding object as a normal new object being reconciled to in said re-reconciling child environment.

9. The method as set forth in claim 6, wherein if said time t₃ equals said time t₄ and equals a non-zero value, and said time t₅ equals a lesser non-zero value, said reconcile transaction being reexecuted outputs a flag indicating a conflict, and requires said conflict to be resolved before it updates said parent environment handling said corresponding object as a normal old object being reconciled to in said re-reconciling child environment.

10. The method as set forth in claim 6, wherein if said time t₃ equals a non-zero value, and said time t₄ and time t₅ equal a value zero, said reconcile transaction being reexecuted updates said parent environment handling said corresponding object as a normal new object being reconciled to in said re-reconciling child environment.

11. The method as set forth in claim 6, wherein if said time t₃ equals a non-zero value, and said time t₄ equals time t₅ and equal a smaller non-zero value, said reconcile transaction being reexecuted updates said parent environment handling said corresponding object as a normal old object being reconciled to in said re-reconciling child environment.

12. The method as set forth in claim 6, wherein if said time t₃ equals said time t₄ and time t₅, and equals a non-zero value, said reconcile transaction being reexecuted takes no action.

13. The method as set forth in claim 1, wherein if a transaction is resynchronizing an object in one of said child environments to its corresponding revision object in said parent environment, said corresponding revision object affected by said resynchronizing transaction is repaired by reexecuting said resynchronizing transaction, said re-executed resynchronizing transaction handling said corresponding revision object as a normal object being resynchronized from said re-resynchronizing child environment.

14. The method as set forth in claim 1, wherein if a transaction is acquiring a revision of an object from said parent environment into one of said child environments, said acquired object affected by said acquiring transaction is repaired by re-executing said acquiring transaction, said re-executed acquiring transaction handling said revision being reacquired as a normal revision being acquired from said parent environment.

15. The method as set forth in claim 14, wherein if a transaction is acquiring a revision of an object from said parent environment into one of said child environments when said child environment was being created, said acquired object affected by said acquiring transaction is repaired by reexecuting said acquiring transaction after said aquiring child environment is deleted.

16. In a network of computer systems comprising a parent environment and a plurality of child environments, wherein said parent and child environments logically comprise a plurality of objects, an apparatus for aligning said parent environment to said child environments with minimal data loss after restoring said parent environment, comprising:

transaction means for acquiring a revision of an object from said parent environment into one of said child environments, resynchronizing an object in one of said child environments to a corresponding revision of said object in said parent environment, reconciling a revision of an object in said parent environment to one of its corresponding objects in one of said child environments, said transaction means being invoked by users of said child environments and capable of being re-executed in accordance to their original order of execution for aligning said parent and child environments;

logging means for logging said transactions when said transactions are executed, said logging means being invoked by said transactions;

identifying means for identifying said transactions occurred between a first time t₀ and second time t₁ where t₁ is greater than t₀, said parent environment being damaged at said second time t₁ and restored to its last backed up time which is said first time t₀, said identifying means being invoked by a user of said parent environment; and

sorting means for sorting said identified transactions into a chronological order in accordance to their time of execution, said sorting means being invoked by said identifying means.

17. The apparatus as set forth in claim 16, wherein said transaction means, said logging means, said identifying means, and said sorting means are logically organized as methods of a first class defining a root environment, which is a super class to a second class defining said parent environment, which in turn is a super class to a third and fourth classes defining a first and second child environments.

18. The apparatus as set forth in claim 16, wherein said transactions are logged in command log files of said child environments.

19. The apparatus as set forth in claim 18, wherein said command log files are logically organized as class instance variables of classes defining said child environments.

20. The apparatus as set forth in claim 16, wherein when a reconcile transaction is re-executed to align said parent environment to said child environments, said re-executed reconcile transaction handles said corresponding object being in accordance to a plurality of timing parameters extracted for said revision and said corresponding object.

21. The apparatus as set forth in claim 20, wherein said reconcile transaction being re-executed extracts a third and fourth time, t₃ and t₄, from a directory structure and a transaction time database in said child environment of said corresponding object, and a fifth time t₅ from a revision database in said parent environment, said corresponding object being last modified in said re-reconciling child environment at said third time t₃, said corresponding object being last involved in an transaction between said re-reconciling child environment and said parent environment at said third time t₄, and said corresponding object being last revised in said parent environment at said fifth time t₅.

22. The apparatus as set forth in claim 21, wherein,

said directory is logically organized as a class directory of a first class defining said child environment of said corresponding object;

said transaction database is logically organized as a first class instance variable of said first class defining said child environment of said corresponding object; and

said revision database is logically organized as a second class instance variable of a second class defining said parent environment, which is a super class to said first class defining said child environment of said corresponding object.

23. The apparatus as set forth in claim 21, wherein if said time t₃ equals said time t₄ and equals a non-zero value, and said time t₅ equals a value zero, said reconcile transaction being reexecuted resets said corresponding object in said child environment of said corresponding object, and updates said parent environment handling said corresponding object as a normal new object being reconciled to in said re-reconciling child environment.

24. The apparatus as set forth in claim 21, wherein if said time t₃ equals said time t₄ and equals a non-zero value, and said time t₅ equals a lesser non-zero value, said reconcile transaction being reexecuted outputs a flag indicating a conflict, and requires said conflict to be resolved before it updates said parent environment handling said corresponding object as a normal old object being reconciled to in said re-reconciling child environment.

25. The apparatus as set forth in claim 21, wherein if said time t₃ equals a non-zero value, and said time t₄ and time t₅ equal a value zero, said reconcile transaction being reexecuted updates said parent environment handling said corresponding object as a normal new object being reconciled to in said re-reconciling child environment.

26. The apparatus as set forth in claim 21, wherein if said time t₃ equals a non-zero value, and said time t₄ equals time t₅ which equals a smaller non-zero value, said reconcile transaction being reexecuted updates said parent environment handling said corresponding object as a normal old object being reconciled to in said re-reconciling child environment.

27. The apparatus as set forth in claim 21, wherein if said time t₃ equals said time t₄ and time t₅, and equals a non-zero value, said reconcile transaction being reexecuted takes no action.

28. The apparatus as set forth in claim 16, wherein when a resynchronizing transaction is re-executed for aligning said parent environment to said child environments, said reexecuted resynchronizing transaction handles said object being re-resynchronized as a normal object being resynchronized in said re-resynchronizing child environment.

29. The apparatus as set forth in claim 16, wherein when an acquiring transaction is re-executed for aligning said parent environment to said child environments, said reexecuted acquiring transaction handles said revision being re-acquired as a normal revision being acquired from said parent environment.

30. The apparatus as set forth in claim 29, wherein if said acquiring transaction was executed when said child environment was being created, said acquiring transaction is re-executed after said acquiring child environment is deleted.