Method for logically consistent backup of open computer files

• US 20060123210A1
• Filed: 12/06/2004
• Published: 06/08/2006
• Est. Priority Date: 12/06/2004
• Status: Abandoned Application

• Current Assignee: St Bernard Software Incorporated (GoSecure, Inc.)
• Original Assignee: St Bernard Software Incorporated (GoSecure, Inc.)
• Inventors: Pritchett, Gary, Wong, Terence Ping, Piotrowski, Anatol, Neill, Christopher J., Razavipour, Reza, Burdette, David C.
• Application Number:
  US11/006,410
• Publication Number:
  US 20060123210A1
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1466 to make the backup process non-disruptive

Abstract

A method for providing logically-consistent computer file backups in an operating environment whose file backup provisions rely on application programs recognizing a freeze writes command but where the operating system also hosts programs that do not recognize such a command. The method intercepts a system level command issued during the backup process that signals the file system manager to flush write operations cached in memory and hold any subsequent write operations. (“Flush and Hold Writes”). File write operations are then monitored to find a quiescent period, which signals that all current file transactions are complete. Application level write operations are halted, preventing any further file transactions. The Flush and Hold Writes Command is then allowed to pass to the file system and volume manager so that these operation system components can flush to permanent storage any write operations that are cached in memory and hold any new write operations.

Claims

1. A method of creating back-up data files in a computer operating system comprising:

observing operating system commands to detect issuance of a command to flush and hold write operations;

intercepting said command to flush and hold write operations;

observing data storage write operations to detect a period of inactivity of said data storage write operations;

determining that said period of inactivity indicates that all stored data to be backed up is logically consistent; and

releasing said flush and hold write operations command to said operating system.

2. The method of claim 1, wherein said releasing follows said determining and further comprising:

blocking application write operations after said determining and before said releasing; and

unblocking said application write operations after said releasing.

3. The method of claim 2, further comprising:

creating a temporary snapshot of said stored data if said period of inactivity occurs within a set time limit; and

permanently storing said snapshot.

4. The method of claim 3 further comprising providing a snapshot provider application program that creates said temporary snapshot.

5. The method of claim 2 further comprising setting a minimum threshold for said period of inactivity to be detected, said minimum threshold having a value within a range of 2 to 5 seconds.

6. The method of claim 3 wherein, after said releasing, said operating system waits for said flush and hold write operations to complete before said creating a temporary snapshot.

7. The method of claim 3 further comprising determining whether said period of inactivity occurs within said set time limit, and, if said period of inactivity does not occur within said set time limit, no snapshot is created.

8. The method of claim 7 wherein said set time limit is within a range of 25 to 35 seconds.

9. A method of creating back-up data files in a computer operating system comprising:

initiating a data backup process;

signaling application programs that accept a freeze writes command to complete all current data storage write operations and halt all future data storage write operations;

issuing a flush and hold write operations command;

intercepting said flush and hold write operations command;

observing data storage write operations to detect a period of inactivity of said data storage write operations;

determining that said period of inactivity indicates that all stored data to be backed up is logically consistent;

blocking application write operations;

releasing said flush and hold write operations command to said operating system;

unblocking said application write operations after execution of said flush and hold write operations command; and

,

signaling application programs that accept said freeze writes command to resume normal data storage write operations.

10. The method of claim 9 further comprising setting a minimum threshold for said period of inactivity to be detected, said minimum threshold having a value within a range of 2 to 5 seconds.

11. The method of claim 9, further comprising:

creating a temporary snapshot of said stored data if said period of inactivity occurs within a set time limit; and

,

permanently storing said snapshot.

12. The method of claim 11 further comprising providing a snapshot provider application program that creates said temporary snapshot.

13. The method of claim 11 wherein, after said releasing, said operating system waits for said flush and hold write operations to complete before said creating a temporary snapshot.

14. The method of claim 11 further comprising determining whether said period of inactivity occurs within said set time limit, and if said period of inactivity does not occur within said set time limit, no snapshot is created.

15. The method of claim 14 wherein said set time limit is within a range of 25 to 35 seconds.

16. A computer program product with encoded instructions for performing operations comprising:

observing operating system commands to detect issuance of a command to flush and hold write operations;

intercepting said command to flush and hold write operations;

observing data storage write operations to detect a period of inactivity of said data storage write operations;

determining that said period of inactivity indicates that all stored data to be backed up is logically consistent; and

releasing said flush and hold write command to said operating system.

17. The computer program product of claim 16, further comprising encoded instructions for:

blocking application write operations after said determining and before said releasing; and

unblocking said application write operations after said releasing.

18. The computer program product of claim 17, further comprising encoded instructions for performing operations:

creating a temporary snapshot of said stored data if said period of inactivity occurs within a set time limit; and

permanently storing said snapshot.

19. The computer program product of claim 17 wherein said encoded instructions include a minimum threshold for said period of inactivity to be detected, said minimum threshold having a value within a range of 2 to 5 seconds.

20. The computer program product of claim 18, further comprising encoded instructions for waiting for said flush and hold write operations to complete before creating said temporary snapshot.

21. The computer program product of claim 18, further comprising encoded instructions for determining whether said period of inactivity occurs within said time limit, and if said period of inactivity does not occur within said time limit, for no snapshot being created.

22. The computer program product of claim 21 wherein said set time limit is within a range of 25 to 35 seconds.

23. The computer program product of claim 17, further comprising encoded instructions for performing operations:

signaling applications programs that accept a freeze writes command to complete all current write operations and halt all future write operations prior to said observing operating system commands to detect issuance of a command to flush and hold write operations;

signaling said application programs that accept a freeze writes command to resume normal operations after said releasing said flush and hold write operations command.