System of and method for transparent management of data objects in containers across distributed heterogenous resources

• US 7,801,850 B2
• Filed: 05/21/2007
• Issued: 09/21/2010
• Est. Priority Date: 04/27/2000
• Status: Expired due to Fees

• Current Assignee: General Atomics, Inc.
• Original Assignee: General Atomics, Inc.
• Inventors: Rajasekar, Arcot, Moore, Reagan W., Wan, Michael Y.
• Primary Examiner(s): Woo; Isaac M
• Application Number:
  US11/751,554
• Publication Number:
  US 20070220199A1
• Time in Patent Office: 1,219 Days
• Field of Search: 707600-831
• US Class Current: 707/610
• CPC Class Codes: G06F 16/188 Virtual file systems
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A system of and method for maintaining data objects in containers across a network of distributed heterogeneous resources in a manner which is transparent to a client. A client request pertaining to containers is resolved by querying meta data for the container, processing the request through one or more copies of the container maintained on the system, updating the meta data for the container to reflect any changes made to the container as a result processing the request, and, if a copy of the container has changed, changing the status of the copy to indicate dirty status or synchronizing the copy to one or more other copies that may be present on the system.

Claims

1. A method of importing a data object into a container comprising the steps of:

specifying the container;

querying meta-data for the container, including a next available offset;

locating on or staging to a selected physical resource a copy of the container;

writing the data object into the copy at the next available offset;

updating meta-data for the copy to reflect the write operation; and

marking the copy as dirty to indicate that the copy is to overwrite any non-current copies or synchronizing the copy with any other copies by overwriting any non-current copies with the copy, thereby helping avoid accesses to non-current copies.

2. A method of importing a data object into a container comprising the steps of:

specifying the container;

querying meta-data for the container, including a next available offset;

locating on or staging to a selected physical resource a copy of the container;

writing the data object into the copy at the next available offset;

updating meta-data for the copy to reflect write operation;

marking the copy as dirty to indicate that the copy is to overwrite any non-current copies or synchronizing the copy with any other copies by overwriting any non-current copies with the copy, thereby helping avoid accesses to non-current copies;

creating the container by performing the following substeps;

specifying, in response to a client request, a name or identifier of the container and a logical resource to be allocated to the container, the logical resource being associated with one or more physical resources, including at least one archive and at least one cache;

creating meta-data for the container, including meta-data specifying a container name and the logical resource to be allocated to the container;

storing the meta-data for the container in a meta-data catalog; and

reserving one or more of the resources allocated to the container.

3. The method of claim 2 further comprising creating the logical resource by performing the following substeps:

associating one or more physical resources with the logical resource;

for each physical resource, specifying a type thereof from the group comprising an archive, a cache, a primary archive, and a primary cache; and

for each physical resource, also specifying size, access control, and optionally other relevant meta-information.

4. The method of claim 3 wherein the one or more physical resources are located in a distributed system.

5. The method of claim 3 wherein the one or more physical resources are heterogenous.

6. The method of claim 2 further comprising synchronizing a plurality of copies of the container by performing the following substeps:

if no copies of the container are marked as dirty, ending the method;

if a cache copy of the container is marked as dirty, synchronizing such to one or more archival copies that are not marked as dirty;

if all archival copies are thereby written over, resetting dirty flags of all such archival copies; and

if one or more but not all archival copies are thereby written over, setting the dirty flags of the one or more archives that are written over.

7. The method of claim 2 wherein the selected physical resource is a cache resource.

8. The method of claim 7 wherein the cache resource is a principal cache resource.