Method and system for disaster recovery

• US 6,981,177 B2
• Filed: 03/25/2003
• Issued: 12/27/2005
• Est. Priority Date: 04/19/2002
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Beattie, Andrew M. H.
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): LOHN, JOSHUA A
• Application Number:
  US10/397,511
• Publication Number:
  US 20030200480A1
• Time in Patent Office: 1,008 Days
• Field of Search: 714/6, 714/15, 714/20, 714/16, 707/202, 707/204
• US Class Current: 714/20
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

A method for disaster recovery includes copying at least a portion of information from a first database to a backup system as backup information. The method also includes storing an incremental change in a second database. The incremental change represents a change to at least a portion of the information in the first database. The method further includes restoring the first database using at least one of the backup information and the incremental change.

Claims

1. A method for disaster recovery, comprising:

starting a replication task operable to detect an incremental change in a second database;

accessing a taskfile to identify at least one of a first file to be monitored for incremental changes, a first folder to be monitored for incremental changes, a first registry to be monitored for incremental changes, a second file to be excluded from monitoring, a second folder to be excluded from monitoring, and a second registry to be excluded from monitoring;

communicating at least a portion of the information from the second database for storage in a backup system as backup information after the replication task has started;

communicating a detected incremental change from the replication task for storage in a first database, the incremental change representing a change to at least a portion of information in the second database;

receiving at least one of backup information and the incremental change; and

restoring the second database using at least one of the backup information and the incremental change.

2. The method of claim 1, wherein restoring the second database comprises:

storing the backup information in the second database; and

implementing the incremental change to at least a portion of the information in the second database.

3. The method of claim 1, wherein receiving the incremental change comprises:

receiving a first incremental change from the backup system; and

receiving a second incremental change from the first database.

4. The method of claim 3, wherein restoring the second database comprises:

storing the backup information in the second database;

implementing the first incremental change to at least a portion of the information in the second database; and

implementing the second incremental change to at least a portion of the information in the second database after implementing the first incremental change.

5. The method of claim 3, further comprising receiving a restoration time;

and

wherein restoring the second database comprises;

storing the backup information in the second database;

implementing the first incremental change to at least a portion of the information in the second database when a first time associated with the first incremental change does not exceed the restoration time; and

implementing the second incremental change to at least a portion of the information in the second database when a second time associated with the second incremental change does not exceed the restoration time.

6. The method of claim 1, wherein communicating the incremental change for storage in the first database comprises:

detecting incremental changes in at least one file system;

accumulating a plurality of incremental changes detected during each of a plurality of time windows; and

communicating the accumulated incremental changes for storage in the first database after each time window.

7. A system for disaster recovery, comprising:

at least one computer readable medium; and

logic encoded on the at least one computer readable medium and operable when executed to;

start a replication task operable to detect an incremental change in a second database;

access a taskfile to identify at least one of a first file to be monitored for incremental changes, a first folder to be monitored for incremental changes, a first registry to be monitored for incremental changes, a second file to be excluded from monitoring, a second folder to be excluded from monitoring, and a second registry to be excluded from monitoring;

communicate at least a portion of the information from the second database for storage in a backup system as backup information after the replication task has started;

communicate a detected incremental change from the replication task for storage in a first database, the incremental change representing a change to at least a portion of information in the second database;

receive at least one of backup information and the incremental change; and

restore the second database using at least one of the backup information and the incremental change.

8. The system of claim 7, wherein the logic is operable to restore the second database by:

storing the backup information in the second database; and

implementing the incremental change to at least a portion of the information in the second database.

9. The system of claim 7, wherein the logic is operable to receive the incremental change by:

receiving a first incremental change from the backup system; and

receiving a second incremental change from the first database.

10. The system of claim 9, wherein the logic is operable to restore the second database by:

storing the backup information in the second database;

implementing the first incremental change to at least a portion of the information in the second database; and

implementing the second incremental change to at least a portion of the information in the second database after implementing the first incremental change.

11. The system of claim 9, wherein:

the logic is further operable to receive a restoration time; and

the logic is operable to restore the second database by;

storing the backup information in the second database;

implementing the first incremental change to at least a portion of the information in the second database when a first time associated with the first incremental change does not exceed the restoration time; and

implementing the second incremental change to at least a portion of the information in the second database when a second time associated with the second incremental change does not exceed the restoration time.

12. A system for disaster recovery, comprising:

a first database operable to store information; and

one or more processors collectively operable to;

start a replication task operable to detect an incremental change in the first database;

access a taskfile to identify at least one of a first file to be monitored for incremental changes, a first folder to be monitored for incremental changes, a first registry to be monitored for incremental changes, a second file to be excluded from monitoring, a second folder to be excluded from monitoring, and a second registry to be excluded from monitoring;

communicate at least a portion of the information from the first database for storage in a backup system as backup information after the replication task has started;

communicate a detected incremental change from the replication task for storage in a second database, the incremental change representing a change to at least a portion of information in the first database;

receive at least one of backup information and the incremental change; and

