Clustered Hierarchical File System

• US 20070103984A1
• Filed: 12/22/2006
• Published: 05/10/2007
• Est. Priority Date: 02/11/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Storage Technologies Corporation (Oracle Corporation)
• Inventors: Hughes, James, Kavuri, Ravi
• Granted Patent: US 7,580,950 B2
• Time in Patent Office: Days
• US Class Current: 365/185.170
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/0664 at device level, e.g. emulation of a storage device or system
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A system for object-based archival data storage includes an object-based storage subsystem having respective data storage devices, at least one file presentation interface that interfaces to client platforms, an administration interface having graphical user interface (GUI) and a command line interface (CLI), a meta data subsystem for storing meta data about files, and includes a virtual file subsystem having a virtual file server (VFS), a policy subsystem that provides system rules predetermined by a user, and a scalable interconnect to couple the object-based storage subsystem, the at least one file presentation interface, the administration interface, the meta data subsystem, and the policy subsystem, wherein the meta data subsystem stores meta data about data files and object files including local file system location, object identification for data, hash, and presented file system information.

Claims

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

an object-based storage subsystem having respective data storage devices;

at least one file presentation interface that interfaces to client platforms;

an administration interface having graphical user interface (GUI) and a command line interface (CLI);

a meta data subsystem for storing meta data about files, and includes a virtual file subsystem having a virtual file server (VFS);

a policy subsystem that provides system rules predetermined by a user;

a scalable interconnect to couple the object-based storage subsystem, the at least one file presentation interface, the administration interface, the meta data subsystem, and the policy subsystem; and

an audit module interfacing with the meta data subsystem to access and evaluate the stored meta data for the data files and object files including local file system location, object identification for data, hash, and presented file system information without accessing the object-based storage subsystem.

2. The system according to claim 1 wherein the meta data subsystem further categorizes data into classes and maps classes to policies that are stored in the policy subsystem.

3. The system according to claim 1 wherein the meta data subsystem further assigns unique ids to the meta data, stores the meta data in a local file system, and stores data in the object-based storage subsystem.

4. The system according to claim 1 wherein the meta data subsystem further calculates and stores meta data hash.

5. The system according to claim 1 wherein the object-based storage subsystem stores data onto physical storage and manages free space in response to the policy subsystem rules and provides at least one of mirrored writes to disk, optimization for small objects, data security erase via expungement of obsolete data, and direct support for media change libraries.

6. The system according to claim 1 further comprising a scheduler that is coupled to the scalable interconnect, and that manages background activities, and operates using absolute time based scheduling from an external time source.

7. The system according to claim 1 wherein the audit module of the meta data subsystem further comprises a file system Application Program Interface (API) data interface that is implemented in connection with the VFS.

8. The system according to claim 1 wherein the audit module of the meta data subsystem interfaces with a standard GUI user interface that is implemented in connection with the VFS.

9. The system according to claim 1 wherein the audit module of the meta data subsystem allows access to the meta data in the subsystem but does not allow access to the data files associated with the meta data.

10. The system according to claim 1 further comprising a security subsystem coupled to the administration interface subsystem, and that creates roles for each user, and assigns credentials, creates resources and resource groups and assigns role based enforcement criterion, maintains pluggable security modules for validation, interfaces with a key management system for symmetric key management, and provides rules for client authentication for physical resources including disks and tapes.

15. The method according to claim 11 wherein the object-based storage subsystem stores data onto physical storage and manages free space in response to the policy subsystem rules, and provides at least one of mirrored writes to disk, optimization for small objects, data security erase via expungement of obsolete data, and direct support for media change libraries.

16. The method according to claim 11 further comprising coupling a scheduler to the scalable interconnect, wherein the scheduler manages background activities, and operates using absolute time based scheduling from an external time source.

17. The method according to claim 11 wherein the audit module of the meta data subsystem further comprises a file system Application Program Interface (API) data interface that is implemented in connection with the VFS.

18. The method according to claim 11 further comprising coupling an indexer to the file presentation interface, wherein the indexer creates searchable, content based indices, and is externally accessible via the file presentation interface.

19. The method according to claim 11 further comprising coupling a security subsystem to the administration interface subsystem, wherein the security subsystem provides for the creation of roles for each user, and assigns credentials, provides the ability to create resources and resource groups and assigns role based enforcement criterion, maintains pluggable security modules for validation, interfaces with a key management system for symmetric key management, and provides rules for client authentication for physical resources including disks and tapes.

11. A method of object-based archival data storage, the method comprising:

interconnecting;

an object-based storage subsystem having respective data storage devices,

at least one file presentation interface that interfaces to client platforms,

an administration interface having graphical user interface (GUI) and a command line interface (CLI),

a meta data subsystem for storing meta data about files, and including a virtual file subsystem having a virtual file server (VFS),

a policy subsystem that provides system rules predetermined by a user, using a scalable interconnect, and

an audit module interfacing with the meta data subsystem;

storing at least one of meta data about data and object files including local file system location, object identification for data, hash, and presented file system information using the meta data subsystem; and

evaluating the stored meta data for the data files and object files including local file system location, object identification for data, hash, and presented file system information without accessing the object-based storage subsystem for auditing purposes.

12. The method according to claim 11 wherein the meta data subsystem further categorizes data into classes and maps classes to policies that are stored in the policy subsystem.

13. The method according to claim 11 wherein the meta data subsystem further performs the steps of:

assigning unique ids to the meta data, stores the meta data in a local file system, and stores data in the object-based storage subsystem; and

calculating and storing meta data hash.

14. The method according to claim 11 wherein the step of evaluating the stored meta data further comprises allowing access to the meta data in the subsystem but does not allow access to the data files associated with the meta data.

20. For use in an object-based archival data storage system, an audit module for use in a meta data subsystem, the audit module comprising:

a meta data server interface;

a file database coupled to the meta data server interface;

a file control interface coupled to the file data base; and

a hash calculation operator coupled to the meta data server interface,

wherein the meta data subsystem stores meta data about files, and includes a virtual file subsystem having a virtual file server (VFS), and the data storage system comprises;

an object-based storage subsystem having respective data storage devices,

at least one file presentation interface that interfaces to client platforms,

an administration interface having graphical user interface (GUI) and a command line interface (CLI),

a policy subsystem that provides system rules predetermined by a user,

a scalable interconnect to couple the object-based storage subsystem, the at least one file presentation interface, the administration interface, the meta data subsystem, and the policy subsystem, and

a policy subsystem that provides system rules predetermined by a user, using a scalable interconnect,

wherein the audit module interfaces with the meta data subsystem to access and evaluate the stored meta data for the data files and object files including local file system location, object identification for data, hash, and presented file system information without accessing the object-based storage subsystem.