Clustered hierarchical file services

• US 7,529,784 B2
• Filed: 06/02/2005
• Issued: 05/05/2009
• Est. Priority Date: 02/11/2004
• Status: Active Grant

• Current Assignee: Storage Technology Corp (Oracle Corporation)
• Original Assignee: Storage Technology Corp (Oracle Corporation)
• Inventors: Eichel, Dale R., Holdman, Jon M., Hewitt, Randall K., Hughes, James P., Kavuri, Ravi K.
• Primary Examiner(s): Breene; John E
• Assistant Examiner(s): Jami; Hares
• Application Number:
  US11/143,779
• Publication Number:
  US 20050226059A1
• Time in Patent Office: 1,433 Days
• Field of Search: 707/1, 707/100, 707/200, 707/201, 707/204, 711/113, 709/217
• US Class Current: 1/1
• 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, 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 policy subsystem provides system rules predetermined by a user for at least one of hash based integrity checking, read-only/write-ability/erase-ability control, and duplicate data treatment corresponding to files and file objects.

Claims

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

an administration interface subsystem having a graphical user interface (GUI) and a command line interface (CLI), the administration interface subsystem allowing an administrator to interface with;

an object-based storage subsystem having an object store meta data subsystem, wherein the object store meta data subsystem maintains the persistent recta-data about the stored object and executes the actions desired to enforce storage management policies,

a meta data subsystem including a virtual file subsystem having a virtual file server (VFS) storing meta data about files, and the meta data subsystem including a meta data server interface, a file database coupled to the meta data server interface and a file control interface coupled to the file data base,

a policy subsystem that provides system rules predetermined by the administrator for at least one of hash based integrity checking, read-only/write-ability/erase-ability control, and duplicate data treatment corresponding to files and file objects,

a scheduler subsystem having a job scheduler control interface that communicates with the policy subsystem in order to receive policy enforcement scheduling rules, the scheduler further communicating with the object-based storage subsystem in order to duplicate, delete and migrate existing data,

an audit subsystem that provides system wide logging capability, threshold management of audits and logs at local processing environments, different notification mechanisms, and an administrator configurable parameter system that defines the type and length of audit information to be kept by the system, and

at least one file presentation interface that interfaces a client platform to the VFS of the meta data subsystem; and

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

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 comprises a file system Application Program Interface (API) data interface that is implemented in connection with the VFS.

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

6. The system according to claim 1 further comprising a hash calculation operator coupled to the meta data server interface that creates profiles of data storage objects from meta data, wherein the meta data subsystem stores meta data about files, and includes a virtual file subsystem having a virtual file sewer (VFS).

7. 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.

8. The system according to claim 1 wherein the meta data subsystem further assigns the profile of the data object from the meta data generated by the hash calculation operator, stores the meta data in a local file system, and stores data in the object-based storage subsystem.

9. The system according to claim 8 wherein the meta data subsystem manages the data objects stored on the system to maintain data integrity, including detection of data duplication for archival and removal of the data objects.

10. The system according to claim 1 wherein the policy subsystem further comprises rules engines that interface with the scheduler to perform on demand and lazy scheduled activities of replica creation and migration, and receive system enforced policies based on maintained file system meta data.

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

Interfacing an administration interface subsystem having a graphical user interface (GUI) and a command line interface (CLI), the administration interface subsystem allowing an administrator to interface with;

an object-based storage subsystem having an object store meta data subsystem that manages the information about stored objects, the object store meta data subsystem providing persistent recta-data about the stored object and executing the storage management policies,

a meta data subsystem for storing meta data about files, and includes a virtual file subsystem having a virtual file server (VFS), wherein the meta data subsystem categorizes data into classes and maps classes to policies that are stored in the policy subsystem,

a policy subsystem that provides system rules predetermined by the administrator for at least one of hash based integrity checking, read-only/write-ability/erase-ability control, and duplicate data treatment corresponding to files and file objects using the policy subsystem, using a scalable interconnect,

a scheduler subsystem having a job scheduler control interface that communicates with the policy subsystem in order to receive policy enforcement scheduling rules, the scheduler further communicating with the object-based storage subsystem in order to duplicate, delete and migrate existing data, and an audit subsystem that provides system wide logging capability, threshold management of audits and logs at local processing environments, different notification mechanisms, and an administrator configurable parameter system that defines the type and length of audit information to be kept by the system;

interfacing a client platform to the VFS of the meta data subsystem using at least one file presentation interface; and

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

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 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.

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

15. The method according to claim 11 wherein the meta data subsystem further calculates and stores meta data hash.

16. The method according to claim 11 wherein the policy subsystem further comprises rules engines that interface with the scheduler to perform on demand and lazy scheduled activities of replica creation and migration, and receive system enforced policies based on maintained file system meta data.