Method and system for caching remote files locally

• US 20060117018A1
• Filed: 11/30/2004
• Published: 06/01/2006
• Est. Priority Date: 11/30/2004
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Thind, Ravinder S., Christiansen, Neal R., Eller, Alexis J.
• Application Number:
  US10/999,380
• Publication Number:
  US 20060117018A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files

Abstract

A method and system for caching remote objects locally. A request to access an object is received. A determination is made as to whether the object is cached. If the object is cached and the request is not to create a new object, modify an existing object, or open a directory, the request is directed to a local file system. Otherwise, the request is directed to a remote file system. Information about which objects are requested may be used to copy objects stored remotely to a local server as specified by a caching policy.

Claims

1. A computer-readable medium having computer-executable instructions, comprising:

receiving a request to access an object that is stored on a remote server;

examining the request by a filter to determine whether to forward the request to the remote server or to redirect the request to a local file system, wherein the filter has an opportunity to monitor requests to the remote server; and

if the object is cached, redirecting the request to the local file system.

2. The computer-readable medium of claim 1, further comprising if the request to access the object comprises a request to create the object, forwarding the request to the remote server.

3. The computer-readable medium of claim 1, further comprising if the request to access the object comprises a request to modify the object, forwarding the request to the remote server.

4. The computer-readable medium of claim 1, further comprising if the object comprises a directory, forwarding the request to the remote server.

5. The computer-readable medium of claim 1, further comprising notifying a caching service that the object was requested and was not contained on the local file system.

6. The computer-readable medium of claim 5, further comprising obtaining the object from the remote server and storing it on the local file system.

7. The computer-readable medium of claim 1, further comprising notifying a caching service that the object was requested and was contained on the local file system.

8. The computer-readable medium of claim 7, further comprising keeping the object in the local file system based on a frequency with which the object is requested.

9. The computer-readable medium of claim 1, wherein the filter executes in kernel-mode.

10. The computer-readable medium of claim 1, further comprising opening and closing the object and directing input/output operations that affect the object between opening and closing the object without examination of the input/output operations by the filter.

11. The computer-readable medium of claim 1, further comprising receiving a notification that the object has changed and deleting a cached copy of the object on the local file system.

12. The computer-readable medium of claim 11, wherein the filter receives the notification and deletes the cached copy of the object.

13. In a computing environment, a method, comprising:

receiving a request to access an object that is associated with a reparse point, wherein the reparse point includes names of a local directory and a remote directory;

determining whether the object is cached in the local directory;

if the object is cached in the local directory, providing access to the object via the local directory.

14. The method of claim 13, wherein the local directory is stored in a local file system and wherein the remote directory is stored on a remote file system.

15. The method of claim 14, wherein the reparse point is persisted on the local file system.

16. The method of claim 14, wherein the local file system returns the reparse point when an attempt to access the object is received by the local file system.

17. The method of claim 16, wherein determining whether the object is cached in the local directory comprises examining, by a filter, the reparse point that the local file system returns.

18. The method of claim 17, wherein determining whether the object is cached in the local directory further comprises the filter obtaining the local directory from the reparse point and attempting to open the object in the local directory.

19. The method of claim 18, further comprising redirecting the request to the local directory if attempting to open the object in the local directory succeeds.

20. The method of claim 18, further comprising redirecting the request to the remote file system if attempting to open the object in the local directory fails.

21. The method of claim 17, wherein the filter has an opportunity of examining any request from user-mode processes to access an object on the local file system.

22. The method of claim 13, further comprising if the object is not cached in the local directory, obtaining the object from the remote directory and caching it in the local directory.

23. The method of claim 13, further comprising if the request to access an object is a request to create the object, redirecting the request to the remote directory.

24. The method of claim 13, further comprising if the request to access an object is a request to change the object, redirecting the request to the remote directory.

25. The method of claim 13, further comprising if the object is a directory, redirecting the request to the remote directory.

26. The method of claim 13, wherein the object has a name that identifies the object to a file system, wherein the reparse point is associated with a directory that has a name that identifies the directory to the file system, and wherein the object is associated with a reparse point if a prefix of the name of the object includes the name of the directory.

27. An apparatus for caching, comprising:

a local file system arranged to store objects;

a component arranged to determine which objects to store on the local file system; and

a filter arranged to monitor input and output and to report to the component names of objects for which access is sought.

28. The apparatus of claim 27, wherein the objects comprise directories and files.

29. The apparatus of claim 27, wherein the filter has an opportunity to examine any communication to or from the local file system.

30. The apparatus of claim 27, wherein the filter has an opportunity to examine any communication to or from a remote file system.

31. The apparatus of claim 30, wherein the filter is arranged to register to be notified of any communication to or from the remote file system that involves a create operation.

32. The apparatus of claim 31, wherein the create operation comprises an operation to open an already-existing object.

33. The apparatus of claim 31, wherein the create operation comprises an operation to create a new object.

34. The apparatus of claim 27, wherein the filter is arranged to perform actions, comprising:

receiving a request to access an object that is stored on a remote server; and

determining whether to forward the request to the remote server or to redirect the request to the local file system.

35. The apparatus of claim 34, wherein the filter is further arranged to forward the request to the remote server if the request comprises a request to create a new object, change an existing object, or open a directory.

36. The apparatus of claim 34, wherein the filter is further arranged to forward the request to the local file system if the object is cached on the local file system.

37. The apparatus of claim 27, wherein the component applies a policy to the objects reported by the filter to determine which objects to store on the local file system.