Hitachi Data Systems Corporation

Hitachi Vantara Corporation

Richard Rogers

Benjamin Isherwood

Donald P Pannese

Matthew Michael McDonald

David B Pinkney

Alan Bryant

Vitaly Zolotusky, Jr

Christopher S Lacasse

Vitaly Zolotusky

Vitaly Zolutusky

Alan G Bryant

A method, of managing storage of content of a system in storage units including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units, based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

Content selection for storage tiering

A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into a plurality of systems each having multiple nodes. A data protection level method comprises setting a numerical value of a system dynamic data protection level for each system of nodes; and in response to user input, setting a value of a data protection level for one or more data objects in a system, the value being a fixed numerical value or a dynamic value. If the one or more data objects have a dynamic value of the data protection level in a system, the one or more data objects inherit the system dynamic data protection level of the system in which the one or more data objects reside. The value of the data protection level represents a number of copies of data of the one or more data objects to be kept where the one or more data objects reside.

System and method for optimizing protection levels when replicating data in an object storage system

A method, of managing storage of content of a system () in storage units () including run units which do not allow spin-down functionality and spin-down units which allow spin-down functionality, comprises: establishing a storage tiering rule () which sets a policy indicating what content is eligible to be stored on a run unit and what content is eligible to be stored on a spin-down unit, the storage tiering rule being applicable to at least a group of the contents in the content system to determine stored content eligibility thereof for storage in the storage units and migration between the storage units; and identifying candidates of contents to migrate between the storage units (), based on the storage tiering rule, state of the content system, and the stored content eligibility of the at least a group of the contents.

A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into a plurality of systems each having multiple nodes. An object recovery method comprises: receiving, by a first system of the plurality of systems from a client application, a read request for an object, the object having been replicated to/from at least one second system among the plurality of systems; if the object of the read request is available in the first system, returning by the first system the object of the read request to the client application; and if the object of the read request is not available in the first system, performing a read from replica process by the first system to access a replica of the object from a second system among the plurality of systems and using the replica of the object to return the object of the read request to the client application.

System and method for transparent recovery of damaged or unavailable objects in a replicated object storage system

A content platform (or 'cluster') that comprises a redundant array of independent nodes is logically partitioned. Using a web-based interface, an administrator defines one or more 'tenants' within the cluster, wherein a tenant has a set of attributes: namespaces, administrative accounts, data access accounts, and a permission mask. A namespace is a logical partition of the cluster that serves as a collection of objects typically associated with at least one defined application. Each namespace has a private file system with respect to other namespaces. This approach enables a user to segregate cluster data into logical partitions. Using the administrative interface, a namespace associated with a given tenant is selectively configured without affecting a configuration of at least one other namespace in the set of namespaces. One configuration option is a &#x201c;disposition service&#x201d; that, once enabled for a namespace, automatically deletes objects that were once under retention and whose retention time has expired. Preferably, the disposition service deletes objects that do not have a &#x201c;retention hold&#x201d; associated therewith. The service enables the content platform to automatically reclaim cluster capacity while minimizing external involvement and archive load.

Growing community of inventors

Stoughton, MA, United States of America

Richard Rogers