Clustered hierarchical file services

• US 20050226059A1
• Filed: 06/02/2005
• Published: 10/13/2005
• Est. Priority Date: 02/11/2004
• Status: Active Grant

• Current Assignee: Storage Technologies Corporation (Oracle Corporation)
• Original Assignee: Storage Technologies Corporation (Oracle Corporation)
• Inventors: Hughes, James P., Eichel, Dale R., Kavuri, Ravi K., Holdman, Jon M., Hewitt, Randall K.
• Granted Patent: US 7,529,784 B2
• Time in Patent Office: Days
• US Class Current: 365/189.50
• 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 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.

2. The system according to claim 1 wherein the duplicate data treatment includes at least one of keeping all original and duplicated data copies, keeping only original data and deleting duplicate data, and replacing original data with new duplicate data, and detection of duplicate data is recorded in an audit log.

3. The system according to claim 1 wherein the policy subsystem further provides controls for policy modifications, and absolute time based controls.

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

5. The system according to claim 1 wherein the object-based storage subsystem 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 6 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 F/S meta data.

8. The system according to claim 1 further comprising an indexer that creates searchable, content based indices, and is externally accessible via the file presentation interface.

9. The system according to claim 1 wherein the policy subsystem further comprises a policy control interface that interfaces with the administration interface subsystem to collect class and policy definitions, maintain and process class and policy definitions, extract data management rules, and maintain the hierarchy of functions to be performed.

10. The system according to claim 1 further comprising a security subsystem coupled to the administration interface subsystem, and that 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); and

a policy subsystem, using a scalable interconnect; and

implementing 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 using the policy subsystem.

12. The method according to claim 11 wherein the duplicate data treatment includes at least one of keeping all original and duplicated data copies, keeping only original data and deleting duplicate data, and replacing original data with new duplicate data, and detection of duplicate data is recorded in an audit log.

13. The method according to claim 11 wherein the policy subsystem further provides controls for policy modifications, and absolute time based controls.

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

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

16. The method according to claim 15 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 F/S meta data.

17. 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 fife presentation interface.

18. The method according to claim 17 wherein the policy subsystem further comprises a policy control interface that interfaces with the administration interface subsystem to collect class and policy definitions, maintain and process class and policy definitions, extract data management rules, and maintain the hierarchy of functions to be performed, and 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 F/S meta data.

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.

20. For use in an object-based archival data storage system, a policy subsystem, the policy subsystem comprising:

a policy control interface;

a policy database; and

a policy rules engine, wherein the rules are 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 using the policy subsystem, 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 meta data subsystem for storing meta data about files, and including a virtual file subsystem having a virtual file server (VFS); 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.