SYSTEM AND METHOD FOR VIRTUAL CLUSTER FILE SERVER

• US 20120310892A1
• Filed: 10/19/2011
• Published: 12/06/2012
• Est. Priority Date: 12/21/2004
• Status: Abandoned Application

• Current Assignee: James Patrick Hughes, Ravi K. Kavuri, Shanthi Paladugu, Tru Q. Dam
• Original Assignee: James Patrick Hughes, Ravi K. Kavuri, Shanthi Paladugu, Tru Q. Dam
• Inventors: Dam, Tru Q., Kavuri, Ravi K., Hughes, James P., Paladugu, Shanthi
• Application Number:
  US13/276,584
• Publication Number:
  US 20120310892A1
• Time in Patent Office: Days
• US Class Current: 707/659
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/1748 De-duplication implemented within the file system, e.g. based on file segments de-duplication techniques in storage systems for the management of data blocks G06F3/0641
• CPC Class Codes: G06F 16/188 Virtual file systems

Abstract

A system for object-based data storage includes a plurality of object-based storage nodes having respective data storage devices, at least one file presentation node, a virtual cluster file server (VFS), and a scalable interconnect to couple the virtual cluster file server to the storage nodes, and to the at least one file presentation node. The VFS mirrors a same data object for a data file across the plurality of data storage devices.

Claims

1. A system for object-based data storage, the system comprising:

a plurality of object-based storage nodes having respective data storage devices;

at least one file presentation node;

a virtual cluster file server (VFS); and

a scalable interconnect to couple the virtual cluster file server to the storage nodes, and to the at least one file presentation node, wherein the VFS mirrors a same data object for a data file across the plurality of data storage devices.

2. The system according to claim 1 wherein the data object and the mirrored data objects are assigned a global unique identifier (GUID) when the data object and the mirrored data objects are generated.

3. The system according to claim 1 wherein an object identifier and location of the object identify the object.

4. The system according to claim 1 wherein data that is written to the data object is further written to all respective mirrored objects, and the data object is incremented by one from the previous version, when the data object is backed up.

5. The system according to claim 1 wherein a hash value is generated when the data object is generated, and the hash value remains fixed unless modification is performed on the data object.

6. The system according to claim 5 wherein storage space compaction is performed by comparing hash values and when hash values match, comparing files and when files match, and erasing new file objects.

7. The system according to claim 1 wherein the VFS receives requests from external clients and translates the requests to kernel file system calls, the file system calls are trapped by the VFS and translated to VFS file input/output (I/O) requests to respective storage nodes.

8. The system according to claim 1 wherein the object-based storage nodes reside on the VFS.

9. A method of managing data storage at a file level, the method comprising:

interconnecting a plurality of object-based storage nodes having respective data storage devices, at least one file presentation node, and a virtual cluster file server (VFS) using a scalable interconnect; and

mirroring a data object for a data file across the plurality of data storage devices when the data object is generated using the VFS.

10. The method according to claim 9 further comprising assigning a global unique identifier (GUID) to the data object and the mirrored data objects when the data object and the mirrored data objects are generated.

11. The method according to claim 9 wherein an object identifier and location of the object identify the object.

12. The method according to claim 9 further comprising writing data that is written to the data object to all respective mirrored objects, and incrementing the data object by one from the previous version, when the data object is backed up.

13. The method according to claim 9 further comprising generating a hash value when the data object is generated, and fixing the hash value unless modification is performed on the data object.

14. The method according to claim 13 further comprising compacting storage space by comparing hash values and when hash values match, comparing files and when files match, and erasing new file objects.

15. The method according to claim 9 wherein the VFS receives requests from external clients and translates the requests to kernel file system calls, the file system calls are trapped by the VFS and translated to VFS file input/output (I/O) requests to respective storage nodes.

16. The method according to claim 9 wherein the object-based storage nodes reside on the VFS.

17. For use in an object-based data storage system, a virtual cluster file server (VFS), the server comprising:

interconnections to scalably couple a plurality of object-based storage nodes each having at least one respective data storage device, and at least one file presentation node; and

a translator that receives requests from external clients, translates the requests to kernel file system calls, traps the file system calls, and translates the file system calls to VFS file input/output (I/O) requests to respective storage nodes, wherein the VFS mirrors a data object for a data file across the plurality of data storage devices when the data object is generated.

18. The server according to claim 17 wherein the data object and the mirrored data objects are assigned a global unique identifier (GUID) when the data object and the mirrored data objects are generated.

19. The server according to claim 17 wherein a hash value is generated when the data object is generated, and the hash value remains fixed unless modification is performed on the data object.

20. The server according to claim 19 wherein data that is written to the data object is further written to all respective mirrored objects, and the data object is incremented by one from the previous version, when the data object is backed up.