Remote access agent for caching in a SAN file system

• US 7,685,128 B2
• Filed: 06/10/2004
• Issued: 03/23/2010
• Est. Priority Date: 06/10/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Pereira, Manuel Vasconcellos III, Riegel, Geoffrey Albert, Anderson, Owen Theodore, Gill, Binny Sher, Luan, Leo Shyh-Wei
• Primary Examiner(s): Jalil; Neveen Abel
• Assistant Examiner(s): Pulliam; Christyann R
• Application Number:
  US10/864,605
• Publication Number:
  US 20060004765A1
• Time in Patent Office: 2,112 Days
• Field of Search: None
• US Class Current: 707/770
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

Addressed is a system and method for remote data caching and replication by local copy maintenance of remote data within a SAN file system. Distributed Storage Tank (DST), an extension to a SAN file system, provides for transparent SAN client access of local copies by importing, exporting, and storing data using network file access protocols as well as by providing assurance of metadata and file content validity. A Remote Access Agent (RAA) handles protocol implementation and conversion necessary for communication with remote data sources. Controlled by a consistency policy, consistency is maintained by RAA fetching and updating local copies if modifications have occurred to a file since it was first stored as a local copy in local storage. Additionally, RAA returns metadata pertaining to the requested data. A SAN client obtains metadata corresponding to the requested data and utilizes it to directly access locally stored copies of remote data.

Claims

1. A method implemented in a Remote Access Agent (RAA) to store and access remotely obtained data as a copy local to a Storage Area Network (SAN), wherein said method comprises the steps of:

a. receiving, at said SAN, remote data from a remote source;

said remote source external to said SAN;

b. said SAN decoupling attributes from content in said received remote data to form decoupled attributes and decoupled content;

c. said SAN locally storing in computer storage said decoupled attributes as metadata and a copy of said decoupled content, separately, said metadata comprising at least;

a content storage attribute if said local copy represents a file, a directory mapping if said local copy represents a directory entry, and object attributes, said decoupled attributes being updatable by fetching attribute data from said remote source, said storage storing SAN file system contents in containers holding managed data originating from remote sources, with each container comprising one or more directories and each directory further comprises one or more files, attachment points, and symbolic links; and

d. said SAN obtaining file-level access to said decoupled content based on said locally stored decoupled attributes only when a consistency guarantee exists for said locally stored decoupled attributes, said consistency guarantee providing assurance of metadata and file content validity and said consistency policy defining conditions for freshness check of attributes, and said consistency guarantee expiring after a pre-determined period of time, said freshness check comprising;

triggering a check of attributes associated with a local object, checking for metadata defining a consistency guarantee for said local object, based on said checking step, fetching from said remote source attributes of a remote object associated with said local object, based on said fetching step, creating a consistency guarantee for said local object, and merging said fetched attributes with attributes already associated with said local object.

2. The method of claim 1, wherein said RAA obtains said remote data from said remote source via protocol-specific communication.

3. The method of claim 1, wherein said decoupled content is stored on a storage device attached to said SAN.

4. The method of claim 3, wherein said metadata is locally stored in a metadata server.

5. The method of claim 4, wherein said RAA converts said decoupled attributes to a form of metadata compatible with said metadata server and sends said metadata to said metadata server.

6. The method of claim 1, wherein said content storage attribute is either of:

a storage object identifier and offset, or a list of block address;

said content storage attribute corresponding to a physical storage location for said decoupled content.

7. The method of claim 6, wherein said file-level access comprises:

a. obtaining said metadata associated with said decoupled content;

b. extracting said content storage attribute from said obtained metadata; and

c. reading from or writing to a physical storage location in said SAN;

said physical location specified by said content storage attribute.

8. A system for storing a local copy of remote file system data in a Storage Area Network (SAN);

said system comprising;

a. a client on said SAN requesting, storing, and accessing said local copy;

b. a metadata server, local to said SAN, storing metadata describing attributes of said local copy;

c. a source of remote file system data external to said SAN;

d. a storage device attached to said SAN; and

e. a Remote Access Agent (RAA) receiving said remote file system data from said source of remote file system data, decoupling attributes from said remote file system data to form decoupled attributes and decoupled remote file system data, and maintaining said local copy by storing said decoupled attributes as metadata and decoupled remote file system data in said storage device attached to said SAN,

said metadata in said metadata server comprising at least;

a content storage attribute if said local copy represents a file, a directory mapping if said local copy represents a directory entry, and object attributes,

said decoupled attributes being updatable by fetching attribute data from said remote source,

wherein said decoupled attributes are used to obtain file-level access to said decoupled remote file system data only when a consistency guarantee exists for said locally stored decoupled attributes, said consistency guarantee providing assurance of metadata and file content validity and said consistency policy defining conditions for freshness check of attributes, and said consistency guarantee expiring after a pre-determined period of time, said freshness check comprising;

triggering a check of attributes associated with a local object, checking for metadata defining a consistency guarantee for said local object, based on said checking step, fetching from a remote source attributes of a remote object associated with said local object, based on said fetching step, creating a consistency guarantee for said local object, and merging said fetched attributes with attributes already associated with said local object.

9. The system of claim 8, wherein said storage device attached to said SAN is a SAN disk.

10. The system of claim 8, wherein said RAA stores content of said local copy in said storage device attached to said SAN.

11. The system of claim 8, wherein said RAA converts said decoupled attributes of said local copy to a form of metadata compatible with said metadata server and sends said metadata to said metadata server.

12. The system of claim 8, wherein said RAA obtains said remote file system data from said external, source of remote file system data via protocol-specific communication.

13. The system of claim 8, wherein said client obtains metadata from said metadata server and performs either of:

a read operation or a write operation on content of said local copy stored in said storage device attached to said SAN.

14. The system of claim 8, wherein content of said local copy is obtained from said source of remote file system data in varying increments of granularity as follows:

parts of files, whole files, or entire replicas.

15. The system of claim 8, wherein said content storage attribute is either of:

a storage object identifier and offset, or a list of block address;

said content storage attribute corresponding to a physical storage location in said storage device for content of said local copy.

16. The system of claim 13, wherein said client sends to said metadata server, at least one attribute pertaining to said read operation or write operation performed on said local copy.

17. The system of claim 15, wherein said RAA stores content of said local copy in said storage device using said content storage attribute.

18. The system of claim 16, wherein said RAA obtains and forwards to said source of remote file system data, modification resulting from said read operation or write operation performed on content of said local copy from said storage device and said at least one attribute pertaining to said read operation or write operation from said metadata server.