restore the first database using at least one of the backup information and the incremental change.

13. The system of claim 12, wherein the one or more processors are collectively operable to restore the first database by:

storing the backup information in the first database; and

implementing the incremental change to at least a portion of the information in the first database.

14. The system of claim 12, wherein the one or more processors are collectively operable to receive the incremental change by:

receiving a first incremental change from the backup system; and

receiving a second incremental change from the second database.

15. The system of claim 14, wherein the one or more processors are collectively operable to restore the first database by:

storing the backup information in the first database;

implementing the first incremental change to at least a portion of the information in the first database; and

implementing the second incremental change to at least a portion of the information in the first database after implementing the first incremental change.

16. The system of claim 14, wherein:

the one or more processors are further collectively operable to receive a restoration time; and

the one or more processors are collectively operable to restore the first database by;

storing the backup information in the first database;

implementing the first incremental change to at least a portion of the information in the first database when a first time associated with the first incremental change does not exceed the restoration time; and

implementing the second incremental change to at least a portion of the information in the first database when a second time associated with the second incremental change does not exceed the restoration time.

17. The system of claim 12, wherein the one or more processors are further collectively operable to communicate at least a portion of the information from the first database for storage in the backup system as the backup information.

18. A system for disaster recovery, comprising:

a file system monitor operable to;

access a taskfile to identify at least one of a first file to be monitored for incremental changes, a first folder to be monitored for incremental changes, a first registry to be monitored for incremental changes, a second file to be excluded from monitoring, a second folder to be excluded from monitoring, and a second registry to be excluded from monitoring; and

detect a plurality of incremental changes to information in at least one first file system based, at least in part, on the taskfile;

a transaction accumulator operable to receive the plurality of incremental changes and to accumulate the plurality of incremental changes received during a determined time period; and

a service operable to execute a replication task, the replication task operable to receive the accumulated incremental changes and to communicate the accumulated incremental changes for storage in a second file system, wherein the at least one first file system may be restored using at least one of backup information and the incremental change, the backup information comprising at least a portion of the information from the at least one first file system previously stored in a backup system.

19. A system for disaster recovery, comprising:

means for starting a replication task operable to detect an incremental change in a second database;

means for accessing a taskfile to identify at least one of a first file to be monitored for incremental changes, a first folder to be monitored for incremental changes, a first registry to be monitored for incremental changes, a second file to be excluded from monitoring, a second folder to be excluded from monitoring, and a second registry to be excluded from monitoring;

means for communicating at least a portion of the information from the second database for storage in a backup system as backup information after the replication task has started;

means for communicating a detected incremental change from the replication task for storage in a first database, the incremental change representing a change to at least a portion of information in the second database;

means for receiving at least one of backup information and the incremental change; and

means for restoring the second database using at least one of the backup information and the incremental change.

20. A method for disaster recovery, comprising:

receiving an incremental change representing a change to at least a portion of information in a first database, the incremental change consisting of information associated with one of a first file monitored for incremental changes, a first folder monitored for incremental changes, or a first registry monitored for incremental changes;

storing the incremental change in a second database;

communicating the incremental change for use in restoring the first database, the first database restored using at least one of backup information and the incremental change, the backup information comprising at least a portion of the information from the first database previously stored in a backup system;

renaming the second folder from an old name to a new name before communicating at least a portion of the second folder for storage in the backup system, the new name comprising a timestamp; and

creating the first folder, the first folder having the old name of the second folder.

21. The method of claim 20, wherein the incremental change comprises a first incremental change;

and

further comprising;

receiving a second incremental change, the second incremental change consisting of information associated with one of a second file monitored for incremental changes, a second folder monitored for incremental changes, or a second registry monitored for incremental changes;

storing the second incremental change in the second database; and

communicating the second incremental change for storage in the backup system, the backup system operable to communicate the second incremental change for use in restoring the first database.

22. The method of claim 21, wherein:

storing the first incremental change in the second database comprises storing the first incremental change in a first folder; and

communicating the second incremental change for storage in the backup system comprises communicating at least a portion of a second folder containing the second incremental change for storage in the backup system.

23. The method of claim 20, wherein:

the incremental change is associated with a first file located in a first file system folder in the first database, the first file system folder located in a first drive folder, the first file having a file name; and

storing the incremental change in the second database comprises storing the incremental change in a second file located in a second file system folder, the second file system folder associated with the first file system folder, the second file system folder located in a second drive folder associated with the first drive folder, the second file having the file name.

24. The method of claim 23, wherein storing the incremental change in the second file comprises:

determining if the second drive system folder exists;

creating the second drive system folder if it does not exist;

determining if the second file system folder exists;

creating the second file system folder if it does not exist;

determining if the second file exists; and

creating the second file if it does not exist.

25. The method of claim 20, wherein the incremental change is stored in one of a plurality of timestamp folders, one of the timestamp folders representing a current time period, at least one of the remaining timestamp folders representing at least one previous time period.

26. The method of claim 25, further comprising receiving a restoration time;

and

wherein communicating the incremental change for use in restoring the first database comprises;

determining whether a time associated with the timestamp folder in which the incremental change is stored exceeds the restoration time; and

communicating the incremental change for use in restoring the first database when the time associated with the timestamp folder does not exceed the restoration time.

27. The method of claim 20, further comprising:

receiving the backup information; and

storing the backup information in the backup system.

28. A system for disaster recovery, comprising:

at least one computer readable medium; and

logic encoded on the at least one computer readable medium and operable when executed to;

receive a first incremental change representing a change to at least a portion of information in a first database, the first incremental change consisting of information associated with one of a first file monitored for incremental changes, a first folder monitored for incremental changes, or a first registry monitored for incremental changes;

store the first incremental change in a first folder in a second database; and

communicate the incremental change for use in restoring the first database, the first database restored using at least one of backup information and the incremental change, the backup information comprising at least a portion of the information from the first database previously stored in a backup system;

receive a second incremental change, the second incremental change consisting of information associated with one of a second file monitored for incremental changes, a second folder monitored for incremental changes, or a second registry monitored for incremental changes;

store the second incremental change in a second folder in the second database;

rename the second folder from an old name to a new name before communicating at least a portion of the second folder for storage in the backup system, the new name comprising a timestamp;

create the first folder, the first folder having the old name of the second folder; and

communicate the second incremental change for storage in the backup system by communicating at least a portion of the second folder for storage in the backup system, the backup system operable to communicate the second incremental change for use in restoring the first database.

29. The system of claim 28, wherein:

the incremental change is associated with a first file located in a first file system folder in the first database, the first tile system folder located in a first drive folder, the first tile having a file name; and

the logic is operable to store the incremental change by;

determining if a second drive system folder associated with the first drive system folder exists in the second database;

creating the second drive system folder if it does not exist;

determining if a second file system folder associated with the first file system folder exists in the second database;

creating the second file system folder if it does not exist;

determining if a second file having the file name exists;

creating the second tile if it does not exist; and

storing the incremental change in the second file.

30. The system of claim 28, wherein:

the incremental change is stored in one of a plurality of timestamp folders, one of the timestamp folders representing a current time period, at least one of the remaining timestamp folders representing at least one previous time period;

the logic is further operable to receive a restoration time; and

the logic is operable to communicate the incremental change for use in restoring the first database by;

determining whether a time associated with the timestamp folder in which the incremental change is stored exceeds the restoration time; and

communicating the incremental change for use in restoring the first database when the time associated with the timestamp folder does not exceed the restoration time.

31. The system of claim 28, wherein the logic is further operable to:

receive the backup information; and

store the backup information in the backup system.

32. A system for disaster recovery, comprising:

a first database operable to store an incremental change; and

one or more processors collectively operable to;

receive the incremental change, the incremental change representing a change to at least a portion of information in a second database and consisting of information associated with one of a first file monitored for incremental changes, a first folder monitored for incremental changes, or a first registry monitored for incremental changes;

store the incremental change in the first database;

communicate the incremental change for use in restoring the second database, the second database restored using at least one of backup information and the incremental change, the backup information comprising at least a portion of the information from the second database previously stored in a backup system;

receive a second incremental change, the second incremental change consisting of information associated with one of a second file monitored for incremental changes, a second folder monitored for incremental changes, or a second registry monitored for incremental changes;

store the second incremental change in a second folder in the second database;

rename the second folder from an old name to a new name before communicating at least a portion of the second folder for storage in the backup system, the new name comprising a timestamp;

create the first folder, the first folder having the old name of the second folder; and

communicate the second incremental change for storage in the backup system by communicating at least a portion of the second folder for storage in the backup system, the backup system operable to communicate the second incremental change for use in restoring the first database.

33. The system of claim 32, wherein:

the incremental change is associated with a first file located in a first file system folder in the second database, the first file system folder located in a first drive folder, the first file having a tile name; and

the one or more processors are collectively operable to store the incremental change by;

determining if a second drive system folder associated with the first drive system folder exists in the first database;

creating the second drive system folder if it does not exist;

determining if a second file system folder associated with the first file system folder exists in the first database;

creating the second file system folder if it does not exist;

determining if a second file having the file name exists;

creating the second file if it does not exist; and

storing the incremental change in the second file.

34. The system of claim 32, wherein:

the incremental change is stored in one of a plurality of timestamp folders, one of the timestamp folders representing a current time period, at least one of the remaining timestamp folders representing at least one previous time period;

the one or more processors are further collectively operable to receive a restoration time; and

the one or more processors are collectively operable to communicate the incremental change for use in restoring the second database by;

determining whether a time associated with the timestamp folder in which the incremental change is stored exceeds the restoration time; and

communicating the incremental change for use in restoring the second database when the time associated with the timestamp folder does not exceed the restoration time.

35. The system of claim 32, wherein the one or more processors are further collectively operable to:

receive the backup information; and

store the backup information in the backup system.